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/Storage/BoardWriter.swift

@@ -585,9 +585,9 @@ public enum BoardWriter: Sendable {
     ///
     /// - **`.DS_Store`** — the Finder writes one into every folder a user looks at, and on a board
     ///   that means one per lane and one per card, each churning as icons and window positions move.
-    ///   On a git board it would be committed by the whole-tree stage, forever, under the user's own
-    ///   name; on every board it is now also the plainest thing the loose-file heal must not treat as
-    ///   a card's attachment.
+    ///   Once committed by the whole-tree stage on a git board, forever, under the user's own name;
+    ///   app-managed git is gone now (`strategy/01-git-excision.md`), and on every board it is the
+    ///   plainest thing the loose-file heal must not treat as a card's attachment.
     /// - **`.*.lanework-*`** — this file's own temp pattern, and the one entry the app is entitled to
     ///   have an opinion about: `atomicReplace` writes `.<name>.lanework-<uuid>` beside its target,
     ///   so a crashed write's residue is the app's litter rather than the user's file. The two must
@@ -1890,7 +1890,8 @@ public enum BoardWriter: Sendable {
     /// `updateIndex`'s closure cannot. Everything else is identical and deliberately so — read
     /// fresh from disk, refuse an uneditable frontmatter shape, edit, stamp `modified` and clear
     /// `modified-by`, replace atomically. A toggle is "an ordinary user edit — the standard atomic
-    /// write, auto-committed and undoable on git boards" (05), not a special case of anything.
+    /// write" (05) — once "auto-committed and undoable on git boards" too, before app-managed git was
+    /// excised (`strategy/01-git-excision.md`, 2026-08-08) — not a special case of anything.
     ///
     /// ### The offset, and why it is re-checked
     ///
@@ -2085,7 +2086,7 @@ public enum BoardWriter: Sendable {
     ///
     /// Text identical to what is already on disk writes nothing and returns `false` — `writeBody`'s
     /// untouched gate, applied to the whole file instead of the body span. Apply on a buffer the user
-    /// only read must not churn `mtime`, wake every watcher, and (on git boards) mint an empty commit.
+    /// only read must not churn `mtime` or wake every watcher.
     ///
     /// - Returns: `true` when bytes were written, `false` when the file already read exactly like
     ///   `text`.
@@ -2591,9 +2592,11 @@ public enum BoardWriter: Sendable {
     ///    reminting it would change an identity for no reason at all — the vanished-duplicate race,
     ///    read from the surviving side.
     ///
-    /// **Heal-marked**, because the app started it on its own: the receipt is what splits the remint
+    /// **Heal-marked**, because the app started it on its own: once the receipt that split the remint
     /// into its own commit on git boards, named for the Repair verb (06-history-undo.md ▸ Commit
-    /// messages). Undo never sees it — heals are not gestures (13-native-undo.md).
+    /// messages, retired with app-managed git, `strategy/01-git-excision.md`) — the receipt still
+    /// exists for whatever consumes it next. Undo never sees it — heals are not gestures
+    /// (13-native-undo.md).
     ///
     /// - Parameter duplicate: the withheld occurrence, `path` relative to `boardRoot` so the write
     ///   lands wherever the board lives *now*.
@@ -3020,7 +3023,8 @@ public enum WriteOperation: Sendable, Equatable, CustomStringConvertible {
 
     /// The board-root `.gitignore` being seeded — at creation, at instantiation, and by the
     /// scheduled heal that gives a board born before the ruling the file it now needs
-    /// (06-history-undo.md ▸ Repository hygiene, re-ruled 2026-07-31; `seedGitignoreIfAbsent`).
+    /// (06-history-undo.md ▸ Repository hygiene, retired with app-managed git,
+    /// `strategy/01-git-excision.md`; `seedGitignoreIfAbsent`).
     ///
     /// **No payload**, for `.agentGuide`'s reason: there is one such file per board, its name is
     /// fixed, and it is not an item with a title. Its own case beside `.agentGuide` rather than a