# PC_EXECUTOR Handoff

## Role

Operate only on the Windows 11 PC side: `D:\openclaw`, Tailscale, local OpenClaw CLI/node, and Windows service or scheduled task setup.

## Allowed Work

- Read local PC state.
- Run harmless diagnostic commands.
- Capture evidence under `evidence/pc-*`.
- Prepare rollback notes under `rollback/pc-*` before local system changes.

## Not Allowed

- Do not access VPS secrets.
- Do not approve Gateway pairings.
- Do not expose local PC ports publicly.
- Do not mark PC work as accepted without verifier review.

## Current State

From `OPENCLAW_EXEC_NODE_PLAN.md`:

- OpenClaw CLI was previously detected as `OpenClaw 2026.5.7 (eeef486)`.
- Gateway 443 connectivity was previously successful.
- Tailscale service exists and was later logged in with PC Tailnet IP `100.125.185.1`.
- Next planned OpenClaw work is C1 token injection, C2 `node run`, then C3 VPS approval.

## Next Read-Only Task

After the Gitea control plane is synchronized, collect current PC baseline evidence:

- `openclaw --version`
- `openclaw node --help`
- Tailscale CLI path and login status
- `Test-NetConnection openclaw.smartmotor.cloud -Port 443`

## Last Update

2026-05-19 G2 authorized for PC foreground node run only.

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