Sync agent state from VPS at 2026-05-19 12:17:29

This commit is contained in:
ubuntu
2026-05-19 12:17:29 +08:00
parent 53a40b00ca
commit 588db237c0
5 changed files with 33 additions and 17 deletions

View File

@@ -24,8 +24,9 @@ This task does not authorize service restarts, reloads, token rotation, Gateway
- G2 pre-execution plan is documented in `docs/G2_RUNBOOK.md`.
- Sync-health has been confirmed healthy and T7 sync-health blocked state is cleared.
- This task remains `draft` because G2 execution and VPS-side approval have not been explicitly authorized.
- Planning confirmation does not authorize `nodes pending`, `devices approve`, `nodes approve`, service restarts/reloads, token rotation, Gateway config mutation, Nginx changes, Docker changes, or frozen website changes.
- User authorized G2 on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only.
- This task remains `draft` until T9 produces a non-secret pairing request ID or pending node ID that can be matched to the intended PC node.
- Authorization covers only the corresponding pairing approval after T9 evidence exists; it does not authorize service restarts/reloads, token rotation, Gateway config mutation, Nginx changes, Docker changes, or frozen website changes.
## Required Evidence
@@ -39,7 +40,7 @@ This task does not authorize service restarts, reloads, token rotation, Gateway
## Command Drafts
Do not run these until G2 approval is explicitly authorized.
Do not run these until T9 evidence provides a matching non-secret request/node ID. Approval must target only the intended PC pairing.
```bash
docker exec openclaw-gateway node openclaw.mjs nodes pending

View File

@@ -2,7 +2,7 @@
## Status
draft
ready
## Owner
@@ -22,10 +22,17 @@ This task does not authorize PC/VPS configuration mutation.
- Confirm `sync-state/heartbeat-pc.json` and `sync-state/heartbeat-vps.json` are present and fresh before G2 execution starts.
- Confirm no `sync-state/error-pc.md` or `sync-state/error-vps.md` file exists.
- Confirm user authorization is limited to foreground PC node run and corresponding VPS pairing approval.
- Confirm PC and VPS agents can see the same latest G2 task state and evidence through Git.
- Block G2 if any task bypasses explicit user authorization, records a secret, or risks changing frozen `smartmotor.cloud` website output.
- Record findings in `handoff/CORRECTION.md` and, if needed, update this task status to `blocked`.
## Current Authorization
- User authorized G2 on 2026-05-19.
- Allowed: foreground PC node run under `docs/G2_RUNBOOK.md` and corresponding VPS pairing approval after T9 produces a matching non-secret request/node ID.
- Forbidden: service persistence, `openclaw node install/start`, Nginx/Docker/website changes, firewall/network changes, and recording any token or secret.
## Stop Conditions
- Heartbeat older than the sync policy threshold.

View File

@@ -2,7 +2,7 @@
## Status
draft
ready
## Owner
@@ -26,8 +26,9 @@ This task is not ready until ORCHESTRATOR records explicit user authorization fo
- G2 pre-execution plan is documented in `docs/G2_RUNBOOK.md`.
- Sync-health has been confirmed healthy and T7 sync-health blocked state is cleared.
- This task remains `draft` because G2 execution has not been explicitly authorized.
- Planning confirmation does not authorize token use, `openclaw node run`, service changes, firewall changes, network changes, or public port exposure.
- User authorized G2 on 2026-05-19 for foreground PC node run and corresponding VPS pairing approval only.
- This task is ready for PC_EXECUTOR under `docs/G2_RUNBOOK.md`.
- Authorization covers only local-session token use without disclosure and foreground `openclaw node run`; it does not authorize service changes, firewall changes, network changes, persistence, or public port exposure.
## Required Evidence
@@ -41,7 +42,7 @@ This task is not ready until ORCHESTRATOR records explicit user authorization fo
## Command Drafts
Do not run these until G2 is explicitly authorized.
Authorized only within `docs/G2_RUNBOOK.md` and only on the Windows PC by PC_EXECUTOR. Do not record the token value.
```powershell
$env:OPENCLAW_GATEWAY_TOKEN = "<user-pastes-token-locally>"