recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

status(2): Q4.3 bluesky-pds P4 overlay (atproto account marker) authored, full-lifecycle run in flight

Browse Source
This commit is contained in:
autonomic-bot
2026-05-30 02:49:27 +01:00
parent 74da6dc46b
commit ad53a7c6c4
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
machine-docs/STATUS-2.md
View File

@ -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