wangzhendong/openclaw-control-plane
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Sync agent state from VPS at 2026-05-19 12:09:21

Browse Source
This commit is contained in:
ubuntu
2026-05-19 12:09:21 +08:00
parent 0ad51fa1a6
commit 0ee4fff12a
4 changed files with 4 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
tasks/T11-G2-PC-verify.md
View File

@@ -55,40 +55,3 @@ Review PC evidence only. Do not execute PC commands unless a later user instruct
## 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
draft
## Owner
PC_VERIFIER
## Dependencies
- T9 done
## Scope
Independently verify PC-side G2 evidence before ORCHESTRATOR accepts the PC half of G2.
## Required Evidence
- Review `evidence/pc-g2-node-run-YYYYMMDD.md`.
- Confirm PC foreground node connected to the expected Gateway.
- Confirm token value is absent from evidence and handoffs.
- Confirm no `openclaw node install`, `start`, `restart`, `stop`, `uninstall`, service, scheduled task, firewall, network, environment persistence, or public-port exposure mutation occurred.
- Write verification evidence to `evidence/verify-pc-g2-YYYYMMDD.md`.
- Update `handoff/PC_VERIFIER.md`.
## Stop Conditions
- Missing PC executor evidence.
- Evidence includes secrets.
- PC node command or Gateway target does not match `docs/G2_RUNBOOK.md`.
- Evidence suggests a G4 persistence action occurred during G2.
## Acceptance
ORCHESTRATOR may count the PC half of G2 as accepted only after PC_VERIFIER records acceptance.

39
tasks/T12-G2-VPS-verify.md
View File

@@ -56,42 +56,3 @@ Review VPS evidence only. Do not execute VPS commands unless a later user instru
## 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
draft
## Owner
VPS_VERIFIER
## Dependencies
- T10 done
## Scope
Independently verify VPS-side G2 approval evidence and frozen website compliance before ORCHESTRATOR accepts the VPS half of G2.
## Required Evidence
- Review `evidence/vps-g2-approve-YYYYMMDD.md`.
- Confirm only the intended pairing approval occurred.
- Confirm no token value, password, API key, private key, cookie, or `OPENCLAW_GATEWAY_TOKEN` value appears in evidence or handoffs.
- Confirm no restart, reload, token rotation, Nginx edit, Docker compose edit, bind mount change, image change, service-state mutation, or public website output change occurred.
- Track existing `/opt/service` versus `/opt/services`, `docker-composite.yml` versus `docker-compose.openclaw.yml`, and Nginx route/config anomalies as follow-up observations unless they directly affect G2.
- Write verification evidence to `evidence/verify-vps-g2-YYYYMMDD.md`.
- Update `handoff/VPS_VERIFIER.md`.
## Stop Conditions
- Missing VPS executor evidence.
- Evidence includes secrets.
- Approval cannot be tied to the intended PC node.
- Frozen `smartmotor.cloud` website compliance is uncertain.
- Evidence suggests service, Docker, Nginx, route, bind mount, image, or public content mutation.
## Acceptance
ORCHESTRATOR may count the VPS half of G2 as accepted only after VPS_VERIFIER records acceptance.

4
tasks/T7-correction-monitor.md
View File

@@ -30,8 +30,8 @@ This task does not authorize PC or VPS configuration mutation. CORRECTION may bl
- 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.
- Historical note from 2026-05-15: T3/T4 were `ready`, T5/T6 were `draft`, and G1 was pending at that time.
- Current G2 planning state from 2026-05-19: G1 is done, T9/T10/T11/T12 remain `draft`, and G2 execution is not authorized.
- No executor overreach, frozen `smartmotor.cloud` website mutation, pre-G1 configuration mutation, rollback-note gap, sync conflict, or secret-bearing evidence was detected in tracked repository contents.
- Correction decision: no task is blocked in this pass, but no PC/VPS mutation-stage work is authorized until G1 is independently verified and accepted.