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
27 lines
1.5 KiB
XML
27 lines
1.5 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
|
|
<plist version="1.0">
|
|
<dict>
|
|
<key>com.apple.security.app-sandbox</key>
|
|
<true/>
|
|
<key>com.apple.security.files.user-selected.read-write</key>
|
|
<true/>
|
|
<key>com.apple.security.files.bookmarks.app-scope</key>
|
|
<true/>
|
|
<!-- **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*
|
|
apps, and there is one app (12-editions.md ▸ App-side state, re-ruled 2026-07-30). The
|
|
board registry and its Application Support peers home in the ordinary sandbox container
|
|
(`AppStateHome`), which the sandbox already scopes to this app alone. -->
|
|
</dict>
|
|
</plist>
|