Why
Main promotion PR #555 at 68f28d2fad6f92f027953b608390882e5f6a0cba passes Typecheck, the complete unit/HttpAPI suite, Linux/Windows E2E, CodeQL, and local SpecGit 1.13.1 acceptance. GitHub SpecGit runs 33934130360 and 33935651980 nevertheless fail with worktree_mismatch before provider or PR checks. The delivery record binds a local linked-worktree label, while GitHub checks out the same branch and commit in a normal checkout with a different directory label. This blocks the authorized stable release.
Scope
Repair the execution-context mismatch for the existing #554/#555 delivery, retaining its issues, PR, branch identity, approved main policy, required checks, and accepted DAG runtime. Preserve the original dirty project checkout. Do not bypass branch protection, change required checks, or treat local acceptance as sufficient to merge.
Approach
Continue the exact reviewed branch from a standalone ordinary clone, then use specgit bind --issue <repair-number> --json to derive the real branch context from live Git and merge the repair issue into the existing delivery. SpecGit 1.13.1 does not let issue append new titles to a delivery that already has a PR, so this existing-delivery repair uses its supported bind command after issue creation. Preserve both Closes references in PR #555. Keep a separate record of the failed runs and verify the resulting context against the actual checkout, then repeat current-head CI and SpecGit acceptance. Runtime code, workflow checks, and approved policy stay byte-identical.
Acceptance
The final delivery record resolves to the real execution branch and checkout, preserves issue #554 and PR #555, and also binds this repair issue. Both local specgit finish --json and the current GitHub SpecGit Acceptance check pass on the repaired head. All other current-head checks pass without policy relaxation. The PR merges normally to main, and this repair issue is confirmed closed before the stable release is reported complete.
Why
Main promotion PR #555 at
68f28d2fad6f92f027953b608390882e5f6a0cbapasses Typecheck, the complete unit/HttpAPI suite, Linux/Windows E2E, CodeQL, and local SpecGit 1.13.1 acceptance. GitHub SpecGit runs 33934130360 and 33935651980 nevertheless fail withworktree_mismatchbefore provider or PR checks. The delivery record binds a local linked-worktree label, while GitHub checks out the same branch and commit in a normal checkout with a different directory label. This blocks the authorized stable release.Scope
Repair the execution-context mismatch for the existing #554/#555 delivery, retaining its issues, PR, branch identity, approved main policy, required checks, and accepted DAG runtime. Preserve the original dirty project checkout. Do not bypass branch protection, change required checks, or treat local acceptance as sufficient to merge.
Approach
Continue the exact reviewed branch from a standalone ordinary clone, then use
specgit bind --issue <repair-number> --jsonto derive the real branch context from live Git and merge the repair issue into the existing delivery. SpecGit 1.13.1 does not letissueappend new titles to a delivery that already has a PR, so this existing-delivery repair uses its supportedbindcommand after issue creation. Preserve bothClosesreferences in PR #555. Keep a separate record of the failed runs and verify the resulting context against the actual checkout, then repeat current-head CI and SpecGit acceptance. Runtime code, workflow checks, and approved policy stay byte-identical.Acceptance
The final delivery record resolves to the real execution branch and checkout, preserves issue #554 and PR #555, and also binds this repair issue. Both local
specgit finish --jsonand the current GitHub SpecGit Acceptance check pass on the repaired head. All other current-head checks pass without policy relaxation. The PR merges normally to main, and this repair issue is confirmed closed before the stable release is reported complete.