diff --git a/USER_STATUS.md b/USER_STATUS.md
index 2e0518d..ad99a25 100644
--- a/USER_STATUS.md
+++ b/USER_STATUS.md
@@ -86,3 +86,13 @@ No additional user decision is needed for T9 if PC_EXECUTOR stays within `docs/G
 - Next work: T13 guard and T9 foreground PC node run.
 - Public website freeze: still active.
 - Mutation/setup phase: limited G2 foreground pairing may start; service persistence and infrastructure changes remain forbidden.
+
+## Session Freeze
+
+- Freeze time: 2026-05-19 14:46 UTC+8.
+- Current phase: G2 limited foreground pairing is authorized under `docs/G2_RUNBOOK.md`.
+- Completed: G0A, G0B, G1, G2 runbook, role-misdirection recovery, and second G2 authorization.
+- Blocked: T10/VPS approval until T9 produces one matching non-secret pairing request/node ID. G3 and G4 remain closed.
+- Safety constraints: no secret recording, no `openclaw node install/start`, no service persistence, no Nginx/Docker/website/firewall/network changes.
+- Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
+- Single next action: PC_EXECUTOR claims T9, writes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md
index ee5a584..a9431af 100644
--- a/handoff/ORCHESTRATOR.md
+++ b/handoff/ORCHESTRATOR.md
@@ -115,3 +115,37 @@ Coordinate freshly authorized G2 execution strictly under `docs/G2_RUNBOOK.md`:
 - T12: VPS G2 verification and freeze compliance, draft.
 - T13: G2 correction guard, ready.
 - Authorization judgment: fresh second authorization is valid only for the G2 runbook scope and expires if sync blocks, role/workspace mismatches, secrets appear, pairing identity is ambiguous, steps drift from the runbook, or freeze risk appears.
+
+## Session Freeze - 2026-05-19 14:46 UTC+8
+
+Current phase: G2 limited foreground pairing is authorized under `docs/G2_RUNBOOK.md`.
+
+Completed:
+
+- G0A, G0B, and G1 accepted.
+- Role-misdirection recovery completed and second G2 authorization reconfirmed.
+- G2 control plane opened only for T13 and T9.
+
+Blocked:
+
+- T10 remains blocked until T9 evidence contains one matching non-secret pairing request/node ID.
+- G3 smoke test and G4 persistence remain closed.
+
+Safety constraints:
+
+- Do not record secrets or `OPENCLAW_GATEWAY_TOKEN`.
+- Do not run `openclaw node install/start`.
+- Do not perform service persistence, service restart, Nginx/Docker/website/firewall/network changes, or public port exposure.
+
+Next owner: PC_EXECUTOR for T9, with CORRECTION monitoring T13.
+
+Single next action: PC_EXECUTOR claims T9, writes `rollback/pc-g2-node-run-YYYYMMDD.md`, then follows only the foreground node flow in `docs/G2_RUNBOOK.md`.
+
+Resume prompt:
+
+```text
+You are ORCHESTRATOR resuming OpenClaw G2.
+Read USER_STATUS.md, AGENT_BOARD.md, handoff/ORCHESTRATOR.md, tasks/T9-G2-PC-node-run.md, tasks/T10-G2-VPS-pairing-approve.md, tasks/T13-G2-correction-guard.md, docs/G2_RUNBOOK.md, and sync-state/README.md.
+Current state: G2 is In Progress under limited runbook scope; T13 and T9 are Ready; T10 is Blocked until T9 produces one matching non-secret pairing request/node ID.
+Do not execute PC/VPS commands from ORCHESTRATOR. Do not handle or record secrets. Keep G3/G4 closed.
+```
diff --git a/sync-state/heartbeat-pc.json b/sync-state/heartbeat-pc.json
index e5b5661..68b2d2e 100644
--- a/sync-state/heartbeat-pc.json
+++ b/sync-state/heartbeat-pc.json
@@ -1,9 +1,9 @@
 {
     "host":  "pc",
-    "time":  "2026-05-19T14:46:03+08:00",
+    "time":  "2026-05-19T14:47:05+08:00",
     "branch":  "main",
-    "head":  "b320e69",
-    "status":  "clean",
+    "head":  "4373564",
+    "status":  "dirty",
     "intervalSeconds":  30,
     "heartbeatEverySeconds":  60
 }
diff --git a/tasks/T10-G2-VPS-pairing-approve.md b/tasks/T10-G2-VPS-pairing-approve.md
index cc5cd29..e0dfe6c 100644
--- a/tasks/T10-G2-VPS-pairing-approve.md
+++ b/tasks/T10-G2-VPS-pairing-approve.md
@@ -65,3 +65,11 @@ docker exec openclaw-gateway node openclaw.mjs nodes approve <nodeId>
 ## Acceptance
 
 VPS_VERIFIER must review this evidence before ORCHESTRATOR can count the VPS half of G2 as accepted.
+
+## Session Freeze - 2026-05-19 14:46 UTC+8
+
+- Status at freeze: blocked.
+- Blocker: waiting for T9 evidence with one matching non-secret pairing request ID or pending node ID.
+- Next owner after unblock: VPS_EXECUTOR.
+- Do not run `nodes pending`, `devices approve`, or `nodes approve` until ORCHESTRATOR opens T10 after T9 evidence exists.
+- Do not restart/reload services, change Gateway config, edit Nginx/Docker/website state, or record secrets.
diff --git a/tasks/T9-G2-PC-node-run.md b/tasks/T9-G2-PC-node-run.md
index 5c0b2f5..895309b 100644
--- a/tasks/T9-G2-PC-node-run.md
+++ b/tasks/T9-G2-PC-node-run.md
@@ -68,3 +68,10 @@ openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-na
 ## Acceptance
 
 PC_VERIFIER must review this evidence before ORCHESTRATOR can count the PC half of G2 as accepted.
+
+## Session Freeze - 2026-05-19 14:46 UTC+8
+
+- Status at freeze: ready.
+- Next owner: PC_EXECUTOR.
+- Single next action: claim T9, write `rollback/pc-g2-node-run-YYYYMMDD.md`, then follow only the foreground node flow in `docs/G2_RUNBOOK.md`.
+- Do not record token values, install/start services, change firewall/network state, expose public ports, or start G3/G4 work.