review+inbox(canon): DEFECT-3 — real timer fire reds gitea on MISSING git-lfs in nightly-sweep.service runtimeInputs (same class as bash gap); manual sweep env (had git-lfs, gitea cold-green) != production timer env → M2.2 promote evidence must be re-validated under the real timer; heads-up sent

machine-docs/BACKLOG-canon.md

@@ -73,3 +73,16 @@ pieces). M2 = proven end-to-end in real CI.
   overlay + ready-probes). **Close only after a fresh full sweep where the green recipes actually
   write canonicals at the tested tag (incl. the 4 failure classes), AND determinism (M2.3) holds
   (run-twice → skip-all).** Note the drone 600s timeout may be node-contention, not wiring — watch it.
+- [ ] **DEFECT-3 [adversary] (deployed nightly-sweep.service env missing git-lfs → manual-sweep env ≠
+  production-timer env)** — OPEN. The REAL timer fire (12:34Z, nightly-sweep.service, /etc/cc-ci@cebd293)
+  reds gitea at the custom tier: `tests/gitea/custom/test_lfs_roundtrip.py` → `git: 'lfs' is not a git
+  command` → level 3/5 → rc=1. Same bug-class as the missing-`bash` gap (cebd293): the systemd
+  service's nix `runtimeInputs` lacks `git-lfs`. BUT in the MANUAL authoritative sweep gitea cold-PASSED
+  (rc=0, git-lfs present) and only the warm-advance failed. So: (a) real deploy defect — add `git-lfs`
+  (and audit runtimeInputs for any other tool the manual env has but the service lacks: openssl, jq,
+  curl, rsync, restic, etc.); (b) METHODOLOGICAL — the manual M2.2 authoritative sweep ran in a RICHER
+  environment than the production timer, so its 16 promoted canonicals are NOT proven to reproduce under
+  the real timer. The DoD is "proven end-to-end in REAL CI (the timer)". Repro: `journalctl -u
+  nightly-sweep.service | grep -A40 "sweep: gitea RUN"`. **Close only after: git-lfs (+ any other missing
+  tool) added to runtimeInputs, redeployed, and a REAL TIMER FIRE re-validates the promoted set in the
+  production environment (the manually-promoted canonicals hold, OR are re-promoted by the timer itself).**