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

KanbanTests/CardSessionUndoTests.swift

@@ -21,7 +21,7 @@ import Testing
 /// **A provider that retires every step on arrival** — the minimal fake `HistoryProviding.backedContent`'s
 /// own doc names ("a substrate that keeps no steps... and a test fake's"). `register(_:)` runs the
 /// step's retirement immediately and keeps nothing, which is what makes "purge rides the close flush"
-/// true over such a substrate with no tier check anywhere in the call path.
+/// true over such a substrate with no substrate check anywhere in the call path.
 @MainActor
 private final class NoBackingHistoryProvider: HistoryProviding {
     var canUndo = false
@@ -843,8 +843,9 @@ struct CardSessionPurgeTests {
         let window = try makeWindow(fixture)
         window.comments.reload()
         // A substrate that keeps no steps drops every registration and retires it on the way past —
-        // which is what makes "purge rides the close flush" true structurally, with no tier check at
-        // any call site. `history` is weak, so the fake is held locally for the assertion's duration.
+        // which is what makes "purge rides the close flush" true structurally, with no substrate
+        // check at any call site. `history` is weak, so the fake is held locally for the assertion's
+        // duration.
         let noBackingProvider = NoBackingHistoryProvider()
         window.store.history = noBackingProvider