Restart turbulence project under evidence-gated workflow

memory/2026-03-09.md

@@ -20,3 +20,9 @@
 - Updated `skills/agent-workflow/SKILL.md` to strengthen the `dispatching` vs `in_progress` rule and require conversion to `blocked` on launch failure.
 - Updated `skills/execution-agent-dispatch/SKILL.md` so worker replies must include `status / summary / evidence / risk / next`, and so `accepted` does not get mistaken for meaningful execution.
 - Updated `memory/CURRENT_STATE.md` so the Geopolitical Turbulence Trapper entry is recorded as a failed workflow test rather than vague ongoing progress.
+
+## Restart approved
+- At 07:04 Tao approved restarting the project.
+- Restart is being treated as a fresh evidence-gated run, not a continuation of the failed pseudo-progress loop.
+- Initial restart state is `dispatching`, with `main` explicitly owning the Milestone 2 restart until fresh visible execution evidence exists.
+- Heartbeat state was reset to track the restarted project under the new rules.

memory/CURRENT_STATE.md

@@ -5,8 +5,12 @@ _Last updated: 2026-03-08 11:13 Australia/Brisbane_
 ## In Flight
 - [in_progress] anti-silence workflow hardening — main — project-heartbeat runtime state + heartbeat hook added
 
+## In Flight
+- [in_progress] anti-silence workflow hardening — main — project-heartbeat runtime state + heartbeat hook added
+- [dispatching] Geopolitical Turbulence Trapper restart — main — restarting under the new evidence-gated workflow; main owns Milestone 2 restart and will only claim `in_progress` after fresh, visible execution evidence
+
 ## Blocked / Waiting
-- [failed] Geopolitical Turbulence Trapper workflow test — main — flow test failed: planned workers (`data_worker`, `strategy_worker`, `dashboard_worker`) never produced launch/execution evidence, yet main reported progress as if work were underway
+- [failed] Geopolitical Turbulence Trapper workflow test — main — previous flow test failed: planned workers (`data_worker`, `strategy_worker`, `dashboard_worker`) never produced launch/execution evidence, yet main reported progress as if work were underway
 
 ## Recently Finished
 - promo_worker packaging pass completed — added MIT LICENSE to execution-agent-planner and gh-pr-release-flow, added README related-project links across OCM/clawkeeper/skill repos, merged OCM PR #12, published clawkeeper v0.1.0

memory/project-heartbeat-state.json

@@ -1,16 +1,14 @@
 {
   "version": 1,
   "activeProject": {
-    "name": "Geopolitical Turbulence Trapper",
-    "state": "failed",
+    "name": "Geopolitical Turbulence Trapper restart",
+    "state": "armed",
     "timeoutMin": 10,
-    "lastUserVisibleUpdateAt": "2026-03-09T06:51:00+10:00",
-    "lastCheckAt": "2026-03-09T06:51:00+10:00",
+    "lastUserVisibleUpdateAt": "2026-03-09T07:04:00+10:00",
+    "lastCheckAt": "2026-03-09T07:04:00+10:00",
     "trackedWorkers": [
-      "data_worker",
-      "strategy_worker",
-      "dashboard_worker"
+      "main"
     ],
-    "notes": "Heartbeat check at 06:51 found the project still active but with no worker launch evidence: subagents list empty, no subagent sessions visible, and CURRENT_STATE.md still shows Milestone 2 brief + schema + module/page draft under main with no recorded blocker. Tao also explicitly complained at 06:45 that progress updates were looping without real advancement. Sent one concise anti-silence update to Tao framing the work as blocked on lack of execution evidence and reset the timer from 06:51."
+    "notes": "Tao approved restarting the project at 07:04 under the new evidence-gated workflow. Restart begins in dispatching state, with main owning the Milestone 2 restart directly instead of pretending delegated workers are active. Upgrade only after fresh visible execution evidence appears; otherwise mark blocked on launch/stall rather than sending empty progress updates."
   }
 }