Sync agent state from VPS at 2026-05-19 12:08:50

tasks/T11-G2-PC-verify.md

@@ -1,3 +1,60 @@
+# T11 - G2 PC Evidence Verification
+
+## Status
+
+draft
+
+## Owner
+
+PC_VERIFIER
+
+## Dependencies
+
+- T9 produces `evidence/pc-g2-node-run-YYYYMMDD.md`
+- User explicitly authorizes G2 execution before T9 runs
+- CORRECTION confirms sync-health is not blocked
+
+## Scope
+
+Independently verify PC-side G2 evidence after PC_EXECUTOR runs the foreground node task.
+
+This task is evidence review by default. It does not authorize PC mutation, service installation, service start/stop/restart, firewall changes, network changes, scheduled task changes, environment persistence, or public port exposure.
+
+## Planning Status
+
+- G2 pre-execution plan is documented in `docs/G2_RUNBOOK.md`.
+- This task remains `draft` until T9 evidence exists.
+- Planning confirmation does not authorize verifier-side PC commands.
+
+## Required Evidence
+
+- Review `docs/G2_RUNBOOK.md`.
+- Review PC_EXECUTOR evidence from T9.
+- Confirm the node command targeted `openclaw.smartmotor.cloud` and foreground mode.
+- Confirm the token value is absent from evidence, handoffs, logs, commits, and chat.
+- Confirm no `openclaw node install`, `start`, `restart`, `stop`, `uninstall`, firewall, network, scheduled task, environment persistence, or public-port exposure change was performed.
+- Confirm PC-side evidence is synchronized through Git and visible to the VPS side.
+- Write findings to `evidence/verify-pc-g2-YYYYMMDD.md`.
+- Update `handoff/PC_VERIFIER.md`.
+
+## Command Drafts
+
+Do not run PC commands during planning. By default, verification is evidence review only:
+
+```text
+Review PC evidence only. Do not execute PC commands unless a later user instruction explicitly authorizes verifier-side read-only checks.
+```
+
+## Stop Conditions
+
+- T9 evidence is missing, incomplete, or not synchronized.
+- Evidence contains a secret.
+- Evidence shows service persistence, firewall/network mutation, public port exposure, or command drift from `docs/G2_RUNBOOK.md`.
+- PC node identity cannot be tied to the intended Gateway pairing.
+
+## Acceptance
+
+PC_VERIFIER may mark T9 accepted only after non-secret evidence is sufficient. ORCHESTRATOR decides whether PC-side G2 is ready to count toward G2 completion.
 # T11 - G2 PC Verification
 
 ## Status

tasks/T12-G2-VPS-verify.md

@@ -1,3 +1,61 @@
+# T12 - G2 VPS Approval Verification
+
+## Status
+
+draft
+
+## Owner
+
+VPS_VERIFIER
+
+## Dependencies
+
+- T10 produces `evidence/vps-g2-approve-YYYYMMDD.md`
+- User explicitly authorizes VPS-side approval before T10 runs
+- CORRECTION confirms sync-health is not blocked
+
+## Scope
+
+Independently verify VPS-side G2 approval evidence and filing-freeze compliance after VPS_EXECUTOR performs the authorized pairing approval.
+
+This task is evidence review by default. It does not authorize VPS mutation, service restart/reload, token rotation, Gateway config changes, Nginx edits, Docker compose edits, bind mount changes, image changes, or public website changes.
+
+## Planning Status
+
+- G2 pre-execution plan is documented in `docs/G2_RUNBOOK.md`.
+- This task remains `draft` until T10 evidence exists.
+- Planning confirmation does not authorize verifier-side VPS commands.
+
+## Required Evidence
+
+- Review `docs/G2_RUNBOOK.md`.
+- Review VPS_EXECUTOR evidence from T10.
+- Confirm the approved request or node ID matches PC evidence and display name.
+- Confirm the token value is absent from evidence, handoffs, logs, commits, and chat.
+- Confirm no restart, reload, token rotation, Gateway config mutation, Nginx route edit, Docker compose edit, bind mount change, image change, service-state mutation, or frozen website output change was performed.
+- Confirm existing VPS baseline anomalies are tracked as observations and were not changed during G2.
+- Confirm VPS-side evidence is synchronized through Git and visible to the PC side.
+- Write findings to `evidence/verify-vps-g2-YYYYMMDD.md`.
+- Update `handoff/VPS_VERIFIER.md`.
+
+## Command Drafts
+
+Do not run VPS commands during planning. By default, verification is evidence review only:
+
+```text
+Review VPS evidence only. Do not execute VPS commands unless a later user instruction explicitly authorizes verifier-side read-only checks.
+```
+
+## Stop Conditions
+
+- T10 evidence is missing, incomplete, or not synchronized.
+- Evidence contains a secret.
+- Approval cannot be tied to the intended PC node.
+- Evidence shows restart, reload, token rotation, Gateway config mutation, Nginx edit, Docker edit, bind mount change, image change, service-state mutation, or frozen website output change.
+
+## Acceptance
+
+VPS_VERIFIER may mark T10 accepted only after non-secret evidence is sufficient. ORCHESTRATOR decides whether VPS-side G2 is ready to count toward G2 completion.
 # T12 - G2 VPS Verification
 
 ## Status

tasks/T7-correction-monitor.md

@@ -28,6 +28,7 @@ This task does not authorize PC or VPS configuration mutation. CORRECTION may bl
 
 ## Monitoring Findings
 
+- 2026-05-19 12:07 UTC+8: User confirmed sync-health is healthy and T7 sync-health blocked state is cleared. G2 entered pre-execution planning only. `docs/G2_RUNBOOK.md` and G2 task files define authorization gates, stop conditions, rollback, secret handling, and filing-freeze constraints. No G2 execution is authorized by this planning pass.
 - 2026-05-15 11:42 UTC+8: Read `AGENT_BOARD.md`, `README.md`, `.cursor/rules/agent-orchestration.mdc`, this task, and all relevant PC/VPS handoffs and baseline tasks.
 - Current state: T3/T4 are `ready`, T5/T6 are `draft`, and G1 remains pending.
 - Evidence state: only `evidence/README.md` exists; no PC/VPS baseline or verifier evidence exists yet.