Sync agent state from PC at 2026-05-19 12:28:51

handoff/PC_EXECUTOR.md

@@ -38,12 +38,10 @@ After the Gitea control plane is synchronized, collect current PC baseline evide
 
 ## Last Update
 
-2026-05-19 G2 authorized for PC foreground node run only.
+2026-05-19 G2 execution paused after role-misdirection correction.
 
-- Read `docs/G2_RUNBOOK.md` before acting.
-- T9 is ready for PC_EXECUTOR.
-- 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.
-- 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.
-- Stop immediately if a command prints or asks to store a secret, asks for persistence, changes firewall/network state, or drifts from `docs/G2_RUNBOOK.md`.
+- T9 is blocked and must not be claimed or executed.
+- Do not set or inject `OPENCLAW_GATEWAY_TOKEN`.
+- Do not run `openclaw node run`.
+- Do not run `openclaw node install`, `openclaw node start`, service persistence, scheduled task, firewall, network, or public-port exposure changes.
+- Wait for ORCHESTRATOR to record fresh explicit user authorization after the role-misdirection correction before any G2 action.

handoff/VPS_EXECUTOR.md

@@ -38,13 +38,11 @@ After the Gitea control plane is synchronized, collect current VPS baseline evid
 
 ## Last Update
 
-2026-05-19 G2 authorized for corresponding VPS pairing approval only after PC evidence exists.
+2026-05-19 G2 execution paused after role-misdirection correction.
 
-- Read `docs/G2_RUNBOOK.md` before acting.
-- T10 remains draft until T9 provides a matching non-secret pairing request ID or pending node ID.
-- Before approval action, write `rollback/vps-g2-approve-YYYYMMDD.md`.
-- Approve only the intended PC request/node that matches T9 evidence and display name.
-- Do not run approval commands if multiple pending requests are indistinguishable.
+- T10 is blocked and must not be claimed or executed.
+- Do not run `openclaw devices approve`, `openclaw nodes pending`, or `openclaw nodes approve` for G2.
+- Do not approve any pairing request.
 - Do not request, print, record, rotate, or store any token/password/secret.
 - Do not restart/reload services, change Gateway config, edit Nginx, edit Docker/compose/bind mounts/images, change service state, or alter frozen `smartmotor.cloud` website output.
-- Evidence should go to `evidence/vps-g2-approve-YYYYMMDD.md` and must include no secrets.
+- Wait for ORCHESTRATOR to record fresh explicit user authorization after the role-misdirection correction and for T9 to produce matching non-secret evidence before any VPS-side G2 action.

sync-state/heartbeat-pc.json

@@ -1,9 +1,9 @@
 {
     "host":  "pc",
-    "time":  "2026-05-19T12:27:47+08:00",
+    "time":  "2026-05-19T12:28:51+08:00",
     "branch":  "main",
-    "head":  "aa8b047",
-    "status":  "clean",
+    "head":  "06f0b9e",
+    "status":  "dirty",
     "intervalSeconds":  30,
     "heartbeatEverySeconds":  60
 }

tasks/T10-G2-VPS-pairing-approve.md

@@ -2,7 +2,7 @@
 
 ## Status
 
-draft
+blocked
 
 ## Owner
 
@@ -24,9 +24,9 @@ This task does not authorize service restarts, reloads, token rotation, Gateway
 
 - 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 remains `draft` until T9 produces a non-secret pairing request ID or pending node ID that can be matched to the intended PC node.
-- Authorization covers only the corresponding pairing approval after T9 evidence exists; it does not authorize service restarts/reloads, token rotation, Gateway config mutation, Nginx changes, Docker changes, or frozen website changes.
+- 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 and T9 later produces a matching non-secret request/node ID.
+- `docs/G2_RUNBOOK.md` remains the planned procedure, but it does not authorize VPS approval by itself.
 
 ## Required Evidence
 
@@ -56,7 +56,7 @@ docker exec openclaw-gateway node openclaw.mjs nodes approve <nodeId>
 
 ## 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 VPS_EXECUTOR.
 - Request identity is ambiguous or multiple indistinguishable pending requests exist.
 - A command asks for or prints a token/password.

tasks/T13-G2-correction-guard.md

@@ -2,7 +2,7 @@
 
 ## Status
 
-ready
+blocked
 
 ## Owner
 
@@ -10,7 +10,7 @@ CORRECTION
 
 ## Dependencies
 
-- G2 user authorization recorded by ORCHESTRATOR
+- Fresh G2 user authorization recorded by ORCHESTRATOR after role-misdirection correction
 
 ## Scope
 
@@ -22,15 +22,16 @@ This task does not authorize PC/VPS configuration mutation.
 
 - Confirm `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` are present and fresh before G2 execution starts.
 - Confirm no `sync-state/error-pc.md` or `sync-state/error-vps.md` file exists.
-- Confirm user authorization is limited to foreground PC node run and corresponding VPS pairing approval.
+- Confirm fresh user authorization is limited to foreground PC node run and corresponding VPS pairing approval.
 - Confirm PC and VPS agents can see the same latest G2 task state and evidence through Git.
 - Block G2 if any task bypasses explicit user authorization, records a secret, or risks changing frozen `smartmotor.cloud` website output.
 - Record findings in `handoff/CORRECTION.md` and, if needed, update this task status to `blocked`.
 
 ## Current Authorization
 
-- User authorized G2 on 2026-05-19.
-- Allowed: foreground PC node run under `docs/G2_RUNBOOK.md` and corresponding VPS pairing approval after T9 produces a matching non-secret request/node ID.
+- Role-misdirection audit on 2026-05-19 paused G2 execution.
+- Current state: blocked until ORCHESTRATOR records fresh explicit user authorization after the correction.
+- Planned allowed scope after fresh authorization: foreground PC node run under `docs/G2_RUNBOOK.md` and corresponding VPS pairing approval after T9 produces a matching non-secret request/node ID.
 - Forbidden: service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret.
 
 ## Stop Conditions