Retire the verbs, reads and views no surface reaches

[danbarua]

What this retires

Anything that no CLI command or MCP tool reaches. I checked each item with a grep of read./write. calls in app-cli, app-mcp, app-web, app-vscode, view-model and records. The only verbs those call are the ones listed in packages/app-cli/commands/*.ts and packages/app-mcp/tools.ts, and none of the items below is among them.

• Write verbs (packages/core-domain/write/): sharpen, recordReview, closeGate, reverify, isUndecided, undo, replaceAnalysis, keep, reinterpret. Their bodies, their command shapes in commands.ts, and the report codecs only they returned are gone. Revising now holds only isConfirmed.
• Reads (packages/core-domain/read/): pursuitsOf, originOf, whatWasKnown, criteriaGoverning, designHistory, reproductionOf, interpretationHistory, doTheseConflict, reproducibilityOf, whatDependsOn, how and learned. Also gone:
  • LearnedGroup and read/learned.ts;
  • their queries in queries.ts;
  • their codecs and types in reports.ts and report.ts;
  • the barrel exports;
  • the private helpers only they called: sideOf, restingOnArtefact, artefactNamed, amendmentChain, assertedBy, decidedOnTheStrengthOf, findingFor, conclusionEvents, enquiryOf, supersessionOf.
• What why and now call stays. explain.ts calls analysisRevision, contractFor, criterionStanding, enquiryInContext, enquiryStatus, gateStatus, neighboursOf, proseFor, stoppedWork, whatIsKnown, whySupported and workList, plus reachable through why. I checked with a grep of self.*.
• CLI views that nothing outside tests/cli/views.test.ts called: renderPursuits, renderAffects, renderInterpretation, renderHistorical, renderHow, renderCriteria, renderDesign, renderLearned, renderEnquiry, renderOrigin, renderReproduction, renderReproducibility, renderContract, renderGate, renderConflict, and the partLine formatter. views/analysis.ts, views/enquiry.ts and views/learned.ts held nothing else.
• Old events: RetiredOperation and PromoteCommand are deleted. No record holds data worth carrying forward. Schema and migrations are unchanged; the edge labels in packages/core-db/domain.ts stay.
• CLI vocabulary: twelve readings are removed for words no remaining schema produces (tests/cli/vocabulary.test.ts requires that).

app-mcp/schemas.ts loses 18 re-exports of deleted codecs. They sit next to the registeredSession line, so git may report a conflict with the PR that drops register_session. Keep both deletions.

Lines

Against main (37b97f1): 100 files, +455 / −9,639.

Area	Files	Added	Removed
packages/	28	39	3,163
tests/	50	376	6,031
docs/scenarios	22	40	445

Tests

Counts (full bun test --timeout 20000, read from the output file):

	Tests	Files	Pass	Skip	Fail
Before	1,765	232	1,762	2	1
After	1,632	216	1,629	2	1

The one failure is the same test both times: packages/app-acp/http.test.ts "the CLI serves --http until SIGTERM…". It fails on an ANSI reset in the URL it reads, and this PR does not touch it.

Deleted test files, and why nothing live lost coverage. Each one tested only a retired verb or a retired read:

• tests/domain/how.test.ts: how only.
• tests/consumer/historical_survey.test.ts: whatWasKnown only.
• tests/domain/survey-after-reinterpretation.test.ts: how reinterpret itself behaves.
• s9c, s9e: reproducibilityOf only.
• s10b, s10c, s10d, s10e: reverify with reproductionOf, reproducibilityOf and whatDependsOn.
• s11c, s11d: whatDependsOn and reproducibilityOf only.
• s11b: the reason a finding was superseded was the verdict of the review that replaceAnalysis cited. Only that verb wrote this.
• s12b: chains of reinterpret read through interpretationHistory.
• s20: isUndecided, which has no remaining equivalent.
• s24, s24b: undo, which has no remaining equivalent.

Rewritten in the remaining verbs where a retired verb was one step on the way to a live assertion:

• the test helper replaceAnalysis became reanalyse: a fresh run whose conclusions name what they replace, through conclude --replacing;
• sharpen became note + pose;
• reverify became recordAnalysis + conclude;
• reinterpret became a conclude on the same analysis with the narrower proposition, replacing the claim;
• reads of retired reports became why, whySupported, gateStatus or a list read.

Each rewrite was checked by removing the replacing it depends on, and the test then failed: domain-session's withdrawn-verdict test, s3b, and five of s3c's tests. Where an assertion held only because of the retired verb's graph shape, it was deleted rather than weakened:

• the lineage decision behind analysisRevision;
• the implied pairing in s11g;
• s4's why on the replacement.

One test that was not checking anything is fixed: s9b's comparison read an empty bucket in both worlds.

Evidence

• bun run check:quick passes (typecheck, depcruise, every check:*, including check:scenario-docs after bun run scenarios:build).
• bun run bonsai:record passes with gates.toml from the Bonsai checkout, ending "OK: record built …, replay clean." The probe scripts call only CLI commands, so none of them called a retired verb.

Follow-up, not done here

Now that old records need not be read, some live read code handles only shapes the retired verbs wrote. It is still reachable through why, but no remaining verb produces these shapes:

• the review kind in why;
• SHARPENS in originAlready;
• the closed gate state;
• undecided standing;
• retracted nodes, and the undo line in happened;
• revisedBy and INVALIDATED_BY lineage.

Retiring it is a separate decision.

The renderGateList column misalignment in colour (rows() pads by string length including escape codes) is an existing defect. The deleted renderGate padding test was its only coverage.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FWZHuy7xJbVqxyLipnvwdY