Skip to content

v0.1.26 — one visual system across Settings, home and the project directory - #68

Merged
TsekaLuk merged 2 commits into
mainfrom
release/v0.1.26
Aug 21, 2026
Merged

v0.1.26 — one visual system across Settings, home and the project directory#68
TsekaLuk merged 2 commits into
mainfrom
release/v0.1.26

Conversation

@TsekaLuk

Copy link
Copy Markdown
Contributor

What ships

The four-surface visual unification merged in #67, plus the fixes found while verifying it against a real install.

  • Settings, the release-notes dialog, project home and the project directory now share one contract: spacing rhythm, radius scale, type scale, button hierarchy. That replaces four competing row containers in Settings alone, two nav rails sharing no tokens, and two different loading treatments for the same card grid.
  • Every task row names its provider (MOX · gpt-image-2) instead of a bare model id, and an unassigned task states which task it inherits from instead of showing a bare "Auto".
  • The project-directory header no longer breaks above ~1100px, where the description rendered beside the title, ran under the brandmark and squeezed the primary action between them.
  • The model count beside each provider renders again. All four translations bound the placeholder as {0} while the source names it {catalogSize}, so the number came out empty — it shipped in v0.1.25 and was caught from a user screenshot, not from CI. A catalog parity test now fails on that class of mismatch.
  • Non-raster attachments are no longer previewed through an object URL, and a duplicate nested "Updates" landmark introduced with the new section headers is gone.

Release mechanics

Version bumped across display, Cargo, Tauri, the capability manifest and the Codex plugin; reviewed release notes added in all five shipped locales.

Two assertions in scripts/release-notes.test.ts are made self-deriving rather than re-pinned. They encoded the shipping version's own content — the catalog version list and the English highlight titles — so every release edited this file to restate what it had just written. The head now derives from package.json and the render assertions iterate the catalog entry itself. Same guarantee, no per-release edit.

Verification

pnpm lint · tsc --noEmit -p tsconfig.app.json · 464 vitest suites · 136 Playwright visual tests · pnpm build · 322 Rust tests · release-notes:validate --require-all-locales · validate-release-version --expected 0.1.26 — all pass.

🤖 Generated with Claude Code

Bump the display, Cargo, Tauri, capability manifest and Codex plugin versions to
0.1.26 and add the reviewed release-note catalog entry in all five shipped
locales.

Two assertions in `scripts/release-notes.test.ts` are made self-deriving rather
than re-pinned. They encoded the shipping version's own content — the catalog's
version list and the English highlight titles — so every release edited this
file to restate what it had just written. The head now derives from
`package.json` and the render assertions iterate the catalog entry itself, so
the test checks that the CLI carries the catalog's copy rather than a snapshot
of one release's copy.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Comment thread scripts/release-notes.test.ts Fixed
`version.replace(/\./g, '\\.')` escapes dots but leaves backslashes alone, which
CodeQL flags as incomplete sanitization — the same mistake made hours earlier in
`commerce-operator.test.ts` and fixed there by dropping the regex entirely. It
came back because the fix was applied to one call site instead of to the habit.

This assertion never needed a sanitizer. It needs the literal shape the renderer
emits (`Cutout v0\.1\.26`, dots markdown-escaped), so split/join produces it
directly. A sweep for the same pattern across src, scripts and tests finds no
other instance.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@TsekaLuk
TsekaLuk merged commit 71e3b9b into main Aug 21, 2026
14 checks passed
@TsekaLuk
TsekaLuk deleted the release/v0.1.26 branch August 21, 2026 10:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants