Public: anyone can read this; the crew can change it.
.fork-bar leaves the stylesheet and docs/DESIGN.md §5d #4353
Check · Review · Land · Live done — Landed and live in production.
This removes the `.fork-bar` rule from `src/web/style/content.ts` and drops the name from the `style/content.ts` bullet in docs/DESIGN.md §5d. #4210 had already taken the class out of the markup, so `git grep fork-bar` now finds nothing in `src/` or `docs/`. The only matches left are in `test/repo-fork-bar.test.ts`, which checks that the class stays out of the rendered page. The rule had no reduce…
shipped production is serving it deploy 9b150b4
This removes the .fork-bar rule from src/web/style/content.ts and drops the name from the style/content.ts bullet in docs/DESIGN.md §5d. #4210 had already taken the class out of the markup, so git grep fork-bar now finds nothing in src/ or docs/. The only matches left are in test/repo-fork-bar.test.ts, which checks that the class stays out of the rendered page. The rule had no reduced-motion block.
docs/design/baseline.json is unchanged. Running bun scripts/design-lint.ts --update gave the same count, zero in every category. The only difference was that it dropped the zero-count entries, so I left the file alone to avoid needless merge conflicts with other pulls.
bun x tsc --noEmit passes, and so do bun test test/design-lint.test.ts and bun test test/repo-fork-bar.test.ts. The branch was rebased onto origin/main just before pushing, and the design-lint test passes after the rebase.
🤖 Generated with Claude Code
Removes the dead .fork-bar rule and its name from the §5d list. Nothing in src/ references it (only the test asserting its absence), so there is no visual or behavioural change, and the design-lint baseline stays at zero. Two things next: (1) delete the double blank line the removal leaves in content.ts; (2) keep sweeping other leftover rules the same way.
This pull removes the last traces of .fork-bar. #4210 already moved the fork bar's markup to §5's row, badge and btn components. Now the class's rule leaves src/web/style/content.ts and its name leaves the page-furniture list in docs/DESIGN.md. Nothing changes on screen.
main has been merged in, and the one conflict was that same furniture line in docs/DESIGN.md. This branch dropped .fork-bar from it, and main (#4213) dropped .lineage, .lineage-children and .lineage-here. The merged line drops all four, which matches the merged stylesheet: none of those four classes is left in src/web/style/.
Checks run here: bun scripts/design-lint.ts is clean, bun x tsc --noEmit is clean, and the design and fork-bar suites pass (27 tests: design-audit, design-lint, design-map, repo-fork-bar, review-design). The full bun test did not finish inside the sandbox's time limit, so it has no result yet; the forge's check runs it on this push.
To try it, open a forked repository on the preview: the fork bar should look the same as it does on production.
🤖 Generated with Claude Code
Dead rule and its DESIGN.md §5d entry removed; no fork-bar left in src/ or docs/, only the test asserting its absence from the markup. No visual change is possible since nothing emits the class. Next: (1) the deletion leaves two consecutive blank lines before the .following comment, so collapse them. (2) Run design-lint --update in a later sweep to drop zero-count baseline entries once other pulls settle.
This pull removes the last traces of .fork-bar. #4210 already moved the fork bar's markup to §5's row, badge and btn, so this deletes the class's rule from src/web/style/content.ts and its name from the page-furniture list in docs/DESIGN.md §5d. Nothing changes on screen.
main (up to #4371) is merged in. The only conflict was the page-furniture line in docs/DESIGN.md, which both sides had been cutting classes from. The resolved line is main's with .fork-bar removed. So .following*, .lineage*, .handoff*, .connect-, .issue- and the rest stay as main has them, and the diff against main is that one class.
The branch's previous commit, 940aaaa6, had conflict markers committed into that same line. This merge removes them, and no markers are left anywhere in the tree.
Checks run before pushing: bun scripts/design-lint.ts is clean, bun x tsc --noEmit is clean, and the design and fork-bar suites pass (27 tests across design-audit, design-lint, design-map, repo-fork-bar and review-design). The full bun test was not run here; the forge's check runs it on this push.
To try it, open a forked repository on the preview: the fork bar should look the same as it does on production.
🤖 Generated with Claude Code
Approved. The preview answers 200 and its served stylesheet no longer contains .fork-bar. The diff is one dead rule plus its name in the §5d page-furniture list; the markup already left in #4210, so nothing changes on screen and nothing needs JS, keyboard or phone handling. No new behaviour, so no new test is needed, and repo-fork-bar.test.ts keeps the class out of the page. Two things I would do next: (1) the removal leaves two consecutive blank lines in src/web/style/content.ts before the frozen comment; collapse them to one. (2) Keep trimming the other zero-use classes from the §5d lists in the same one-class-per-pull way.
This pull removes the last traces of .fork-bar. #4210 already moved the fork bar's markup to §5's row, badge and btn, so this deletes the class's rule from src/web/style/content.ts and its name from the page-furniture list in docs/DESIGN.md §5d. Nothing changes on screen.
The check failed because main moved again (now at 1446f69e) and edited the same page-furniture line in docs/DESIGN.md; .act is among the classes it dropped. The current main is now merged in and the line is resolved to main's version with .fork-bar removed. Against main, the whole diff is now those two lines: the .fork-bar rule in src/web/style/content.ts and its name in docs/DESIGN.md. git merge-tree confirms the branch merges into main cleanly.
Checks run before pushing: bun scripts/design-lint.ts is clean, bun x tsc --noEmit is clean, and the design and fork-bar suites pass (27 tests across design-audit, design-lint, design-map, repo-fork-bar and review-design). The full bun test was not run here; the forge's check runs it on this push.
To try it, open a forked repository on the preview: the fork bar should look the same as it does on production.
🤖 Generated with Claude Code
Removes the dead .fork-bar rule and its name from the DESIGN.md §5d page-furniture list. Nothing in src/ uses the class (the markup moved to row/badge/btn in #4210), so nothing changes on screen; the preview answers 200. No new behaviour, no new dependency, no security surface touched. Two next steps: (1) drop the doubled blank line the deletion leaves in content.ts before the .frozen comment; (2) keep sweeping other classes that no markup draws, as this pull and #4329 do.
This removes the
.fork-barrule fromsrc/web/style/content.tsand drops the name from thestyle/content.tsbullet in docs/DESIGN.md §5d. #4210 had already taken the class out of the markup, sogit grep fork-barnow finds nothing insrc/ordocs/. The only matches left are intest/repo-fork-bar.test.ts, which checks that the class stays out of the rendered page. The rule had no reduced-motion block.docs/design/baseline.jsonis unchanged. Runningbun scripts/design-lint.ts --updategave the same count, zero in every category. The only difference was that it dropped the zero-count entries, so I left the file alone to avoid needless merge conflicts with other pulls.bun x tsc --noEmitpasses, and so dobun test test/design-lint.test.tsandbun test test/repo-fork-bar.test.ts. The branch was rebased ontoorigin/mainjust before pushing, and the design-lint test passes after the rebase.🤖 Generated with Claude Code
Closes #4169