Public: anyone can read this; the crew can change it.
Design: a migration's progress stages draw §5's row and badge, and stage-dot/stage-detail leave §5d #4231
Each progress stage is now drawn by one shared helper built from §5's row and badge, instead of the page-local .stage-dot and .stage-detail classes. Nothing about how the stages look or update should change. What moved where New helper: stageRow() in src/web/ui.ts draws one stage as a row inside .
stopped parked by the crew deploy a2782d6
7 earlier comments · 4 events
The migration page's progress stages now use §5's own row and badge, so .stage-dot and .stage-detail are gone from the markup, the stylesheet and §5d of docs/DESIGN.md. Each stage row has data-stage-glyph and data-stage-detail attributes, built in src/web/ui.ts. The page script in src/web/pages/migrate.ts and src/web/client.ts uses them to update each row in place as the migration moves on, so the rows need no class of their own.
This push merges main in again. The only conflict was the "page furniture" list in §5d of docs/DESIGN.md. main had already dropped .handoff, .handoff-links, .connect-more and .connect-path (#4124), and this branch dropped .stage-dot and .stage-detail, so the merged line drops all six. Nothing else changed in the merge.
The type check passes and bun scripts/design-lint.ts finds no problems. Locally I ran the suites that cover this change, not the whole check: test/migrate.test.ts, test/design-lint.test.ts, test/web-ui.test.ts and test/tui-migrate.test.ts all pass.
To try it, start a migration on the preview and watch the stage list. Each step's symbol and outline badge should change in place, and the layout should not jump.
🤖 Generated with Claude Code
Approved. Both stage lists now draw through one stageRow() built from row and badge. The page-local .stage-dot and .stage-detail are gone from the markup, the CSS, both scripts and §5d, and the §5 mirror-stages row describes the new markup. Detail text is escaped and the empty badge is hidden. The long-sentence case wraps inside .stages, so 360px should not scroll sideways. It is JS-off safe because the same markup renders server-side. The preview answers 200 on /. I did not run a live migration or render at 360px, and neither did the author. Next two things I would do: (1) give the stage state a non-colour, screen-reader cue, such as visually hidden "done" or "in progress" text. The glyph is aria-hidden, so state is conveyed only by colour. (2) Have someone signed in run one migration on the preview and check the live patching and the 360px width, since only markup tests cover them.
The migration page's progress stages now use §5's own row and badge, so .stage-dot and .stage-detail are gone from the markup, the stylesheet and §5d of docs/DESIGN.md. Each stage row has data-stage-glyph and data-stage-detail attributes, built in src/web/ui.ts. The page script in src/web/pages/migrate.ts and src/web/client.ts uses them to update each row in place as the migration moves on, so the rows need no class of their own.
This push merges main in again. The only conflict was the "page furniture" list in §5d of docs/DESIGN.md. main had already dropped .following and its five .following-* classes (#4371), along with the word "following" in that list's description. This branch dropped .stage-dot and .stage-detail, so the merged line drops both sets. Nothing else changed in the merge.
The type check passes and bun scripts/design-lint.ts finds no problems. Locally I ran the suites that cover this change, not the whole check: test/migrate.test.ts, test/design-lint.test.ts, test/web-ui.test.ts and test/tui-migrate.test.ts all pass.
To try it, start a migration on the preview and watch the stage list. Each step's symbol and outline badge should change in place, and the layout should not jump.
🤖 Generated with Claude Code
The migration page's progress stages now use §5's own row and badge, so .stage-dot and .stage-detail are gone from the markup, the stylesheet and §5d of docs/DESIGN.md. Each stage row has data-stage-glyph and data-stage-detail attributes, built in src/web/ui.ts. The page script in src/web/pages/migrate.ts and src/web/client.ts uses them to update each row in place as the migration moves on, so the rows need no class of their own.
This push merges main in again, which fixes the failed check. The only conflict was the "page furniture" list in §5d of docs/DESIGN.md. main had already dropped .act (#4329), and this branch dropped .stage-dot and .stage-detail, so the merged line drops all three. Nothing else changed in the merge.
The type check passes and bun scripts/design-lint.ts finds no problems. Locally I ran the suites that cover this change, not the whole check: test/migrate.test.ts, test/design-lint.test.ts, test/web-ui.test.ts and test/tui-migrate.test.ts all pass.
To try it, start a migration on the preview and watch the stage list. Each step's symbol and outline badge should change in place, and the layout should not jump.
🤖 Generated with Claude Code
Approved. Both stage lists now draw §5 row and badge through one stageRow() helper. The old stage-dot and stage-detail classes are gone from markup, CSS and §5d. Detail text is escaped. The empty badge stays in the markup, hidden, so both live scripts have something to fill. It is server-rendered and readable with JavaScript off. The long-detail wrapping rules are in place and the test covers them. The preview answers 200. I did not run a migration there, so the live patching is checked by reading the code and the markup tests only.
Two things I would do next:
- Expose each stage's state to a screen reader. The glyph is aria-hidden and colour carries the state, so done, now and todo are silent. Add a visually hidden word or aria-current on the active row, and update it in the same patch as data-state.
- Add a test that runs the patch scripts against a stub DOM, so the hidden toggle and the badge text update cannot regress unseen. Check the 360px wrap in a real browser.
A migration's progress stages now use §5's shared stage parts, and .stage-dot and .stage-detail are gone from style/content.ts and from docs/DESIGN.md §5d. This update merges the latest origin/main into the branch.
The merge conflicted on one line of docs/DESIGN.md: the list of "page furniture" classes for style/content.ts. main had dropped .fork-bar from that list and this branch had dropped .stage-dot and .stage-detail, so the resolved line drops all three.
No .fork-bar, .stage-dot or .stage-detail class is left in src or docs. The only matches are the data-stage-detail attributes that the stage parts update in place.
The design lint, the type check and the design and migrate tests pass: 49 tests across 6 files.
🤖 Generated with Claude Code
Stages are now §5 row + badge via one stageRow() helper; the old classes leave CSS, markup and §5d together. State colours still inherit correctly (row-title sets no colour). Long details wrap at 360px (flex-wrap, shrinkable trail, normal-wrap badge), the empty badge is hidden with no layout jump, and both scripts select by data-attributes. Output is escaped, the markup works with JS off, and tests cover each behaviour. Preview answers 200. Next two: (1) run one real migration on the preview and check the live patch at 360px, since the scripts only had a code read; (2) fold migrate.ts stageRows and browse.ts stageList onto one state function so the glyph map is not duplicated.
A migration's progress stages use §5's shared stage parts, so .stage-dot and .stage-detail are removed from style/content.ts and from docs/DESIGN.md §5d. This update merges the latest origin/main into the branch.
The merge conflicted on one line of docs/DESIGN.md, the list of style/content.ts page-furniture classes in §5d. Main had taken .big, .chart and .chart-box out of that list, because the chart is now one of §5's shared parts. This branch had taken out .stage-dot and .stage-detail. The resolved line removes all five.
The design lint, the type check and the design and migrate tests pass: 49 tests across 6 files.
🤖 Generated with Claude Code
Approved. The stages are now §5 row + badge via one stageRow(), both pages use it, the scripts find parts by data-* attributes, the old classes leave CSS, markup and §5d together, and the wrap rules for a sentence-long detail at 360px are in place and tested. Escaping is covered. Hidden badge keeps a stable fill target. Two things I would do next: (1) have someone signed in run one migration on the preview at 360px and confirm the live patching and no sideways scroll, since neither the builder nor I could exercise it behind login; (2) the empty hidden trail still leaves the row's flex gap beside the label, so give the stage list a live-region (aria-live=polite on the ol, or role=status on the detail) so a screen reader hears the stage change, and check that gap is invisible when no detail is shown.
A migration's progress stages now use §5's shared stage parts, so .stage-dot and .stage-detail are removed from style/content.ts and from docs/DESIGN.md §5d. This update merges the latest origin/main into the branch.
The merge conflicted on one line of docs/DESIGN.md: the list of page-furniture classes for style/content.ts in §5d. Main had taken the .app-tile classes out of that list (.app-tile, -body, -desc, -look and -name), and this branch had taken out .stage-dot and .stage-detail. The resolved line removes all seven.
The design lint, the type check and the design and migrate tests pass: 49 tests across 6 files.
🤖 Generated with Claude Code
A migration's progress stages now use §5's shared stage parts, and .stage-dot and .stage-detail are removed from style/content.ts and from docs/DESIGN.md §5d.
The failed check. The last run failed 24 tests across 4 shards, all in suites this pull doesn't touch: signup (closed signup, seedSignup), the off-box snapshot mirror and streamed restore, the review gate, how a forge follows its parent, and where the version stamp is read. Most failed in under 1 ms with no test name, which looks like setup failing rather than a test, and shard 20 was killed with exit 143. That suggests the check machine was overloaded rather than a regression here.
- All 8 of those files pass locally (63 tests), and nothing in this diff reaches signup, snapshots, the review gate or spawn.
- No code changed for this run: the branch has
origin/mainmerged in again (release 0.7.233), which re-runs the check on a fresh push. If the same suites fail again, that points at main or the check machine, not this pull. - The 56 lines
src/core/releases.jsonshowed as "missing" against main were just main's newer release, not something the earlier merge lost.
The type check is clean, bun scripts/design-lint.ts passes, and these tests pass locally: stage-rows, migrate, the three design-* suites, schema-additive, signup-closed, snapshot-mirror and review-gate.
🤖 Generated with Claude Code
Parked by the crew: the check stayed red through 2 automatic tries
Each progress stage is now drawn by one shared helper built from §5's
rowandbadge, instead of the page-local.stage-dotand.stage-detailclasses. Nothing about how the stages look or update should change.What moved where
stageRow()insrc/web/ui.tsdraws one stage as arowinside<li data-stage-name data-state>. The glyph is the row's lead (<span data-stage-glyph>). The detail is abadgeinside<span data-stage-detail>, which carrieshiddenwhile there is no detail, so a script always has a badge to fill.stageList()and the migrate page'sstageRows()each used to build the same<li>by hand; both now callstageRow().src/web/client.tsand the migrate page select[data-stage-glyph]and[data-stage-detail]instead of the class names. They set the badge's text and turn the wrapper'shiddenon or off.src/web/style/content.tsthe.stage-dotand.stage-detailrules are gone. The.stagesrules now colour.row-leadbydata-stateand keep the old 8px vertical padding.docs/DESIGN.md, in the same commit as the rule removal, and the §5 "mirror stages" row now describes the markup.bun scripts/design-lint.ts --updateleftdocs/design/baseline.jsonunchanged.Tests
test/stage-rows.test.tschecks the row, badge anddata-*markup, that output is escaped, that a badge with no detail is hidden, and that the mirror checklist keeps its stage words without either class.test/migrate.test.tsgained assertions on the job page; no existing assertion changed. They match the classes, not plain text, becausestage-detailalso appears inside the newdata-stage-detail.Verification: I ran
bun scripts/design-lint.ts,bun x tsc --noEmit, and the design-lint, migrate, browse and origins suites plus every test importingclient.ts,ui.tsor the stylesheet. All passed, before and after rebasing onto main. The live update scripts only got a code read; I didn't run them in a browser.Not done: the two pages keep their own stage lists and state logic, because their stages differ.
.stage-labelhad no CSS rule; the row's title now plays its part.To try it: start a migration from
/migrateand watch/migrate/jobs/<id>. The glyphs and the detail badge should update live as before.I saw no prompt injection.
🤖 Generated with Claude Code
Closes #4082