[Deep-Sixed]

Work package: 0.3.1 patch release, step 1 of 2. Branched from main at 7a01888 (the #9 merge). This releases #9's four input and state-boundary fixes as 0.3.1. It keeps contract evidence-v3.2, following the decision recorded on #9.

file	change
CHANGELOG.md	New ## 0.3.1 — contract evidence-v3.2 entry: the four #9 fixes, why the contract is unchanged, the two edge-case trees whose state IDs move, and that the installer pin follows separately.
pyproject.toml	version = "0.3.1"
skills/verification-ladder/bin/verify.py	VERSION = "0.3.1". No other code change.

Why records written by 0.3.0 still compose: verifier_status compares only the compatibility contract, never the build ("two builds of the same contract compose"), and the contract is unchanged.

What this does not do: move the installer pin. install-ladder.sh refuses a pin that isn't already on main, so step 2 (#11) moves PIN and CHECKER_SHA to this PR's merge commit, like #7 did for 0.3.0. Until then, test_the_pin_installs_the_hardened_release correctly still asserts the pinned runtime reports 0.3.0.

Verification

On 3097968, against a baseline captured on main at 7a01888 (baseline gates green: lint, 420 passed / 1 skipped):

• Local: Ruff clean; 420 passed, 1 skipped; drift: false.
• Negative controls, in isolated copies with bytecode off:
  • with the CHANGELOG entry removed, test_the_release_notes_name_the_contract_this_verifier_applies fails;
  • with the pyproject bump reverted, test_the_version_tracks_the_package_it_ships_with fails.
• Judgment rungs attested: task, diff, self-review, requirements, architecture, fresh-review.
• CI: push run 36140570331 (attempt 1, head 3097968): lint, tests-py311, tests-py314 PASS, imported with import-ci. The pull_request run 36140604149 is also green.
• Compose (state sha256:483f9ae5…a387f5): 0 blocked required gates, 0 stale, STATE MATCH TRUE, CLEAN CLIMB TRUE, READY FOR HUMAN GATE TRUE.

🤖 Generated with Claude Code

https://claude.ai/code/session_016m6di8xFVdwwq949mJx9U1

---

Generated by Claude Code