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

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.