T9 - G2 PC Foreground Node Run

Status

blocked

Owner

PC_EXECUTOR

Dependencies

G0A complete
G0B complete
G1 accepted
Fresh user authorization after role-misdirection correction
CORRECTION confirms sync-health is not blocked

Scope

Prepare and run the Windows PC OpenClaw node in foreground mode for Gateway pairing.

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.

Planning Status

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.
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.
docs/G2_RUNBOOK.md remains the planned procedure, but it does not authorize token injection or openclaw node run by itself.

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.
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.

$env:OPENCLAW_GATEWAY_TOKEN = "<user-pastes-token-locally>"
openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"

Expected Output

Foreground node process remains running.
Logs show connection attempt to openclaw.smartmotor.cloud.
Pairing request ID or pending node ID appears if approval is required.
No secret value appears in evidence.

Stop Conditions

Fresh user authorization after the role-misdirection correction is absent or ambiguous.
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.
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.

Acceptance

PC_VERIFIER must review this evidence before ORCHESTRATOR can count the PC half of G2 as accepted.

2.8 KiB Raw Blame History