[darrylschaefer]

Problem and resulting behavior

Writing-version controls occupied a separate title-bar pill. Versions now lives in the right-pane section dropdown alongside Notes and History, with switching, copying, blank versions, and renaming together in one panel. Header Search also opens the same panel through Document versions.

The panel uses the existing section typography, spacing, and action-button styles. Removing the title-bar pill gives the document title more room on phones; version rows and actions use 44-pixel touch targets. Existing version identities, autosave behavior, and stored writing are preserved.

Related issue

Small interface follow-up to named writing versions. No new issue is opened.

Validation

• npm run check passed locally: application/test/browser typechecks, 527 unit/integration tests in 37 files, and the production build.
• Isolated browser checks with the bundled sample manuscript: switch, copy, create a blank version, rename, and open through Search.
• Desktop plus 390px/320px phone layouts; touch sizing, reachable actions, no horizontal overflow, and no browser runtime errors.
• Computed heading typography and section padding match Notes, History, Tools, Meta, and Macros.
• GitHub Actions passed on 627c46c: Linux/Windows validation, Linux Docker build, and all 100 desktop/phone browser cases.

Before: separate title-bar version control.

After: Versions in the right pane.

Risks and rollback

Version controls now require opening Versions in the right pane or through Search. This changes their placement without changing persistence or the document format. Reverting the commit restores the header control without a data migration. Native desktop packaging, physical-phone keyboards, and live provider calls were not exercised for this interface change; the local browser checks use Chromium.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
fthr-m0hg	Ready	Preview	Oct 25, 2026 1:51pm UTC