From 42181b99656070fb9ca07572125ad4b415e016ee Mon Sep 17 00:00:00 2001 From: wangzhendong Date: Fri, 15 May 2026 10:56:42 +0800 Subject: [PATCH] Update VPS control plane path Co-authored-by: Cursor --- AGENT_BOARD.md | 8 ++++---- README.md | 2 +- handoff/ORCHESTRATOR.md | 12 ++++++------ handoff/VPS_EXECUTOR.md | 2 +- 4 files changed, 12 insertions(+), 12 deletions(-) diff --git a/AGENT_BOARD.md b/AGENT_BOARD.md index 54e52e1..ae63fc3 100644 --- a/AGENT_BOARD.md +++ b/AGENT_BOARD.md @@ -14,7 +14,7 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con - Authentication mode: HTTPS access from both the Windows PC and VPS. - Default branch: `main`. - PC control-plane path: `D:\openclaw-control-plane`. -- VPS control-plane path: `/opt/openclaw-control-plane`. +- VPS control-plane path: `/home/ubuntu/openclaw-control-plane`. - Secrets policy: no password, token, API key, or `OPENCLAW_GATEWAY_TOKEN` may be written into repo files, handoffs, evidence, or chat. - Frozen website policy: strict freeze during ICP/public-security filing review. Agents must not change the `smartmotor.cloud` homepage, content reachable from homepage links, static assets, Nginx routing, bind mounts, container images, or `/opt/services/docker-composite.yml` entries that could alter public website output. @@ -46,9 +46,9 @@ Bring the Windows 11 always-on PC, Tencent Cloud VPS OpenClaw Gateway, phone Con |---|---|---|---|---| | T0 | Create local control-plane scaffold | ORCHESTRATOR | None | Done | | T1 | Create standalone Gitea repo for this control plane | User + ORCHESTRATOR | T0 | Done | -| T2 | Sync this scaffold to Gitea and clone/pull on VPS | ORCHESTRATOR + VPS_EXECUTOR | T1 | In Progress | -| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2 | Pending | -| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2 | Pending | +| T2 | Sync this scaffold to Gitea and open on PC/VPS Cursor | ORCHESTRATOR + VPS_EXECUTOR | T1 | Done | +| T3 | Run read-only PC baseline discovery | PC_EXECUTOR | T2 | Ready | +| T4 | Run read-only VPS baseline discovery | VPS_EXECUTOR | T2 | Ready | | T5 | Verify both baselines before any config change | PC_VERIFIER + VPS_VERIFIER | T3, T4 | Pending | ## Acceptance Criteria Draft diff --git a/README.md b/README.md index 5da0cf6..aaad895 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ Shared control-plane repository for coordinating Cursor agents across: - Windows PC workspace: `D:\openclaw` - Control-plane workspace on PC: `D:\openclaw-control-plane` - VPS service workspace: `/opt/service` -- Control-plane workspace on VPS: `/opt/openclaw-control-plane` +- Control-plane workspace on VPS: `/home/ubuntu/openclaw-control-plane` ## Start Here diff --git a/handoff/ORCHESTRATOR.md b/handoff/ORCHESTRATOR.md index 74f96b7..7143bf1 100644 --- a/handoff/ORCHESTRATOR.md +++ b/handoff/ORCHESTRATOR.md @@ -18,21 +18,21 @@ Bootstrap the shared Gitea-backed control plane, then coordinate read-only basel - Standalone Gitea repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`. - PC local path: `D:\openclaw-control-plane`. -- VPS target path: `/opt/openclaw-control-plane`. +- VPS target path: `/home/ubuntu/openclaw-control-plane`. - Access mode: HTTPS. - Default branch: `main`. - Strict `smartmotor.cloud` website freeze is a hard requirement during filing review. ## Next Actions -1. Commit and push the control-plane scaffold to Gitea after user approval. -2. Clone or pull the repository on the VPS at `/opt/openclaw-control-plane`. -3. Run G0 requirements and acceptance review with the user. -4. Assign PC and VPS read-only baseline tasks only after sync is available on both machines. +1. Commit and push this path correction to Gitea. +2. Run G0 requirements and acceptance review with the user. +3. Assign PC and VPS read-only baseline tasks in their respective Cursor windows. +4. Require verifier review before any mutation. ## Open Questions -- Has the VPS cloned the control-plane repository at `/opt/openclaw-control-plane`? +- Has the VPS pulled the latest control-plane repository at `/home/ubuntu/openclaw-control-plane`? - Should Gitea Issues be used immediately for task tracking, or should `AGENT_BOARD.md` remain the first source of truth for the initial run? ## Last Update diff --git a/handoff/VPS_EXECUTOR.md b/handoff/VPS_EXECUTOR.md index 16f154b..7c11f13 100644 --- a/handoff/VPS_EXECUTOR.md +++ b/handoff/VPS_EXECUTOR.md @@ -24,7 +24,7 @@ Operate only on the VPS side: `/opt/service`, OpenClaw Gateway, Docker stack, Ng - VPS public IP: `114.132.222.127`. - OpenClaw Gateway is already deployed and coexists with the existing Docker stack. - The VPS service workspace path is `/opt/service`. -- The VPS control-plane path is `/opt/openclaw-control-plane`. +- The VPS control-plane path is `/home/ubuntu/openclaw-control-plane`. - Gitea control-plane repository: `https://git.smartmotor.cloud/wangzhendong/openclaw-control-plane.git`. ## Next Read-Only Task