Six leftovers from the simplification refactor, one commit each

[brillout]

Findings 1–6 from a review of what #1536 left behind, each in its own commit. Finding 7 (SPEC structure) is a separate PR.

9e770be — the barrel ends where its consumers end: 341 exports become 41

The headline. src/index.ts exported 341 names. Nothing imports this package by name, nothing inside src/ imports the barrel, and bin.ts — the only thing that ships — takes runCli from cli.js directly. Its consumers were the dashboard (85 imports, every one import type) and the dev-mode Vite plugin, which pulled the whole barrel out of dist/index.js to get runDaemon. 269 of the 341 were referenced nowhere outside their defining module.

That is the shape A7 dissolved one level down — a 406-symbol export surface with one consumer — surviving at the top. It costs more than tidiness: an exported name reads as "in use" to anyone grepping, so 269 of them made every future deletion pass start by proving a negative. That fog is where the run.json and sessions/ back-reads sat unnoticed.

The file is now the 41 types the dashboard names, grouped by defining module, type-only (a value re-exported there would pull its module into the browser bundle — the failure client.ts prevents). The dev plugin imports dist/daemon.js. main, types and the exports map go with it: they described a library API for a package that publishes a CLI. bin and files stay, so what someone installs is unchanged.

49389b2 — the meta's version field, and the old-records guard that was its only reader

Correcting my own review here. I reported this field as written and never read, off a grep that covered src/ and not dashboard/. It had exactly one reader — isMetaPublishing in dashboard/lib/live-state.ts — whose own comment calls it "the old-records guard".

That makes it the same class #1545 removed everywhere else. A meta written before #1455 folded handoffReport has no report though its handoff answered long ago, so the gate stopped a list from reading that absence as "still publishing". With nothing carrying a pre-fold record, the gate only ever answers true — and the field exists only to be gated on. Both go.

5f3ebd0 — nothing removes a project, so nothing keeps removeProject

No RPC, no CLI path, no dashboard control; only its own three tests. Its doc gave away how long: "the project's own overrides (#840) go with it" — the tier that promise was about was deleted in B5.

286bd8d — one name for the archive directory, not two spelling the same string

AGENTS_DIR and ARCHIVE_DIR were both 'agents', both exported, both re-exported. What differs between the two placements is the user segment, not the name — which is what the surviving constant's doc now says.

b748fe4 — the archive rule is named for the archive

SESSIONS_RULE → ARCHIVE_RULE; its value was already built from ARCHIVE_DIR. The sweep extends to the prose that carried the same retired word, including the line install writes into every user's repo. Two deliberately left alone, because they change what a user sees rather than what a reader reads: the commit message ([The Framework] a session) and the daemon's no-op reason (no session changes). Both worth renaming; neither is a comment.

eec7ad1 — four comments describe HTTP routes that no longer exist

GET /api/projects, the /api/docs payload, /api/logs+/api/runs, and a read model "backed by the ... legacy /api/* endpoints". daemon.test.ts already called them retired.

Verification

After pnpm clean: both typechecks, a full build, 1442 node tests, 774 dashboard tests (81 files). The dev plugin's new import was additionally checked by importing dist/daemon.js in a real Node process — that line is the one thing here no test covers.

Two observations, not fixed here

• update-check.ts polls npm for @gemstack/the-framework, which has never been published, so the CLI's "up to date?" footer silently reads "unknown" on every run. It degrades correctly; it just never says anything.
• This repo's own .the-framework/.gitignore still carries the pre-D5 rules (!*/sessions/, plus !LOGS.md and !conversations/ from records B3 collapsed). The archives already tracked stay tracked, and ensureArchiveIgnored appends the current rule on the next agent run, so it self-heals — but until then a new user directory's archive would be ignored.

---

Generated by Claude Code