Add automation status surface

docs/runbook.md

@@ -136,6 +136,47 @@ The response reports:
 - `schedules.deleted_orphans`
 - bounded `errors[]`
 
+## Automation status
+
+Use the repo-native status command to answer operator questions such as "how did
+our automations go since Friday?". This is the baseline evidence surface; LLMs
+or coding assistants may summarize the output, but they are not the scheduler or
+source of truth.
+
+```bash
+# Human-readable status. `friday` resolves in Europe/Berlin by default.
+make automation-status SINCE=friday
+
+# JSON for scripts or assistant summarization.
+make automation-status-json SINCE=2026-06-26
+```
+
+The command reads activity-core owned evidence only: ActivityDefinition files or
+DB rows, `activity_runs`, State Hub progress, working-memory report notes, and
+Temporal visibility when `TEMPORAL_HOST` is configured. Missing live sources are
+reported as warnings rather than hidden. It exits non-zero for real automation
+failures such as `missed`, `validation_failed`, or `sink_failed`.
+
+Useful knobs:
+
+```bash
+AUTOMATION_STATUS_TIMEOUT_SECONDS=10 make automation-status SINCE=friday
+make automation-status SINCE=2026-06-26 FORMAT=json
+make automation-status SINCE=2026-06-26 UNTIL=2026-06-27 ACTCORE_DB_URL=
+```
+
+Example distinction from the June 2026 daily triage evidence:
+
+```text
+- Activity 6fca51fa-387a-4fd0-bc4e-d62c29eb859a [validation_failed] expected=0 runs=0 evidence=2
+  evidence state_hub_progress event_type=daily_triage run=ebec6e41... output_validated=false validation_error=Unterminated string...
+  evidence state_hub_progress event_type=daily_triage run=c7370f9c... output_validated=false validation_error=Expecting ',' delimiter...
+```
+
+That means the schedule/report path left evidence, but the report was not a
+clean validated output. Disabled schedules, such as the gated weekly coding
+retro, are reported as `disabled` and are not counted as missed runs.
+
 `event_types` defaults to `false` for this endpoint because event-triggered
 definitions already reload from the DB in the event router path; opt in when
 the operator intentionally changed event type definition files: