# Authoring environment note

The sealed technical evidence reports a clean 432/432 result from controlled Windows/Linux validation runs.

During preparation of this presentation layer, a fresh full-suite attempt inside the outer Codex execution sandbox was intentionally not accepted as new authority evidence. The sandbox remaps the Python process ID while exposing a different PID namespace through `/proc`. Detached-child tests therefore cannot bind `subprocess.Popen.pid` to `/proc/<pid>` and report a false orphan even though the subreaper call succeeds.

This is detected by:

```bash
python scripts/process_environment_preflight.py
```

Run the complete process-hazard suite on a normal Windows host or in a Docker environment with a consistent PID namespace:

```bash
docker build -t agent-reliability-core .
docker run --rm --init agent-reliability-core python run_all.py --tests-only
```

This note does not convert the interrupted authoring-sandbox run into PASS evidence. The public portfolio numbers remain bound to the pre-existing sealed technical receipts listed in `technical_validation_summary.json`.
