taodeng/memory-continuity
1
0
Fork 0
mirror of https://github.com/dtzp555-max/memory-continuity.git synced 2026-07-22 13:35:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix completion-consumption gap in agent workflow

Browse Source
This commit is contained in:
taodeng
2026-03-09 07:48:39 +10:00
parent 22208cf803
commit ea325f6bcb
5 changed files with 40 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory/2026-03-09.md
+14
View File
@@ -26,3 +26,17 @@
- 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.
## Validation + new failure mode found
- Tao approved a minimal validation run using a single temporary worker.
- The validation worker successfully launched, wrote `/Users/taodeng/.openclaw/workspace/main/tmp/worker-validation-2026-03-09.txt`, and returned a structured success report.
- This confirmed the base execution-agent pipeline is functional.
- However, the result auto-announced to Tao before main performed its own state-consumption and summary step.
- New root-cause finding: the system is vulnerable to a `completion-consumption` bug where runtime-visible worker completion does not automatically flip main out of its local waiting posture.
- Agreed fix direction: harden agent-workflow, project-heartbeat, and dispatch checklist rules so main must immediately consume visible worker completion/milestone/blocker and cannot continue behaving as if it is still waiting.
## 07:16 watchdog result: launch failure / blocked
- The project-heartbeat watchdog re-checked the restarted run after the 10-minute window.
- No fresh worker/session execution evidence appeared beyond the 07:04 user-visible restart acknowledgment; active session traces showed no new milestone/work output for this project.
- Per the new workflow rule, the restart must be treated as `blocked` with reason `launch failure`, not as silent `in_progress` work.
- Heartbeat state was paused after reporting the blocker so Tao does not get repeated empty nudges without a new restart decision.
memory/CURRENT_STATE.md
+3 -6
View File
@@ -1,13 +1,10 @@
# CURRENT_STATE
_Last updated: 2026-03-08 11:13 Australia/Brisbane_
_Last updated: 2026-03-09 07:47 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
- [in_progress] anti-silence workflow hardening — main — workflow rules hardened again after finding a completion-consumption bug: runtime worker results can reach Tao before main updates state and summarizes them
- [blocked] Geopolitical Turbulence Trapper restart — main — no fresh execution evidence appeared within the 10-minute dispatch window after the 07:04 restart; treating as launch failure / blocked pending Tao’s direction
## Blocked / Waiting
- [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