pdurlej/platform

Fork 0

fix(backup): record cold restore proof #708

Merged

pdurlej merged 1 commit from codex/backup-restore-python-compat into main

2026-06-04 16:26:50 +02:00

codex commented

2026-06-04 16:21:57 +02:00

Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Summary

Fixes scripts/backup/restore_check.py for macOS 12 / older Python by using datetime.timezone.utc instead of datetime.UTC.
Records the actual M02 unique-knowledge restore posture after the old MacBook and Synology checks.
Reclassifies Synology as hot retrieval / hot-copy evidence and macbook-pro-old as the cold full-restore node.
Updates #608 preflight wording now that backup posture is green enough for operator-gated package planning, while reboot remains separately gated.

Evidence

macbook-pro-old SSH confirmed 500 GB APFS container and enough free space.
Cold copy exists at /Users/pd2/platform-unique-knowledge-backups.
Full restore-check passed on macbook-pro-old with restore_verified=true, items_captured=12, manifest_run_id=20260603T231146Z.
Synology Drive Client hot copy completed; SSH-side check found archive and receipts, verified archive readability, manifest, and receipt/checksum consistency.
Synology full extraction remains deferred because DSM /tmp is too small; use a /volume1 restore root if needed later.

Tests

pytest tests/test_unique_knowledge_backup.py — 5 passed
git diff --check — pass
UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json — exitCode 0

Spec sources read

scripts/backup/restore_check.py — portability failure source and restore semantics.
tests/test_unique_knowledge_backup.py — backup/restore test coverage.
runbooks/unique-knowledge-backup.md — target role documentation.
state/reports/m02-dr-refresh-synology-gate-2026-06-04.md — M02 evidence update.
state/reports/rs2000-ubuntu-update-preflight-2026-06-04.md — #608 readiness wording.
state/STATUS_NOW.md — operator-facing current state.

No issue is closed by this PR; it updates evidence and fixes a restore-check portability bug found during M02 validation.

Canary status: missing — fire canary 3+3 manually before merge ## Summary - Fixes `scripts/backup/restore_check.py` for macOS 12 / older Python by using `datetime.timezone.utc` instead of `datetime.UTC`. - Records the actual M02 unique-knowledge restore posture after the old MacBook and Synology checks. - Reclassifies Synology as hot retrieval / hot-copy evidence and `macbook-pro-old` as the cold full-restore node. - Updates #608 preflight wording now that backup posture is green enough for operator-gated package planning, while reboot remains separately gated. ## Evidence - `macbook-pro-old` SSH confirmed 500 GB APFS container and enough free space. - Cold copy exists at `/Users/pd2/platform-unique-knowledge-backups`. - Full restore-check passed on `macbook-pro-old` with `restore_verified=true`, `items_captured=12`, `manifest_run_id=20260603T231146Z`. - Synology Drive Client hot copy completed; SSH-side check found archive and receipts, verified archive readability, manifest, and receipt/checksum consistency. - Synology full extraction remains deferred because DSM `/tmp` is too small; use a `/volume1` restore root if needed later. ## Tests - `pytest tests/test_unique_knowledge_backup.py` — 5 passed - `git diff --check` — pass - `UV_CACHE_DIR=/tmp/platform-uv-cache PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json` — exitCode 0 ## Spec sources read - `scripts/backup/restore_check.py` — portability failure source and restore semantics. - `tests/test_unique_knowledge_backup.py` — backup/restore test coverage. - `runbooks/unique-knowledge-backup.md` — target role documentation. - `state/reports/m02-dr-refresh-synology-gate-2026-06-04.md` — M02 evidence update. - `state/reports/rs2000-ubuntu-update-preflight-2026-06-04.md` — #608 readiness wording. - `state/STATUS_NOW.md` — operator-facing current state. No issue is closed by this PR; it updates evidence and fixes a restore-check portability bug found during M02 validation.

codex added 1 commit

2026-06-04 16:21:57 +02:00

