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/Changes/ChangeNarration.swift

@@ -64,15 +64,15 @@ public struct ChangeNarrationRequest: Sendable {
     public let snapshot: BoardModel?
 
     /// **The last-committed half** of the "last-committed vs. current" diff — supplied by the caller
-    /// by contract; the narrator itself never reads this from anywhere. The git stack supplied it from
-    /// HEAD's tree (`GitHeadSnapshot`), the former git-backed supplier; the journal will supply it from
-    /// memory/snapshots.
+    /// by contract; the narrator itself never reads this from anywhere. The retired git substrate
+    /// materialized it from HEAD's tree; the journal will supply it from memory/snapshots.
     ///
-    /// `nil` when the caller has nothing to diff against — the git stack's case was an unborn HEAD
-    /// (where `isRootCommit` already says everything) or a HEAD whose tree did not load as a board. The
-    /// git stack read it from the repository rather than carrying it forward from the last commit the
-    /// app made, because the app is not the only writer and because launch catch-up has no carried
-    /// value to offer: see `GitHeadSnapshot` for the whole of that argument.
+    /// `nil` when the caller has nothing to diff against — a first window (where `isRootCommit`
+    /// already says everything), or a stored state that did not load as a board.
+    ///
+    /// **A supplier reads it rather than carrying it forward** from the last window it described, and
+    /// deliberately: the app is not the only writer, and catch-up after a period of not watching has
+    /// no carried value to offer.
     public let previousSnapshot: BoardModel?
 
     /// **The board-root `CLAUDE.md` as it now reads**, when this commit touches it — the one
@@ -92,8 +92,7 @@ public struct ChangeNarrationRequest: Sendable {
     /// comments' own `created`, folder name on ties" (06 ▸ Rules ▸ Auto-commit, blessed 2026-07-31),
     /// and `created` lives in a comment's own `index.md` because comments are window-scoped and the
     /// board snapshot never carries them (01-storage-format.md § Enhanced schema). The flush resolves
-    /// it once (`GitAutoCommitter.commentTimestamps(for:boardRoot:)`) and the engine stays a pure
-    /// function of values.
+    /// it once, off disk, and the engine stays a pure function of values.
     ///
     /// **Missing is normal, not a defect.** A comment whose folder left the tree in this very commit
     /// (the close purge), one whose `index.md` does not parse, one written by hand with no `created`
@@ -141,7 +140,7 @@ public protocol ChangeNarrating: Sendable {
 
 // MARK: - The wired composer
 
-/// **The semantic composer**, and the committer's default (`GitAutoCommitter.composer`).
+/// **The semantic composer**, and the seam's default.
 ///
 /// A one-line conformance over `ChangeNarrator`, deliberately: the vocabulary is worth a file of
 /// its own and nothing about it should have to know that a protocol exists. The type stays because