Runner: run a voyage remotely as the kab-automation identity

- 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>
This commit is contained in:
2026-11-16 05:08:31 +00:00
parent 07060dbb37
commit 099f9a87e8
22 changed files with 1546 additions and 1 deletions

13
config/runner.yaml Normal file
View File

@@ -0,0 +1,13 @@
# Shakedown runner settings. Committed, so every change is reviewed; the environment can't widen them.
# The KAB projects whose review points the runner may decide itself (plan §5b): only Shakedown's own use-case
# projects. In any other project it waits for a person. It continues a gate only on a critic `pass` with no failed
# step (shakedown_lib/gate.py), never on a `fail`, and its note says the system decided.
#
# Empty until the owner names the projects. For the Cymbal voyage that would be the "Cymbal Bank" project:
# - 5a2da83b-cf1e-48d8-9b07-0a84f5e5f026
gate_projects: []
poll_seconds: 30
stage_timeout_minutes: 360 # one stage, start to package
person_wait_hours: 24 # the workflows' own review timeout (hitl.timeout_hours)