PC G2 Foreground Node Run Rollback - 2026-05-21

Owner: PC_EXECUTOR

Scope

This rollback note covers the T9 foreground-only PC node run authorized under docs/G2_RUNBOOK.md.

User sets OPENCLAW_GATEWAY_TOKEN only in a dedicated local PC PowerShell terminal.
User runs the PC node in foreground mode in that same local terminal with:

openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"

PC_EXECUTOR does not receive the token and does not run the token-bearing node flow in the Agent shell.

Target role/workspace: PC_EXECUTOR in D:\openclaw-control-plane.
git pull --ff-only reported already up to date.
tasks/T9-G2-PC-node-run.md top-level status is ready.
AGENT_BOARD.md and USER_STATUS.md show G2 authorized and In Progress.
tasks/T10-G2-VPS-pairing-approve.md remains blocked.
docs/G2_RUNBOOK.md confirms the corrected user-run local PowerShell token/node model.
T13 fresh PASS is recorded in tasks/T13-G2-correction-guard.md at 2026-05-21 16:42 UTC+8.
Sync-health is not blocked: PC heartbeat is clean at 2026-05-21T16:46:11+08:00, VPS heartbeat is clean at 2026-05-21T16:45:28+0800, and no sync-state/error-*.md files are present.
No G2 PC service persistence is installed by this task.

Stop the foreground node process with Ctrl+C in the same dedicated local PowerShell terminal.
Clear the session token by closing the shell or removing the session environment variable without printing its value.
Do not run openclaw node install, openclaw node start, service persistence, scheduled task, firewall, network, or public-port exposure commands.
If the pairing request or node ID is ambiguous, stop the foreground node and record a blocker without approving anything.

Do not record, print, commit, or chat-send any token or secret value.
Evidence may record only that the user reported setting the token in a dedicated local PowerShell terminal and that its value was not displayed or recorded.