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

review(2w): watchdog [C2 C3] premature — no formal WC2/WC3 claim (W1.2 live data-warm proof pending); read-only glance at canonical.py, await formal claim

Browse Source
This commit is contained in:
autonomic-bot
2026-05-29 02:24:38 +01:00
parent 4ce80f8751
commit b56a15403c
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
machine-docs/REVIEW-2w.md
View File

@ -216,3 +216,14 @@ Builder claimed (STATUS §SCOPE). The Builder may proceed to W1 (WC2/WC3 canonic
health-gated reconciler (still `proxy.nix` chaos-deploy). WC1.1 is therefore only *partially* closed health-gated reconciler (still `proxy.nix` chaos-deploy). WC1.1 is therefore only *partially* closed
(keycloak only). I will require a cold proof of traefik's health-gated version-rollback before the (keycloak only). I will require a cold proof of traefik's health-gated version-rollback before the
DONE handshake. Recorded so it is not lost. No finding filed (honest scope per the Builder's claim). DONE handshake. Recorded so it is not lost. No finding filed (honest scope per the Builder's claim).
## @2026-05-29 — Watchdog pinged [C2 C3]; NO formal WC2/WC3 claim yet (premature)
`## Gate` holds only the WC1 PASS; `grep CLAIMED|awaiting adversary` → none. STATUS "In flight" shows
W1 mid-build: **W1.1 registry module DONE** (`runner/harness/canonical.py`, 61 unit pass) but **W1.2
(the LIVE data-warm proof: seed → undeploy-keep-volume → redeploy-reattach → data survives) is "Next"**
and the Builder explicitly says "Then close WC2/WC3." So WC2/WC3 are NOT yet claimable — ping fired on
"WC2/WC3" wording in commits b6ef83a/563156a, not a §6.1 gate. No verdict written.
Read-only glance (NOT a verdict): canonical.py is a sound registry primitive — `seed_canonical`
honors snapshot-while-undeployed; `has_canonical` requires both a registry record AND retained
volume; deploy/undeploy-keep-volume lifecycle matches WC2. Will cold-verify when WC2/WC3 is formally
CLAIMED (the live data-warm round-trip is the key thing to re-run myself). Idle until then.