Adopt chock v0.9.0 and agentseam 0.3.0 - #74
Merged
Merged
Conversation
`.framework-ref` moves v0.8.0 -> v0.9.0 and `requirements/chock.in` follows chock's pyproject at that tag (agentseam 0.2.1 -> 0.3.0); `requirements/chock.txt` is regenerated by pip-compile with hashes for the 0.3.0 wheel. Everything else is `chock sync --repo .` on the 0.9.0 release wheel, committed as it came out: - `.chock/compiled/<id>/pre-tool-use/` and `stop/` for the four policies that declare `on: [commit, tool_use]` -- the write-path gate and the turn-end backstop 0.9.0 emits for content policies, which 0.8.0 compiled to nothing. - The ten `.chock/bin/` runtimes and `gate.py`, built with agentseam 0.3.0 and refusing rather than falling through when the judge crashes. - This repo's own vendor configs gain the new entries (`.claude/settings.json` gets `Stop` beside `PreToolUse`; gemini, codex, devin, tabnine and `.agents/hooks.json` get theirs). - `.chock/coverage.json`: for those four policies the claude and gemini cells move from `enforced-at-commit` to `best-effort` with a stated basis, because the write-path hook is now installed and credited at the word its evidence can back. The commit hook underneath is unchanged. `stop` credits nothing. - `chock.lock` follows the manifests. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Jothi Mani Rajendran <250249270+jothimani-rajendran@users.noreply.github.com>
jothimani-rajendran
marked this pull request as ready for review
September 20, 2026 15:47
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
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
Step three of the release train (agentseam 0.3.0 → chock 0.9.0 → the adopters).
.framework-refmovesv0.8.0→v0.9.0;requirements/chock.infollows chock'spyproject.tomlat that tag (agentseam0.2.1→0.3.0), andrequirements/chock.txtis regenerated by pip-compile with hashes for the 0.3.0 wheel, header kept in the form the other locks underrequirements/carry. Everything else in the diff ischock sync --repo .on the 0.9.0 release wheel, committed as it came out: the four policies that declareon: [commit, tool_use]gainpre-tool-use/andstop/compiled artifacts (the write-path gate and turn-end backstop 0.9.0 emits for content policies, which 0.8.0 compiled to nothing); the ten.chock/bin/runtimes andgate.pyare rebuilt with agentseam 0.3.0 and now refuse rather than fall through when the judge crashes; this repo's own vendor configs gain the new entries (.claude/settings.jsongetsStopbesidePreToolUse; gemini, codex, devin, tabnine and.agents/hooks.jsonget theirs);chock.lockfollows. One derived change in a published word: in.chock/coverage.jsonthe claude and gemini cells for those four policies move fromenforced-at-committobest-effortwith a stated basis, because the write-path hook is now installed and credited at the word its evidence can back — the commit hook underneath is unchanged, andstopcredits nothing. No figure script reads chock state, sodocs/figures/is untouched. Nothing under.github/workflows/changed: thepoliciesjob reads the pin from.framework-ref, which is the point of that file.Definition of done
python -m ruff check .andpython -m ruff format --check .clean —All checks passed!,240 files already formattedpython -m pytest -qgreen; new checks have attack + ordinary-data tests —407 passed, 1 skipped; no check addedspec/attestation/v0.1/schema.jsonand its example stay in sync — no schema changechock checkandchock sync --repo . --checkclean, if.agents/policies/changed — both clean on chock 0.9.0 ([PASS] All checks passed.,Compiled artifacts match their manifests.);.agents/policies/itself is unchanged, the compiled output under.chock/is what movedClaims
re-derivableunless it actually recomputes from the subject plus its recorded configuration and carries aninputHash. A row that could not be measured saysNotAvailable,Error, orNotApplicableand why. — no row or measurement changes in this PR; it touches the engine pin and its generated output only🤖 Generated with Claude Code