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

Sync agent state from PC at 2026-05-19 12:28:51

Browse Source
This commit is contained in:
wangzhendong
2026-05-19 12:28:51 +08:00
parent 06f0b9e08a
commit e30a0db0f9
5 changed files with 25 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
handoff/PC_EXECUTOR.md
View File

@@ -38,12 +38,10 @@ After the Gitea control plane is synchronized, collect current PC baseline evide
## Last Update
2026-05-19 G2 authorized for PC foreground node run only.
2026-05-19 G2 execution paused after role-misdirection correction.
- 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`.
- T9 is blocked and must not be claimed or executed.
- Do not set or inject `OPENCLAW_GATEWAY_TOKEN`.
- Do not run `openclaw node run`.
- Do not run `openclaw node install`, `openclaw node start`, service persistence, scheduled task, firewall, network, or public-port exposure changes.
- Wait for ORCHESTRATOR to record fresh explicit user authorization after the role-misdirection correction before any G2 action.

12
handoff/VPS_EXECUTOR.md
View File

@@ -38,13 +38,11 @@ After the Gitea control plane is synchronized, collect current VPS baseline evid
## Last Update
2026-05-19 G2 authorized for corresponding VPS pairing approval only after PC evidence exists.
2026-05-19 G2 execution paused after role-misdirection correction.
- 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.
- T10 is blocked and must not be claimed or executed.
- Do not run `openclaw devices approve`, `openclaw nodes pending`, or `openclaw nodes approve` for G2.
- Do not approve any pairing request.
- 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.
- Wait for ORCHESTRATOR to record fresh explicit user authorization after the role-misdirection correction and for T9 to produce matching non-secret evidence before any VPS-side G2 action.