fix(lab): transport relaunch mints a fresh run dir
The first live firing of the relaunch (insurance gen-4, 2026-08-07) classified the transport death correctly, then hit main's own refusing-to-reuse-existing-run-directory guard: run dirs are append-only evidence, so pinning --run-id was wrong by the script's own doctrine. The relaunch now strips any --run-id and lets the re-execed parent mint a fresh timestamp; the dead attempt's partial artifacts stay behind as forensics. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011pfUVhNFTRvhYGXBwoKNj6
| Repository | eliziff/Beaver |
|---|---|
| Author | Eli Ziff <eliasziff@gmail.com> |
| Authored | |
| Parents | 6f65dd42 |
| Stats | 1 file changed , +16 , -8 |
| Part of | Evaluation harness: Beaver-CAN and LegalBench-RAG adapters |
Capture this commit into my fork
Download a Markdown prompt that tells Claude how to port this
exact commit into your working tree. Run it via
claude -p < capture-commit-093be19d.md
from inside the repo you want the change in.