Finish verify-framing on the repo's own agent discovery surfaces#147
Merged
Merged
Conversation
PR #144 migrated the downstream renderers, prompts, skill, Cursor rule, and slash command to verify-framing, but the repo's own top-level discovery surfaces still led with scan and lacked the anti-bypass mandate. Bring them in line (dogfooding) using #144's exact wording: - AGENTS.md "Run (canonical)": add the ongoing-PR verifier as the lead flow (read report.json.release_decision.decision first; verifier.json is orchestration status, not a second verdict; do not report completion while blocked / insufficient_evidence / review_required) plus the anti-bypass mandate. Keep scan as the first-time-setup path. - llms.txt: add verify to Quickstart and verifier.json / pr-comment.md to Outputs. - .well-known/agents-shipgate.json: add the verify command. - .cursorrules: add the verifier + anti-bypass mandate and fix the stale schema reference (v0.20 -> v0.22). - Regenerate llms-full.txt (AGENTS.md is a build source). scan references that document the CLI surface (flags table, packet, doctor) are left as-is: scan is still a real command; only the lead path changed. Full suite: 2338 passed, 4 skipped. No code changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Finishes the scan→verify migration on the repo's own agent discovery surfaces. #144 already migrated the downstream renderers, the
verify-agent-diffprompt, the Claude/Codex skills, the.cursor/rules/agents-shipgate.mdc, and the slash command — but the repo's own top surfaces (the ones an agent reads first) still led withscanand lacked the anti-bypass mandate. This is dogfooding: shipgate's own surfaces should say what it tells everyone else to do.Changes (all using #144's exact anti-bypass wording — no new vocabulary)
report.json.release_decision.decisionfirst, treatverifier.jsonas orchestration status (not a second verdict), and don't report completion whileblocked/insufficient_evidence/review_required. Plus the anti-bypass mandate.scanstays as the first-time-setup path.verifyadded to Quickstart;verifier.jsonandpr-comment.mdadded to Outputs.verifycommand added (outputs already listedverifier_json; gating signal alreadyrelease_decision.decision).v0.20→v0.22).test_llms_full_is_up_to_date).Deliberately not touched: the renderers and
verify-agent-diffprompt (already migrated by #144), andSKILL.md's body (already verify-aware via #144).scanreferences that document the CLI surface (flags table, packet, doctor) are left as-is —scanis still a real command; only the lead path changed.Verification
Full suite 2338 passed, 4 skipped, 0 failed (incl.
test_public_surface_contract,test_docs_links,test_init_agent_instructions,test_agent_instructions_renderers). No code changes.🤖 Generated with Claude Code