binky-control/integrations/executor-cutover-runbook.md
tegwick 2fbbf9fc76
Some checks failed
Work Records / validate (push) Has been cancelled
BINKY-WP-0006: close with three clean railiance mail cycles
Host LLM_CONNECT_URL discovery uses ClusterIP when DNS is unreachable;
mail path fails hard if triage fails. Mark T06 done and workplan finished;
update residual docs (OperatingRhythm, cutover runbook, llm-rhythm).
2026-07-22 10:28:11 +02:00

63 lines
2.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Executor Cutover Runbook (BINKY-WP-0004-T06)
> Status: **cutover completed 2026-07-21**. Workstation cron bridge removed.
> Railiance host timers installed; three definition completion event types
> verified the same day. Residual automation gaps tracked as BINKY-WP-0006.
## Gates (all cleared)
1. ~~DEC-2026-002 / agent-harness~~ done
2. ~~Lanes 23 + binky-control write deploy key~~ done (key id 2)
3. ~~HARNESS-WP-0001 T06T07~~ done
4. ~~DEC-2026-003 cutover go~~ done 2026-07-18
5. ~~activity-core definitions `enabled: true`~~ (commit 73cc785)
6. ~~Three completion event types verified 2026-07-21~~
- `binky_daily_brief` (harness run + brief commit)
- `binky_mail_intake` (**railiance01** deterministic mail-scan, 86 new)
- `binky_weekly_review` (harness review-prep commit)
7. ~~Workstation crontab line removed~~ 2026-07-21
## What runs where (after cutover)
```text
activity-core schedules (Europe/Berlin)
├─ (ideal) IssueSink → claimable work → agent-harness poller
│ currently: ISSUE_SINK_TYPE=state-hub → progress only (no claim)
└─ interim: railiance01 systemd user timers
scripts/railiance-rhythm/run-{daily,mail,review}.sh
→ agent-harness run | mail-scan
→ hub progress + local commits (deploy key)
```
Install / reinstall timers on railiance01:
```bash
cd ~/binky-control && git pull
./scripts/railiance-rhythm/install-on-railiance.sh
```
## Residual after BINKY-WP-0006 (2026-07-22)
| Gap | Status / follow-up |
| --- | --- |
| Post-scan **triage** via llm-connect | **Done**`agent-harness mail-triage`; three clean railiance cycles 2026-07-22 |
| Daily brief without host coding agent | **Done**`brief-daily` |
| Weekly review prep without host coding agent | **Open** — need `brief-weekly` (same pattern) |
| Host timers dual activity-core schedules | Simplify when in-cluster CronJob/poller owns cadence |
| **Out of scope / rejected:** install Claude Code on railiance01 | — |
## Rollback
1. `ssh railiance01 'systemctl --user disable --now binky-rhythm-*.timer'`
2. Re-add workstation cron line (see OperatingRhythm.md rollback).
3. Optionally set activity-core definitions `enabled: false` if schedules must pause.
## Verification evidence (2026-07-21)
| Event | Time (UTC) | Notes |
| --- | --- | --- |
| `binky_mail_intake` | 21:48:22 | railiance01 AppRole mail-scan ok |
| `binky_daily_brief` | 21:49:34 | brief `briefs/2026-07-21-daily-brief.md` |
| `binky_weekly_review` | 21:50:29 | weekly prep commit |