rzen/lanework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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:
rzen
2026-08-08 13:40:13 -04:00
parent df986566e5
commit 2d919b8131
21 changed files with 58 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Kanban/Kanban.entitlements
+8 -8
View File
@@ -8,14 +8,14 @@
<true/>
<key>com.apple.security.files.bookmarks.app-scope</key>
<true/>
<!-- Remotes: pull/push and auth (07-sync-collab.md), which only the git provider ever makes.
**Declared now, dormant until Pro ships** — the one-app collapse traded "the free app
provably has no network access" for "no network use until you subscribe", with eyes open
(12-editions.md ▸ The target, re-ruled 2026-07-30). It sits in the shipped entitlements
from the start because a key added later is a new provisioning profile and a new review
surface for what is meant to be a StoreKit-only change. No `keychain-access-groups`
alongside it: a group shares items *between* apps, and there is one app — Pro's
credentials go to the sandbox's own keychain, which needs no key at all. -->
<!-- **Declared now and exercised by nothing.** Nothing in the shipped app opens a socket: the
git provider that would have used this key is excised (strategy/01-git-excision.md), and
the ops-based sync capability that will is a design pass still to come. The key stays
because that capability needs it regardless (12-editions.md ▸ PIVOT 2026-08-08), and
because a key added later is a new provisioning profile and a new review surface — cheaper
to carry from the start than to introduce. No `keychain-access-groups` alongside it: a
group shares items *between* apps, and there is one app, so whatever credentials sync
eventually holds go to the sandbox's own keychain, which needs no key at all. -->
<key>com.apple.security.network.client</key>
<true/>
<!-- No `com.apple.security.application-groups`: a group exists to share a container *between*