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
This commit is contained in:
@@ -522,9 +522,10 @@ struct EchoLedgerStoreTests {
|
||||
/// **The Writer's heal operations drop heal-marked receipts** (06-history-undo.md ▸ Commit messages,
|
||||
/// ruled 2026-07-29: "attribution machinery like the author split, never message tagging").
|
||||
///
|
||||
/// **Inert in base beyond the ledger itself**: nothing here reads the flag and nothing renders it —
|
||||
/// it is what pro-m1's committer will read to split a heal's paths into their own commit, and these
|
||||
/// tests pin the seam it will read from, not a committer that does not exist yet.
|
||||
/// **Inert beyond the ledger itself**: nothing here reads the flag and nothing renders it — it is
|
||||
/// what whatever records history next (the foreign-change journal, `strategy/01-git-excision.md` ▸
|
||||
/// Successors) would read to split a heal's paths out from a user's own, and these tests pin the
|
||||
/// seam it will read from, not a consumer that does not exist yet.
|
||||
@Suite("EchoLedger — heal-marked receipts")
|
||||
struct EchoLedgerHealMarkTests {
|
||||
|
||||
|
||||
Reference in New Issue
Block a user