fix(backup): record cold restore proof

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

Details

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

Details

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

Details

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

Details

python-ci / Python 3.13 (pull_request) Successful in 47s

Details

python-ci / Python 3.11 (pull_request) Successful in 45s

Details

python-ci / Python 3.12 (pull_request) Successful in 47s

Details

canary-required / canary (pull_request) Successful in 15s

Details

patchwarden-client-dry-run / dry-run (pull_request) Successful in 19s

Details

patchwarden-pr-sanity / sanity (pull_request) Successful in 1m34s

Details

5db6f2d104

codex commented

2026-06-04 16:26:39 +02:00

Author

Collaborator

Patchwarden PR sanity

Status: eligible_sanity_clean
PR: 708
Commit: 5db6f2d10410b8a33e446351b1611106001863e4
Security-sensitive label: missing
Authority: advisory model review plus deterministic blockers only
3+3 canary: still alive; this does not replace it

Deterministic findings

No deterministic findings.

Model reviewers

`global-glm` / `glm-5.1:cloud`

Status: ok
Verdict: OK
medium Synology reclassified from hard gate to hot-retrieval without full extraction proof
- Evidence: state/reports/m02-dr-refresh-synology-gate-2026-06-04.md: Synology full extraction skipped because DSM /tmphad ~889 MB free for a 3.1 GB archive. Previous status was BLOCKED as a hard gate; now PASS with full extraction deferred.full_e`
- Next: Document the /volume1 restore-root workaround as a future action item. Consider whether operator sign-off on the reduced Synology verification scope was explicitly recorded, or if the reclassification should be noted as an accepted risk in STATUS_NOW.md.
low Canary status missing per PR description
- Evidence: PR description states: 'Canary status: missing — fire canary 3+3 manually before merge'
- Next: Ensure canary is fired before or immediately after merge per project process requirements.

`global-deepseek` / `deepseek-v4-pro:cloud`

Status: ok
Verdict: OK
Findings: none

`redteam` / `kimi-k2.6:cloud`

Status: ok
Verdict: OK
Findings: none

Policy notes

GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot.
Optional red-team model is enabled only when PLATFORMCTL_PR_SANITY_REDTEAM_MODEL is configured.
Auto-merge is not enabled here.

# Patchwarden PR sanity - Status: `eligible_sanity_clean` - PR: `708` - Commit: `5db6f2d10410b8a33e446351b1611106001863e4` - Security-sensitive label: `missing` - Authority: advisory model review plus deterministic blockers only - 3+3 canary: still alive; this does not replace it ## Deterministic findings No deterministic findings. ## Model reviewers ### `global-glm` / `glm-5.1:cloud` - Status: `ok` - Verdict: `OK` - **`medium`** Synology reclassified from hard gate to hot-retrieval without full extraction proof - Evidence: `state/reports/m02-dr-refresh-synology-gate-2026-06-04.md: Synology full extraction skipped because DSM `/tmp` had ~889 MB free for a 3.1 GB archive. Previous status was BLOCKED as a hard gate; now PASS with full extraction deferred. `full_e` - Next: Document the `/volume1` restore-root workaround as a future action item. Consider whether operator sign-off on the reduced Synology verification scope was explicitly recorded, or if the reclassification should be noted as an accepted risk in STATUS_NOW.md. - **`low`** Canary status missing per PR description - Evidence: `PR description states: 'Canary status: missing — fire canary 3+3 manually before merge'` - Next: Ensure canary is fired before or immediately after merge per project process requirements. ### `global-deepseek` / `deepseek-v4-pro:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ### `redteam` / `kimi-k2.6:cloud` - Status: `ok` - Verdict: `OK` - Findings: none ## Policy notes - GLM 5.1 + DeepSeek V4 Pro are the operator-required model mix for this bot. - Optional red-team model is enabled only when `PLATFORMCTL_PR_SANITY_REDTEAM_MODEL` is configured. - Auto-merge is not enabled here.