From ad53a7c6c4a7c849b39d173e7f8027de17ba909e Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 02:49:27 +0100 Subject: [PATCH] status(2): Q4.3 bluesky-pds P4 overlay (atproto account marker) authored, full-lifecycle run in flight --- machine-docs/STATUS-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md index 4f7331b..3563fda 100644 --- a/machine-docs/STATUS-2.md +++ b/machine-docs/STATUS-2.md @@ -75,6 +75,15 @@ P4 overlay is correct + non-vacuous (it caught a real bug). NOT claimed — reci / DEFERRED). Node clean. (cc-ci is now catching DB backup/restore defects in BOTH immich and mattermost — exactly its purpose.) +**Q4.3 bluesky-pds — P4 overlay authored, full-lifecycle run IN FLIGHT @2026-05-30** +(`/root/ccci-bluesky-full.log`). bluesky already had strong P3 (account+post §4.3 + describe_server); +added the missing P4 data-integrity overlay — a DETERMINISTIC atproto ACCOUNT marker (recipe-aware, in +the PDS sqlite under /pds, the backed-up volume) via `_p4.py` + ops/test_upgrade/backup/restore. The +account-marker (vs a loose file) is chosen to CATCH a restore that fails to reload the running PDS's +held-open sqlite (the data-loss class caught in immich/mattermost). EXPECTED: restore tier +`test_restore_returns_state` GREEN (marker account survives). If RED → recipe-PR (restore reload). NOT +claimed. (bluesky-pds was Q4.3 FULL functional earlier; this completes its P4.) + **Q4.6 discourse — BLOCKED/DEFERRED @2026-05-29.** Upstream recipe pins `bitnami/discourse:*` images that Docker Hub no longer serves (manifest unknown; swarm task Rejected "No such image"). Image exists at `bitnamilegacy/discourse` but the install tier deploys the prev published version (also gone), so a