From 83239eb6736233647916f4184960c6501e161d2f Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Sat, 30 May 2026 03:52:33 +0100 Subject: [PATCH] =?UTF-8?q?status(2):=20Q4.3=20bluesky-pds=20Adversary=20P?= =?UTF-8?q?ASS=20(REVIEW-2=20e45e0ee)=20=E2=80=94=20DONE;=20next=20unblock?= =?UTF-8?q?ed:=20ghost=20P4+create-post=20deeper?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- machine-docs/STATUS-2.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/machine-docs/STATUS-2.md b/machine-docs/STATUS-2.md index f013f1e..e006f3e 100644 --- a/machine-docs/STATUS-2.md +++ b/machine-docs/STATUS-2.md @@ -75,7 +75,7 @@ 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 — ✅ FULL LIFECYCLE GREEN @2026-05-30 — CLAIMED (see ## Gate Q4.3), awaiting Adversary.** P4 added (atproto account marker survives backup/restore/upgrade — bluesky's volume restore WORKS, NO recipe-PR needed, unlike the postgres recipes); all 5 tiers + 4 custom green, deploy-count=1, clean teardown; log `/root/ccci-bluesky-full.log`. (Detail below.) +**Q4.3 bluesky-pds — ✅ Adversary PASS @2026-05-30 (REVIEW-2 `e45e0ee`). DONE.** Cold full lifecycle GREEN, deploy-count=1, P4 atproto account-marker survives (non-vacuous in-band), 2 distinct P3, clean teardown. No veto. (Detail below.) (`/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 @@ -224,7 +224,10 @@ SKIP no longer yields a GREEN `!testme`. ## Gate -**Gate: Q4.3 bluesky-pds — CLAIMED @2026-05-30, awaiting Adversary.** +**Gate: Q4.3 bluesky-pds — ✅ Adversary PASS @2026-05-30 (REVIEW-2 `e45e0ee`).** Cold full lifecycle +GREEN, deploy-count=1, real upgrade crossover 0.1.1+v0.4→0.2.0+v0.4, P4 atproto account-marker survives +backup→restore (non-vacuous, in-band delete-assert), 2 distinct P3 functional, clean teardown. No veto. +DONE. (Claim detail retained below.) **WHAT.** bluesky-pds (atproto Personal Data Server; pds + caddy) runs its **full lifecycle GREEN** — install + upgrade (real prev→latest crossover) + backup + restore + custom. This completes its P4 (the