dr(w3): record vps1000 sandbox restore pass #522

Merged

pdurlej merged 1 commit from codex/w3d-vps1000-sandbox-pass into main

2026-05-27 15:26:11 +02:00

codex commented

2026-05-27 12:30:02 +02:00

Collaborator

Canary status: missing - not fired; touched scripts/dr and state evidence only, not mandatory canary paths.

Canary Context Pack

Product story

W3d needs evidence that restore mechanics work beyond one local Docker sandbox, without buying or relying on a third standing VPS. This PR records a second restore pass using vps1000 as an isolated Docker sandbox host.

What changed

Allows the W3d disposable drill wrapper to target vps1000 only with explicit W3D_ALLOW_LIVE_HOST_SANDBOX=1.
Keeps rs2000 blocked as a restore target for this drill.
Generalizes W3d report wording so local and remote sandbox reports use the same evidence shape.
Adds the vps1000 restore report and updates W3/status notes.
Records the platform policy correction: no third standing VPS; use RS2000, VPS1000, Mac/local Docker, or temporary/serverless-per-minute only when truly needed.

Why it changed

The previous W3d pass proved local mechanics. The operator clarified that vps1000 is the right second sandbox host and that buying another server is not acceptable default infrastructure.

Files touched

scripts/dr/w3d-disposable-vps-drill.sh
scripts/dr/w3d-local-sandbox-drill.sh
state/reports/w3d-vps1000-sandbox-drill-2026-05-27.md
state/cycle/W3-dr-restore-confidence-output.md
state/STATUS_NOW.md

Runtime evidence

Target: vps1000 / v2202603338414444051, Docker-only isolated Compose project w3d-20260527t101906z.
Backup root: /opt/vps-home-platform-infra/backups/20260527-120006-critical.
Routed smoke: Traefik ping 200, Forgejo /api/healthz 200, Honcho /openapi.json 200.
Restored counts: Forgejo repositories 19, Forgejo users 7, Honcho documents 26141, message embeddings 13572, sessions 202, messages 13590.
RTO from backup-on-disk on vps1000 to routed smoke: 97s; target drill elapsed after staging: 130s.
Cleanup verified: no w3d* containers, volumes, or staging dirs remained on vps1000.

Known constraints

No RS2000 production restore, restart, apply, promote, or service mutation was performed.
No live OpenClaw/Iskra service on vps1000 was recreated or touched.
The sandbox did not receive direct production secret access; artifacts were staged through the operator machine.
Semantic OpenClaw/Iskra persona continuity is not proven here; split to W3e if needed.

Explicit out-of-scope

Buying or provisioning a third standing VPS.
Forgejo upgrade.
Runtime cleanup/destructive deletion.
Persona/memory semantic restore validation.

Requested decision

Merge to accept W3d restore mechanics as green across local Docker and vps1000 remote sandbox evidence.

Merge blockers

Any overclaim that this proves persona continuity.
Missing cleanup evidence.
Secret or private-data leakage in report text.

Spec sources read

AGENTS.md - Forgejo/identity and PR contract.
docs/forgejo-agent-operations.md - Forgejo API write contract.
state/cycle/W3-dr-restore-confidence-output.md - W3d acceptance state.
state/reports/w3d-local-sandbox-drill-2026-05-27.md - local W3d evidence shape.
Forgejo issue #433 - W3 DR/restore confidence coordination.
Recent W3d PR context #520/#521 - first local-pass closeout and operator correction.

Refs #433

Canary status: missing - not fired; touched scripts/dr and state evidence only, not mandatory canary paths. ## Canary Context Pack ### Product story W3d needs evidence that restore mechanics work beyond one local Docker sandbox, without buying or relying on a third standing VPS. This PR records a second restore pass using `vps1000` as an isolated Docker sandbox host. ### What changed - Allows the W3d disposable drill wrapper to target `vps1000` only with explicit `W3D_ALLOW_LIVE_HOST_SANDBOX=1`. - Keeps `rs2000` blocked as a restore target for this drill. - Generalizes W3d report wording so local and remote sandbox reports use the same evidence shape. - Adds the `vps1000` restore report and updates W3/status notes. - Records the platform policy correction: no third standing VPS; use RS2000, VPS1000, Mac/local Docker, or temporary/serverless-per-minute only when truly needed. ### Why it changed The previous W3d pass proved local mechanics. The operator clarified that `vps1000` is the right second sandbox host and that buying another server is not acceptable default infrastructure. ### Files touched - `scripts/dr/w3d-disposable-vps-drill.sh` - `scripts/dr/w3d-local-sandbox-drill.sh` - `state/reports/w3d-vps1000-sandbox-drill-2026-05-27.md` - `state/cycle/W3-dr-restore-confidence-output.md` - `state/STATUS_NOW.md` ### Runtime evidence - Target: `vps1000` / `v2202603338414444051`, Docker-only isolated Compose project `w3d-20260527t101906z`. - Backup root: `/opt/vps-home-platform-infra/backups/20260527-120006-critical`. - Routed smoke: Traefik ping `200`, Forgejo `/api/healthz` `200`, Honcho `/openapi.json` `200`. - Restored counts: Forgejo repositories `19`, Forgejo users `7`, Honcho documents `26141`, message embeddings `13572`, sessions `202`, messages `13590`. - RTO from backup-on-disk on `vps1000` to routed smoke: `97s`; target drill elapsed after staging: `130s`. - Cleanup verified: no `w3d*` containers, volumes, or staging dirs remained on `vps1000`. ### Known constraints - No RS2000 production restore, restart, apply, promote, or service mutation was performed. - No live OpenClaw/Iskra service on `vps1000` was recreated or touched. - The sandbox did not receive direct production secret access; artifacts were staged through the operator machine. - Semantic OpenClaw/Iskra persona continuity is not proven here; split to W3e if needed. ### Explicit out-of-scope - Buying or provisioning a third standing VPS. - Forgejo upgrade. - Runtime cleanup/destructive deletion. - Persona/memory semantic restore validation. ### Requested decision Merge to accept W3d restore mechanics as green across local Docker and `vps1000` remote sandbox evidence. ### Merge blockers - Any overclaim that this proves persona continuity. - Missing cleanup evidence. - Secret or private-data leakage in report text. ## Spec sources read - `AGENTS.md` - Forgejo/identity and PR contract. - `docs/forgejo-agent-operations.md` - Forgejo API write contract. - `state/cycle/W3-dr-restore-confidence-output.md` - W3d acceptance state. - `state/reports/w3d-local-sandbox-drill-2026-05-27.md` - local W3d evidence shape. - Forgejo issue #433 - W3 DR/restore confidence coordination. - Recent W3d PR context #520/#521 - first local-pass closeout and operator correction. Refs #433

codex added 1 commit

2026-05-27 12:30:02 +02:00

dr(w3): record vps1000 sandbox restore pass

base-is-main / guard (pull_request) Successful in 1s

Details

canary-required / collect-diff (pull_request) Successful in 4s

Details

patchwarden-client-dry-run / collect-diff (pull_request) Successful in 4s

Details

patchwarden-pr-sanity / collect-diff (pull_request) Successful in 5s

Details

canary-required / canary (pull_request) Has been skipped