Implement ACTIVITY-WP-0026 ops_run claim queue (T01–T06).

Add durable claimable ops_runs table, emit dual-write on TaskSpec, REST
claim/lease/complete/fail API, ops status visibility, and consumer docs
aligned with ACT-ADR-005. T07 railiance rollout remains deploy-side.

docs/recurring-automations-playbook.md

@@ -20,14 +20,15 @@ issue-core projection — never as the default ops claim queue.
 ┌─────────────────────────────────────────────────────────────┐
 │ 1. activity-core  — WHEN / WHAT / WHERE                     │
 │    Temporal schedule · context resolvers · rules            │
-│    → emits activity_task_spawn (state-hub sink by default)  │
+│    → INSERT ops_run (open) + dual-write activity_task_spawn │
+│    Claim API: POST /ops-runs/claim  (docs/ops-run-queue.md) │
 └────────────────────────────┬────────────────────────────────┘
                              │
 ┌────────────────────────────▼────────────────────────────────┐
 │ 2. rein-aharness (or domain executor) — DOES THE WORK       │
-│    llm-connect · repo checkout · commit · completion event  │
-│    Host timers on railiance are *interim* until poll/claim  │
-│    of spawns is fully wired (state-hub sink is not claimable)│
+│    claim ops_run · llm-connect · checkout · complete/fail   │
+│    Host timers on railiance are *interim* until REIN-A-0002 │
+│    claim loop is live (state-hub spawn alone is not claimable)│
 └────────────────────────────┬────────────────────────────────┘
                              │
 ┌────────────────────────────▼────────────────────────────────┐
@@ -151,17 +152,22 @@ Do not flip production to `rest` globally.
 
 ## Operator daily habit
 
-1. Ops console: did automations run? (`/ops/automations/status`)  
-2. State Hub: `activity_task_spawn` + domain completion events  
-3. Domain repo: brief/artifact files + git history  
-4. If something is missing, **fix activity-core first** (schedule paused?
-   definition disabled? resolver due stuck? sink errors?) — do not invent a new cron  
+1. Ops console: did automations run? (`/ops/automations/status`) — includes
+   `ops_runs.counts` and `stuck_open_or_claimed` (SLA, default 1h)  
+2. Claim queue: `GET /ops-runs?state=open` (or failed) — harness backlog  
+3. State Hub: `activity_task_spawn` + domain completion events  
+4. Domain repo: brief/artifact files + git history  
+5. If something is missing, **fix activity-core first** (schedule paused?
+   definition disabled? resolver due stuck? open ops_run with no claim?) —
+   do not invent a new cron  
 
 ---
 
 ## Related
 
 - `INTENT.md` — when/what/where boundary  
+- `docs/adr/adr-005-ops-runs-vs-dev-work-records.md` — ops vs dev work  
+- `docs/ops-run-queue.md` — claim API  
 - `docs/task-emission-consumer-contract.md` — spawn payload + consumer duties  
 - `docs/runbook.md` — sync, trigger, ops UI  
 - `docs/adr/adr-002-definition-format.md` — definition files