Release 0.11.1

[jothimani-rajendran]

What

Release 0.11.1: the version moves to 0.11.1 in pyproject.toml, CITATION.cff, action.yml, docs/installation.md and docs/reviewer-evidence.md. The Unreleased changelog section becomes 0.11.1 — The plugins page tells a gate from a guard, and the social preview is regenerated for the new version string. It's the same file set as the 0.11.0 release, plus the reviewer-evidence pin, which #161 moved onto the current version.

What ships:

• The generated plugins page tells a gate from a guard (plugin: the generated plugins page tells a gate from a guard #162). PLUGINS.md in every distribution repo misdescribed five of its fourteen enforcing packages as shell-command guards. The paragraph is now derived from each package's published hooks.
• The documentation audit (docs: correct what chock writes, grades and enforces #161). The only user-visible code change there is one line of chock plugin build's summary output for the Cursor format.

Why a patch

Under the emitter-stability promise in CONTRIBUTING.md, a patch means tests/test_emitter_stability.py passes against the committed golden, which it does. That makes chock sync's compile output byte-identical, so an adopter who bumps rewrites nothing. The source changes since v0.11.0 are the plugins-page renderer, two comments and that one summary line.

PLUGINS.md output does change, but it isn't something chock sync adopters commit. The distribution repos rebuild it only when the catalog moves its .framework-ref. Their generated-only check builds with that same pin, so the committed tree and the verifying build stay on one version.

After merge

1. Tag v0.11.1 on the merge commit. The release workflow checks the tag against pyproject.toml, and they now match.
2. Adopt v0.11.1 in chock-catalog with tools/adopt_framework.py v0.11.1.
3. Run Publish in the four plugin repos with the framework ref left on auto. That is what carries the corrected PLUGINS.md to them.

Definition of done

• chock check → 0 errors, 0 warnings, 0 infos (release consistency: pyproject and the top changelog heading both read 0.11.1)
• chock check --only matrix passes
• chock sync --repo . --check clean
• chock check --only verify clean
• Registry rescanned; no stale entries
• pytest -q green (1463 passed, 2 skipped), including tests/test_emitter_stability.py
• pytest acceptance/ — not applicable; packaging, init, add and hook installation are unchanged since v0.11.0
• Existing artifacts migrated — none needed for a patch
• Touched manifests — none
• ruff check . and ruff format --check . clean

Also verified: docs/assets/gen_brand_assets.py --check is current after regeneration, and the docs/figures/make_*.py output is unchanged.

Claims

• No surface is described as enforcing more than it installs. Both changes in this release narrow claims toward what the code does.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CzNYfzP8ymU3r4JB9Sz8Ha

---

Generated by Claude Code