The paper agrees with the code — guide v11, README, DESIGN re-rulings, and the adjudicated sweep

Step 7 of strategy/01-git-excision.md, the companions. The agent guide bumps to v11: the Git section teaches repo-resident etiquette alone (stage only your own paths, commit your own changes, leave app-maintained files to the app) — existing boards heal to the new text on next open. README re-anchors: the four git feature bullets out, tiers say the complete Mac experience is free, and one bullet states the format's git-friendliness promise. The changelog drops the never-shipped git entries. DESIGN re-rules: 06 retired with Undo routing migrated to 13 (now the sole substrate's doc, seam kept open), 07 retired as written pending the ops-service workstream, 14 retired as superseded record, 12 carries the second pivot note, the index reflects all of it; the charter gets a pointer note (the anchors' full re-ruling stays with the user). InertGitTests renames to GitAgnosticStorageTests — the excision restores its original claim app-wide. And the sweep: ~70 comment sites across 36 files adjudicated against the keeper list, every present-tense description of the excised machinery made past tense or repointed, keepers untouched. 2,707 tests green.

Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy

Kanban/LiveStore/BoardDiff.swift

@@ -12,20 +12,22 @@ import Foundation
 /// is explicit about why that is the right shape: "a value-type snapshot comparison is both cheaper
 /// and more trustworthy than trying to reconstruct a tree mutation from a stream of paths that may
 /// have been coalesced, dropped, or reordered". So this is a comparison of two `BoardModel` values
-/// and nothing else — no FSEvents paths, no receipts, no git. That is also what makes it work on a
-/// no-git board, which 10 requires in as many words ("on no-git boards the same classifier runs
-/// without the committer").
+/// and nothing else — no FSEvents paths, no receipts, no git. That is also what makes it work
+/// regardless of git: app-managed git is gone now (`strategy/01-git-excision.md`, 2026-08-08), and 10
+/// once required this in as many words for the no-git case specifically ("on no-git boards the same
+/// classifier runs without the committer") — today there is no other case to distinguish it from.
 ///
 /// ### Why it lives in `LiveStore/` and not beside the announcement
 ///
-/// 10 says announcements "reuse the auto-committer's summarizer" and 06-history-undo.md says the
-/// committer synthesizes its commit messages from the same comparison. The committer is Pro-tier
-/// work (pro-m1) and does not exist yet, so the summarizer is built here first, in the layer both
-/// consumers can reach: the store layer is below the history providers, so it is available to the
-/// committer by construction, where a type living inside the git provider would not be reachable
-/// from the announcer (12-editions.md ▸ The provider seam). It imports
+/// 10 once said announcements "reuse the auto-committer's summarizer" and 06-history-undo.md said the
+/// committer synthesized its commit messages from the same comparison — Pro-tier work (pro-m1) that
+/// never shipped before app-managed git was excised entirely (`strategy/01-git-excision.md`,
+/// 2026-08-08). The summarizer was built here first anyway, in the layer any future consumer can
+/// reach: the store layer sits below the history providers, so it stays available to whatever
+/// replaces the committer — today the foreign-change journal (`strategy/01-git-excision.md` ▸
+/// Successors) — by construction. It imports
 /// `Foundation` alone and touches no view, no window, and no `NSAccessibility` — the phrasing is
-/// `AccessibilityPhrases`' job, and pro-m1's message composer will phrase the very same counts
+/// `AccessibilityPhrases`' job, and a future message composer will phrase the very same counts
 /// differently without either of them knowing about the other.
 ///
 /// The per-category **identity sets** rather than bare tallies are for that second consumer: a