openclaw-control-plane/rollback/pc-g2-node-run-20260519.md

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

Owner: PC_EXECUTOR

Scope

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

Intended Change

• Set OPENCLAW_GATEWAY_TOKEN only in the local PC shell session.
• Run the PC node in foreground mode with:

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

Current State Before Action

• T9 is ready.
• T10 remains blocked until T9 produces one matching non-secret pairing request ID or pending node ID.
• T13 fresh guard PASS is recorded in tasks/T13-G2-correction-guard.md at 2026-05-19 16:29 UTC+8 and released by ORCHESTRATOR in AGENT_BOARD.md.
• Sync-health is not blocked: PC and VPS heartbeats are present and clean, and no sync-state/error-*.md files are present.
• 2026-05-19 16:55 UTC+8 pre-run check: git pull --ff-only reported already up to date; tasks/T9-G2-PC-node-run.md top-level status is ready; PC heartbeat was clean at 2026-05-19T16:55:01+08:00; VPS heartbeat was clean at 2026-05-19T16:55:28+0800; no sync-state/error-*.md files were present; no stale openclaw process was found.
• 2026-05-19 16:39 UTC+8 pre-run check: git pull --ff-only reported already up to date; PC heartbeat was clean at 2026-05-19T16:39:26+08:00; VPS heartbeat was clean at 2026-05-19T16:39:14+0800.
• No G2 PC service persistence is installed by this task.
• 2026-05-19 15:56 UTC+8 pre-run check: local workspace is D:\openclaw-control-plane, git pull --ff-only reported already up to date, local HEAD matches origin/main, and no sync error files are present.

Rollback Steps

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

Secret Handling

• Do not record, print, commit, or chat-send any token or secret value.
• Evidence may record only that the token was set in the local shell session and that its value was not displayed or recorded.