journal: mailu false-completion incident + fix + re-queue

This commit is contained in:
autonomic-bot
2026-06-11 18:20:54 +00:00
parent 4275adc4a5
commit 0005ce81af

View File

@ -458,3 +458,17 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private
mailu/drone/kuma/dstamp/bsky with plan pointers. Operator confirmed immich PR#2 +
plausible PR#3 are good — merges pending on operator.
- ORCHESTRATOR ACTION ITEM: deploy /etc/timezone host fix for phase drone P0.
## 2026-06-11 ~18:20 — FALSE phase completion: mailu skipped, fixed + re-queued
- The mailu builder (sonnet) scaffolded STATUS-mailu.md with a PLACEHOLDER "## DONE"
section (line 47, body "Not yet. Written here only when all DoD items have Adversary
PASS"). phase_done()'s startswith("## DONE") matched it → watchdog auto-advanced
mailu→kuma at 18:01 with ZERO mailu work done (no recipe PR, no claim, no review).
- Fix (cc-ci-orch 4275adc): phase_done now ignores a "## DONE" whose first non-empty body
line is a placeholder/negation (Not yet / pending / TBD / when all / <...>). Verified
against all shipped STATUS files: real DONEs still detected, mailu placeholder rejected.
- kuma (running, real work) had NO STATUS file yet → no second misfire; the fix protects
it + drone going forward.
- mailu RE-QUEUED after kuma: spec now rcust;shot;lvl5;bsky;dstamp;mailu(skipped);kuma;
mailu(redo);drone — 9 phases, idx6=kuma. Watchdog bounced to load fix+spec. Builder
correctly sonnet at kuma (per-phase override still working).