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/UI/Card/CommentEditSession.swift

@@ -20,7 +20,7 @@ import Observation
 /// Added, and the only genuinely new thing in this type: **session-start bytes**. The body has no
 /// Cancel — leaving Edit is a commit, and ⌘Z in the editor is the text view's own undo — while an
 /// inline comment edit has a Cancel button and an Escape that means it. 13-native-undo.md forbids
-/// byte capture *on the undo stack* in every tier, and this is not that: the capture is a live
+/// byte capture *on the undo stack* anywhere, and this is not that: the capture is a live
 /// buffer's, held for the length of one session, discarded when the session ends, and never
 /// registered anywhere. `BoardStoreComments`' own note says so — "an inline edit's revert is its
 /// *session*'s … which is a live buffer, not a stack entry".