Settings → About: name official, development, and self-host builds

[nedtwigg]

Adds an About topic at the end of Settings that says which build this is, and folds the Activity topic into Notifications.

What About shows

• Official release — built by release.yml in diffplug/dormouse from tag vX.Y.Z, at that tag's commit, from a clean tree.
• Development build — anything else, local dogfood builds included, with X.Y.Z+N, the commit, and "with uncommitted changes" when dirty.
• Self-host build — ahead of official or not; names the one Relay it reaches and that it never updates itself. Read from the Burrow's status, since the VS Code webview is built without the relay define.
• Web playground — on the website: simulated terminals, nothing runs locally, plus a download link.

Every kind shows version, commit, and host, with changelog/source/license/security links and a Copy details button (diagnostics including the user agent, built only on click so the settings search never indexes it).

Build stamp

scripts/build-stamp.mjs replaces generate-dor-version.mjs. A Vite plugin defines the stamp (version, commit, commits past the tag, dirty, official, host) in the Standalone, VS Code, and website bundles, and fails vite build if the define does not land. dor version and About share one buildTag; an unresolvable tag (shallow clone) now prints +? instead of reading as zero. The playground's dor version reads the same stamp.

Release behavior change: a release.yml tag run whose stamp would not be official (CHANGELOG/tag mismatch, tag ≠ HEAD, dirty tree) fails the build rather than shipping a build labelled Development forever. Simulated against a clean v1.2.0 checkout (official) and HEAD (throws); a full pnpm build plus the standalone build leave the tree clean. The first real tag push is the live test.

Spec: docs/specs/deploy.md → "Build stamp" (with rationale); the stamp never decides trust, updates, or features.

Also

• Settings topics are now General, Notifications (speech, push, then the animation watcher and inactivity timeout), Network, Labs, About.
• One shared CopyButton (with "Couldn't copy") for About, the one-time Copy link, and the theme debugger's Copy report.

Testing

• scripts/build-stamp.test.mjs, lib (build-info, AboutSettings, SettingsDialog), dor version with an unknown count, and the website, standalone, and vscode-ext suites.
• Storybook: Modals/SettingsDialog → About* stories cover each kind inline in the dialog; existing dialog snapshots will diff since the nav changed.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying mouseterm with    Cloudflare Pages

Latest commit:	22e46eb
Status:	✅  Deploy successful!
Preview URL:	https://9ed231bd.mouseterm.pages.dev
Branch Preview URL:	https://about.mouseterm.pages.dev

View logs

[dormouse-bot]

In a real build, searching Settings for "version" finds nothing, though the new SettingsDialog test says it finds About alone. The test renders unstamped: vitest sets VITEST, so buildStampVitePlugin skips the define and About shows Dormouse, version unknown, which is the only place the word appears. A stamped bundle shows Dormouse 1.2.0+14, a kind line, an explanation, and link labels, none of which contain "version". About doesn't match version by its group id or topic label either, so in the Standalone, VS Code, and website bundles About is hidden for what is probably its most likely search. About needs searchable text with the word in it, for example a rendered Version 1.2.0+14. The suggestion inline makes the test render a stamp, so it covers what ships.

[dormouse-bot]

Build & Test fails on this head because of the new import in standalone/vite.config.ts. The standalone dev-runner tests (standalone/scripts/dev-standalone.test.mjs and its siblings) build a throwaway tree in devWorkspace in standalone/scripts/dev-fixture.mjs. That function copies vite.config.ts and scripts/relay-origin.mjs, but not scripts/build-stamp.mjs, so Vite can't load the config (run):

[UNRESOLVED_IMPORT] Could not resolve '../scripts/build-stamp.mjs' in vite.config.ts

Every test in that file fails as a result. The website suite only shows "Failed" because pnpm's fail-first run stopped it, and its own tests were passing.

Copying the module won't be enough. These tests run under node --test, so VITEST is unset and the plugin's config() calls buildStamp(). That reads CHANGELOG.md from the copied module's parent (the temp root), so the fixture also needs a CHANGELOG.md there: a copy of the real one or a one-line ## [0.0.0] stub. git fails outside a repo, and runGit already treats that as null. Because dev-fixture.mjs is outside this diff, I can't post an inline suggestion. I can push the two copyFile lines if you'd like.

CI failed — standalone dev-runner tests can't resolve scripts/build-stamp.mjs in their fixture tree.

[nedtwigg]

Fixed in 22e46eb: devWorkspace copies scripts/build-stamp.mjs, and the stamp reads a tree with no CHANGELOG.md as an unofficial 0.0.0 (git failing is already null), so no fixture changelog is needed. standalone node --test scripts/*.test.mjs passes locally (37/37).

[dormouse-bot]

Confirmed: Build & Test passes at 22e46eb, standalone dev-runner tests included. The missing-changelog fallback also keeps the release guard intact. On a tag run, '' reads as v0.0.0, which won't match the tag, so a release with no CHANGELOG.md still throws rather than shipping unofficial. The Argos diffs are the nav change the description already expects.