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

status(2w): W1.1 registry module done; next W1.2 enroll custom-html + live data-warm proof

Browse Source
This commit is contained in:
autonomic-bot
2026-05-29 02:15:35 +01:00
parent b6ef83ab0b
commit 9144eeac2f
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
machine-docs/STATUS-2w.md
+8
View File
@@ -84,6 +84,14 @@ nightly full-cold sweep. Definition of Done = WC1–WC9 (plan §1), each Adversa
**W0 COMPLETE — Adversary PASS @2026-05-29.** Now in **W1 (canonical registry, WC2/WC3)**. **W0 COMPLETE — Adversary PASS @2026-05-29.** Now in **W1 (canonical registry, WC2/WC3)**.
**W1 progress:** W1.1 canonical registry module DONE (b6ef83a) — `runner/harness/canonical.py`
(enrollment via recipe_meta.WARM_CANONICAL, registry canonical.json, deploy/undeploy-keep-volume/
seed lifecycle) + 4 unit tests (61 unit pass). **Next: W1.2** — enroll custom-html
(`tests/custom-html/recipe_meta.py: WARM_CANONICAL=True`) + LIVE data-warm proof: seed a
warm-custom-html canonical with content → undeploy-keep-volume (verify volume retained, app down) →
deploy_canonical (reattach) → assert the written content survives; re-warmable from scratch. Then
close WC2/WC3.
**W1 plan (WC2 data-warm canonical model + WC3 closure):** **W1 plan (WC2 data-warm canonical model + WC3 closure):**
- WC2: a declarative **canonical registry** — which recipes are canonical + at which known-good - WC2: a declarative **canonical registry** — which recipes are canonical + at which known-good
commit/version — with each canonical app at a **stable domain `warm-<recipe>`**, kept **data-warm** commit/version — with each canonical app at a **stable domain `warm-<recipe>`**, kept **data-warm**