Repository navigation
[MEDIUM] fix(verifier): repairs from the 1.16.0 sync review, and the sync lever - #5
Conversation
It reproduces this merge's deterministic resolutions on a fresh branch and leaves only the judgment files conflicted. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 50b853e)
The live gate classifies every path a PR changes and refuses an unmapped one; the operator script is not a shipped surface. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 1c6b00c)
The script swallowed every merge failure, so a refusal to overwrite local edits still reached the unconditional manifest and provenance rewrites. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 1215fec)
…anch's policy The verifier refused any PR touching front-door.py, cloud-setup.sh or the cloud test as unmapped. The cloud test asserted a passive kit, which the branch has not shipped since October 5; it now asserts the installed skill matches the source byte for byte. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit ba74600)
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit d4efe19)
Claude Code 2.1.316 refuses a Write under any .claude/skills/ folder in dontAsk mode, so the creation case could not land the generated skill and the live gate failed. The port's setup cases already run this way for the same reason. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit 7bfdd73)
A Claude permission override on a shared recipe refused the routed run for Codex too, which needs no override. The check is now a function with its own test. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit c19fcc6)
…git diff base The live gate's sessions record the sync point three ways: a table cell, a labelled line, or the base of the git diff command the skill tells the reader to run. The check now takes the commit from that record and compares the whole token as a prefix of the expected commit, so a stale record fails even when prose names the new head, and a history line naming the old commit does not fail a correct update. A test drives the maintain assertion itself through both outcomes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…e sync-commit line The sync script no longer overwrites the fork's provenance files, refuses a tag already merged, and leaves a file one side deleted for a person; tests/sync-port-test.sh exercises it on a throwaway history and runs with the static invariants. The two formal fixture prompts ask for one line, "Sync commit: <full commit hash>", and the parser reads only that label, so words before it and prose do not count and records naming different commits count as none. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Live evidence: Open Pstack
|
… own git identity "Sync commit: <hash>^" named a different commit than it declared and passed. The record's value must now be a bare hash, optionally quoted, followed by nothing but punctuation or prose. The sync-port test sets user.name and user.email inside its throwaway repository, so the merge under test does not depend on the runner's git identity. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Live evidence: Open Pstack
|
Review record (MEDIUM tier)Who reviewed. Codex (gpt-6-astra), read-only through Pull request 3, round 1 (the fork's whole delta over port v1.16.0): REPAIR FIRST, seven findings. Four were in scope and are fixed here: the sync script swallowed every merge failure; the fork's operator scripts were unmapped in the verifier registry; the cloud test asserted a passive kit; FORK.md omitted the verifier's routing adaptation. Three predate this work (added in pull request 2 on October 19) and stay deferred, recorded on pull request 3 because Issues are disabled on this repository: the formal creation case can pass without a real mutation, routed evidence publishes the request hash as transcriptHash, and Rounds 2 to 6 on pull request 3, rounds 1 to 3 here. One or two findings each, each fixed with a test, until round 3 here returned READY on Live gate. On pull request 3, runs 4 and 5 passed all ten sessions in both harnesses ( Risk tier. MEDIUM. The affected surface is the verifier every fork PR runs and the next sync. The kit on the lanes is unchanged by this PR. Where the work lives: pushed to |
Merged and rolled outWhere the work lives: merged into VERIFIED after merge: all five lanes ( |
Why
Pull request 4 merged the 1.16.0 sync into
adam/releasewithout the repairs that pull request 3's Codex review and live-gate runs produced. Without them the live gate cannot pass on the kit now installed: Claude Code 2.1.316 refuses the generated skill's write in the formal creation case, and the verifier refuses any PR that touches the fork's operator scripts as unmapped.What changed
scripts/sync-port.shdoes the deterministic part of the next port sync; it and the other operator scripts are registered as non-runtime paths; the cloud test asserts the installed skill matches the source;FORK.mdpatch 7 records the verifier's routing adaptation.Scope
--native-modelduplicates the catalog's effort list.Blast Radius
The verifier every fork PR runs, and the next sync. The kit on the lanes is unchanged by this PR.
Verification
bun run static,bun run typecheck, the verifier's tests (209 pass) andtests/cloud-setup-test.sh(all checks pass) on the head, bun 1.4.4.Risk tier: MEDIUM.
Where the work lives: pushed to
adam/verifier-repairson this fork, not merged, nothing deploys.🤖 Generated with Claude Code