coulomb/activity-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

WP-0039-T03 done: both worker tokens minted in OpenBao

Browse source 
Founder-attended run of scripts/wp0039-seed-worker-tokens.sh succeeded. Both
paths were absent beforehand, then written and verified. Earlier failures
never started the script, because the relative path did not resolve.

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 18:02:39 +02:00
parent 482c868f2f
commit 9d55e1b421
1 changed files with 8 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/ACTIVITY-WP-0039-multi-worker-identity-and-token-custody.md
View file

@ -104,7 +104,7 @@ confirm the metered path for its catalog.
```task
id: ACTIVITY-WP-0039-T03
status: wait
status: done
priority: high
state_hub_task_id: "73d7f032-5ec3-550e-83ac-b9852c09ace4"
```
@ -144,6 +144,13 @@ 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.
The failed runs never started the script. The founder's terminal was outside the
repository, so the relative script path did not resolve, and no status file
was written. With the absolute path, the founder's run on 2026-09-23 succeeded.
warden reported no failure and no revocation warning. The status trace shows
both paths absent beforehand, then written, then verified with a 64-character
token field, then exit 0. No value was printed or logged.
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
lands.