# STATUS — phase mailu (backupbot labels for mailu recipe)

**Phase plan:** `/srv/cc-ci/cc-ci-plan/plan-phase-mailu-backup.md`
**Builder:** autonomic-bot / Claude (Builder loop)
**Started:** 2026-06-11T18:00Z

---

## Current state

**Active work:** Bootstrapping — authoring recipe PR + cc-ci ops/test changes.

**Gate M1:** NOT YET CLAIMED

**Gate M2:** NOT YET CLAIMED

---

## DoD tracker (M1)

- [ ] Data-layout research documented (which volumes hold durable state, justification in PR desc)
- [ ] Recipe-mirror PR open with backupbot v2 labels (admin `/data` + imap `/mail`)
- [ ] Version label bumped in compose.yml
- [ ] cc-ci: `tests/mailu/ops.py` with pre_backup (seed mailbox) + pre_restore (delete mailbox)
- [ ] cc-ci: `tests/mailu/test_backup.py` asserting mailbox present at backup time
- [ ] cc-ci: `tests/mailu/test_restore.py` asserting mailbox restored after restore
- [ ] cc-ci: `tests/mailu/PARITY.md` updated (P4 now covered, not N/A)
- [ ] Full lifecycle green at PR head (L5) including backup/restore rung — via drone `!testme`
- [ ] Before/after level recorded (was: L4 intentional skip → now: L5 earned)

## DoD tracker (M2)

- [ ] Fresh Adversary cold pass (independent re-trigger at PR head)
- [ ] Levels reconciled
- [ ] DEFERRED entry closed
- [ ] STATUS-mailu.md operator summary
- [ ] REVIEW-mailu.md shows PASS for M1 + M2 (within 24h)

---

## Blocked items

(none)

---

## DONE

Not yet. Written here only when all DoD items have Adversary PASS in REVIEW-mailu.md.