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

feat: agent-harness tenant #1 instance manifest (HARNESS-WP-0001-T07)

Browse source 
Extend .kaizen/schedule.yml with harness fields for daily rhythm, weekly
mail intake, and weekly review-prep; add task files, onboarding handoff
doc, and cutover gate updates for BINKY-WP-0004-T06.
This commit is contained in:
tegwick 2026-07-18 11:07:12 +02:00
parent 04410c6269
commit efe4e55e6a
13 changed files with 186 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

17
integrations/executor-cutover-runbook.md
View file

@ -8,14 +8,15 @@
1. ~~DEC-2026-002 resolved~~ **done 2026-07-17**: single shared
`agent-harness` repo (ADR-001 there); prototype adopted as its seed.
2. **Lane 2 + Lane 3 Red-lane provisioning** done
(`integrations/executor-worker-secrets.md`): forgejo deploy key
(sandbox repo first, binky-control at cutover) and AppRole
`agent-harness-binky-mail`.
3. **Harness deployed on Railiance** (HARNESS-WP-0001-T06 in the
agent-harness repo) and one sandbox task executed there end-to-end
(same smoke as the 2026-07-17 workstation run, sandbox commit
e043f21). Tenant onboarding = HARNESS-WP-0001-T07.
2. ~~Lane 2 + Lane 3 Red-lane provisioning~~ **done 2026-07-17**
(`integrations/executor-worker-secrets.md`): forgejo deploy key on
`coulomb/executor-sandbox` + AppRole `agent-harness-binky-mail` on
railiance01. **Still at cutover:** attach the same deploy key write
access to `coulomb/binky-control`.
3. ~~Harness on Railiance + tenant onboarding~~ **done 2026-07-18**:
HARNESS-WP-0001-T06 (image + k8s + host smoke) and T07 (instance
manifest + three definition runs). See
`integrations/harness-tenant-onboarding.md`.
## Cutover steps