Sync agent state from PC at 2026-05-19 17:10:35
This commit is contained in:
@@ -8,19 +8,22 @@ This rollback note covers the T9 foreground-only PC node run authorized under `d
|
||||
|
||||
## Intended Change
|
||||
|
||||
- Set `OPENCLAW_GATEWAY_TOKEN` only in the local PC shell session.
|
||||
- Run the PC node in foreground mode with:
|
||||
- User sets `OPENCLAW_GATEWAY_TOKEN` only in a dedicated local PC PowerShell terminal.
|
||||
- User runs the PC node in foreground mode in that same local terminal with:
|
||||
|
||||
```powershell
|
||||
openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"
|
||||
```
|
||||
|
||||
- PC_EXECUTOR does not receive the token and does not run the token-bearing node flow in the Agent shell.
|
||||
|
||||
## Current State Before Action
|
||||
|
||||
- T9 is `ready`.
|
||||
- T10 remains `blocked` until T9 produces one matching non-secret pairing request ID or pending node ID.
|
||||
- T13 fresh guard PASS is recorded in `tasks/T13-G2-correction-guard.md` at 2026-05-19 16:29 UTC+8 and released by ORCHESTRATOR in `AGENT_BOARD.md`.
|
||||
- Sync-health is not blocked: PC and VPS heartbeats are present and clean, and no `sync-state/error-*.md` files are present.
|
||||
- 2026-05-19 17:09 UTC+8 pre-run check: `git pull --ff-only` fast-forwarded `sync-state/heartbeat-vps.json`; `tasks/T9-G2-PC-node-run.md` top-level status is `ready`; `USER_STATUS.md` and `AGENT_BOARD.md` confirm G2 authorized and `In Progress`; `docs/G2_RUNBOOK.md` confirms the user-run local PowerShell token/node model; PC heartbeat was clean at `2026-05-19T17:09:00+08:00`; VPS heartbeat was clean at `2026-05-19T17:09:43+0800`; no `sync-state/error-*.md` files were present.
|
||||
- 2026-05-19 16:55 UTC+8 pre-run check: `git pull --ff-only` reported already up to date; `tasks/T9-G2-PC-node-run.md` top-level status is `ready`; PC heartbeat was clean at `2026-05-19T16:55:01+08:00`; VPS heartbeat was clean at `2026-05-19T16:55:28+0800`; no `sync-state/error-*.md` files were present; no stale `openclaw` process was found.
|
||||
- 2026-05-19 16:39 UTC+8 pre-run check: `git pull --ff-only` reported already up to date; PC heartbeat was clean at `2026-05-19T16:39:26+08:00`; VPS heartbeat was clean at `2026-05-19T16:39:14+0800`.
|
||||
- No G2 PC service persistence is installed by this task.
|
||||
@@ -28,7 +31,7 @@ openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-na
|
||||
|
||||
## Rollback Steps
|
||||
|
||||
1. Stop the foreground node process with `Ctrl+C` in the same local shell.
|
||||
1. Stop the foreground node process with `Ctrl+C` in the same dedicated local PowerShell terminal.
|
||||
2. Clear the session token by closing the shell or removing the session environment variable without printing its value.
|
||||
3. Do not run `openclaw node install`, `openclaw node start`, service persistence, scheduled task, firewall, network, or public-port exposure commands.
|
||||
4. If the pairing request or node ID is ambiguous, stop the foreground node and record a blocker without approving anything.
|
||||
@@ -36,4 +39,4 @@ openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-na
|
||||
## Secret Handling
|
||||
|
||||
- Do not record, print, commit, or chat-send any token or secret value.
|
||||
- Evidence may record only that the token was set in the local shell session and that its value was not displayed or recorded.
|
||||
- Evidence may record only that the user reported setting the token in a dedicated local PowerShell terminal and that its value was not displayed or recorded.
|
||||
|
||||
Reference in New Issue
Block a user