WP-0039-T03: document status trace and first failed run
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 4s
Build and Publish Container Image / build-and-push (push) Successful in 11s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 151606@bnt-lap001
Assistant-Session: 3c0a4ad5-bb8b-4bf7-b9f0-fa5f29204e48
This commit is contained in:
tegwick 2026-09-23 17:56:52 +02:00
parent ebb12b00c7
commit 482c868f2f

View file

@ -133,10 +133,17 @@ on stdin. The founder runs it in their own terminal:
```bash ```bash
BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200 \ BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200 \
WP0039_STATUS=$HOME/.local/state/wp0039-seed.status \
warden access openbao-platform-admin-login --exec -- \ warden access openbao-platform-admin-login --exec -- \
sh scripts/wp0039-seed-worker-tokens.sh sh scripts/wp0039-seed-worker-tokens.sh
``` ```
The first founder run on 2026-09-23 failed closed ("returned a failure or
unexpected output"). warden discards the child's output, so the script now
writes a non-secret step trace to `WP0039_STATUS`. The trace holds the failing
step, the exit code, and bao's error text, never the value. The script was
tested against a stub `bao`: silent, and a no-op on rerun.
Read warden's printed line rather than its exit code (orientation section 5). Read warden's printed line rather than its exit code (orientation section 5).
Minting does not depend on T02, but ESO cannot read the paths until the policy Minting does not depend on T02, but ESO cannot read the paths until the policy
lands. lands.