From f64809990ae249375dca5d4f42ebc9961291a58d Mon Sep 17 00:00:00 2001 From: wangzhendong Date: Tue, 19 May 2026 12:28:19 +0800 Subject: [PATCH] Sync agent state from PC at 2026-05-19 12:28:19 --- AGENT_BOARD.md | 12 ++++++------ USER_STATUS.md | 24 +++++++++++++----------- handoff/ORCHESTRATOR.md | 27 +++++++++++++++++---------- tasks/T9-G2-PC-node-run.md | 10 +++++----- 4 files changed, 41 insertions(+), 32 deletions(-) diff --git a/AGENT_BOARD.md b/AGENT_BOARD.md index 784622b..55d1f77 100644 --- a/AGENT_BOARD.md +++ b/AGENT_BOARD.md @@ -45,7 +45,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | G0A Collaboration mechanism aligned | User-approved agent roles, Git polling MVP, sync-health handling, status entry, and hard safety boundaries | ORCHESTRATOR | Done | | G0B OpenClaw system requirements aligned | User-approved target architecture, component boundaries, PC permissions, Tailscale role, phone/QQ behavior, and G2/G3/G4 acceptance criteria | ORCHESTRATOR | Done | | G1 Baseline discovered | PC and VPS read-only status snapshots accepted by independent verifiers | PC_EXECUTOR, VPS_EXECUTOR, verifiers | Done | -| G2 Gateway/node pairing ready | PC `node run` evidence and VPS approval evidence | PC_EXECUTOR, VPS_EXECUTOR | In Progress | +| G2 Gateway/node pairing ready | PC `node run` evidence and VPS approval evidence | PC_EXECUTOR, VPS_EXECUTOR | Pending | | G3 Execution smoke test | Harmless command result proves execution came from the PC node | PC_VERIFIER | Pending | | G4 Persistent service verified | `node install/start/status` and reboot survival evidence | PC_VERIFIER, CORRECTION | Pending | | G5 Security posture reviewed | Secrets absent, public exposure avoided, least-privilege notes captured | VPS_VERIFIER, CORRECTION | Pending | @@ -64,11 +64,11 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con | T6 | Verify VPS baseline before any VPS change | VPS_VERIFIER | T4 | Accepted | | T7 | Monitor drift, sync-health failures, conflicts, unsafe changes, and missing evidence | CORRECTION | G0A | Claimed | | T8 | Solidify COACH role, session freeze, and knowledge capture | COACH | T2.1 | Done | -| T9 | G2 PC foreground node run | PC_EXECUTOR | User G2 authorization, T7 healthy | Ready | -| T10 | G2 VPS pairing approval | VPS_EXECUTOR | T9, explicit approval authorization | Draft | +| T9 | G2 PC foreground node run | PC_EXECUTOR | Fresh user G2 authorization, T7 healthy | Blocked | +| T10 | G2 VPS pairing approval | VPS_EXECUTOR | T9, explicit approval authorization | Blocked | | T11 | Verify G2 PC evidence | PC_VERIFIER | T9 | Draft | | T12 | Verify G2 VPS evidence and freeze compliance | VPS_VERIFIER | T10 | Draft | -| T13 | Guard G2 sync, secret, and freeze risks | CORRECTION | User G2 authorization | Ready | +| T13 | Guard G2 sync, secret, and freeze risks | CORRECTION | Fresh user G2 authorization | Blocked | ## Confirmed OpenClaw Target Design @@ -100,8 +100,8 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con ## G2 Authorization Boundary -- User authorized G2 on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only. -- T9 may proceed under `docs/G2_RUNBOOK.md`; T10 must wait for T9 evidence with a non-secret request/node ID before any approval. +- Role-misdirection audit on 2026-05-19 paused G2 execution. Fresh explicit user authorization is required before T9/T10/T13 can proceed. +- `docs/G2_RUNBOOK.md` remains the planned G2 procedure, but it does not authorize token injection, `openclaw node run`, VPS approval, or any mutation by itself. - G2 must remain foreground-only for the PC node; service persistence belongs to G4. - G2 still forbids service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. - G2 must not change the frozen `smartmotor.cloud` homepage, homepage-linked content, static assets, Nginx routing, Docker bind mounts, container images, `/opt/services/docker-compose.openclaw.yml`, or any equivalent website-affecting compose/service entries. diff --git a/USER_STATUS.md b/USER_STATUS.md index 6191261..04817b2 100644 --- a/USER_STATUS.md +++ b/USER_STATUS.md @@ -4,9 +4,9 @@ ## Current Stage -Stage 2A: G2 authorized, foreground node pairing only. +Stage 2A Paused: role-misdirection correction in progress. -The user has authorized G2 only for the foreground Windows PC node run and corresponding VPS pairing approval described in `docs/G2_RUNBOOK.md`. Service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret remain forbidden. +G2 planning artifacts exist, but execution is paused after a role-misdirection audit. Do not start the PC node, do not inject a token, and do not approve pairing until ORCHESTRATOR records a fresh explicit user authorization after this correction. ## Completed @@ -14,7 +14,7 @@ The user has authorized G2 only for the foreground Windows PC node run and corre - OpenClaw target design was confirmed: QQ and phone Control UI are control entries, VPS Gateway is the always-on hub, DeepSeek handles white-listed autonomous decisions, and Windows PC is the main execution node. - G2 runbook and draft role tasks were prepared for review. - `docs/G2_RUNBOOK.md` was completed as the G2 pre-execution plan. -- G2 was authorized on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only. +- G2 runbook remains available as planning material, but role-misdirection correction paused execution. - The `smartmotor.cloud` filing-review website freeze is active as a hard rule. - PC baseline was collected and independently accepted. - VPS baseline was collected and independently accepted. @@ -23,21 +23,23 @@ The user has authorized G2 only for the foreground Windows PC node run and corre ## Current Blockers -- No active sync blocker is recorded. -- VPS pairing approval must wait until PC_EXECUTOR produces a non-secret pairing request ID or pending node ID from T9. +- No active sync-health blocker is recorded. +- G2 execution is blocked by the role-misdirection incident until ORCHESTRATOR restates the next step and the user gives fresh explicit authorization. ## Allowed Actions - Keep the sync scripts running. - Agents may update user-facing status, handoffs, evidence, and internal ledgers. - Agents may continue read-only monitoring for sync-health, drift, missing evidence, and freeze-policy risk. -- PC_EXECUTOR may perform T9 exactly as `docs/G2_RUNBOOK.md` allows: write rollback note, set the Gateway token only in the local shell/session without recording it, and run the PC node in foreground mode. -- VPS_EXECUTOR may perform T10 only after T9 provides a matching non-secret request/node ID; approval must be limited to the intended pairing. +- ORCHESTRATOR may update control-plane status and task files to correct the role-misdirection incident. +- CORRECTION may continue read-only monitoring and keep G2 blocked if evidence or sync state is unsafe. ## Forbidden Actions - Do not start Gateway/node pairing or approval outside the T9/T10 sequence in `docs/G2_RUNBOOK.md`. - Do not run any G2 command outside `docs/G2_RUNBOOK.md`. +- Do not run T9 or T10 while the role-misdirection block is active. +- Do not set or inject `OPENCLAW_GATEWAY_TOKEN`. - Do not install, start, restart, stop, or persist PC/VPS services. - Do not run `openclaw node install`, `openclaw node start`, or any service persistence command. - Do not change firewall, routing, Nginx, Docker compose, bind mounts, container images, environment variables, or service state. @@ -46,11 +48,11 @@ The user has authorized G2 only for the foreground Windows PC node run and corre ## Single Recommended Next Step -PC_EXECUTOR should claim T9, write the rollback note, and run only the foreground PC node flow from `docs/G2_RUNBOOK.md` without recording any token or secret. +Wait for ORCHESTRATOR to finish the control-plane correction and ask for a fresh explicit G2 authorization when appropriate. ## User Decision Needed -No additional user decision is needed before T9 starts, as long as PC_EXECUTOR stays within the G2 runbook and the restrictions above. A new decision is required for any service persistence, firewall/network change, Nginx/Docker/website change, G3 smoke test, or action outside the runbook. +Not needed right now. A fresh explicit user authorization will be required before any G2 execution can start. ## Confirmed Target Design @@ -76,6 +78,6 @@ No additional user decision is needed before T9 starts, as long as PC_EXECUTOR s - VPS sync heartbeat: clean at `2026-05-19T12:16:28+0800`. - Sync error files: none observed. - G2 runbook: `docs/G2_RUNBOOK.md` complete. -- G2 authorization: granted only for foreground PC node run and corresponding VPS pairing approval. +- G2 authorization: paused after role-misdirection audit; fresh explicit authorization required before execution. - Public website freeze: still active. -- Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden. +- Mutation/setup phase: not active; all PC node run, token injection, and VPS approval actions are paused. diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md index d716a51..d7d7d43 100644 --- a/handoff/ORCHESTRATOR.md +++ b/handoff/ORCHESTRATOR.md @@ -6,7 +6,7 @@ Own requirements alignment, task decomposition, dependency tracking, and final a ## Current Objective -Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foreground PC node run first, then corresponding VPS pairing approval only after a matching non-secret request/node ID exists. +Correct the control plane after a role-misdirection incident, keep G2 paused, and ensure no executor starts token injection, foreground node run, or VPS pairing approval without fresh explicit user authorization. ## Must Read @@ -27,7 +27,7 @@ Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foregrou - Strict `smartmotor.cloud` website freeze is a hard requirement during filing review. - Communication MVP uses polling Git sync scripts in `sync/` and task files in `tasks/`. - `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user. -- G2 is authorized as of 2026-05-19, limited to foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`. +- G2 execution is paused after the role-misdirection audit. Any earlier G2 authorization must be treated as not active until the user gives fresh explicit authorization after ORCHESTRATOR correction. - `docs/G2_RUNBOOK.md` has been prepared as the G2 execution-before-action runbook. It does not authorize execution by itself. - Sync-health is currently healthy: tracked PC and VPS heartbeats are present and clean, and no `sync-state/error-*.md` files are observed in the latest control-plane snapshot. - T2.1 and T8 are now treated as complete control-plane setup work; G2 remains Pending. @@ -36,24 +36,31 @@ Coordinate authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: foregrou ## Next Actions -1. Let PC_EXECUTOR claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, set the Gateway token only in the local shell/session without recording it, and run only the foreground PC node command from `docs/G2_RUNBOOK.md`. +1. Keep T9/T10/T13 blocked and do not allow token injection, foreground node run, or VPS pairing approval. 2. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes. 3. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk. -4. Keep T10 draft until T9 evidence includes a matching non-secret pairing request ID or pending node ID. -5. When T10 becomes eligible, require `rollback/vps-g2-approve-YYYYMMDD.md` before approval and approve only the matching request/node. -6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. +4. If the user later gives fresh explicit G2 authorization, move T13 then T9 to ready, keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID, and require rollback notes before any token/run/approval action. +5. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret. ## Open Questions -- When should the user authorize G2 Gateway/node pairing? +- When should the user give fresh explicit authorization for G2 Gateway/node pairing after this correction? - When should the Git polling MVP be upgraded to webhook, Issues, OpenClaw events, or Cursor SDK based coordination? ## Last Update -2026-05-19 12:16 UTC+8: User authorized G2 with strict scope. +2026-05-19 12:27 UTC+8: ORCHESTRATOR took over after role-misdirection audit and paused G2 execution. -- Allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`. -- T9 and T13 are ready; T10 remains draft until T9 provides a matching non-secret request/node ID. +- VPS_VERIFIER self-reported that prompts intended for ORCHESTRATOR were mistakenly sent to VPS_VERIFIER. +- CORRECTION found cross-role control-plane edits from VPS-origin commits but no evidence of live G2 approval, token handling, service restart/reload, Gateway config mutation, Nginx/Docker/website mutation, or secret leak. +- ORCHESTRATOR adopts `docs/G2_RUNBOOK.md` as planning material only, but corrects the active state: G2 is Pending, T9/T10/T13 are blocked, and fresh explicit user authorization is required before any G2 execution. +- No PC/VPS command was executed by ORCHESTRATOR during this correction. + +2026-05-19 12:16 UTC+8: Prior G2 authorization record is superseded by the 12:27 role-misdirection correction. + +- Previously recorded allowed scope: foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`. +- Current corrected state: this authorization is paused and must not be used for execution without fresh explicit user confirmation. +- T9/T10/T13 are blocked. - G2 quality gate is In Progress, not accepted. - No PC/VPS command was executed by ORCHESTRATOR, no token was handled, no node was started here, no VPS approval was performed here, and no service was modified. diff --git a/tasks/T9-G2-PC-node-run.md b/tasks/T9-G2-PC-node-run.md index c1bfe72..ea606b7 100644 --- a/tasks/T9-G2-PC-node-run.md +++ b/tasks/T9-G2-PC-node-run.md @@ -2,7 +2,7 @@ ## Status -ready +blocked ## Owner @@ -26,9 +26,9 @@ This task is not ready until ORCHESTRATOR records explicit user authorization fo - G2 pre-execution plan is documented in `docs/G2_RUNBOOK.md`. - Sync-health has been confirmed healthy and T7 sync-health blocked state is cleared. -- User authorized G2 on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only. -- This task is ready for PC_EXECUTOR under `docs/G2_RUNBOOK.md`. -- Authorization covers only local-session token use without disclosure and foreground `openclaw node run`; it does not authorize service changes, firewall changes, network changes, persistence, or public port exposure. +- Role-misdirection audit on 2026-05-19 paused G2 execution. +- This task must not be claimed or executed until ORCHESTRATOR records fresh explicit user authorization after the correction. +- `docs/G2_RUNBOOK.md` remains the planned procedure, but it does not authorize token injection or `openclaw node run` by itself. ## Required Evidence @@ -58,7 +58,7 @@ openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-na ## Stop Conditions -- User authorization is absent or ambiguous. +- Fresh user authorization after the role-misdirection correction is absent or ambiguous. - `docs/G2_RUNBOOK.md` has not been read by PC_EXECUTOR. - Any command asks to print, persist, or store a token. - Any command prints a secret.