journal(canon): production re-fire COMPLETE (Result=success, gitea cold-green via lfs PASS under parity PATH) — DEFECT-3 closed; launched clean determinism 2nd sweep (custom-html now at 1.13.0 → all 16 promoted at-latest)

machine-docs/JOURNAL-canon.md

@@ -186,3 +186,28 @@ This fire so far (journalctl -u nightly-sweep.service --since 13:01):
 - Now at discourse (RUN seed, deploying). CRUX still pending: gitea (8th) must flip cold-GREEN under
   the parity PATH (git-lfs now present) — that is the DEFECT-3 acceptance criterion.
 Polling every ~5 min (single node, fire in flight). Not touching the node until it completes.
+
+## 2026-06-17 ~14:40 — production re-fire COMPLETE; DEFECT-3 closed; launching clean determinism 2nd sweep
+
+The DEFECT-3 re-fire (nightly-sweep.service, 13:01:01→14:37:22, Result=success, status=0, single
+serial) completed cleanly under the deployed Drone-parity PATH. **gitea crux RESOLVED:**
+`test_lfs_roundtrip PASSED` (the test that redded on the missing-git-lfs fire) → gitea cold-GREEN in
+production env, then the documented app.ini warm-advance exception (3.5.3 kept). So the only reason
+gitea redded before was the timer-env git-lfs gap, now fixed by host-PATH parity — confirming the fix
+is the right one (the sweep validates exactly as Drone CI does). No NEW promote failures surfaced that
+the manual env had masked → DEFECT-3 is the LAST env-parity gap, now closed.
+
+custom-html 1.11.0→1.13.0 advance promoted in this real timer fire: this is simultaneously the M2.5
+non-hollow real-fire proof AND the M2.6 constructed older→new advance (canonical(older)→new tagged,
+real delta, samever step-back never fires because tag>canon by construction). 14 promoted-at-latest
+recipes SKIP no-new-version live = determinism preview inside the production fire.
+
+**Why a clean 2nd sweep now (M2.3):** in this fire custom-html was the one promoted recipe that RAN
+(I'd reset its canonical to 1.11.0 pre-fire to stage the advance). Now it's at 1.13.0 = latest, so all
+16 promoted canonicals are at-latest. An immediate 2nd sweep therefore yields the clean run-twice
+result the plan's M2.3 asks for: the 15 promoted-at-latest SKIP (incl. custom-html), and ONLY the 5
+documented exceptions RUN (gitea 3.6.0 advance retry, discourse/mattermost-lts/mumble reds, bluesky
+warm-routing). Reds re-running is the accepted, DECISIONS-recorded deviation from the literal "skip
+every recipe" (cannot weaken a test to force a promote). Launching it as the real service again
+(systemctl start) for max faithfulness; ~96 min (discourse's deterministic 60-min deploy-timeout
+dominates). Disk budget healthy: ci-warm 1.1G / 16 volumes, 38G free.