`python -m venv` spawning fine and exiting non-zero had no honest code. The tools venv
bootstrap (next commit) is the first thing that can hit it, so the code lands before the
error path that raises it rather than being retrofitted onto one.
None of the three candidates worked. PD-NET-011 is Area::Net, and run::exit_for derives
the exit code from the area — so `tools sync || wait-for-network && retry` would loop
forever on a stripped Python, and both locales' shipped copy is explicitly about
downloading. PD-HLT-001 tells the user to re-sync the tools environment, which is the
operation that just failed. PD-INT-001 is "a PipDock bug", and a Python built without the
venv module is not one. Area::Hlt already maps to exit 1, which is right.
All eight places from CLAUDE.md in one commit, because seven of them are a broken build:
the variant, Code::ALL, both count assertions (32 -> 33), classifier_corpus's
internally_raised table without which the no-code-without-a-fixture gate fails, en+vi copy
under the 90-char cap, regenerated codes.json and bindings, and the catalog doc. Three
goldens re-blessed — Code plus the two schemas that embed it, StepResult and
ExecutionSummary. ResolutionReport does not embed it and did not move.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>