46 lines
2.1 KiB
Markdown
46 lines
2.1 KiB
Markdown
# PC G2 Foreground Node Run Evidence - 2026-05-21
|
||
|
||
Owner: PC_EXECUTOR
|
||
|
||
Scope: T9 - G2 PC foreground node run, using the corrected user-run local PowerShell model in `docs/G2_RUNBOOK.md`.
|
||
|
||
## Authorization and Preconditions
|
||
|
||
- G2 was authorized and `In Progress` in `AGENT_BOARD.md` and `USER_STATUS.md`.
|
||
- T9 top-level status was `ready` before the user-run foreground node flow.
|
||
- T10 remained `blocked`.
|
||
- T13 fresh PASS was recorded in `tasks/T13-G2-correction-guard.md` at 2026-05-21 16:42 UTC+8.
|
||
- Sync-health was healthy before prompting the user-run flow: PC and VPS heartbeats were clean and no `sync-state/error-*.md` files were present.
|
||
- Rollback note was written before user token/node action: `rollback/pc-g2-node-run-20260521.md`.
|
||
|
||
## Execution Model
|
||
|
||
- PC_EXECUTOR did not request, receive, read, print, record, or handle `OPENCLAW_GATEWAY_TOKEN`.
|
||
- PC_EXECUTOR did not run the token-bearing flow in the Agent shell.
|
||
- User was instructed to use a dedicated local PC PowerShell terminal and not send the token to chat or files.
|
||
|
||
User-run command template provided:
|
||
|
||
```powershell
|
||
$env:OPENCLAW_GATEWAY_TOKEN = "<在本地粘贴 Gateway token，不要发到聊天>"
|
||
openclaw node run --host openclaw.smartmotor.cloud --port 443 --tls --display-name "desktop-vuor0gs"
|
||
```
|
||
|
||
## Non-Secret Result Reported by User
|
||
|
||
- User reported: connected to `openclaw.smartmotor.cloud`.
|
||
- Pairing request ID or pending node ID: not provided in this report.
|
||
- Error summary: none provided.
|
||
|
||
## Safety Confirmation
|
||
|
||
- No token or secret value was recorded in this evidence.
|
||
- No Agent-shell `openclaw node run` was executed.
|
||
- No `openclaw node install`, `start`, `restart`, `stop`, or `uninstall` command was executed by PC_EXECUTOR.
|
||
- No service, scheduled task, firewall, network, environment persistence, or public-port exposure change was performed by PC_EXECUTOR.
|
||
|
||
## Follow-Up
|
||
|
||
- T10 remains blocked until a matching non-secret pairing request ID or pending node ID is available, or ORCHESTRATOR updates the dependency based on verifier/Gateway state.
|
||
- PC_VERIFIER must review this PC-side evidence before ORCHESTRATOR counts the PC half of G2 as accepted.
|