fix: restore minimal long-task watchdog execution chain

state/long-task-watchdog/2026-05-07T090000Z-reporting-governance-plugin-watchdog.json

@@ -0,0 +1,30 @@
+{
+  "generatedAt": "2026-05-07T09:00:00.000Z",
+  "tool": "long_task_watchdog",
+  "watchdog": {
+    "id": "reporting-governance-plugin-watchdog",
+    "task": "reporting-governance plugin spec development",
+    "ownerSession": "main-telegram-eric",
+    "ownerSessionKey": "agent:coder:main",
+    "reportChannel": "telegram",
+    "reportTarget": "864811879",
+    "intervalMinutes": 10,
+    "lastMilestoneAt": "2026-05-07T16:46:00+08:00",
+    "lastAlertAt": null
+  },
+  "evaluation": {
+    "watchdogId": "reporting-governance-plugin-watchdog",
+    "id": "reporting-governance-plugin-watchdog",
+    "active": true,
+    "overdue": true,
+    "action": "emit_external_evidence",
+    "reason": "active watchdog is overdue and has not been externally evidenced for this interval",
+    "dueAt": "2026-05-07T08:56:00.000Z",
+    "minutesOverdue": 4
+  },
+  "nextExpectedExternalAction": [
+    "nudge owner session",
+    "report owner-visible checkpoint",
+    "or respawn / inspect locally if owner appears stalled"
+  ]
+}

state/long-task-watchdog/README.md

@@ -0,0 +1,19 @@
+# Long-task watchdog evidence
+
+This directory stores file-backed external evidence produced by `scripts/long_task_watchdog.mjs`.
+
+## Purpose
+
+The original watchdog chain had state registration but no active external executor.
+This directory is the minimal proof surface for the rebuilt execution chain:
+
+- each overdue run writes a timestamped evidence artifact
+- cron can append to `cron.log`
+- `memory/watchdog-state.json` records `lastAlertAt`
+
+## Expected files
+
+- `cron.log` — append-only stdout/stderr from cron-triggered runs
+- `<timestamp>-<watchdog-id>.json` — overdue evidence artifact per emitted interval
+
+These artifacts are meant to be machine-verifiable and safe to inspect from the repo worktree.