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

docs: record worker validation and clarify Claude sample

Browse Source
This commit is contained in:
taodeng
2026-03-13 19:16:56 +10:00
parent 0c2d1465b0
commit 541458535d
3 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory/2026-03-13.md
+3 -1
View File
@@ -34,4 +34,6 @@
- Conservative decision taken: do not force compaction on the main live session. Run compaction testing later in a disposable/sacrificial test session instead.
- Additional boundary discovered after fresh Discord testing: Discord main/channel/thread sessions are not currently in the supported continuity set for `v0.3.0-probe`. Even with fresh `/new`, new thread, and new channel tests, Discord main failed to preserve short facts or restore concrete working-state details across sessions. Treat resident subagents as the validated support surface; treat Discord main continuity as unsupported for this alpha.
- New fallback-path finding: during a main-session fallback/new-session event, `memory-continuity-probe`'s `before_prompt_build` hook did run but logged `workspaceDir=<missing> statePath=<missing>`, so startup recovery could not resolve `CURRENT_STATE.md`. Opened upstream issue `openclaw/openclaw#44746` and currently suspect an OpenClaw lifecycle/runtime contract gap rather than a pure plugin logic bug.
- ACP capability clarified: this machine does have ACPX installed and enabled; a Codex ACP smoke test successfully started and inherited workspace context. Current safe operational model is therefore `main -> ACP worker -> main`, not free-form stable agent↔agent ACP communication.
- ACP capability clarified: this machine does have ACPX installed and enabled; a Codex ACP smoke test successfully started and inherited workspace context, and later returned a valid worker-style result. Current safe operational model is therefore `main -> ACP worker -> main`, not free-form stable agent↔agent ACP communication.
- Additional execution-path validation: temporary subagents were tested in three modes and all worked — single reply, follow-up reply, and parallel two-worker fan-out with main-side aggregation.
- Important sample-quality note: a same-day Claude ACP smoke test failed, but Tao later confirmed Claude had already entered timeout/overuse state from work usage. Therefore that Claude result should be treated as an invalid/contaminated sample, not evidence that Claude ACP is broken.
memory/CURRENT_STATE.md
+2
View File
@@ -29,3 +29,5 @@ Two-track next step:
- `tech_geek` recovered plugin-injected startup continuity state without using `read`.
- `travel_assistant` also recovered the correct upgraded smoke-test state after fixing its old workspace pollution and startup rule.
- Fresh Discord main/channel/thread tests failed to preserve short facts or concrete working-state recovery across new sessions; treat Discord main continuity as unsupported for this alpha.
- New execution-model finding: main can successfully dispatch and consume results from temporary subagents (single, follow-up, and parallel two-worker tests all succeeded).
- New ACP finding: Codex ACP worker is validated as a usable execution worker for main; Claude ACP today remains an invalid sample because Tao confirmed Claude was already in timeout/overuse state, so do not classify that failure as product/runtime evidence.