Leave Python bytecode out of a pack's lockfile hash

[jothimani-rajendran]

What

In the first Copilot run of the java-security agent kit on Windows, chock check reported java-security: hash mismatch in a workspace where nobody had edited the pack.

Cause: a script gate runs its implementation out of .agents/policies/<id>/implementations/. Python therefore writes __pycache__/ into the pack on the first gate run, per interpreter version, and more of it as more rules are imported. lock.compute_pack_hash hashed every file under the pack, bytecode included, so the lockfile ended up depending on which gates had run, on which Python.

Reproduced:

1. Set up a fresh agent-kit workspace and run kit.py doctor once. That leaves 171 .pyc files in the pack.
2. The same workspace then fails chock check --only verify under 0.11.3's hashing, and passes with this change.

Fix: the pack hash leaves out __pycache__/, .pyc and .pyo, which plugin/build.py, plugin/gate_package.py and scaffold/skills.py already skip. A lockfile written while bytecode sat in a pack is reported once, and chock sync rewrites it (changelog says so).

Definition of done

• chock check → 0 errors, 0 warnings, 0 infos
• chock check --only matrix passes; matrix unchanged
• chock sync --repo . --check clean
• chock check --only verify clean (chock's own lockfile unchanged)
• Registry rescanned; no stale entries
• pytest: new tests/test_lock_ignores_bytecode.py. Bytecode leaves the hash alone (fails on main); a source change still changes it. test_vendored_guardrails.py passes.
• Acceptance: no packaging, init, add or hook change
• Existing artifacts migrated: none needed; chock's own lock hash is unchanged
• Touched manifests: none; changelog Unreleased entry
• ruff check . and ruff format --check . clean

Claims

• No surface or claim changes.

Meant to ship in 0.11.4 alongside #168.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CzNYfzP8ymU3r4JB9Sz8Ha

---

Generated by Claude Code