diff --git a/evidence/pc-g2-node-run-20260519.md b/evidence/pc-g2-node-run-20260519.md
deleted file mode 100644
index e61ee41..0000000
--- a/evidence/pc-g2-node-run-20260519.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# PC G2 Foreground Node Run Evidence - 2026-05-19
-
-Owner: PC_EXECUTOR
-
-Scope: T9 G2 PC foreground node run under `docs/G2_RUNBOOK.md`.
-
-## Status
-
-Blocked before foreground node run.
-
-## Pre-Run Confirmation
-
-- Target role/workspace confirmed: PC_EXECUTOR in `D:\openclaw-control-plane`.
-- `git pull --ff-only` returned already up to date.
-- G2 status confirmed as authorized and `In Progress`.
-- T13 fresh guard PASS confirmed from `tasks/T13-G2-correction-guard.md` and `AGENT_BOARD.md`.
-- T9 status confirmed as `ready` before token check.
-- T10 status confirmed as `blocked`.
-- Sync-health confirmed healthy from clean PC/VPS heartbeat files and no observed `sync-state/error-*.md` files.
-- Rollback note confirmed/refreshed: `rollback/pc-g2-node-run-20260519.md`.
-
-## Token Handling
-
-- User confirmed token was set locally.
-- PC_EXECUTOR performed only a non-secret presence check.
-- Presence check output: `OPENCLAW_GATEWAY_TOKEN_PRESENT=false`.
-- No token value was read, printed, recorded, committed, or chat-sent.
-
-## Foreground Node Command
-
-Planned command:
-
-```powershell
-openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"
-```
-
-Result: not executed, because the token was not present in the Agent execution shell.
-
-## Pairing Identity
-
-- Pairing request ID: not produced.
-- Pending node ID: not produced.
-
-## Safety Confirmation
-
-- No `openclaw node run` command was executed.
-- No `openclaw node install`, `start`, `restart`, `stop`, or `uninstall` command was executed.
-- No service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed.
-- No G3 smoke test or G4 persistence work was started.
-
-## Blocker
-
-T9 remains blocked until `OPENCLAW_GATEWAY_TOKEN` is available in the same non-persistent local shell session that will run the foreground node, without printing or recording the token value.
diff --git a/handoff/PC_EXECUTOR.md b/handoff/PC_EXECUTOR.md
index c8f6d54..a63fd43 100644
--- a/handoff/PC_EXECUTOR.md
+++ b/handoff/PC_EXECUTOR.md
@@ -38,23 +38,18 @@ After the Gitea control plane is synchronized, collect current PC baseline evide
 
 ## Last Update
 
-2026-05-19 16:39 PC_EXECUTOR T9 foreground node flow stopped before node run.
+2026-05-19 16:20 PC_EXECUTOR T9 execution request stopped before token/node action.
 
 - Target role/workspace matched: PC_EXECUTOR in `D:\openclaw-control-plane`.
 - `git pull --ff-only` returned already up to date.
-- G2 authorization and `In Progress` state confirmed from `USER_STATUS.md` and `AGENT_BOARD.md`.
-- T13 fresh guard PASS confirmed from `tasks/T13-G2-correction-guard.md` and `AGENT_BOARD.md`.
-- T9 was `ready` before token presence check; T10 remained `blocked`.
-- Sync-health was healthy from clean PC/VPS heartbeat files and no observed `sync-state/error-*.md` files.
-- Rollback note refreshed: `rollback/pc-g2-node-run-20260519.md`.
-- Evidence written: `evidence/pc-g2-node-run-20260519.md`.
-- User confirmed token setup locally, but the Agent execution shell reported `OPENCLAW_GATEWAY_TOKEN_PRESENT=false`.
-- `openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"` was not executed.
-- T9 was returned to `blocked` until the token is available in the same non-persistent local shell session that will run the foreground node, without printing or recording the token value.
+- `tasks/T9-G2-PC-node-run.md` currently says `blocked`, with blocker that the Agent execution shell did not have `OPENCLAW_GATEWAY_TOKEN` in the same non-persistent local shell session.
+- `AGENT_BOARD.md` shows T9 as Ready and T10 as Blocked, but the assigned task file is blocked; per role-confirmation rules, execution agents must not execute blocked tasks.
+- T13 guard PASS was not confirmed from the required files; `AGENT_BOARD.md` shows T13 as Ready, not PASS.
+- No rollback/evidence for this new attempt was written, because T9 did not pass pre-execution confirmation.
 - No token was requested, read, printed, recorded, committed, or chat-sent.
 - No `openclaw node run`, `install`, `start`, `stop`, or persistence command was executed.
 - No service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed.
-- No G3 smoke test or G4 persistence work was started.
+- Await ORCHESTRATOR/CORRECTION to clear the blocked T9 state and confirm T13 guard PASS before retrying T9.
 
 Earlier T9 instructions remain the safety boundary after unblock: