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

KanbanTests/GitignoreRulesTests.swift

@@ -7,9 +7,12 @@ import Testing
 ///
 /// `GitignoreRules` is pure — text in, verdicts out — so this suite is a table and nothing else: no
 /// filesystem, no board, no store. What it pins is that the app's own matcher is **git's**, because
-/// the ruling's whole premise is one definition of noise shared with the committer: "on Pro boards
-/// the same file governs the committer, so ignored noise neither relocates nor commits". A matcher
-/// that read the file differently from libgit2 would make that one sentence two behaviours.
+/// `gitignore(5)` is the format's own semantics and a file a user may also be handing to their own
+/// git — a matcher that read it differently from git itself would make the file lie to one reader or
+/// the other. (Once doubly true while a committer shared this definition too — "on Pro boards the
+/// same file governs the committer, so ignored noise neither relocates nor commits" — before
+/// app-managed git was excised entirely, `strategy/01-git-excision.md`, 2026-08-08; libgit2 is gone,
+/// but the format's own semantics remain the standard regardless.)
 ///
 /// The claims are grouped as `gitignore(5)` states them, in its order, plus the seed the app writes
 /// and the three deliberate divergences the type documents.