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/CommentWriteTests.swift

@@ -796,7 +796,7 @@ struct CommentUndoTests {
         #expect(store.editComment(ItemID(rawValue: CommentIdent.one), inCard: cardID, body: "revised\n"))
         store.purgeCommentTrash(inCard: cardID)
 
-        #expect(!history.canUndo, "no byte capture in any tier — 13's rule")
+        #expect(!history.canUndo, "no byte capture on the undo stack, anywhere — 13's rule")
         // The gate did not make the purge inert: nothing on the stack names this entry, so it goes —
         // per entry, and still without a step to show for it.
         #expect(!fixture.exists("\(card)/comments/.trash/\(CommentIdent.two)"))