docs: record worker validation and clarify Claude sample

2026-07-21 21:15:07 +00:00 · 2026-03-13 19:16:56 +10:00
parent 0c2d1465b0
commit 541458535d
3 changed files with 7 additions and 2 deletions
@@ -28,7 +28,8 @@
 ## 4) ACP/Codex delegation constraints
 - Telegram channel plugin currently does **not** support `subagent_spawning` hooks → cannot bind persistent subagent sessions with `thread=true`; use `sessions_spawn(mode="run")` as workaround.
 - Current durable conclusion on `execution-agent-dispatch`: it is a **process/protocol skill**, not a fix for OpenClaw/ACP runtime communication. We previously tested parent↔child / agent↔agent flows and did **not** get stable bidirectional communication. Default behavior is still closer to spawn + announce than reliable free-form agent-to-agent conversation. Keep the skill frozen as a workflow aid only; wait for OpenClaw ACP/runtime support to become stable before resuming development aimed at true inter-agent communication.
- New clarified split after ACP re-check on 2026-03-13: **main → ACP worker** invocation is now confirmed basically usable on this machine (ACPX installed/enabled; Codex ACP smoke test could start, inherit workspace, and read expected files). But this does **not** prove stable **agent↔agent** or **subagent↔subagent** communication over ACP. Treat the safe default as: main acts as PM/architect/reviewer, ACP workers execute tasks and report back to main; do **not** assume a reliable free-form multi-agent ACP communication mesh.
+- New clarified split after ACP re-check on 2026-03-13: **main → ACP worker** invocation is now confirmed basically usable on this machine (ACPX installed/enabled; Codex ACP smoke test could start, inherit workspace, read expected files, and return a worker-style result). But this does **not** prove stable **agent↔agent** or **subagent↔subagent** communication over ACP. Treat the safe default as: main acts as PM/architect/reviewer, ACP workers execute tasks and report back to main; do **not** assume a reliable free-form multi-agent ACP communication mesh.
 - Clarification on Claude ACP testing: a same-day Claude ACP smoke test failed, but Tao confirmed Claude usage had already hit timeout/overuse state that day. Therefore do **not** record that sample as a product/runtime failure; mark Claude ACP as **not yet cleanly validated**, not “broken.”
 ## 5) OCM (OpenClaw Manager) repo policies
 - OCM repo path: `~/.openclaw/ocm`.
@@ -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.
@@ -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.