The prose catches up with the one-version app — tier qualifiers retired, the entitlement comment carried over

The excision's follow-up sweep: present-tense prose that still implied an edition axis now reads
correctly under one version ("in every tier" clauses dropped or turned substrate-shaped, the
announcer's "every free-tier bracket today" is "every bracket today" — nothing passes a phrase),
and forward-looking promises pinned to the mooted pro-m1/pro-m2 milestones now name the thing
itself (the change narrator in Kanban/Changes/, the foreign-change journal successor) or fall to
past tense. Kanban.entitlements' network-client comment sheds its "dormant until Pro ships"
framing for the pivot's own reasoning: the key stays because the sync capability to come needs
it regardless. Untouched on purpose: the storage layer's coerce/tolerate/refuse tiers, the
chooser's bundled/user/keyless tiers, verbatim design-doc quotations, and genuine past-tense
record. One dangling reference repaired en route: EndToEndVerification.md cited the long-renamed
InertGitTests. Comment-only throughout; 2,686 unit tests green, unchanged.

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

Kanban/History/HistoryProviding.swift

@@ -258,13 +258,13 @@ public struct HistoryStep {
 /// "Two levels: one stack per board, one per open card window" (13-native-undo.md ▸ Rules, re-ruled
 /// 2026-07-31). The **board** stack is the session's, shared by board surfaces, and its
 /// implementation is what this protocol is a seam for. A **card window** owns a second stack for its
-/// own gestures — always a `NativeHistoryProvider`, in either tier, because a window's fine-grained
-/// inverses are values-based whatever the board's substrate is (`CardWindowUndo`); what reaches this
+/// own gestures — always a `NativeHistoryProvider`, because a window's fine-grained inverses are
+/// values-based whatever the board's substrate is (`CardWindowUndo`); what reaches this
 /// 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 — **always `NativeHistoryProvider`** now (two step stacks over the
-/// inverses registered at the Writer boundary), on every board, in every tier
+/// inverses registered at the Writer boundary), on every board there is
 /// (`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
@@ -286,7 +286,7 @@ public struct HistoryStep {
 ///   `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
-///   (13-native-undo.md ▸ Undo routing, tier-independent) — `BoardUndoRouting`.
+///   (13-native-undo.md ▸ Undo routing) — `BoardUndoRouting`.
 ///
 /// ### One obligation every implementation shares: retire what you let go of
 ///