wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync agent state from PC at 2026-05-19 17:06:56

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 17:06:57 +08:00
parent a87e03456e
commit 21b1a1f988
4 changed files with 47 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
USER_STATUS.md
View File

@@ -6,7 +6,7 @@
Stage 2A Authorized: foreground G2 may start under runbook.
Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane`. CORRECTION recorded a fresh T13 PASS, so T9 may proceed under `docs/G2_RUNBOOK.md`; T10 must wait until T9 produces a matching non-secret pairing request ID or pending node ID.
Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane`. CORRECTION recorded a fresh T13 PASS, so T9 may proceed under `docs/G2_RUNBOOK.md` using a user-run local PowerShell token/node flow; T10 must wait until T9 produces a matching non-secret pairing request ID or pending node ID.
## Completed
@@ -34,7 +34,7 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
- 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.
- CORRECTION may monitor T13 for sync, secret, role, and freeze risks.
- PC_EXECUTOR may claim T9, write the required rollback note, set the Gateway token only in the local shell/session without recording it, and run only the foreground PC node flow in `docs/G2_RUNBOOK.md`.
- PC_EXECUTOR may claim T9, confirm or refresh the required rollback note, give the user the dedicated local PowerShell command template, and collect only non-secret status from the user-run foreground PC node flow in `docs/G2_RUNBOOK.md`.
- VPS_EXECUTOR may not act yet; T10 waits for T9 evidence with a matching non-secret pairing request/node ID.
## Forbidden Actions
@@ -42,7 +42,8 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
- 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 T10 until T9 produces a matching non-secret pairing request/node ID.
- Do not record, print, commit, or chat-send `OPENCLAW_GATEWAY_TOKEN`; token may only be set locally by PC_EXECUTOR within T9.
- Do not record, print, commit, or chat-send `OPENCLAW_GATEWAY_TOKEN`; token may only be set by the user in a dedicated local PC PowerShell terminal during T9.
- PC_EXECUTOR must not receive the token, paste it into an Agent shell, or run the token-bearing foreground node flow directly.
- 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.
@@ -51,7 +52,7 @@ Fresh second G2 authorization was reconfirmed for ORCHESTRATOR in `D:\openclaw-c
## Single Recommended Next Step
PC_EXECUTOR should claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, and follow only the foreground node flow in `docs/G2_RUNBOOK.md`.
PC_EXECUTOR should claim T9, confirm or refresh `rollback/pc-g2-node-run-YYYYMMDD.md`, give the user the dedicated local PowerShell command template, and collect only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.
## User Decision Needed
@@ -83,7 +84,7 @@ No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G
- G2 runbook: `docs/G2_RUNBOOK.md` complete.
- G2 authorization card: `docs/G2_AUTHORIZATION_CARD.md` prepared for user review.
- G2 authorization: fresh second authorization reconfirmed for foreground PC node run and corresponding VPS pairing approval only.
- Next work: T9 foreground PC node run by PC_EXECUTOR.
- Next work: T9 user-run foreground PC node flow guided by PC_EXECUTOR.
- Public website freeze: still active.
- Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden.
@@ -95,4 +96,4 @@ No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G
- Blocked: T10/VPS approval until T9 produces one matching non-secret pairing request/node ID. G3 and G4 remain closed.
- Safety constraints: no secret recording, no `openclaw node install/start`, no service persistence, no Nginx/Docker/website/firewall/network changes.
- Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
- Single next action: PC_EXECUTOR claims T9, confirms or refreshes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
- Single next action: PC_EXECUTOR claims T9, confirms or refreshes `rollback/pc-g2-node-run-YYYYMMDD.md`, gives the user the dedicated local PowerShell command template, then records only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.

20
handoff/ORCHESTRATOR.md
View File

@@ -6,7 +6,7 @@ Own requirements alignment, task decomposition, dependency tracking, and final a
## Current Objective
Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: T13 has recorded a fresh PASS, T9 is released for PC_EXECUTOR, and T10 remains blocked until T9 evidence provides one matching non-secret request/node ID.
Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`: T13 has recorded a fresh PASS, T9 uses a user-run local PowerShell token/node model, and T10 remains blocked until T9 evidence provides one matching non-secret request/node ID.
## Must Read
@@ -39,7 +39,7 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
1. Keep `USER_STATUS.md` current when gate, blocker, heartbeat, or required user decision changes.
2. Keep T7/CORRECTION monitoring active for sync-health, drift, missing evidence, and freeze-policy risk.
3. Keep CORRECTION monitoring T13 for sync/secret/freeze guardrails during T9.
4. Let PC_EXECUTOR claim T9, confirm or refresh `rollback/pc-g2-node-run-YYYYMMDD.md`, set token only in the same local shell/session without recording it, and run only the foreground node command in `docs/G2_RUNBOOK.md`.
4. Let PC_EXECUTOR claim T9, confirm or refresh `rollback/pc-g2-node-run-YYYYMMDD.md`, give the user the dedicated local PowerShell command template, and collect only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.
5. Keep T10 blocked until T9 evidence includes a matching non-secret pairing request ID or pending node ID.
6. Continue forbidding service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, G3 smoke test, G4 setup, and recording any token or secret.
@@ -50,6 +50,16 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
## Last Update
2026-05-19 17:05 UTC+8: ORCHESTRATOR corrected the T9 token execution model, without executing G2.
- Repeated T9 `blocked` states were caused by an invalid assumption that the Agent shell could safely receive `OPENCLAW_GATEWAY_TOKEN` from a separate user PowerShell session.
- Corrected model: the user sets `OPENCLAW_GATEWAY_TOKEN` and runs foreground `openclaw node run` in a dedicated local PC PowerShell terminal.
- PC_EXECUTOR must not request, read, print, record, or handle the token and does not need to run `openclaw node run` in the Agent shell.
- PC_EXECUTOR should confirm or refresh rollback guidance, provide the user command template, warn not to send the token to chat/files, then collect only non-secret status and any non-secret pairing request ID or pending node ID.
- `docs/G2_RUNBOOK.md`, `tasks/T9-G2-PC-node-run.md`, and `USER_STATUS.md` were updated to reflect this model.
- T9 is ready for the user-manual token and foreground node step. T10 remains blocked until T9 produces one matching non-secret pairing request/node ID.
- ORCHESTRATOR did not execute PC/VPS commands, did not handle a token, did not start a node, did not approve pairing, and did not change services.
2026-05-19 16:52 UTC+8: ORCHESTRATOR reconciled T9 task-file state with the existing release, without executing G2.
- `git pull` returned already up to date.
@@ -140,7 +150,7 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
## G2 Planning State
- T9: PC foreground node run, ready after fresh T13 PASS with healthy sync; PC_EXECUTOR must still ensure same-session token availability without disclosure.
- T9: PC foreground node run, ready after fresh T13 PASS with healthy sync; user performs token setup and foreground node run in a dedicated local PC PowerShell terminal, while PC_EXECUTOR records only non-secret status.
- T10: VPS pairing approval, blocked until T9 evidence.
- T11: PC G2 verification, draft.
- T12: VPS G2 verification and freeze compliance, draft.
@@ -170,13 +180,13 @@ Safety constraints:
Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
Single next action: PC_EXECUTOR claims T9, writes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
Single next action: PC_EXECUTOR claims T9, confirms or refreshes `rollback/pc-g2-node-run-YYYYMMDD.md`, gives the user the dedicated local PowerShell command template, then records only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.
Resume prompt:
```text
You are ORCHESTRATOR resuming OpenClaw G2.
Read USER_STATUS.md, AGENT_BOARD.md, handoff/ORCHESTRATOR.md, tasks/T9-G2-PC-node-run.md, tasks/T10-G2-VPS-pairing-approve.md, tasks/T13-G2-correction-guard.md, docs/G2_RUNBOOK.md, and sync-state/README.md.
Current state: G2 is In Progress under limited runbook scope; T13 has fresh PASS; T9 is Ready for PC_EXECUTOR under docs/G2_RUNBOOK.md; T10 is Blocked until T9 produces one matching non-secret pairing request/node ID.
Current state: G2 is In Progress under limited runbook scope; T13 has fresh PASS; T9 is Ready for PC_EXECUTOR to guide a user-run local PowerShell token/node flow under docs/G2_RUNBOOK.md; T10 is Blocked until T9 produces one matching non-secret pairing request/node ID.
Do not execute PC/VPS commands from ORCHESTRATOR. Do not handle or record secrets. Keep G3/G4 closed.
```

