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 16:26:32

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 16:26:32 +08:00
parent 0ef1d50a3e
commit d4361a6de9
5 changed files with 34 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
AGENT_BOARD.md
View File

@@ -64,7 +64,7 @@ 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 | Fresh user G2 authorization, T7 healthy | Ready |
| T9 | G2 PC foreground node run | PC_EXECUTOR | Fresh user G2 authorization, fresh T13 PASS, 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 |
@@ -100,7 +100,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con
## G2 Authorization Boundary
- Fresh second G2 authorization was received on 2026-05-19 for ORCHESTRATOR in `D:\openclaw-control-plane`; T13 and T9 may proceed under `docs/G2_RUNBOOK.md`.
- Fresh second G2 authorization was received on 2026-05-19 for ORCHESTRATOR in `D:\openclaw-control-plane`; T13 may proceed under `docs/G2_RUNBOOK.md`, but T9 is blocked until CORRECTION records a fresh T13 PASS with healthy sync.
- `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.
- T10 remains blocked until T9 evidence contains a matching non-secret pairing request ID or pending node ID.
- G2 must remain foreground-only for the PC node; service persistence belongs to G4.

51
evidence/pc-g2-node-run-20260519.md
View File

@@ -1,51 +0,0 @@
# PC G2 Foreground Node Run Evidence - 2026-05-19
Owner: PC_EXECUTOR
Task: T9 - G2 PC foreground node run
## Result
Stopped before `openclaw node run`.
## Pre-Run Confirmation
- Target role confirmed: PC_EXECUTOR.
- Workspace confirmed: `D:\openclaw-control-plane`.
- `git pull --ff-only` completed and reported already up to date.
- G2 authorization was present in `USER_STATUS.md` and `AGENT_BOARD.md`.
- T13 pre-flight guard recorded PASS, and current sync check found no `sync-state/error-*.md` files.
- T9 was `ready`.
- T10 remained `blocked` until T9 produces one matching non-secret pairing request ID or pending node ID.
- Rollback note updated before token/node action: `rollback/pc-g2-node-run-20260519.md`.
## Token Handling
- The user confirmed token setup in a local PC shell.
- Before running the node, PC_EXECUTOR checked only whether the token key was present in the Agent execution shell.
- The Agent execution shell reported `OPENCLAW_GATEWAY_TOKEN_PRESENT=false`.
- No token value was read, printed, recorded, committed, or chat-sent.
## Node Command
The authorized foreground command was not executed:
```powershell
openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"
```
## Blocker
The Agent execution shell could not read `OPENCLAW_GATEWAY_TOKEN` as a session environment variable. Running the foreground node from this shell would likely fail or drift from the runbook.
## Safety Confirmation
- No `openclaw node run` command was executed.
- No `openclaw node install`, `start`, `restart`, `stop`, or `uninstall` command was executed.
- No service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed.
- No Gateway/VPS approval command was executed.
- No pairing request ID or pending node ID was produced.
## Next Required Action
T9 remains blocked for PC_EXECUTOR until the token is available in the same non-persistent local shell session that will run the foreground node, without printing or recording the token value.

22
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 guard and T9 foreground PC node run may proceed; 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 guard must record a fresh PASS before T9 can resume; T10 remains blocked until T9 evidence provides one matching non-secret request/node ID.
## Must Read
@@ -29,7 +29,7 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
- `USER_STATUS.md` is the user-facing status entry; internal agent ledgers should not be required reading for the user.
- Fresh second G2 authorization was received and reconfirmed for ORCHESTRATOR in `D:\openclaw-control-plane` on 2026-05-19.
- `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.
- Sync-health is not currently cleared for T9: latest tracked PC and VPS heartbeats are clean but stale relative to the 5-minute blocked threshold, 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 is In Progress under the limited runbook scope.
- The polling sync is intentionally temporary; design an async notification/coordinator layer when PC/VPS baseline work is stable.
- Filing-review freeze path wording has been corrected from the obsolete single `docker-composite.yml` reference to `/opt/services/docker-compose.openclaw.yml` plus any equivalent compose/service entries that could affect public website output.
@@ -38,8 +38,8 @@ 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. Let CORRECTION claim T13 and verify sync/secret/freeze guardrails before or alongside T9.
4. Let PC_EXECUTOR claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, set token only in the local shell/session without recording it, and run only the foreground node command in `docs/G2_RUNBOOK.md`.
3. Require CORRECTION to rerun T13 and record a fresh PASS with healthy sync/secret/freeze guardrails before T9 resumes.
4. Keep PC_EXECUTOR blocked on T9 until that fresh T13 PASS exists; after unblock, PC_EXECUTOR may write `rollback/pc-g2-node-run-YYYYMMDD.md`, set token only in the local shell/session without recording it, and run only the foreground node command 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 16:24 UTC+8: ORCHESTRATOR reconciled G2 execution state without executing G2.
- `git pull` returned already up to date.
- `tasks/T13-G2-correction-guard.md` and `handoff/CORRECTION.md` contain a prior 14:50 pre-flight PASS, but no fresh current PASS after PC_EXECUTOR's 16:20 stop.
- Current tracked sync heartbeats are clean but stale for the 5-minute blocked threshold: PC `2026-05-19T16:18:46+08:00`, VPS `2026-05-19T16:18:22+0800`.
- `sync-state/` contains `README.md`, `heartbeat-pc.json`, and `heartbeat-vps.json`; no tracked `error-*.md` files were observed.
- `tasks/T9-G2-PC-node-run.md` is already blocked because token was not available in the same non-persistent local shell session and `openclaw node run` was not executed.
- `AGENT_BOARD.md` was corrected so T9 is Blocked pending fresh T13 PASS and healthy sync. T10 remains Blocked pending one matching non-secret T9 pairing request/node ID.
- ORCHESTRATOR did not execute PC/VPS commands, did not handle a token, did not start a node, and did not approve pairing.
2026-05-19 12:27 UTC+8: ORCHESTRATOR took over after role-misdirection audit and paused G2 execution.
- VPS_VERIFIER self-reported that prompts intended for ORCHESTRATOR were mistakenly sent to VPS_VERIFIER.
@@ -109,7 +119,7 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
## G2 Planning State
- T9: PC foreground node run, ready.
- T9: PC foreground node run, blocked pending fresh T13 PASS with healthy sync and same-session token availability.
- T10: VPS pairing approval, blocked until T9 evidence.
- T11: PC G2 verification, draft.
- T12: VPS G2 verification and freeze compliance, draft.
@@ -146,6 +156,6 @@ 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 and T9 are Ready; 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 is Ready for a fresh guard check; T9 is Blocked until fresh T13 PASS with healthy sync; 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.
```

27
handoff/PC_EXECUTOR.md
View File

@@ -38,24 +38,23 @@ After the Gitea control plane is synchronized, collect current PC baseline evide
## Last Update
2026-05-19 T9 attempted pre-run setup but stopped before `openclaw node run`.
2026-05-19 16:20 PC_EXECUTOR T9 execution request stopped before token/node action.
- Target role/workspace confirmed: PC_EXECUTOR in `D:\openclaw-control-plane`.
- `git pull --ff-only` reported already up to date.
- G2 authorization was present, T13 pre-flight guard recorded PASS, T9 was `ready`, and T10 remained `blocked`.
- Rollback note updated: `rollback/pc-g2-node-run-20260519.md`.
- User confirmed token setup in a local PC shell, but the Agent execution shell reported only `OPENCLAW_GATEWAY_TOKEN_PRESENT=false`.
- No token value was read, printed, recorded, committed, or chat-sent.
- `openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"` was not executed.
- No node install/start/restart/stop/uninstall, service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed.
- Evidence written: `evidence/pc-g2-node-run-20260519.md`.
- Blocker: token is not available in the same non-persistent Agent execution shell that would run the foreground node.
- Target role/workspace matched: PC_EXECUTOR in `D:\openclaw-control-plane`.
- `git pull --ff-only` returned already up to date.
- `tasks/T9-G2-PC-node-run.md` currently says `blocked`, with blocker that the Agent execution shell did not have `OPENCLAW_GATEWAY_TOKEN` in the same non-persistent local shell session.
- `AGENT_BOARD.md` shows T9 as Ready and T10 as Blocked, but the assigned task file is blocked; per role-confirmation rules, execution agents must not execute blocked tasks.
- T13 guard PASS was not confirmed from the required files; `AGENT_BOARD.md` shows T13 as Ready, not PASS.
- No rollback/evidence for this new attempt was written, because T9 did not pass pre-execution confirmation.
- No token was requested, read, printed, recorded, committed, or chat-sent.
- No `openclaw node run`, `install`, `start`, `stop`, or persistence command was executed.
- No service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed.
- Await ORCHESTRATOR/CORRECTION to clear the blocked T9 state and confirm T13 guard PASS before retrying T9.
2026-05-19 fresh second G2 authorization recorded for T9.
Earlier T9 instructions remain the safety boundary after unblock:
- T9 is ready for PC_EXECUTOR under `docs/G2_RUNBOOK.md`.
- Before token or node-run action, write `rollback/pc-g2-node-run-YYYYMMDD.md`.
- Set `OPENCLAW_GATEWAY_TOKEN` only in the local shell/session and never record, print, commit, or paste the token value.
- Set `OPENCLAW_GATEWAY_TOKEN` only in the same local shell/session that will run the foreground node and never record, print, commit, or paste the token value.
- Run only the foreground node flow from the runbook.
- Do not run `openclaw node install`, `openclaw node start`, service persistence, scheduled task, firewall, network, or public-port exposure changes.
- Evidence should go to `evidence/pc-g2-node-run-YYYYMMDD.md` and must include no secrets.

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

@@ -1,9 +1,9 @@
{
"host": "pc",
"time": "2026-05-19T16:18:46+08:00",
"time": "2026-05-19T16:26:31+08:00",
"branch": "main",
"head": "084fafc",
"status": "clean",
"head": "0ef1d50",
"status": "dirty",
"intervalSeconds": 30,
"heartbeatEverySeconds": 60
}