App Store distribution is not repository landing (v1.64.11.0)

CHANGELOG.md

@@ -7,6 +7,20 @@
 > completion state and remaining P0 gates. No version bump or release claim is
 > made here while that status holds.
 
+## [1.64.11.0] - 2026-07-24
+
+**Shipping to the App Store is not landing a PR.**
+**The branch gate no longer blocks store releases.**
+
+A release run on an Xcode project aborted at "you're on the base branch, ship from a feature branch" — without ever reaching the Apple journey. That gate belongs to repository landing (commit, review, PR, merge), which is a different release path than store distribution. The ship dispatcher now loads the Apple adapter FIRST for Apple targets, before any specialist preflight, and the adapter states it outright: an App Store or TestFlight ask proceeds from whatever branch you are on. A solo developer with a clean tree on main is the normal case, not an error.
+
+### Itemized changes
+
+### Changed
+
+- Ship dispatcher step 10: Apple targets read `references/APPLE-RELEASE.md` before any specialist preflight or repository gate; store distribution explicitly does not route through the branch/PR ceremony.
+- `references/APPLE-RELEASE.md` (ship tree): store distribution declared its own release path — branch/PR ceremony applies only to repository-landing asks; never abort an App Store release over branch topology.
+
 ## [1.64.10.0] - 2026-07-24
 
 **Marketing screenshots never required an API key.**

VERSION

@@ -1 +1 @@
-1.64.10.0
+1.64.11.0

package.json

@@ -1,6 +1,6 @@
 {
   "name": "gstack",
-  "version": "1.64.10.0",
+  "version": "1.64.11.0",
   "description": "GStack 2 \u2014 six portable Agent Skills with an optional host-neutral runtime.",
   "license": "MIT",
   "type": "module",

scripts/gstack2/generate-skill-tree.ts

@@ -202,7 +202,7 @@ function rootSkill(dispatcher: DispatcherDefinition): string {
   const supplemental = dispatcher.name === 'qa'
     ? '\n9. When `system-functional` is active, read `references/SYSTEM-FUNCTIONAL.md` completely and execute it alongside the selected preserved specialists.\n'
     : dispatcher.name === 'ship'
-      ? '\n9. Before push, PR creation/update, merge, deploy, rollback, release publication, or external notification, read `references/EXTERNAL-EFFECTS.md` and execute the action through its durable state wrapper.\n10. When the release target is an Apple platform app (an `.xcodeproj`, `.xcworkspace`, or app-product Swift package is present), read `references/APPLE-RELEASE.md` before release preparation and follow its App Store journey end to end.\n'
+      ? '\n9. Before push, PR creation/update, merge, deploy, rollback, release publication, or external notification, read `references/EXTERNAL-EFFECTS.md` and execute the action through its durable state wrapper.\n10. When the release target is an Apple platform app (an `.xcodeproj`, `.xcworkspace`, or app-product Swift package is present), read `references/APPLE-RELEASE.md` FIRST — before any specialist preflight or repository gate — and follow its App Store journey end to end. An App Store or TestFlight ask is store distribution, not repository landing: the specialist branch/PR ceremony does not gate it, and a clean tree on the base branch is a valid state to archive and upload from.\n'
       : dispatcher.name === 'plan'
         ? '\n9. Classify the Scale header line from the Build scale section before any questioning begins. Every planning specialist applies its proportional-planning judgment port to that scale.\n'
         : '';
@@ -638,7 +638,7 @@ function appleReleaseContract(): string {
   return `${GENERATED}
 # Apple App Store release
 
-Applies when the ship target is an Apple platform app: the repository contains an \`.xcodeproj\` or \`.xcworkspace\`, or a Swift package with an app product. This adapter extends the preserved ship judgment to the App Store journey end to end; it replaces no gate, and every upload or submission remains an external effect executed through \`references/EXTERNAL-EFFECTS.md\`.
+Applies when the ship target is an Apple platform app: the repository contains an \`.xcodeproj\` or \`.xcworkspace\`, or a Swift package with an app product. Read this BEFORE any specialist preflight. This adapter extends the preserved ship judgment to the App Store journey end to end, and every upload or submission remains an external effect executed through \`references/EXTERNAL-EFFECTS.md\` — but store distribution is its own release path, not repository landing: the preserved specialist's branch/PR ceremony (feature-branch gate, commit-review-PR pipeline, merge queue) applies only when the user asked to land repository changes. A user shipping to the App Store or TestFlight proceeds through this adapter from whatever branch they are on; a clean working tree on the base branch is a normal and valid state to archive and upload from. Never abort an App Store release over branch topology.
 
 One tool runs the entire release: machine-level fastlane — \`produce\` (app record and bundle ID), \`cert\` and \`sigh\` (signing), \`gym\` (archive and signed export), \`pilot\` (TestFlight), \`deliver\` (metadata, screenshots, Submit for Review), \`frameit\` (device frames). Install it when missing (\`brew install fastlane\`) with a one-line announcement, not a question — the release authorization covers machine-tool installs. Never install additional App Store CLI tools, and never mention API keys, \`.p8\` files, sessions, or any credential format to the user; they paid US$99 and want to ship, and the release itself adds no new dependency to the user's project.