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:18:00

Browse Source
This commit is contained in:
ubuntu
2026-05-19 12:18:00 +08:00
parent 588db237c0
commit 5134f68d5e
4 changed files with 27 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
handoff/CORRECTION.md
View File

@@ -38,4 +38,9 @@ Detect drift, unsafe assumptions, missing evidence, sync-health failures, confli
## Last Update
Template created during control-plane bootstrap.
2026-05-19 12:16 UTC+8: G2 authorization guard update.
- User authorized G2 only for foreground PC node run and corresponding VPS pairing approval under `docs/G2_RUNBOOK.md`.
- T9 and T13 are ready; T10 remains draft until T9 produces a matching non-secret pairing request ID or pending node ID.
- Continue blocking service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, public port exposure, and any token/secret recording.
- Stop G2 if heartbeat becomes stale, any `sync-state/error-*.md` appears, evidence is not visible on both sides, request identity is ambiguous, or freeze compliance becomes uncertain.

10
handoff/PC_EXECUTOR.md
View File

@@ -38,4 +38,12 @@ After the Gitea control plane is synchronized, collect current PC baseline evide
## Last Update
Template created during control-plane bootstrap.
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`.

11
handoff/VPS_EXECUTOR.md
View File

@@ -38,4 +38,13 @@ After the Gitea control plane is synchronized, collect current VPS baseline evid
## Last Update
Template created during control-plane bootstrap.
2026-05-19 G2 authorized for corresponding VPS pairing approval only after PC evidence exists.
- Read `docs/G2_RUNBOOK.md` before acting.
- T10 remains draft until T9 provides a matching non-secret pairing request ID or pending node ID.
- Before approval action, write `rollback/vps-g2-approve-YYYYMMDD.md`.
- Approve only the intended PC request/node that matches T9 evidence and display name.
- Do not run approval commands if multiple pending requests are indistinguishable.
- Do not request, print, record, rotate, or store any token/password/secret.
- Do not restart/reload services, change Gateway config, edit Nginx, edit Docker/compose/bind mounts/images, change service state, or alter frozen `smartmotor.cloud` website output.
- Evidence should go to `evidence/vps-g2-approve-YYYYMMDD.md` and must include no secrets.