Dogfooding during the command-generation extraction found that grouped workspace pytest runs on Windows with CPython 3.13 can intermittently terminate with access violations inside repeated static proof paths (observed in ast.walk/jsonschema/json.loads frames). The same proof commands pass as standalone processes, and the grouped tests pass when run with PYTHONMALLOC=malloc.\n\nObserved while running make test-workspace locally on Windows:\n- Access violation during repeated calls into scripts/check/check_generated_command_packages.py static proof helpers.\n- Standalone uv run python scripts/check/check_generated_command_packages.py passed.\n- make test-workspace passed with PYTHONMALLOC=malloc after product/test fixes.\n\nPotential fixes to evaluate:\n- Isolate heavyweight proof-runner tests in subprocesses instead of repeated in-process imports.\n- Cache or reduce repeated AST/schema validation work inside static proof helpers.\n- Document or set a Windows-local test environment workaround only if isolation is not enough.\n\nThis is not blocking the extraction PR, but it is actionable test/proof robustness debt.
Dogfooding during the command-generation extraction found that grouped workspace pytest runs on Windows with CPython 3.13 can intermittently terminate with access violations inside repeated static proof paths (observed in ast.walk/jsonschema/json.loads frames). The same proof commands pass as standalone processes, and the grouped tests pass when run with PYTHONMALLOC=malloc.\n\nObserved while running make test-workspace locally on Windows:\n- Access violation during repeated calls into scripts/check/check_generated_command_packages.py static proof helpers.\n- Standalone uv run python scripts/check/check_generated_command_packages.py passed.\n- make test-workspace passed with PYTHONMALLOC=malloc after product/test fixes.\n\nPotential fixes to evaluate:\n- Isolate heavyweight proof-runner tests in subprocesses instead of repeated in-process imports.\n- Cache or reduce repeated AST/schema validation work inside static proof helpers.\n- Document or set a Windows-local test environment workaround only if isolation is not enough.\n\nThis is not blocking the extraction PR, but it is actionable test/proof robustness debt.