Commit Graph
23 Commits
Author SHA1 Message Date
d965d819f2 docs: add an unlinked browser demo for production testing (#4280)
Adds a **Try it** page at `/try-it/`, available by direct URL while
production embedding is tested; excluded from navigation, site search,
and the sitemap, with a noindex directive, with a live Worktrunk demo in
a browser-local Alpine ARM64 VM via [Demoshell](https://demoshell.com).
Nothing downloads until Run is pressed. The page includes Demoshell
attribution and a permanent full-page fallback link.

The VM definition lives in `docs/demos/demoshell/`: the setup recipe,
Bash startup rcfile, and guide. The guide covers list → create → edit →
list → merge, followed by an optional manual picker step. Merge commits
the change automatically. Studio must launch Bash explicitly: changing
root's login shell does not replace its running ash session. The prompt
retains the `arm64js:` prefix required by Demoshell's command tracker.
The README maps each file to its Studio field and provides an ARM64
Alpine Docker check using the same Bash entry point.

**Production test rollout:** `m/tui:worktrunk` resolves from the allowed
`worktrunk.dev` origin. The recipe, startup file, and guide draft are
entered in Studio, but the final snapshot upload is stalled at 1% after
setup completes. The currently published snapshot predates the prompt
repair, and visitors still receive the old guide. The page is
intentionally unlinked so it can be merged and tested on the accepted
production origin before broader exposure. The corrected snapshot must
finish saving, then the new guide must be published and tested in a
fresh visitor session.

Validation: the required command patterns and output checks pass on
ARM64 Alpine with `wt v0.81.0`. In the real Studio preview, applying the
Bash/prompt corrections allowed the required steps to check off, merge
to commit automatically, and the shell to return to main. The optional
picker opens and exits; its guide step uses manual completion because
Demoshell did not detect the alternate-screen exit. Local docs build,
type checks, plugin/site tests, and docs sync passed. Final snapshot
publication and a fresh end-to-end run remain blocked by the upload.

The sidebar-order test accepts Astro page routes, and the page-outline
test exempts `/try-it/`, whose table of contents is disabled to give the
demo more width.

Disclosure from the original author: they run Demoshell. Hosting is free
for eligible open-source projects, and the embed carries attribution.

> _This was written by Codex on behalf of max-sixty_

---------

Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Maximilian Roos <m@maxroos.com>
2026-10-21 19:40:15 -07:00
Maximilian Roos c98f5f5028 docs(shell): make config shell help the setup home (#4344)
`wt config shell --help` provides setup, activation and current-shell
diagnostics. The generated config reference now includes the existing
init/install/uninstall help; the specialist shell-integration guide
links to those recipes while retaining installed-file locations,
warnings, wrapper internals and public anchors.

This consolidates the authored recipes and expands the reference. Of
+754/−183 lines across 11 files, +624 come from three generated
config-reference copies. Authored Rust help changes are +40/−12.

Latest main `913ff0547` is integrated, preserving Nushell’s newer 0.113+
requirement. Fresh documentation sync, Astro build and all 16 built-site
checks pass. The current candidate passed the full project gate: 5,196
tests passed and one skipped, with Clippy, formatting, lockfile and
doctest checks passing. The built binary’s help was reviewed at 80
columns.

> _This was written by Codex on behalf of max-sixty_
2026-10-10 18:02:30 -07:00
Worktrunk Botandworktrunk-bot cd5d51dbd5 test(docs): serve a local stand-in for the shields.io badge in browser tests (#4383)
`publish-docs` [run
37425036753](https://github.com/max-sixty/worktrunk/actions/runs/37425036753)
failed on `desktop code examples fit the content column` with
`page.goto: Timeout 30000ms exceeded ... waiting until "load"` on `/`.
That timeout is a side effect of #4382, which switched every
browser-test navigation from `domcontentloaded` to `load`. Every page
header loads the GitHub-stars badge from `img.shields.io`
([`SocialIcons.astro`](https://github.com/max-sixty/worktrunk/blob/220e59ef641ad34d770143959ed103e541275264/docs/src/components/SocialIcons.astro#L8)),
so `load` now also waits on that third-party host. One slow badge
response stalls the navigation.

**Fix.** A `newPage` helper in `docs/tests/browser-site.test.mjs` routes
`https://img.shields.io/**` to a local SVG sized to the badge's declared
90×20, and all five page-creation sites use it. That leaves the local
server and the Google web fonts as the only things `load` waits for. The
fonts have to stay real, because the layout assertions measure text set
in JetBrains Mono. Analytics doesn't load on `127.0.0.1` (it's gated on
`hostname === 'worktrunk.dev'`), and the docs content has no other
remote images.

**Verification.** I ran a local Chromium probe against the built site,
routing the badge to a request that never answers:
- With the stalled badge, `page.goto(..., { waitUntil: 'load' })` times
out, which is the same failure as in CI.
- With the stand-in, `/` loads in about 200 ms. The JetBrains Mono faces
in use report `loaded` after `fonts.ready`, and the badge renders at
90×20.

I couldn't run the WebKit suite locally because it needs sudo-installed
system libraries. This PR's `check-docs` job runs it.

Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
2026-10-06 00:14:19 -07:00
Worktrunk Botandworktrunk-bot dc97142974 test(docs): wait for web fonts before browser layout checks (#4382)
The `link-check` job on [nightly run
37414713723](https://github.com/max-sixty/worktrunk/actions/runs/37414713723)
failed `desktop code examples fit the content column` with
`/claude-code/ wt list scrolls horizontally at 1401px`. The docs content
at that commit is identical to `3e233ef26`, where `publish-docs` ran the
same suite green a few hours earlier, so this was a race in the test
rather than a site regression.

**Cause.** The browser tests measure layout right after
`DOMContentLoaded`. At that point the JetBrains Mono faces, which
`custom.css` loads from Google Fonts with `display=swap`, are still
`loading`, so code renders in the fallback monospace face. Since #4214,
the content column is sized for exactly 99 columns of JetBrains Mono
(0.6em, or 8.4px at 14px). On the Ubuntu runner the fallback is DejaVu
Sans Mono at about 8.43px, roughly 2.8px wider across 99 columns. That
is more than the test's 1px tolerance, so the result depends on whether
the font swap has happened by the time the test measures.

**Fix.** All test navigations now go through an `openPage` helper that
waits for `load` and then `document.fonts.ready`, so every layout
assertion measures the settled page. The helper covers every call site
because the mobile, copy-button, and contrast tests take the same
unsettled measurement.

**Verification.** In a local Chromium probe of the built site:
- At `DOMContentLoaded`, the JetBrains Mono faces report `loading`, and
the `wt list` block measures the same as it does with Google Fonts
blocked.
- After `load` plus `fonts.ready`, the faces report `loaded`.

I couldn't run WebKit here because it needs system libraries that
require sudo. Chromium's headless shell rounds glyph advances to whole
pixels, so its geometry numbers don't stand in for WebKit's. This PR's
`check-docs` job runs the WebKit suite and is the real check.

Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
2026-10-05 23:40:09 -07:00
Maximilian Roos abd7acaa6b docs: align terminal examples with content width (#4214)
The documentation terminal examples were captured one column narrower
than their content rail, leaving a character-sized trailing gap.

Align the content rail with the 99-column documentation capture, reduce
output-row right padding while preserving command-row copy-control
clearance, and cover the geometry across the responsive
table-of-contents transition.

Checks:

- `cargo run -- hook pre-merge --yes`
- `npm --prefix docs run check`
- `npm --prefix docs test`
- `npm --prefix docs run build`
- `npm --prefix docs run test:site`

> _This was written by Codex on behalf of max-sixty_
2026-09-20 23:30:16 -07:00
Maximilian RoosandClaude Opus 5 7649c7057e docs: cut internals, edge-case mechanics, and deprecated behavior (#4157)
Follows #4153, which cut two `wt config update` paragraphs describing
internals and deprecated behavior. This sweeps the rest of the docs for
passages of the same kind: how a command is implemented, edge cases the
command already reports with an error or warning when they happen, and
deprecated or removed behavior. The edits are to the help text in
`src/cli/*.rs` and the non-command docs pages; everything else in the
diff is regenerated (command pages, skill mirrors, help snapshots,
`dev/*.example.toml`).

What went, by kind:

- **Deprecated or removed:** the `wt hook --var` paragraph and its row
in the extending guide's hooks-vs-aliases table; the page for the hidden
`wt config state ci-status` subcommand; the `approved-commands` sentence
in user config (now about pattern keys in `approvals.toml`); the
"retired wrapper" wording in the "shell wrapper is out of date" warning.
- **Internals:** `wt step diff`'s "How it works"; `copy-ignored`'s
background-priority section and `WORKTRUNK_FOREGROUND`; `promote`'s
`rename()`; the three env vars marked "Internal:" in the config page's
table; how the OpenCode plugin loads; skim query operators in the
picker; the `--prs` log tab's data source.
- **Edge cases the command reports itself:** `post-commit` hooks skipped
when `wt merge` removes their worktree; a branch retained because a
second worktree has it checked out (the FAQ keeps this); a registered
worktree whose directory is gone and rollback races in `wt step push`;
template errors in `for-each`; `.bak-2` backup names in `relocate`.
- **Mechanics a user doesn't act on:** measuring against the upstream
when the local default branch lags (`wt merge`, `wt step rebase`, `wt
list`); default-branch cache internals other than the rule that a guess
made during an outage isn't cached; the statusline pace forecast and
cell-dropping rules; the FAQ's fsmonitor and shell-install migration
detail, trimmed down to the facts; the "Three things to get right" list
for agent CLIs without a plugin; the `wt up` recipe's guard
explanations, condensed to the two details that matter when adapting it.

A few label-then-colon-then-link sentences ("How the fragment renders:
[the LLM commits guide]") are rewritten as sentences. The built-site
test's heading count for the config page's table of contents drops from
33 to 32 with the `ci-status` section gone.

Kept on purpose: the "Local CI" section, the homepage, the FAQ's lists
of files Worktrunk creates and deletes, the warning that `post-*` hooks
from user and project config can race, the direct `git config` marker
example, `wt remove`'s notes on the capped default-branch walk and what
"target" means (the command reports neither), the troubleshooting entry
for the retired `template-file` keys (the unknown-field warning doesn't
name the replacement), and the `wt list` "Schema 1" mapping table
(`json-schema = 1` is still supported without a deprecation warning).

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-16 17:08:39 -07:00
Worktrunk Bot a869299624 feat(config)!: split the Pi and oh-my-pi plugin installers (#4135) 2026-09-16 08:19:24 -07:00
Maximilian RoosandClaude Opus 5 5dec423110 docs: leave trailing shell comments out of copied commands (#4091)
Copy buttons copied shell commands with their trailing `#` comments,
e.g. `wt hook pre-merge user: # Run all user hooks`. In zsh without
`interactivecomments`, which is the default, a pasted trailing comment
isn't a comment: the command runs as `wt hook pre-merge user: '#' Run
all user hooks`.

`withoutTrailingShellComments` in
`docs/src/plugins/worktrunk-terminal.mjs` applies the shell's rule, that
a `#` beginning an unquoted word starts a comment, to what shell copy
buttons copy: each per-line button in multi-command `console` blocks,
the command lines of single-command `console` blocks, and whole `bash`
and `sh` blocks. A line that is only a comment stays, as
`docs/CLAUDE.md` already specifies for console blocks. 56 of the site's
339 copy payloads change (47 per-line buttons and 9 `bash` blocks).
TOML, PowerShell and other payloads are unchanged, and a quoted `#`
survives.

Tests: unit tests for the scanner (quotes, escapes, `$#`, operators,
quotes spanning lines) and for a single-command `console` block with a
trailing comment, plus a built-site test that no `bash` or `sh` payload
carries a trailing comment, which fails on the build before this change.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_013U96NY8qKtZhavBSwnfCYq

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-13 10:57:35 -07:00
dependabot[bot]andworktrunk-bot 5b93f1b321 chore: bump the docs-site group in /docs with 5 updates (#4031)
Bumps the docs-site group in /docs with 5 updates:

| Package | From | To |
| --- | --- | --- |
|
[@astrojs/markdown-remark](https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark)
| `7.2.4` | `7.3.0` |
|
[@astrojs/sitemap](https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap)
| `3.7.3` | `3.7.4` |
|
[@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight)
| `0.41.9` | `0.42.0` |
|
[@expressive-code/core](https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core)
| `0.44.1` | `0.44.2` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) |
`7.2.9` | `7.3.1` |

Updates `@astrojs/markdown-remark` from 7.2.4 to 7.3.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/releases">@​astrojs/markdown-remark's
releases</a>.</em></p>
<blockquote>
<h2><code>@​astrojs/markdown-remark</code><a
href="https://github.com/7"><code>@​7</code></a>.3.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17262">#17262</a>
<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>
Thanks <a
href="https://github.com/Princesseuh"><code>@​Princesseuh</code></a>! -
Adds MDX rendering to the <code>unified()</code> and
<code>satteri()</code> processors.</p>
<p>Both processors now compile <code>.mdx</code> files themselves. You
still need to install <code>@astrojs/mdx</code> to add MDX support to
your project.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17262">#17262</a>
<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>
Thanks <a
href="https://github.com/Princesseuh"><code>@​Princesseuh</code></a>! -
Adds a <code>recmaPlugins</code> option to <code>unified()</code> for
adding recma (estree/JSX) plugins to the MDX compiler.</p>
</li>
</ul>
<h3>Patch Changes</h3>
<ul>
<li>Updated dependencies [<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>]:
<ul>
<li><code>@​astrojs/internal-helpers</code><a
href="https://github.com/0"><code>@​0</code></a>.11.0</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/blob/main/packages/markdown/remark/CHANGELOG.md">@​astrojs/markdown-remark's
changelog</a>.</em></p>
<blockquote>
<h2>7.3.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17262">#17262</a>
<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>
Thanks <a
href="https://github.com/Princesseuh"><code>@​Princesseuh</code></a>! -
Adds MDX rendering to the <code>unified()</code> and
<code>satteri()</code> processors.</p>
<p>Both processors now compile <code>.mdx</code> files themselves. You
still need to install <code>@astrojs/mdx</code> to add MDX support to
your project.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17262">#17262</a>
<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>
Thanks <a
href="https://github.com/Princesseuh"><code>@​Princesseuh</code></a>! -
Adds a <code>recmaPlugins</code> option to <code>unified()</code> for
adding recma (estree/JSX) plugins to the MDX compiler.</p>
</li>
</ul>
<h3>Patch Changes</h3>
<ul>
<li>Updated dependencies [<a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>]:
<ul>
<li><code>@​astrojs/internal-helpers</code><a
href="https://github.com/0"><code>@​0</code></a>.11.0</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/withastro/astro/commit/2fdf731428aa738d5dcf3041b4e78eb9d036968c"><code>2fdf731</code></a>
[ci] release (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/17849">#17849</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/f8e94585ab6c38e2702ee1e2e540858f72058a40"><code>f8e9458</code></a>
feat: move MDX into the processors themselves (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/markdown/remark/issues/17262">#17262</a>)</li>
<li>See full diff in <a
href="https://github.com/withastro/astro/commits/@astrojs/markdown-remark@7.3.0/packages/markdown/remark">compare
view</a></li>
</ul>
</details>
<br />

Updates `@astrojs/sitemap` from 3.7.3 to 3.7.4
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/releases">@​astrojs/sitemap's
releases</a>.</em></p>
<blockquote>
<h2><code>@​astrojs/sitemap</code><a
href="https://github.com/3"><code>@​3</code></a>.7.4</h2>
<h3>Patch Changes</h3>
<ul>
<li><a
href="https://redirect.github.com/withastro/astro/pull/17851">#17851</a>
<a
href="https://github.com/withastro/astro/commit/52d3f56999ecdf92510b2c16ed2a3a4785b9c73a"><code>52d3f56</code></a>
Thanks <a
href="https://github.com/apps/astro-factory"><code>@​astro-factory</code></a>!
- Fixes the sitemap outputting a URL with an empty path for the homepage
(e.g. <code>https://example.com</code> instead of
<code>https://example.com/</code>) when <code>trailingSlash</code> is
set to <code>&quot;never&quot;</code> or <code>build.format</code> is
set to <code>&quot;file&quot;</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/blob/main/packages/integrations/sitemap/CHANGELOG.md">@​astrojs/sitemap's
changelog</a>.</em></p>
<blockquote>
<h2>3.7.4</h2>
<h3>Patch Changes</h3>
<ul>
<li><a
href="https://redirect.github.com/withastro/astro/pull/17851">#17851</a>
<a
href="https://github.com/withastro/astro/commit/52d3f56999ecdf92510b2c16ed2a3a4785b9c73a"><code>52d3f56</code></a>
Thanks <a
href="https://github.com/apps/astro-factory"><code>@​astro-factory</code></a>!
- Fixes the sitemap outputting a URL with an empty path for the homepage
(e.g. <code>https://example.com</code> instead of
<code>https://example.com/</code>) when <code>trailingSlash</code> is
set to <code>&quot;never&quot;</code> or <code>build.format</code> is
set to <code>&quot;file&quot;</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/withastro/astro/commit/2fdf731428aa738d5dcf3041b4e78eb9d036968c"><code>2fdf731</code></a>
[ci] release (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap/issues/17849">#17849</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/52d3f56999ecdf92510b2c16ed2a3a4785b9c73a"><code>52d3f56</code></a>
fix(<code>@​astrojs/sitemap</code>): preserve root path <code>/</code>
in sitemap URLs when trailingSl...</li>
<li><a
href="https://github.com/withastro/astro/commit/2bfb179545249786e9f395325c88a9dfef574acb"><code>2bfb179</code></a>
chore: simpler package.json types (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/integrations/sitemap/issues/17229">#17229</a>)</li>
<li>See full diff in <a
href="https://github.com/withastro/astro/commits/@astrojs/sitemap@3.7.4/packages/integrations/sitemap">compare
view</a></li>
</ul>
</details>
<br />

Updates `@astrojs/starlight` from 0.41.9 to 0.42.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/starlight/releases">@​astrojs/starlight's
releases</a>.</em></p>
<blockquote>
<h2><code>@​astrojs/starlight</code><a
href="https://github.com/0"><code>@​0</code></a>.42.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/3572">#3572</a>
<a
href="https://github.com/withastro/starlight/commit/292fb179cbf6e2cd970ced46359c520aa14a80b4"><code>292fb17</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Distributes package as JavaScript files with dedicated type declaration
files instead of TypeScript source files.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4121">#4121</a>
<a
href="https://github.com/withastro/starlight/commit/2623ae60af0fdafc71938f96153b0427fcc2b5aa"><code>2623ae6</code></a>
Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>!
- Simplifies markup for Starlight’s mobile menu toggle</p>
<p><strong>⚠️ Potentially breaking change:</strong> If you use a theme
plugin, custom styles, or component overrides targeting the
<code>MobileMenuToggle</code> button or <code>PageFrame</code>
components, you may need to adjust these for the new markup. The button
is no longer wrapped in a <code>&lt;starlight-menu-button&gt;</code>
custom element and no longer uses the <code>aria-expanded</code>
attribute. Instead, you can use the <code>.sl-menu-button</code> class
name to target the button and the <code>:popover-open</code>
pseudo-class to style the menu open state specifically.</p>
<p>In the following example, custom styles for the menu button are
updated for the new approach:</p>
<pre lang="diff"><code>- starlight-menu-button button {
+ .sl-menu-button {
  color: var(--sl-color-text);
}
<ul>
<li>starlight-menu-button[aria-expanded='true'] button {</li>
</ul>
<ul>
<li>.sl-menu-button:has(~ :popover-open) {
color: var(--sl-color-text-accent-high);
}
</code></pre></li>
</ul>
<p>See <a
href="https://github.com/withastro/starlight/blob/main/packages/starlight/components/MobileMenuToggle.astro"><code>MobileMenuToggle.astro</code></a>
and <a
href="https://github.com/withastro/starlight/blob/main/packages/starlight/components/PageFrame.astro"><code>PageFrame.astro</code></a>
on GitHub for the full source code of the updated components.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/3572">#3572</a>
<a
href="https://github.com/withastro/starlight/commit/292fb179cbf6e2cd970ced46359c520aa14a80b4"><code>292fb17</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Removes the <code>tagline</code> configuration option, which was never
used.</p>
<p>If your configuration included a <code>tagline</code> option, you can
safely remove it without any replacement.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4134">#4134</a>
<a
href="https://github.com/withastro/starlight/commit/6135f015b527453d7083ad01d2dc6c61d72fbefc"><code>6135f01</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Updates internal <code>@astrojs/mdx</code>,
<code>@astrojs/markdown-satteri</code>, and <code>satteri</code>
dependencies.</p>
<p>⚠️ <strong>BREAKING CHANGE:</strong> The following minimum versions
are now required:</p>
<ul>
<li><code>astro</code> v7.2.10 or later</li>
<li><code>@astrojs/markdown-satteri</code> 0.4.0 or later (if you use
it)</li>
<li><code>@astrojs/markdown-remark</code> 7.3.0 or later (if you use
it)</li>
</ul>
<p>Please update Starlight and Astro together:</p>
<pre lang="sh"><code>npx @astrojs/upgrade
</code></pre>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4121">#4121</a>
<a
href="https://github.com/withastro/starlight/commit/2623ae60af0fdafc71938f96153b0427fcc2b5aa"><code>2623ae6</code></a>
Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>!
- Refactors Starlight’s mobile menu toggle to work when JavaScript fails
or is disabled</p>
<p>⚠️ <strong>BREAKING CHANGE:</strong> This release drops official
support for Chromium-based browsers prior to version 116 (released
August 2023), Safari-based browsers prior to version 17.0 (released
September 2023), and Firefox prior to version 125 (released April 2024).
You can find a list of currently supported browsers and their versions
using this <a
href="https://browsersl.ist/#q=%3E+0.5%25%2C+not+dead%2C+Chrome+%3E%3D+116%2C+Edge+%3E%3D+116%2C+Firefox+%3E%3D+125%2C+Safari+%3E%3D+17.0%2C+iOS+%3E%3D+17.0%2C+not+op_mini+all">browserslist
query</a>.</p>
<p>This change also removes the <code>data-mobile-menu-expanded</code>
attribute, which was previously added to <code>&lt;body&gt;</code> while
the mobile menu is open. If you have custom code that was depending on
this attribute, you will need to update it to use a new selector to
check if the mobile menu is open.</p>
<p>In the following example, a custom background colour for the site
header while the menu is open is updated for the new approach:</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md">@​astrojs/starlight's
changelog</a>.</em></p>
<blockquote>
<h2>0.42.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/3572">#3572</a>
<a
href="https://github.com/withastro/starlight/commit/292fb179cbf6e2cd970ced46359c520aa14a80b4"><code>292fb17</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Distributes package as JavaScript files with dedicated type declaration
files instead of TypeScript source files.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4121">#4121</a>
<a
href="https://github.com/withastro/starlight/commit/2623ae60af0fdafc71938f96153b0427fcc2b5aa"><code>2623ae6</code></a>
Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>!
- Simplifies markup for Starlight’s mobile menu toggle</p>
<p><strong>⚠️ Potentially breaking change:</strong> If you use a theme
plugin, custom styles, or component overrides targeting the
<code>MobileMenuToggle</code> button or <code>PageFrame</code>
components, you may need to adjust these for the new markup. The button
is no longer wrapped in a <code>&lt;starlight-menu-button&gt;</code>
custom element and no longer uses the <code>aria-expanded</code>
attribute. Instead, you can use the <code>.sl-menu-button</code> class
name to target the button and the <code>:popover-open</code>
pseudo-class to style the menu open state specifically.</p>
<p>In the following example, custom styles for the menu button are
updated for the new approach:</p>
<pre lang="diff"><code>- starlight-menu-button button {
+ .sl-menu-button {
  color: var(--sl-color-text);
}
<ul>
<li>starlight-menu-button[aria-expanded='true'] button {</li>
</ul>
<ul>
<li>.sl-menu-button:has(~ :popover-open) {
color: var(--sl-color-text-accent-high);
}
</code></pre></li>
</ul>
<p>See <a
href="https://github.com/withastro/starlight/blob/main/packages/starlight/components/MobileMenuToggle.astro"><code>MobileMenuToggle.astro</code></a>
and <a
href="https://github.com/withastro/starlight/blob/main/packages/starlight/components/PageFrame.astro"><code>PageFrame.astro</code></a>
on GitHub for the full source code of the updated components.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/3572">#3572</a>
<a
href="https://github.com/withastro/starlight/commit/292fb179cbf6e2cd970ced46359c520aa14a80b4"><code>292fb17</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Removes the <code>tagline</code> configuration option, which was never
used.</p>
<p>If your configuration included a <code>tagline</code> option, you can
safely remove it without any replacement.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4134">#4134</a>
<a
href="https://github.com/withastro/starlight/commit/6135f015b527453d7083ad01d2dc6c61d72fbefc"><code>6135f01</code></a>
Thanks <a href="https://github.com/HiDeoo"><code>@​HiDeoo</code></a>! -
Updates internal <code>@astrojs/mdx</code>,
<code>@astrojs/markdown-satteri</code>, and <code>satteri</code>
dependencies.</p>
<p>⚠️ <strong>BREAKING CHANGE:</strong> The following minimum versions
are now required:</p>
<ul>
<li><code>astro</code> v7.2.10 or later</li>
<li><code>@astrojs/markdown-satteri</code> 0.4.0 or later (if you use
it)</li>
<li><code>@astrojs/markdown-remark</code> 7.3.0 or later (if you use
it)</li>
</ul>
<p>Please update Starlight and Astro together:</p>
<pre lang="sh"><code>npx @astrojs/upgrade
</code></pre>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/starlight/pull/4121">#4121</a>
<a
href="https://github.com/withastro/starlight/commit/2623ae60af0fdafc71938f96153b0427fcc2b5aa"><code>2623ae6</code></a>
Thanks <a href="https://github.com/delucis"><code>@​delucis</code></a>!
- Refactors Starlight’s mobile menu toggle to work when JavaScript fails
or is disabled</p>
<p>⚠️ <strong>BREAKING CHANGE:</strong> This release drops official
support for Chromium-based browsers prior to version 116 (released
August 2023), Safari-based browsers prior to version 17.0 (released
September 2023), and Firefox prior to version 125 (released April 2024).
You can find a list of currently supported browsers and their versions
using this <a
href="https://browsersl.ist/#q=%3E+0.5%25%2C+not+dead%2C+Chrome+%3E%3D+116%2C+Edge+%3E%3D+116%2C+Firefox+%3E%3D+125%2C+Safari+%3E%3D+17.0%2C+iOS+%3E%3D+17.0%2C+not+op_mini+all">browserslist
query</a>.</p>
<p>This change also removes the <code>data-mobile-menu-expanded</code>
attribute, which was previously added to <code>&lt;body&gt;</code> while
the mobile menu is open. If you have custom code that was depending on
this attribute, you will need to update it to use a new selector to
check if the mobile menu is open.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/withastro/starlight/commit/88ad3c2630487ba227a7b4ccbffc01a2bdf623a5"><code>88ad3c2</code></a>
[ci] release (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4172">#4172</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/74cb3f1a40985eed5f7974e2b1b994a2bdcfd8be"><code>74cb3f1</code></a>
Update dependencies (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4173">#4173</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/6135f015b527453d7083ad01d2dc6c61d72fbefc"><code>6135f01</code></a>
Use Sätteri 0.10 APIs (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4134">#4134</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/2623ae60af0fdafc71938f96153b0427fcc2b5aa"><code>2623ae6</code></a>
Refactor mobile menu to use Popover API (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4121">#4121</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/09af1c621e3bd48fa601d6ce47be181bb44d0e9b"><code>09af1c6</code></a>
chore(deps): update <code>magic-string</code> to v1 (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4082">#4082</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/292fb179cbf6e2cd970ced46359c520aa14a80b4"><code>292fb17</code></a>
[i18nIgnore] Transpile Starlight packages (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/3572">#3572</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/0138f22c04ab2a659b642526345ba53bef7e5033"><code>0138f22</code></a>
[ci] release (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4169">#4169</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/32a5e29127c13946ce746c36d7cb194f35d11952"><code>32a5e29</code></a>
Fix hidden heading anchor links (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4167">#4167</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/cdfafd8eedbbd6653cd6a1d3b1542b44ed1ba19e"><code>cdfafd8</code></a>
perf: optimize route and sidebar lookups (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4148">#4148</a>)</li>
<li><a
href="https://github.com/withastro/starlight/commit/dd7fb9721e117337195fdfdb92a081d7dd23701e"><code>dd7fb97</code></a>
chore: add benchmarks (<a
href="https://github.com/withastro/starlight/tree/HEAD/packages/starlight/issues/4157">#4157</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/withastro/starlight/commits/@astrojs/starlight@0.42.0/packages/starlight">compare
view</a></li>
</ul>
</details>
<br />

Updates `@expressive-code/core` from 0.44.1 to 0.44.2
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/expressive-code/expressive-code/releases">@​expressive-code/core's
releases</a>.</em></p>
<blockquote>
<h2><code>@​expressive-code/core</code><a
href="https://github.com/0"><code>@​0</code></a>.44.2</h2>
<p>No release notes provided.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/expressive-code/expressive-code/blob/main/packages/@expressive-code/core/CHANGELOG.md">@​expressive-code/core's
changelog</a>.</em></p>
<blockquote>
<h2>0.44.2</h2>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/expressive-code/expressive-code/commit/5c5b4522e0db357f453e2e6c9a46790e83ef6322"><code>5c5b452</code></a>
[CI] Release (<a
href="https://github.com/expressive-code/expressive-code/tree/HEAD/packages/@expressive-code/core/issues/469">#469</a>)</li>
<li>See full diff in <a
href="https://github.com/expressive-code/expressive-code/commits/@expressive-code/core@0.44.2/packages/@expressive-code/core">compare
view</a></li>
</ul>
</details>
<br />

Updates `astro` from 7.2.9 to 7.3.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/releases">astro's
releases</a>.</em></p>
<blockquote>
<h2>astro@7.3.1</h2>
<h3>Patch Changes</h3>
<ul>
<li><a
href="https://redirect.github.com/withastro/astro/pull/17899">#17899</a>
<a
href="https://github.com/withastro/astro/commit/03896405717471f7d6ff54986ed6beaec0cac94f"><code>0389640</code></a>
Thanks <a
href="https://github.com/ematipico"><code>@​ematipico</code></a>! -
Fixes an error that prevented projects using <code>astro:assets</code>
from starting or building</li>
</ul>
<h2>astro@7.3.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17767">#17767</a>
<a
href="https://github.com/withastro/astro/commit/ce7c91f77dbd7be03c04bc13f87af9d01fef6cef"><code>ce7c91f</code></a>
Thanks <a
href="https://github.com/apps/astro-factory"><code>@​astro-factory</code></a>!
- Adds <code>--ignore-lock</code> flag to <code>astro preview</code>,
allowing multiple preview servers to run simultaneously on different
ports. This is useful for E2E testing workflows (e.g., Playwright) that
need to run several preview servers at once.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17818">#17818</a>
<a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
Thanks <a
href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>!
- Adds a <code>logger</code> parameter to image services hooks</p>
<p>Custom image services now receive Astro's runtime logger as an extra
argument. Messages logged with it are routed through the destination
configured in <code>logger</code> and respect your log level, instead of
being written straight to the console:</p>
<pre lang="ts"><code>import type { LocalImageService } from 'astro';
<p>const service: LocalImageService = {
// ...
async transform(inputBuffer, transform, imageConfig, logger) {
logger.warn(<code>Could not optimize
&amp;quot;${transform.src}&amp;quot;. Passing it through
unchanged.</code>);
return { data: inputBuffer, format: 'png' };
},
};
</code></pre></p>
<p>Astro's built-in Sharp service now uses this logger for the warnings
it emits when it encounters an unexpected or unsupported source
format.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17818">#17818</a>
<a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
Thanks <a
href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>!
- Adds <code>logger</code> to the context object passed to cache
providers</p>
<p>Custom cache providers now receive Astro's runtime logger on the
context passed to <code>onRequest()</code>. Messages logged with it are
routed through the destination configured in <code>logger</code> and
respect your log level, instead of being written straight to the
console:</p>
<pre lang="ts"><code>import type { CacheProvider } from 'astro';
<p>const provider: CacheProvider = {
name: 'my-cache',
async onRequest({ request, url, logger }, next) {
logger.warn(<code>Skipping cache for ${url.pathname} because the
response sets a cookie.</code>);
return next();
},
// ...
};
</code></pre></p>
<p>Astro's built-in <code>memoryCache()</code> provider now uses this
logger for the warnings it emits when it skips caching a response that
sets cookies, and when a background revalidation fails.</p>
</li>
</ul>
<h3>Patch Changes</h3>
<ul>
<li><a
href="https://redirect.github.com/withastro/astro/pull/17818">#17818</a>
<a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
Thanks <a
href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>!
- Updates Astro's remaining internal warnings and errors to be written
through the configured logger instead of directly to the console, when
possible</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md">astro's
changelog</a>.</em></p>
<blockquote>
<h2>7.3.1</h2>
<h3>Patch Changes</h3>
<ul>
<li><a
href="https://redirect.github.com/withastro/astro/pull/17899">#17899</a>
<a
href="https://github.com/withastro/astro/commit/03896405717471f7d6ff54986ed6beaec0cac94f"><code>0389640</code></a>
Thanks <a
href="https://github.com/ematipico"><code>@​ematipico</code></a>! -
Fixes an error that prevented projects using <code>astro:assets</code>
from starting or building</li>
</ul>
<h2>7.3.0</h2>
<h3>Minor Changes</h3>
<ul>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17767">#17767</a>
<a
href="https://github.com/withastro/astro/commit/ce7c91f77dbd7be03c04bc13f87af9d01fef6cef"><code>ce7c91f</code></a>
Thanks <a
href="https://github.com/apps/astro-factory"><code>@​astro-factory</code></a>!
- Adds <code>--ignore-lock</code> flag to <code>astro preview</code>,
allowing multiple preview servers to run simultaneously on different
ports. This is useful for E2E testing workflows (e.g., Playwright) that
need to run several preview servers at once.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17818">#17818</a>
<a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
Thanks <a
href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>!
- Adds a <code>logger</code> parameter to image services hooks</p>
<p>Custom image services now receive Astro's runtime logger as an extra
argument. Messages logged with it are routed through the destination
configured in <code>logger</code> and respect your log level, instead of
being written straight to the console:</p>
<pre lang="ts"><code>import type { LocalImageService } from 'astro';
<p>const service: LocalImageService = {
// ...
async transform(inputBuffer, transform, imageConfig, logger) {
logger.warn(<code>Could not optimize
&amp;quot;${transform.src}&amp;quot;. Passing it through
unchanged.</code>);
return { data: inputBuffer, format: 'png' };
},
};
</code></pre></p>
<p>Astro's built-in Sharp service now uses this logger for the warnings
it emits when it encounters an unexpected or unsupported source
format.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/withastro/astro/pull/17818">#17818</a>
<a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
Thanks <a
href="https://github.com/florian-lefebvre"><code>@​florian-lefebvre</code></a>!
- Adds <code>logger</code> to the context object passed to cache
providers</p>
<p>Custom cache providers now receive Astro's runtime logger on the
context passed to <code>onRequest()</code>. Messages logged with it are
routed through the destination configured in <code>logger</code> and
respect your log level, instead of being written straight to the
console:</p>
<pre lang="ts"><code>import type { CacheProvider } from 'astro';
<p>const provider: CacheProvider = {
name: 'my-cache',
async onRequest({ request, url, logger }, next) {
logger.warn(<code>Skipping cache for ${url.pathname} because the
response sets a cookie.</code>);
return next();
},
// ...
};
</code></pre></p>
<p>Astro's built-in <code>memoryCache()</code> provider now uses this
logger for the warnings it emits when it skips caching a response that
sets cookies, and when a background revalidation fails.</p>
</li>
</ul>
<h3>Patch Changes</h3>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/withastro/astro/commit/92f23cc121d3a1a03c6fb901a519309662b333de"><code>92f23cc</code></a>
[ci] release (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17900">#17900</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/03896405717471f7d6ff54986ed6beaec0cac94f"><code>0389640</code></a>
fix: dont use internal paths (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17899">#17899</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/f800de13ffab9542f8d1bd13a8f4481c5f5c083a"><code>f800de1</code></a>
[ci] release (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17881">#17881</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/1e0b7e6023128ad25a79ac125f6d33e5936a3def"><code>1e0b7e6</code></a>
[ci] format</li>
<li><a
href="https://github.com/withastro/astro/commit/4671a5c2d215545d8d7f763381ec1084dce9b7d1"><code>4671a5c</code></a>
chore(deps): update react to v19 in <code>0-css</code> fixture (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17888">#17888</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/31b886b75259e5a8d50dc750e587ee9bc97ee099"><code>31b886b</code></a>
Update bundled Zod to 4.5 (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17862">#17862</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/e747cba07fcd2b9e7fb03c02ed42abfe2079daa2"><code>e747cba</code></a>
Skip unsupported Vary responses in the memory cache (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17886">#17886</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/fb5b0d0a952b50c48908a262a702f43dcf42f9e7"><code>fb5b0d0</code></a>
[ci] format</li>
<li><a
href="https://github.com/withastro/astro/commit/ce7c91f77dbd7be03c04bc13f87af9d01fef6cef"><code>ce7c91f</code></a>
Add <code>--ignore-lock</code> flag support to <code>astro
preview</code> (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17767">#17767</a>)</li>
<li><a
href="https://github.com/withastro/astro/commit/c0b65811dfa0dafa1aa04b7d6d67fd09250ff8c1"><code>c0b6581</code></a>
feat: use logger instead of console where possible (<a
href="https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/17818">#17818</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/withastro/astro/commits/astro@7.3.1/packages/astro">compare
view</a></li>
</ul>
</details>
<br />


Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: worktrunk-bot <254187624+worktrunk-bot@users.noreply.github.com>
2026-09-13 10:23:12 -07:00
Maximilian RoosandClaude Opus 5 cff085edf9 docs: fix misplaced copy buttons by dropping terminal frames (#4090)
On every shell code block the copy button sat 40px below the top of the
code: on the second line of multi-line blocks, and hanging below
one-line blocks such as `wt merge --no-ff` on /merge/. Shell blocks were
Expressive Code terminal frames, and the terminal plugin deleted their
title bar, but Expressive Code still offsets the copy button by that
bar's height.

## Changes

- `docs/astro.config.mjs` sets `defaultProps: { frame: 'code' }`, so no
block is a terminal frame and there is no title bar to remove. The
plugin's header-removal hook and its `props.frame = 'terminal'` go, and
so does the `wt-commands-only` class: mobile wrapping in `custom.css`
now keys on whether a block contains captured output
(`:has(.wt-output)`).
- Blocks with several commands had a whole-block copy button and
per-line buttons in the same corner, handed over on hover by opacity. A
hidden button still takes clicks, so clicking a line's button could copy
the whole block, and on touch screens one button covered another. Most
of these blocks are lists of alternatives, so they now get only per-line
buttons, and the hover rule is deleted.
- Those blocks wrap (Expressive Code's `wrap` prop) unless they carry
captured output, since a per-line button sits at the end of its line and
scrolled out of view on the long `jq` examples on /list/. A per-line
button is no taller than its line, so buttons on adjacent lines no
longer overlap.
- The two multi-command blocks that only work run in order, the FAQ's
stash recipe and the `Equivalent to:` block under `wt step diff`'s **How
it works** (in `src/cli/step.rs`), are now `bash` fences, the form
`docs/CLAUDE.md` prescribes for a copyable recipe, so they keep one copy
button for the whole recipe. Terminal `--help` renders `console` and
`bash` fences alike (it strips `$ `), and the help snapshots are
unchanged.

## Side effect

Expressive Code strips comment lines only from what terminal frames
copy. The eight `bash` and `powershell` blocks with comments on
/shell-integration/ now copy them, as console blocks already did. Pasted
into zsh without `interactivecomments`, each comment line prints
`command not found: #`; the commands still run.

## Tests

A browser test checks every copy button on every page, at 393px with
touch and at 1376px, for three things: it sits on the line it copies, it
is inside the visible code, and it doesn't overlap another button. These
checks fail against worktrunk.dev and against a build without the wrap
and the height cap. The built-site and plugin tests now expect per-line
payloads and no block payload on multi-command blocks, and a plugin test
pins that blocks carrying output never wrap.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_013U96NY8qKtZhavBSwnfCYq

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-13 10:00:25 -07:00
Maximilian RoosandClaude Opus 5 10315349f4 Scope docs heading anchors under each subcommand section (#4079)
Command pages on the site append every subcommand's help, so headings
such as "Examples", "Options", and "Command reference" repeat down
`/step/` and `/config/`. The heading-id plugin numbered the repeats by
position (`/step/#examples-3`, `/step/#hooks-1`,
`/step/#command-reference-7`), so an anchor pointed somewhere else once
a same-named heading was added above it.

`docs/src/plugins/stable-heading-ids.mjs` now scopes ids below each
subcommand's H2 (a heading starting `wt `) by that section's id:
"Examples" under `wt step push` is `/step/#wt-step-push--examples`.
Page-level headings and the subcommand headings keep their ids, so the
table of contents and links like `/step/#wt-step-copy-ignored` are
unchanged. A slug never contains `--`, so a scoped id can't equal
another heading's slug — a "Cache" heading under `wt config state` stays
distinct from the `wt config state cache` section.

With the site handling it, the CLI help keeps unqualified headings.
#4000 renamed six `wt config` subcommand headings to "Approval
examples", "Alias examples", and so on to avoid the numbering; they're
back to "Examples", in `--help` as well.

Every anchor inside a subcommand section changes once:
`/step/#min-age-guard` is now `/step/#wt-step-prune--min-age-guard`. The
two internal links that pointed at such anchors — the FAQ's
copy-on-write link and `wt config approvals`' "Reading approval state" —
are updated, and `test:site` checks every internal fragment. External
links to the old anchors land at the top of the page.

The search-index plugin (`pagefind-command-references.mjs`) now imports
the subcommand-heading check from the heading-id plugin rather than
keeping its own copy.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01HUmx2Jd5mTK5TznqGDmLGp

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-12 16:57:33 -07:00
Maximilian RoosandClaude Opus 5 dd389339f0 docs: sit the file-name tab flush with its code block (#4078)
Code blocks titled with a file name (for example `.config/wt.toml` above
a TOML excerpt) showed an awkward gap to the left of the name tab.
Expressive Code's `.header::before` draws a 1px outline around the whole
strip above the code, which our overrides left in place, and the tab was
inset 0.6rem from the frame's left edge, so an empty outlined box sat
beside it. The outline is removed and the tab now sits flush with the
frame's left edge, keeping its own background and rounded corners; the
copper rule still starts where the code does.

The browser test that already checks the label sits directly on its code
now also checks the label and the code share a left edge; with the old
inset restored, it fails.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_016NGjseUKXkyL8qHLhaXsnt

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-12 15:06:02 -07:00
Maximilian RoosandClaude Opus 5 4f26e9a1c1 docs: keep code frames in the content column and dev-server styling current (#4076)
## Code frames leave the content column on wide screens

#4000 stretched every terminal frame to the full content panel at 72rem
and up, to give `wt list --full` room. Once the panel is wider than the
62rem column, Starlight offsets the column inside it, so shell snippets
moved left of the prose they belong to and spanned past it on the right,
while TOML frames stayed in the column. On
https://worktrunk.dev/tips-patterns/ at 2560px, prose starts at x=760
and shell frames at x=248, 1504px wide.

#4039 had already made terminal output fit the column. With the stretch
disabled, no output-bearing frame on any of the 15 pages overflows;
three long one-line commands on `/config/`, `/list/` and `/step/`
scroll, as long TOML lines already do. So the rule is removed rather
than narrowed.

The desktop browser test ran only at 1152px and 1376px, where the panel
and the column are the same width and the rule changed nothing. It now
also runs at 1920px and asserts every code frame stays within the
column; with the old rule restored, it fails on the homepage.

## The dev server loses code styling after a merge

Astro caches rendered Markdown with the Expressive Code stylesheet URL
baked in. That URL's hash comes from the code-rendering config and
plugins, which Astro's content-cache key doesn't cover. A merge that
changes `astro.config.mjs` and the terminal plugin under a running dev
server makes Astro restart it in place: the server serves the new
stylesheet while content keeps rendering with the old renderer, so every
page links a stylesheet that returns 404. Restarting the process doesn't
recover, because the cache survives it.

- `docs/package.json`: `dev` passes `--force`, as `build` already does,
so a restart re-renders.
- `.config/wt.toml`: the docs hook sets `ASTRO_DEV_BACKGROUND=1`. When
`astro dev` detects an AI agent, it respawns itself detached, which
drops `--force` and escapes `wt step tether`; three worktrees currently
run their dev servers that way.
- `docs/CLAUDE.md`: explains the cache and says to restart with `wt hook
post-start docs` after `astro.config.mjs` changes, since the in-place
restart is Astro's to fix.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_016NGjseUKXkyL8qHLhaXsnt

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-12 14:14:09 -07:00
Maximilian RoosandClaude Fable 5.1 89326f14af Publish shell integration, add a footer, dedupe global options (#4000)
Guides and site presentation: one home per topic, a shell-integration
page, a footer, and three rendering fixes.

**Global options were emitted once per command reference**

clap repeats the same ~20-line `Global Options:` block in every
reference it renders, so a page assembled from subdocs stacked 11 copies
on `/config/` and 13 on `/step/`. That padded the pages and gave site
search that many near-identical hits — "squash" returned both
`#command-reference` and `#command-reference-2`. `take_global_options`
cuts each reference at the heading as it is built, keeping only the
first; one `kept` flag threads through the subdoc expansion and the page
streams out rather than accumulating. Terminal `--help` renders through
clap directly and is unchanged.

The config page also carried colliding anchors — two "Hooks" (`#hooks`,
`#hooks-1`), two "Aliases", and seven "Examples" (`#examples` …
`#examples-6`) — now qualified at their source in `src/cli/config.rs`:
User/Project hooks, User/Project aliases, and
Approval/Alias/State/Cache/Log/Variable examples.

`/step/` still has its own set (eight "Examples", two "Options", two
"Arguments", plus "Staging" and "Dry run" pairs). Qualifying those moves
existing `/step/#examples-N` anchors, so it wants a pass of its own with
the inbound links audited; the deduplication above already removes 13
Global Options blocks from that page.

**Shell integration has a page**

Shell-integration debugging was skill-only: five named warning messages,
a PowerShell checklist, and the wrapper mechanism, with no site page —
while the FAQ's answer to "`wt switch` didn't cd" was to install the
Claude Code plugin. It is now `/shell-integration/`, offered first, with
the plugin as the second route. The `llms.txt` listing serves every page
as `/<slug>.md` from a hand-created symlink, so a new page was a 404 the
listing still advertised; the symlink is added and the sync now fails
when a listed page has none.

**Presentation**

- A site footer carries the version (read from `Cargo.toml` at build
time), releases, changelog and license. No page named any of them, and
`/code-signing/` was reachable only from inside a collapsed block on the
homepage. Starlight's `Footer` is wrapped rather than replaced.
- `wt list --full` renders 1157px inside an 800px content column, so 40%
of it sat behind a horizontal scrollbar with the pane beside the column
empty. A terminal frame now takes the whole pane where there is slack,
measured with a query container rather than recomputed from Starlight's
layout formula.
- The `wt-command-reference` frames offered a copy button for 3,877
characters of generated help text; they now expose no copy control. A
console block listing several commands is as often a menu of
alternatives as a recipe, and nothing in the markup tells them apart, so
every command line in such a block carries its own copy control
alongside the block's.
- The four command demos and the two hand-written figures get captions;
the 2.33 MB homepage GIF below the fold loads lazily.

**Sidebar order is pinned**

`site-navigation.mjs` told readers a
`test_sidebar_matches_frontmatter_order` would fail when the authored
sidebar and the pages' `sidebar.order` disagreed. No such test existed,
and the disagreement it describes is exactly what the survey found:
`remove` listed before `merge`, Agent integration ahead of
lower-numbered pages. The test is written, so the sidebar and the
`llms.txt` ordering derived from the frontmatter can't drift apart
again.

<details>
<summary>Guide corrections</summary>

- Tips & patterns was 26 flat H2 recipes in no order, all 26 in the
sidebar. They group under five H2s — setup and layout, aliases and
hooks, per-worktree services, working with agents, status/commits/logs —
with each recipe demoted to H3. Anchors are level-independent, so
existing `/tips-patterns/#…` fragments still resolve.
- `-x 'opencode run'` has been broken since 0.75.0 made `-x` a literal
program: it is `-x opencode -- run '<task>'`.
- The branch-summary preview moved from tab 5 to 6 when the unified-diff
tab landed; the recipe names the `summary` tab instead of a number.
- The Caddy recipe claimed `feature-auth` hashes to port 16460 — that is
`fix-auth`'s port. It is 18283.
- `_` in `wt list` is same-commit *and clean*; the
same-commit-with-changes glyph is `–`, which is not safe to delete.
- `wt step prune` removes branches with no worktree too, and the min-age
guard ages a worktree by its creation time and a bare branch by its
oldest reflog entry.
- `wt step eval -v` prints fifteen variables; the example showed two
under a lead calling them "the available template variables".
- A filter applied to `{{ vars.<key> }}` acts on the placeholder the
preview substitutes, so `{{ vars.port | default('8080') }}` previews as
`{{ vars.port }}`, filter gone.
- The `.git/wt/cache/` table was missing `picker-preview`, and `wt
config state clear` prompts unless `--yes`.
- `skills/worktrunk/reference/README.md` was a symlink to the repo
README that `SKILL.md` never referenced, and the plugin mirror
dereferenced it into a 262-line copy carrying the star-history token,
share links, and a logo path resolving nowhere. Nothing generated it, so
deleting the symlink is the whole fix.
- One home per topic: agent handoffs stay in tips-patterns, activity
markers in `claude-code.md`, alias-template deferral in `extending.md`,
and the `codename` filter's two `worktree-path` recipes give way to the
config page that owns path templates. The FAQ's "Running tests" and "How
can I contribute?" duplicated the README's Contributing block down to
the share URLs.
- The FAQ linked `/worktrunk/#install`, the `noindex` compatibility
route; the plugin hook shim's Windows Terminal hint pointed there too.
Both use `/#install`, where the new sidebar Install entry goes.
- Example names settle on `myproject` / `feature-auth`; "sibling to main
repo" becomes "sibling to the main worktree", and `wt remove`'s "target
worktree" becomes "the worktree being removed" per the project's own
terminology rule.

</details>

UX survey items: `#36`, `#37`, `#38`, `#39`, `#45`, `#47`, `#48`, `#49`,
`#50`, `#51`, `#52`, `#61`, `#94`, `#95`, `#96`, `#97`, `#99`, `#100`.

Reviewable files: the hand-written pages under `docs/src/content/docs/`
(notably the new `shell-integration.md`, `tips-patterns.md`, `faq.md`),
`docs/src/components/Footer.astro`,
`docs/src/plugins/worktrunk-terminal.mjs`,
`docs/src/site-navigation.mjs`, `docs/tests/*.mjs`, `src/help.rs`,
`plugins/worktrunk/hooks/wt.sh`. Generated mirrors and snapshots are
regenerated.

> _This was written by Claude Code on behalf of max-sixty_

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01XAUYWFN9d9oh6jyoQiouHb

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-12 12:44:47 -07:00
Maximilian Roos a0ad432a04 docs: fit terminal examples on desktop (#4039)
Widen the documentation content rail and defer the right-hand table of
contents until the viewport can accommodate it, so terminal examples use
the available desktop space.

Capture every documentation-backed `wt list` example at the shared
98-column width. Full-mode examples now exercise Worktrunk's real column
hiding and truncation instead of embedding 134-column output, and the
activity example no longer inherits the test suite's 500-column default.

Add a browser regression that crawls every public route at both sides of
the responsive breakpoint and rejects horizontal overflow in
output-bearing terminal blocks.

> _This was written by Codex on behalf of max-sixty_
2026-09-07 16:51:23 -07:00
Maximilian Roos 474f93a007 Replace config update --print with --output (#4021)
`wt config update` now uses a destination-based output interface:
`--output <path>` atomically writes the migration artifact, while
`--output=-` emits the same bytes to stdout. This replaces `--print`,
keeps output mode read-only, and includes project-config migrations when
invoked from a linked worktree.

Relative destinations honor the global `-C` directory. When there is
nothing to migrate, stdout stays silent and an existing file destination
remains untouched. If both user and project configs need migration,
stdout emits a labeled inspection artifact while file output fails
before writing. Help text also notes that output artifacts omit legacy
`approved-commands`; the in-place mode remains responsible for moving
those entries to `approvals.toml`.

Integration coverage exercises file replacement, preservation and write
failures, multi-config rejection, stdout piping and broken consumers,
clean configs, linked worktrees, source-file preservation, help text,
and rejection of the removed flag. The full pre-merge gate passed all
4,770 tests, targeted instrumentation covers both file-error branches,
and the production docs build passed all 16 built-site and browser
tests.

> _This was written by Codex on behalf of max-sixty_
2026-09-06 15:07:29 -07:00
ADITYA 7d08f6775f Add Pi activity tracking plugin (#3594)
## Summary

- add `wt config plugins pi install|uninstall`
- install a profile-aware Pi / oh-my-pi hook with atomic writes
- map Pi lifecycle events to Worktrunk working, waiting, and cleared
activity markers
- honor Pi's agent-directory, config-directory, and profile environment
variables
- cover profile paths, explicit directory overrides, uninstall behavior,
and CLI output snapshots

## Validation

- `cargo fmt --check` — passed
- `cargo test --test integration test_pi_ -- --nocapture` — 3 passed
- the same snapshot tests passed again without `INSTA_UPDATE`
- `cargo clippy --bin wt -- -D warnings` — passed

Closes #3571

---------

Signed-off-by: Aditya Datta <crazyme07071996@gmail.com>
2026-09-06 10:52:18 -07:00
Maximilian Roos 03ae3b6f60 Polish terminal gutters and shell strings (#3942)
The homepage merge transcript rendered its ANSI gutter as separate
glyph-height blocks, leaving visible gaps between consecutive rows.
Quoted prompts in the parallel-agent example also shared the same color
as ordinary shell arguments.

This extends the existing gutter spans to fill the line box and adds a
shell-specific quoted-string role to the paired syntax themes. The role
stays scoped to Bash strings, retains distinct accessible colors in both
themes, and leaves TOML strings unchanged. WebKit coverage pins the
complete gutter rail, line geometry, scope boundary, theme contrast, and
mobile containment.

> _This was written by Codex on behalf of max-sixty_
2026-08-27 18:42:31 -07:00
Maximilian Roos d6300f1c1b Color homepage command comparison (#3939)
Extends the site’s semantic Bash colors to the homepage Worktrunk /
Plain git comparison in both responsive layouts. The build-only
transform keeps canonical Markdown, README, and skill mirrors plain
while preserving command text; WebKit verifies every colored token meets
WCAG contrast in both themes.

> _This was written by Codex on behalf of @max-sixty_
2026-08-27 17:40:02 -07:00
Maximilian Roos 750972d2c5 Restore docs code-block hierarchy (#3938)
The Astro site kept the documentation content but lost some of the old
site's visual hierarchy: shell commands flattened into one color,
generated Command References had no semantic roles, dim terminal rows
were barely distinguishable, and file excerpts read like generic
untitled code. This restores those distinctions at their natural
rendering boundaries.

## What changed

- Add paired Worktrunk Shiki themes for source and shell syntax,
preserving the established warm palette with accessible light and dark
contrast.
- Mark generated Command Reference fences at their producer and render
Clap commands, headings, options, values, metadata, possible-value rows,
continued Usage signatures, and variadic metavariables semantically.
- Replace opacity-based terminal dimming with explicit accessible colors
while retaining ANSI hues.
- Present file excerpts as compact attached path tabs with a restrained
craft accent.
- Cover all 30 generated references, every public route at 320px and
393px in both themes, unrelated-fence false positives, command-only
copying, horizontal containment, and WCAG contrast in real WebKit
rendering.

## Mobile demos

The light and dark mobile homepage demos were already re-recorded and
published in `max-sixty/worktrunk-assets` at `4de7bde` by #3936. This
change verifies responsive source selection and viewport containment
against those current recordings, so another lossy re-record is
unnecessary.

## Testing

- `cargo run -- hook pre-merge --yes` — 4,722 passed, 1 skipped
- `cargo test --test integration test_docs_are_in_sync -- --nocapture`
- `npm --prefix docs test`
- `npm --prefix docs run build`
- `npm --prefix docs run test:site`
- `npm --prefix docs run check`
- independent systematic, adversarial, and from-scratch architecture
reviews

> _This was written by Codex on behalf of max-sixty_
2026-08-27 16:07:46 -07:00
Maximilian Roos e5f9589c5c Polish mobile docs terminals (#3936)
## Summary

- re-record and publish both mobile homepage demos with restored ANSI
colors
- preserve exact ANSI roles in every snapshot-backed website terminal
while keeping Markdown portable
- wrap source and command snippets on mobile, contain fixed terminal
tables, and add real WebKit layout and contrast regressions

The corrected GIFs are already published in `max-sixty/worktrunk-assets`
at `4de7bde`.

## Testing

- `cargo run -- hook pre-merge --yes` (4,721 tests passed, 1 skipped)
- `npm --prefix docs run check`
- `npm --prefix docs test`
- `npm --prefix docs run build`
- `npm --prefix docs run test:site`
- independent frame review of both mobile GIF themes
- independent architecture, systematic, and adversarial reviews

Closes #3930
Closes #3931

> _This was written by Codex on behalf of max-sixty._
2026-08-27 12:14:39 -07:00
Maximilian Roos 952a40293c docs: simplify page footer (#3876)
Removes the Previous/Next navigation and the duplicate project and
sharing links from every documentation page. An empty Starlight
Pagination override leaves the default footer and source edit link
intact.

The sticky header also uses an opaque paper surface so page content does
not show through while scrolling. A built-site test covers the footer
contract across every rendered route.

Tested with Astro diagnostics, renderer tests, a 16-page production
build, built-site tests, production search, and browser checks at
desktop and mobile widths.

> _This was written by Codex on behalf of @max-sixty_
2026-08-22 19:39:20 -07:00
Maximilian Roos 8e405bced9 docs: rebuild the site with Astro and Starlight (#3866)
The docs now build with Astro and Starlight instead of Zola. This
removes the Tera 2 migration blocker from #3827 while keeping the
published routes, anchors, generated references, metadata, and crawler
URLs stable. It replaces the approach closed in #3840.

## What changed

- Move the site into Starlight, with a custom Worktrunk homepage and a
shared copper, gold, paper, and ink design system.
- Keep generated docs as portable Markdown. The Rust sync pipeline no
longer needs Zola shortcodes, template escaping, ANSI-to-HTML
conversion, or reverse transforms for skill and README output.
- Preserve terminal semantics and command-only copying, add responsive
handling for short wide tables, retain stable heading IDs, and give
repeated command-reference headings useful search labels.
- Move docs CI and publishing to Node, Astro, and built-site contract
tests. The tests cover public routes, links, assets, metadata,
navigation, tables, terminal frames, and compatibility aliases.
- Record demo themes from isolated environments, add a mobile core demo,
and test the recording contract. The matching mobile assets are
published in `max-sixty/worktrunk-assets`.

Closes #3827.

## Verification

- `cargo run -- hook pre-merge --yes` (4,660 tests)
- `npm --prefix docs run check`
- `npm --prefix docs test` (9 tests)
- `npm --prefix docs run build` (16 pages)
- `npm --prefix docs run test:site` (12 tests)
- `pytest docs/demos/tests/test_recording.py` (4 tests)

> _This was written by Codex on behalf of max-sixty_
2026-08-22 00:01:58 -07:00