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.

.env.example

@@ -25,6 +25,19 @@ ISSUE_CORE_API_KEY=
 # state-hub (default, no Forgejo) | null (dry-run) | rest (issue-core opt-in)
 ISSUE_SINK_TYPE=state-hub
 
+# ── Ops run claim queue (ACTIVITY-WP-0026 / ACT-ADR-005) ───────────────────────
+# Create claimable ops_run rows on emit_tasks (default true). Harness claims via
+# POST /ops-runs/claim — not issue-core / Forgejo.
+OPS_RUN_QUEUE_ENABLED=true
+# Default claim lease (seconds); heartbeat extends.
+OPS_RUN_LEASE_SECONDS=900
+# Permanent fail after this many claims when fail+reopen is requested.
+OPS_RUN_MAX_ATTEMPTS=3
+# Stuck open/claimed threshold for /ops/automations/status ops_runs.sla_hours
+OPS_RUN_SLA_HOURS=1
+# Worker credential for claim/complete/fail (X-Worker-Token or Bearer).
+ACTIVITY_CORE_WORKER_TOKEN=
+
 # ── Activity definitions ───────────────────────────────────────────────────────
 # Colon-separated paths to additional activity-definitions/ directories.
 # The local activity-definitions/ directory is always scanned.