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/History/HistoryProviding.swift

@@ -80,9 +80,10 @@ public enum HistoryStepOutcome: Equatable, Sendable {
 /// holds: move → move back ...; rename → restore title" — and both halves of that write are already
 /// in the caller's hands: the before-value *is* the inverse, and the after-value is what the write
 /// set (which is also what the staleness predicate compares). A step is therefore that pair, in the
-/// design's own terms, and deliberately says nothing about how a stack stores it: a gitless board's
-/// stack is `NSUndoManager`-backed and a Pro git board's is git (12-editions.md ▸ The provider
-/// seam), and neither substrate appears here.
+/// design's own terms, and deliberately says nothing about how a stack stores it: the board's stack
+/// is `NSUndoManager`-backed, and no substrate appears here. (Once two substrates shared this seam —
+/// a gitless board's native stack, a Pro git board's git history, 12-editions.md ▸ The provider
+/// seam — before app-managed git left the app entirely, 2026-08-08, `strategy/01-git-excision.md`.)
 ///
 /// ### `name` is the 06 vocabulary, unprefixed
 ///
@@ -262,27 +263,30 @@ public struct HistoryStep {
 /// seam from a window is the one coarse step its close registers.
 ///
 /// `AppModel.BoardSession` is where the board half's ownership lives, and the composition root binds
-/// which implementation it gets — **following the board, and since the 2026-08-07 pivot the board
-/// alone** (re-ruled 2026-07-31; 12-editions.md ▸ PIVOT 2026-08-07): a board without app-managed git
-/// — repo-nested included (re-ruled 2026-07-31) — binds `NativeHistoryProvider` (two step stacks over
-/// the inverses registered at the Writer boundary), and a git-mode board binds the git provider (undo
-/// as forward restore commits over HEAD's first-parent ancestry — 06-history-undo.md). Both answers
-/// are the same in every tier; the tier used to decide whether git was on the table at all, and no
-/// longer does.
+/// which implementation it gets — **always `NativeHistoryProvider`** now (two step stacks over the
+/// inverses registered at the Writer boundary), on every board, in every tier
+/// (`AppModel.makeHistoryProvider`). A git-mode board once bound a git provider instead — undo as
+/// forward restore commits over HEAD's first-parent ancestry, 06-history-undo.md — between the
+/// 2026-08-07 pivot (12-editions.md ▸ PIVOT 2026-08-07, when the tier stopped deciding whether git
+/// was on the table at all) and the 2026-08-08 excision that removed the git provider outright
+/// (`strategy/01-git-excision.md`).
 ///
 /// ### What this protocol deliberately does not say
 ///
 /// - **No `NSUndoManager`, anywhere in the signature.** It is the native provider's implementation
 ///   detail, and a seam that vended one would be a seam only one provider could ever satisfy — the
 ///   opposite of the reason the seam exists at all ("the free tier's native undo is the first proof
-///   the seam is real", 12 — written when native undo was the free tier's; the proof it names is
-///   two working substrates, which the pivot leaves standing). AppKit still needs an `UndoManager`
-///   to hand the responder chain; that adapter is `BoardUndoManager`, which sits *over* this
-///   protocol rather than inside it.
-/// - **No persistence promise.** The native stack dies with the session (13); the git provider's
-///   survives relaunch because git does (06). Both are honest implementations of these seven members.
+///   the seam is real", 12 — written when native undo was the free tier's; the proof it named was
+///   two working substrates, which the pivot left standing and the 2026-08-08 excision then narrowed
+///   back to one, `strategy/01-git-excision.md` — the seam itself is what stays proved either way).
+///   AppKit still needs an `UndoManager` to hand the responder chain; that adapter is
+///   `BoardUndoManager`, which sits *over* this protocol rather than inside it.
+/// - **No persistence promise.** The native stack dies with the session (13); a git provider's once
+///   survived relaunch because git does, before app-managed git was excised entirely (2026-08-08,
+///   `strategy/01-git-excision.md`). Both were honest implementations of these seven members; only
+///   native's promise is live to keep now.
 /// - **No routing.** Which surface ⌘Z reaches is focus's answer, not the substrate's
-///   (06 ▸ Undo routing, tier-independent) — `BoardUndoRouting`.
+///   (13-native-undo.md ▸ Undo routing, tier-independent) — `BoardUndoRouting`.
 ///
 /// ### One obligation every implementation shares: retire what you let go of
 ///
@@ -298,7 +302,8 @@ public struct HistoryStep {
 /// nonetheless stands to the session's end, because "the skip banner says nothing was applied, and an
 /// irreversible purge riding that gesture would be surprise loss". A substrate that pops stale steps
 /// therefore has a place to put them (`NativeHistoryProvider.strandedSteps`); one that never keeps a
-/// step is untouched by the distinction, which is why the git provider needed no change.
+/// step is untouched by the distinction — which is why the git provider, while it existed, needed no
+/// change for this rule at all.
 ///
 /// ### And its mirror: say what you are still holding
 ///