DEC-2026-002 resolved: agent-harness (single shared runtime)

- DecisionQueue: moved to resolved log with rescoped outcome (three-layer
  model; binky-control = tenant #1); hub decision resolved
- Secret lanes doc: identifiers renamed executor-worker → agent-harness
  before any provisioning happens
- Cutover runbook + WP-0004-T06: gate 1 done; deployment gate now points
  at HARNESS-WP-0001-T06/T07 in the agent-harness repo

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

integrations/executor-cutover-runbook.md

@@ -6,15 +6,16 @@
 
 ## Gates (in order)
 
-1. **DEC-2026-002 resolved** (DecisionQueue.md) — executor worker home.
+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
-   `executor-worker-binky-mail`.
-3. **Worker deployed on Railiance** (repo `~/executor-worker` prototype;
-   deployment per activity-core's Railiance conventions) and one sandbox
-   task executed there end-to-end (same smoke as the 2026-07-17
-   workstation run, sandbox commit e043f21).
+   `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.
 
 ## Cutover steps