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

docs: mark agent-harness Red-lane secrets Lanes 2–3 provisioned

Browse source 
Forgejo sandbox deploy key and mail AppRole delivered to railiance01;
checkboxes closed with host path and catalog ids (no secret values).
This commit is contained in:
tegwick 2026-07-17 23:57:56 +02:00
parent 7c5e644d6f
commit 11bba92b84
1 changed files with 14 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

18
integrations/executor-worker-secrets.md
View file

@ -76,11 +76,21 @@ config `integrations/mailbox-binky-company.yml`, reports to
## Founder Red-lane summary
- [ ] Lane 2: forgejo deploy key (generate, register on sandbox repo, store
in OpenBao, catalog entry)
- [ ] Lane 3: AppRole `agent-harness-binky-mail` (create role, deliver
role_id/secret_id to Railiance, catalog entry)
- [x] Lane 2: forgejo deploy key (generate, register on sandbox repo, store
in OpenBao, catalog entry) — **done 2026-07-17** on railiance01;
write deploy key on `coulomb/executor-sandbox`; catalog
`agent-harness-forgejo-deploy`. Add `binky-control` deploy key at
cutover only.
- [x] Lane 3: AppRole `agent-harness-binky-mail` (create role, deliver
role_id/secret_id to Railiance, catalog entry) — **done 2026-07-17**;
host dir `~/.local/agent-harness/approle-binky-mail`; catalog
`agent-harness-binky-mail-approle`. Positive IMAP field presence +
negative sibling-path deny verified (no values logged).
- [x] Lane 1: nothing to do — reuse confirmed
T04 (worker MVP) can start with Lane 1 alone plus a workstation-side dry
run; Lanes 2–3 gate unattended operation, not development.
Host env helper (railiance01): `source ~/.local/agent-harness/env` sets
`BAO_ADDR`, `EXECUTOR_APPROLE_DIR`, and `PATH` for `bao`. Git SSH alias:
`forgejo-agent-harness` → forgejo.coulomb.social:30022 with the deploy key.