# BACKLOG — phase `regall`

## Build backlog

### Batch 1 (DONE)
- [x] B1a: drone PR#1 → Drone 726 → L5 ✓
- [x] B1b: gitea PR#1 → Drone 727 → L5 ✓
- [x] B1c: matrix-synapse PR#4 → Drone 725 → L5 ✓

### Batch 2 (DONE)
- [x] B2a: mumble PR#1 → Drone 732 → L5 ✓
- [x] B2b: lasuite-meet PR#7 → Drone 730 → L5 ✓
- [x] B2c: n8n PR#6 → Drone 731 → L5 ✓

### Batch 3 (DONE)
- [x] B3a: custom-html PR#5 → Drone 737 → L5 ✓
- [x] B3b: mattermost-lts PR#2 → Drone 739 → L5 ✓
- [x] B3c: mailu PR#4 → Drone 738 → L5 ✓

### Batch 4 (DONE)
- [x] B4a: ghost PR#6 → Drone 744 → L5 ✓
- [x] B4b: immich PR#3 → Drone 745 → L5 ✓
- [x] B4c: lasuite-docs PR#6 → Drone 743 → L5 ✓

### Batch 5 (DONE)
- [x] B5a: lasuite-drive PR#3 → Drone 749 → L5 ✓
- [x] B5b: plausible PR#3 → Drone 758 → L5 ✓ (genuine upgrade; recipe bug in PR#4 no-op)
- [x] B5c: uptime-kuma PR#4 → Drone 748 → L5 ✓

### Batch 6 (DONE)
- [x] B6a: custom-html-tiny PR#8 → Drone 752 → L5 ✓
- [x] B6b: bluesky-pds PR#3 → Drone 753 → L5 ✓

### Post-sweep (DONE)
- [x] B7: Results table built — all 21 GREEN, 0 prevb regressions (see STATUS-regall.md)
- [x] B8: No prevb-caused regressions to fix
- [x] B9: N/A (no fixes needed)
- [x] B10: M1 CLAIMED — 2026-06-17T04:45Z
- [x] B11: M2 CLAIMED — 2026-06-17T04:45Z

## Adversary findings

### A-regall-2 [adversary] OPEN @2026-06-17T03:25Z — plausible backup_restore=fail; classify prevb regression or flake

**Filed:** 2026-06-17T03:25Z
**Severity:** MEDIUM — backup_restore failure drops plausible from baseline L5 to L2. Blocks M1 classification.

**Run:** 750 (Drone 750, PR#4). Result: level=2, backup_restore=fail.
**Baseline:** run 658, level=5, backup_restore=pass.

**Failure:** `test_restore_returns_state` — `ERROR: relation "ci_marker" does not exist` after restore.
- Backup test passed (only checks artifact file exists, 0.134s — does NOT verify ci_marker content)
- Restore completes (test_restore_healthy passes), but ci_marker table absent from DB

**Prevb-specific difference:**
- Run 750 upgrade: `version=3.0.1+v2.0.0→3.0.1+v2.0.0` (NO-OP: UPGRADE_BASE_VERSION='3.0.1+v2.0.0' matches recipe.yml version)
- Run 658 upgrade: `version=d77adba4698b` (git ref — genuine upgrade from published base to tested commit)
- Hypothesis: prevb's new base-resolution path resolves UPGRADE_BASE_VERSION to a static version; if recipe.yml also pins that same version, the upgrade is a no-op, which may change the DB state sequence enough to break backup/restore
- Same failure pattern in m2r-plausible and m2rr-plausible (prevb development runs) — both level=2, backup_restore=fail

**Builder rerun:** Drone 754 — **ALSO FAILED** (same error, same level=2, backup_restore=fail).

**Adversary verdict: GENUINE REGRESSION (2/2 runs failed) — NOT a flake.**

Both runs 750 and 754:
- `version=3.0.1+v2.0.0→3.0.1+v2.0.0` (no-op upgrade via UPGRADE_BASE_VERSION)
- `ERROR: relation "ci_marker" does not exist` after restore
- Backup test passes (artifact only, not content)
- Restore test fails

**Required:** Builder must diagnose the no-op upgrade path and either:
(a) Fix the backup/restore to work correctly under same-version upgrades, OR
(b) Update UPGRADE_BASE_VERSION to an older version so upgrade is genuine, OR
(c) Document why plausible backup_restore is not feasible and mark as known-fail

Builder-INBOX written @2026-06-17T03:30Z with full details.

**CLOSED @2026-06-17T03:45Z:** Builder diagnosis accepted. Run 758 (PR#3, d77adba4698b) → L5, backup_restore=pass. Pre-existing recipe bug in 3.0.1+v2.0.0, NOT prevb regression. Plausible counts as L5 GREEN in regall sweep.

---

### A-regall-1 [adversary] CLOSED @2026-06-17T02:20Z — mailu baseline table corrected

**CLOSED:** Builder corrected STATUS-regall.md in commit 7c6134a: mailu upgrade rung now shows "pass" not "skip (no deployable base)".

~~### A-regall-1 [adversary] OPEN — mailu baseline table has incorrect upgrade rung~~

**Filed:** 2026-06-17T02:10Z
**Severity:** LOW (informational — does not block the sweep, but affects regression classification)

**Discrepancy:** STATUS-regall.md baseline table shows mailu upgrade rung = "skip (no deployable base)".
The actual baseline run 526 (Jun 12) shows `upgrade: "pass"` in both `results` and `rungs` sections.

**Evidence (cold-verified from /var/lib/cc-ci-runs/526/results.json):**
```
"results": { ..., "upgrade": "pass", ... }
"rungs": { ..., "upgrade": "pass", "backup_restore": "skip", ... }
```
The `skip` in run 526 applies to `backup_restore` (mailu is not backup-capable), NOT to upgrade.

**Impact:** If post-prevb mailu runs show upgrade=skip or upgrade=fail, it would be incorrectly
considered within-baseline (the table says "skip") rather than a regression from the true baseline
(upgrade=pass).

**Required correction:** STATUS-regall.md should read: `mailu | 5 | pass | 526` for the upgrade rung.

**Adversary closes:** after Builder corrects the baseline table in STATUS-regall.md.