Jesse.Markowitz/interactive-story
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Say where release evidence must be written, and what the crash took

Browse Source 
The M11 harness examples wrote to /tmp, which a reboot clears. One
100-turn campaign was lost that way at 97 turns. The examples now
write under $HOME, which is also the only place the browser harness
works. G.0 records what the run reached, that its evidence is gone,
and that M01 must be re-run before acceptance.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015aH3G73fEdh4qTQdZNUwty
This commit is contained in:
JesseMarkowitz
2026-09-07 14:19:27 -04:00
co-authored by Claude Opus 5
parent 144406cd48
commit fedb7144d0
2 changed files with 44 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DEVELOPMENT.md
+15 -5
View File
@@ -351,28 +351,38 @@ behind `planning/reports/M11-IMPLEMENTATION-REPORT.md`, and they live in the
repository so a reviewer can re-run them rather than take the report's word for
anything. None is part of the application and none is imported by it.
**Write their output somewhere durable, never `/tmp`.** `--out` is required on
every harness precisely so the location is a decision rather than a default, and
the examples below use `$HOME/m11-evidence`. A reboot clears `/tmp`, and a
long-run campaign is hours of evidence that cannot be reproduced by re-reading a
file — one run was lost exactly that way (see the addendum at §G.0 of the M11
report). Snap Firefox independently refuses a WebDriver file path under `/tmp`
and needs one under `$HOME`, so `$HOME` is the only location the browser harness
works from in any case.
```bash
cd backend
mkdir -p "$HOME/m11-evidence"
# The 100-turn release campaign (M01-M04): real narrator, genuine process
# restarts, every history operation. Hours, not minutes.
AIDND_TEST_ENDPOINT=https://<host>:<port>/v1 \
AIDND_TEST_MODEL=<model> AIDND_TEST_EMBED_MODEL=<embedding model> \
.venv/bin/python -m tools.m11_long_run --turns 100 --out /tmp/m01
.venv/bin/python -m tools.m11_long_run --turns 100 --out "$HOME/m11-evidence/m01"
# What that campaign is worth on a machine that has never seen it (I01-I07).
.venv/bin/python -m tools.m11_recovery --bundle /tmp/m01/bundle.json --out /tmp/m01
.venv/bin/python -m tools.m11_recovery --bundle "$HOME/m11-evidence/m01/bundle.json" --out "$HOME/m11-evidence/m01"
# The browser release regression and the accessibility measurements. Needs
# `frontend/dist` built and geckodriver on PATH.
.venv/bin/python -m tools.m11_browser --out /tmp/browser
.venv/bin/python -m tools.m11_browser --out "$HOME/m11-evidence/browser"
# A container with no network at all: the offline run and the packaging path.
.venv/bin/python -m tools.m11_offline --out /tmp/offline
.venv/bin/python -m tools.m11_offline --out "$HOME/m11-evidence/offline"
# The multi-character identity diagnostic (post-M8 finding D), and the run that
# proves its detectors fire.
.venv/bin/python -m tools.m11_identity --out /tmp/identity
.venv/bin/python -m tools.m11_identity --out "$HOME/m11-evidence/identity"
.venv/bin/python -m tools.m11_identity --scripted --inject
# The palette, against WCAG AA.