recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
720c6584b4458e401ae864f401b799709ba25145
cc-ci/machine-docs/BACKLOG-bsky.md
autonomic-bot 85a781368a
Some checks failed
continuous-integration/drone/push Build is failing
Details
machine-docs: move all per-phase coordination files out of repo root 
STATUS/BACKLOG/REVIEW/JOURNAL for bsky/conc/dstamp/kuma/lvl5/mailu/rcust/shot
(32 files) were at the repo root; move them into machine-docs/ to match the
mandated file-location rule (DECISIONS/DEFERRED/INBOX + older phases already
live there). AGENTS.md gains an explicit File-location rule. No content change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-11 20:57:03 +00:00

1.2 KiB
Raw Blame History

BACKLOG — phase bsky

Build backlog

  • B1: Root-cause diagnosis — inspect recipe compose/entrypoint + actual :0.4 image vs exact tags on cc-ci (2026-06-11)
  • B2: Upstream research persisted to cc-ci-plan/upstream/bluesky-pds.md (plan repo f395247)
  • B3: DECISIONS.md entry — pin choice (exact 0.4.219 over 0.5.1-main / digest pin), version label bump
  • B4: Mirror PR branch upgrade-0.3.0+v0.4.219 — compose.yml re-pin + label bump; open PR on recipe-maintainers/bluesky-pds
  • B5: !testme on the PR → full lifecycle green (install/health, upgrade-path status justified, backup/restore, functional, L5 lint); record level under de-capped semantics + reconcile expected baseline
  • B6: Screenshot on the green PR run — verify PNG real/representative/credential-free (Read it); SCREENSHOT hook only if needed
  • B7: Claim M1 (root cause + green fix PR + screenshot verified)
  • B8: Close DEFERRED bluesky entries with pointers; JOURNAL note updating shot-phase N/A disposition
  • B9: Operator handoff summary in STATUS-bsky.md (what was wrong, what the PR changes, post-merge expectations incl. canonical/warm reseed)
  • B10: Claim M2

Adversary findings

(Adversary-owned)