Document dual reporting protocol and initialize CURRENT_STATE

AGENTS.md

@@ -45,7 +45,6 @@ Capture what matters. Decisions, context, things to remember. Skip the secrets u
 - This file is **not** a journal; it is a short-lived task/state board
 - Keep it small and overwrite-oriented
 - Use it to survive `/new`, gateway restarts, compaction, and context loss
-- Update it when important task state changes: dispatch, block, completion, next-step changes
 - Remove stale items instead of appending endlessly
 
 Capacity guidance:
@@ -59,6 +58,53 @@ Suggested sections:
 - `Next`
 - `Reset Summary`
 
+Update only on state changes, not on a timer. The key triggers are:
+- task accepted / formally started
+- task dispatched to a worker
+- task becomes blocked / waiting
+- milestone reached
+- next-step changes
+- task/phase completed
+
+## Dual reporting protocol
+
+### A) Execution agent → main (执行回包协议)
+Execution agents report to main, not directly to Tao.
+
+They must report at these points:
+- accepted
+- blocked
+- milestone
+- done
+- model/environment abnormal (especially GPT-5.4 unavailable/fallback, repo/cwd/tool/auth issues)
+
+Preferred worker reply format:
+- `status`
+- `summary`
+- `evidence`
+- `risk`
+- `next`
+
+### B) main → Tao (对外汇报协议)
+Main reports user-visible progress to Tao.
+
+Main must update Tao at these points:
+- task accepted / formally started
+- worker dispatched
+- blocked
+- milestone reached
+- task/phase completed
+
+Preferred Tao update format:
+- who
+- status
+- output
+- next
+
+Ordering rule:
+- When a worker reports milestone/completion/blocker, main should first update `CURRENT_STATE.md`, then update Tao, then continue with review/commit/next dispatch.
+- If there is no evidence point yet (sessionKey / commit / branch / PR / log), do not claim work has “already started”; say it is about to start.
+
 - **Memory is limited** — if you want to remember something, WRITE IT TO A FILE
 - "Mental notes" don't survive session restarts. Files do.
 - When someone says "remember this" → update `memory/YYYY-MM-DD.md` or relevant file

memory/CURRENT_STATE.md

@@ -1,18 +1,23 @@
 # CURRENT_STATE
 
-_Last updated: TBD Australia/Brisbane_
+_Last updated: 2026-03-08 11:13 Australia/Brisbane_
 
 ## In Flight
-- none
+- [in_progress] continuity architecture rollout — main — defining CURRENT_STATE + dual reporting protocol
+- [in_progress] anti-silence workflow hardening — main — turning reporting into explicit state-change rules
 
 ## Blocked / Waiting
 - none
 
 ## Recently Finished
-- none
+- Tao's original 1-5 task list completed (clawkeeper switch --dry-run, OCM checklist, repo rule detector, execution-agent dispatch drill, OCM CLI copy helper)
+- All recurring cron jobs disabled except Daily OpenClaw backup
+- GPT-5.4 support restored again after update-related breakage; if it breaks again, report Tao immediately
 
 ## Next
-- none
+- apply CURRENT_STATE + dual reporting rules in practice
+- later decide whether to package continuity workflow as a skill, clawkeeper feature, or both
+- monitor GPT-5.4 availability and report any fallback/unavailability immediately
 
 ## Reset Summary
-- No active summary yet.
+- We finished Tao’s original 1-5 task list. Current focus is continuity and anti-silence hardening: every agent now has a CURRENT_STATE file, and main/worker reporting rules are being formalized so work can survive /new, restart, and worker stalls.