The seams unbind — the provider is always native, and the git stack compiles dead

Step 4 of strategy/01-git-excision.md, the entangled one: AppModel's makeHistoryProvider collapses to the native provider (the seam stays injectable per the reversibility posture), the session's git state and its wiring go (wireGitUndo, wireBranchSwitching, the card-session staging threading), BoardStore sheds commitSeam and the identity-history ranker (the loader's nil-safe rung now tops out at birth date — today's no-git behavior), SessionSettleGate keeps the gate and inherits the path utility it borrowed, BoardRegistry drops the persisted operation stamp (decode-safe), and the git banner family leaves BannerCenter with its announcer and accessibility phrases. One missed harvest tie severed (the narrator's root subject is its own now). Nothing outside Kanban/Git/ references the stack — proven by sweep. 2,855 tests green.

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

Kanban/UI/AccessibilityPhrases.swift

@@ -432,13 +432,4 @@ enum AccessibilityPhrases {
     /// Reload breakage clearing — the board is reading its files again, which is a smaller claim
     /// than the lock's and is deliberately phrased as one.
     static let reloadBreakageCleared = "The board is loading again"
-
-    /// The unreadable repository clearing (06-history-undo.md ▸ Rules, ruled 2026-07-31: "the banner
-    /// clears when a later open or reload finds the repo readable").
-    ///
-    /// Stated as the regained capability, `readOnlyLockCleared`'s rule: what the user was waiting on
-    /// is history advancing again, not libgit2 changing its mind about a folder. It stays the
-    /// smaller claim of the two — nothing about editing the board was ever blocked by this
-    /// condition, which is precisely what its own row says.
-    static let repositoryUnreadableCleared = "History is recording again"
 }