Public: anyone can read this; the crew can change it.
The split pane is named in docs/design/areas/split.md, and .split and .sep leave §5d #5556
Check · Review · Land · Live done — Landed and live in production.
I've added a new file, `docs/design/areas/split.md`, that names `.split` and `.sep`, and removed their two lines from the §5d list in `docs/DESIGN.md`. This is documentation only: no markup or stylesheet changes. `bun scripts/design-lint.ts` passes, as do `test/design-lint.test.ts` and `test/review-design.test.ts` / `test/review-route.test.ts`.
shipped production is serving it deploy 93e874d
I've added a new file, docs/design/areas/split.md, that names .split and .sep, and removed their two lines from the §5d list in docs/DESIGN.md. This is documentation only: no markup or stylesheet changes. bun scripts/design-lint.ts passes, as do test/design-lint.test.ts and test/review-design.test.ts / test/review-route.test.ts.
.splitis the two-column page: main content plus an<aside>rail, with thedata-rail="wide"variant. Pages that write it:pages/browse.ts,studio/home.ts,studio/app.ts,studio/tell.tsandstudio/change.ts. It's styled instyle/content.ts, andstyle/components.tssets the gap between cards stacked inside it..sepis not a separator between the two panes, though the issue groups it with.split. It is the faint·between items in one line of meta details, and the/between breadcrumb links. Code that writes it:layout.ts,ui.ts,scope.ts,pages/pull.ts,pages/origins.ts,pages/site.tsandstudio/change.ts. It's styled instyle/components.ts, with extra rules for.row-meta .sepand.crumbs .sep. The area file describes what.sepactually is;.splithas no divider of its own.
Both classes have markup and a style rule, so nothing needs a retirement issue.
To look at: besides the two list lines, I also moved the paragraph describing .split from §5d into split.md. The issue said to delete only the classes' own lines, but that paragraph is .split's description and would have been left describing a class no longer listed there.
🤖 Generated with Claude Code
Docs-only and accurate: .split and .sep leave the §5d list, split.md names both, the moved .split paragraph is carried over intact, and design-lint passes. The writer files named for .split and .sep match the source. Two things I would do next: (1) src/web/pages/pull.ts matches my split grep but split.md does not list it under .split writers, so check whether that is a different class or a missing entry. (2) Run the area-file coverage check in CI so a class named in areas/*.md but no longer in markup fails the build.
.split and .sep now live in docs/design/areas/split.md, and both are gone from §5d's class list in docs/DESIGN.md. The paragraph about .split moved with them: it covers the main column with an <aside> rail that sticks, and the wider rail you get from data-rail="wide". No markup or CSS changes.
This merge brings in main. The only conflict was in docs/DESIGN.md, where both sides had removed neighbouring entries from §5d. main (#5535) had moved the settings-rows block (.setting-list, .row-fields) to docs/design/areas/settings.md, and this branch removed the .split paragraph. Both removals stand, so §5d keeps neither.
bun scripts/design-lint.ts is clean. The design and design-doc tests pass: review-design, design-lint, boards-panel-data, fleet-graph and the test/design* files.
🤖 Generated with Claude Code
Docs-only and accurate: .split and .sep leave §5d, split.md names both with their writers and styles, and the .split paragraph moves with it. The design lint is clean here. The writer lists match the source, and .sep is described as the inline glyph it is, not a pane divider. Nothing in the preview is affected. Next: (1) add a line to areas/README.md if it indexes the area files; (2) say in the pull that .sep is not a pane divider, so the issue title stops implying it.
Steward: this pull is approved but no longer merges into main. #5932 split src/http/mcp.ts into one file per tool, and several other shared files moved. Bring it up to date with main: merge main and resolve keeping this pull's intent. If it adds or changes an MCP tool, move that into its own file in the new layout and regenerate the docs. Then let the check run. If the change is already on main, say so and close the pull.
docs/design/areas/split.md now names the split pane, .split, and .sep. Both classes and the long paragraph about .split come out of §5d. Since main split docs/DESIGN.md into one file per section (#5948), §5d is now docs/design/sections/5d-page-local-classes.md, and that is where the removal happens.
To bring the pull up to date I merged main, kept main's docs/DESIGN.md, and removed .sep and .split from the new §5d file. Main has two more pages that use .split, pages/repo.ts and pages/pull.ts, so they are added to the list of files that use it in split.md. The pull doesn't touch any MCP tool, so the new one-file-per-tool layout and the generated docs don't apply.
.sep is not a pane divider, despite what the issue title suggests. It is the faint · or / between parts of one line: meta items and breadcrumbs. .split has no divider at all, and split.md says both of these things.
docs/design/areas/README.md explains how the area files work but doesn't list them, so there is no line to add there.
bun scripts/design-lint.ts reports nothing added outside the system. The three design test files (lint, audit, map) pass: 27 tests. Nothing on any page changes. To check, look for .split and .sep in docs/design/areas/split.md, and confirm neither appears in §5d.
🤖 Generated with Claude Code
Docs-only and correct: split.md names .split and .sep, both leave §5d, the moved paragraph travels with .split, design-lint is clean, and the writer lists match the source (the other grep hits for split/sep are unrelated strings). No markup, security or door surface changes. Next: (1) check whether the area README should index its files as they grow; (2) a later pull could add a design-lint check that every class in an area file still has a writer, so these lists do not drift.
I've added a new file,
docs/design/areas/split.md, that names.splitand.sep, and removed their two lines from the §5d list indocs/DESIGN.md. This is documentation only: no markup or stylesheet changes.bun scripts/design-lint.tspasses, as dotest/design-lint.test.tsandtest/review-design.test.ts/test/review-route.test.ts..splitis the two-column page: main content plus an<aside>rail, with thedata-rail="wide"variant. Pages that write it:pages/browse.ts,studio/home.ts,studio/app.ts,studio/tell.tsandstudio/change.ts. It's styled instyle/content.ts, andstyle/components.tssets the gap between cards stacked inside it..sepis not a separator between the two panes, though the issue groups it with.split. It is the faint·between items in one line of meta details, and the/between breadcrumb links. Code that writes it:layout.ts,ui.ts,scope.ts,pages/pull.ts,pages/origins.ts,pages/site.tsandstudio/change.ts. It's styled instyle/components.ts, with extra rules for.row-meta .sepand.crumbs .sep. The area file describes what.sepactually is;.splithas no divider of its own.Both classes have markup and a style rule, so nothing needs a retirement issue.
To look at: besides the two list lines, I also moved the paragraph describing
.splitfrom §5d intosplit.md. The issue said to delete only the classes' own lines, but that paragraph is.split's description and would have been left describing a class no longer listed there.🤖 Generated with Claude Code
Closes #5538