6
sync-state/heartbeat-pc.json
View File

@@ -1,9 +1,9 @@
{
"host": "pc",
"time": "2026-05-19T17:05:53+08:00",
"time": "2026-05-19T17:06:56+08:00",
"branch": "main",
"head": "c8560b4",
"status": "clean",
"head": "a87e034",
"status": "dirty",
"intervalSeconds": 30,
"heartbeatEverySeconds": 60
}

32
tasks/T9-G2-PC-node-run.md
View File

@@ -2,7 +2,7 @@
## Status
blocked
ready
## Owner
@@ -18,7 +18,7 @@ PC_EXECUTOR
## Scope
Prepare and run the Windows PC OpenClaw node in foreground mode for Gateway pairing.
Prepare the Windows PC OpenClaw node foreground pairing flow, with the user running token setup and `openclaw node run` manually in a dedicated local PowerShell terminal.
This task is not ready until ORCHESTRATOR records explicit user authorization for G2. It does not authorize service installation, startup persistence, firewall changes, network changes, or any public port exposure.
@@ -28,7 +28,16 @@ This task is not ready until ORCHESTRATOR records explicit user authorization fo
- Sync-health has been confirmed healthy and T7 sync-health blocked state is cleared.
- Fresh second G2 authorization was recorded by ORCHESTRATOR on 2026-05-19 for target window ORCHESTRATOR in `D:\openclaw-control-plane`.
- 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, public port exposure, G3 smoke testing, or G4 service setup.
- Authorization covers only user-run local-session token use without disclosure and user-run foreground `openclaw node run`; it does not authorize Agent-shell token use, service changes, firewall changes, network changes, persistence, public port exposure, G3 smoke testing, or G4 service setup.
## Execution Model - 2026-05-19 17:05 UTC+8
- ORCHESTRATOR corrected T9 to use a user-run local terminal model.
- PC_EXECUTOR must not request, read, print, record, or handle `OPENCLAW_GATEWAY_TOKEN`.
- PC_EXECUTOR does not need to run `openclaw node run` in the Agent shell.
- The user opens a dedicated local PC PowerShell terminal, sets `OPENCLAW_GATEWAY_TOKEN` only in that terminal, and runs the foreground node command in the same terminal.
- PC_EXECUTOR provides the command template, confirms/refreshes rollback guidance, reminds the user not to send the token to chat or files, and records only non-secret status plus any non-secret pairing request ID or pending node ID.
- T9 is `ready` for this user-manual token and foreground node step. T10 remains blocked until T9 produces one matching non-secret pairing request/node ID.
## Blocker - 2026-05-19 15:56 UTC+8
@@ -68,21 +77,23 @@ This task is not ready until ORCHESTRATOR records explicit user authorization fo
- No token value was read, printed, recorded, committed, or chat-sent.
- No service, scheduled task, firewall, network, environment persistence, public-port exposure, G3 smoke test, or G4 persistence change was performed.
- Evidence: `evidence/pc-g2-node-run-20260519.md`.
- T9 is blocked until the token is available in the same non-persistent local PowerShell session that will run the foreground node, without printing or recording the token value.
- This blocker is covered by the 2026-05-19 17:05 UTC+8 execution-model correction: the token is expected to remain only in the user's dedicated local PowerShell terminal, not in the Agent shell.
- T9 is ready again for PC_EXECUTOR to guide the user-run local terminal flow without handling the token.
## Required Evidence
- `rollback/pc-g2-node-run-YYYYMMDD.md` written before token or node-run action.
- Confirmation that `OPENCLAW_GATEWAY_TOKEN` was set only in the local shell/session and that the token value was not printed or recorded.
- Exact foreground node command used, without secrets.
- Connection status summary and non-secret pairing request ID or pending node ID if shown.
- `rollback/pc-g2-node-run-YYYYMMDD.md` confirmed or refreshed before user token or node-run action.
- Confirmation that PC_EXECUTOR provided the user command template and warned the user not to send the token to chat/files.
- Confirmation that the user reported `OPENCLAW_GATEWAY_TOKEN` was set only in a dedicated local PC PowerShell terminal and that the token value was not printed or recorded.
- Exact foreground node command template used, without secrets.
- Non-secret connection status summary and non-secret pairing request ID or pending node ID if shown.
- Confirmation that no `openclaw node install`, `start`, `restart`, `stop`, `uninstall`, firewall, network, scheduled task, environment persistence, or public-port exposure change was performed.
- Evidence written to `evidence/pc-g2-node-run-YYYYMMDD.md`.
- `handoff/PC_EXECUTOR.md` updated.
## Command Drafts
Authorized only within `docs/G2_RUNBOOK.md` and only on the Windows PC by PC_EXECUTOR. Do not record the token value.
Authorized only within `docs/G2_RUNBOOK.md` and only for the user to run in a dedicated local PC PowerShell terminal. PC_EXECUTOR must not execute this in the Agent shell or record the token value.
```powershell
$env:OPENCLAW_GATEWAY_TOKEN = "<user-pastes-token-locally>"
@@ -102,6 +113,7 @@ openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-na
- `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.
- PC_EXECUTOR is asked to receive the token, paste it into an Agent shell, or run the token-bearing flow directly.
- Any step requires PC service install/start, scheduled task changes, firewall changes, network changes, or public port exposure.
- Gateway host or display name differs from the runbook without ORCHESTRATOR review.
@@ -113,5 +125,5 @@ PC_VERIFIER must review this evidence before ORCHESTRATOR can count the PC half
- Status at freeze: ready.
- Next owner: PC_EXECUTOR.
- Single next action: claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, then follow only the foreground node flow in `docs/G2_RUNBOOK.md`.
- Single next action: claim T9, confirm or refresh `rollback/pc-g2-node-run-YYYYMMDD.md`, give the user the local terminal command template, and collect only non-secret status from the user-run foreground node flow in `docs/G2_RUNBOOK.md`.
- Do not record token values, install/start services, change firewall/network state, expose public ports, or start G3/G4 work.