From b6c583f411d867de326c4350dabe383bf168ae23 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sat, 18 Jul 2026 14:27:23 +0200 Subject: [PATCH] cutover runbook: deploy-key attach via warden lane, not founder UI clicks MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per ops-warden INTENT §7 / WARDEN-WP-0029 (founder directive 2026-07-18). Co-Authored-By: Claude Fable 5 --- integrations/executor-cutover-runbook.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/integrations/executor-cutover-runbook.md b/integrations/executor-cutover-runbook.md index a3281d0..3155f97 100644 --- a/integrations/executor-cutover-runbook.md +++ b/integrations/executor-cutover-runbook.md @@ -11,8 +11,12 @@ 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`. + railiance01. **Still at cutover** (agent-executable via the + `forgejo-admin-api-token` warden lane — founder act is one OIDC login, + per ops-warden INTENT §7, no UI clicks): fetch the public key from + `platform/workloads/agent-harness/forgejo-deploy-key` and POST it as a + write deploy key to `repos/coulomb/binky-control/keys` via + `warden access "forgejo admin pat" --exec -- …`. 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