The owner named the KAB project "Cymbal Bank" (5a2da83b-...; voyage
ENG-CYMBAL-001) as one of Shakedown's own. There, the runner continues a
review point only on a critic pass with no failed step (plan 5b). Every
other project still waits for a person.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- shakedown_lib: runs F01 -> F02 -> F03 for one engagement on KAB with no
personal token. Signs in as the kab-automation client (client credentials,
provisioned by Stellwerk from crucible-platform-deploy) and renews the token
itself.
- Each stage checks its workflow id against the registered sub-agent name,
builds inputs from the case and upstream stages, starts the run, follows it
and judges it with cp1-agents evaluate_case.py.
- Gates (plan 5b): in config/runner.yaml gate_projects only, continue on a
critic pass with no failed step and a note saying the system decided.
Never on a fail. Elsewhere, wait for a person and record who decided.
gate_projects is empty for now.
- Ledger per voyage run, with --resume; nothing secret is written.
- Cymbal voyage ENG-CYMBAL-001; workflow registry; Dockerfile and an
unapplied Job template; 15 tests against a fake KAB.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>