docs: describe what this repository actually publishes - #8
Merged
Merged
Conversation
A full audit of the README against the published tree. The verify recipe could not work: it pinned --branch v0.7.0 while the catalog declares v0.11.0, so a reader following it would fail at the diff. It now reads the catalog's own .framework-ref, which is what the publish and Generated-only workflows read, so it cannot drift again. The README described only the guard-script story. Since 0.11.0 five of the packages here carry a policy's gate instead, wired at the events this client records, and nothing said so. This README is not the only hand-written file: SECURITY.md and the workflows are hand-written too, and the generated-only check regenerates none of them. Guard scripts are verbatim copies of their policy's source in the catalog, not of a framework source; only the adapter comes from the framework. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Signed-off-by: Claude <noreply@anthropic.com>
jothimani-rajendran
marked this pull request as ready for review
September 23, 2026 21:26
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
2 participants
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.
A full audit of the README against the tree this repository actually publishes. Four findings.
The verify recipe could not work. It pinned
--branch v0.7.0while the catalog declaresv0.11.0in.framework-ref, so building with v0.7.0 would not emit the 0.11.0 gate payload committed here and the documentedgit diff --exit-codewould fail. This is the exact failure modepublish.yml's own comment warns about, where a literal default "sat at v0.4.0 across three releases". The recipe now reads the catalog's.framework-ref, which is what both workflows read, so it cannot drift again.The README described only the guard-script story. Five packages here are enforced but are not guards and never touch
beforeShellExecution: block-invisible-unicode, block-wildcard-agent-permissions, java-security, pin-github-actions and scan-secrets. Theirhooks/hooks.jsonwirespreToolUseandstopagainstscripts/gate.json, judging the file a write would create and then re-reading what the turn left on disk. The old text presented a false dichotomy where anything not a guard was advisory.The fail-open claim was wrong for those five as well. Guards fail open without
python3andbash, and every guard's description says so. A gate that cannot reach a decision refuses rather than allowing something it never judged, and Cursor does not hold the turn's end, so a refusal atstopcomes back as a follow-up message once."The one hand-written file in this repository" is not true.
SECURITY.mdand the workflows under.github/are hand-written too, and the generated-only check regenerates none of them — it diffs afterchock plugin buildandchock marketplace build, which touch neither.Guard scripts are copies of the catalog's source, not the framework's. Verified:
chock-catalog/base/block-destructive-commands/implementations/block-destructive.shis byte-identical to the published copy here, while the framework repo's own copy differs. Only the adapter is framework-side.No generated file is touched, so
chock marketplace build --dist . --check --tree cursorand the regenerate-and-diff verification are unaffected.🤖 Generated with Claude Code
https://claude.ai/code/session_01CzNYfzP8ymU3r4JB9Sz8Ha
Generated by Claude Code