Archilyzer · Source

archilyzer

Archilyzer
git clone https://archilyzer.pages.dev/source/archilyzer.git
Log | Files | Refs | README | LICENSE

commit b29e34ccb4e9dce6bbf6bc9375357833e7700e4d
parent a7501cb3f4b84831663a44b93cc68c68252d05d7
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Wed, 23 Sep 2026 20:20:01 -0400

plans: gate B record — reachable media only, applied 2026-09-23

The backfill lane is held with allowRedownload off, set through the lane
form on /operations/diarization; before/after, counts, and what is
deliberately left undone (the lane stays disabled).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
Mplans/one-core-phase-1.md | 43+++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+), 0 deletions(-)

diff --git a/plans/one-core-phase-1.md b/plans/one-core-phase-1.md @@ -1538,6 +1538,8 @@ where it read *Idle*. `backfill.allowRedownload` and the channel scope. As configured today it would re-fetch audio for ~66,540 `missingInput` videos. The 1.3 migration left the lane `enabled: false`; the tree's channel leaves are the scope from now on. + **Decided and applied 2026-09-23 — reachable media only; see "Gate B — PASSED + 2026-09-23" below.** - **`video-page.spec.ts:216`** ("Delete directory wrong-id confirmation shows an error") is a known ordering flake, reported in 1.3 and 1.4 and not fixed: it passes 20/20 when re-run alone on the same commit, and nothing in this phase @@ -1565,3 +1567,44 @@ time; add them here if they were kept. Consequence: the 1.3 retirements stand, and the 2026-09 integration (`integrate/2026-09-storage-priority`, Phase 2 included) fast-forwards to `main`. Gate B (the backfill lane on production) is still owed before that lane is armed. +*(Done 2026-09-23 — next section.)* + +## Gate B — PASSED 2026-09-23 + +**Decision (operator, 2026-09-23): reachable media only.** `backfill.allowRedownload: false`, +the lane held, scope every channel. Folded into the one-core Phase 3 release +(`one-core-phase-3.md`, "Release 2026-09-23") as a prelude: a settings change made through the +existing surface, plus this record — **no code**. + +**Surface.** The backfill lane form on `/operations/diarization` (`LaneSettingsForm` → +`saveBackfillLaneSettingsAction`, `editor/app/operations/settingsActions.ts:207`), driven by +Playwright against the live editor on `:3001`, then at `main` `54cf1b31`. No hand edit of +`settings.json`, and no ops route — none carries `allowRedownload`. + +Before (`settings.json`, read-only): + +``` +backfill: {"enabled": true, "concurrency": 1, "allowRedownload": true} (enabled = retired legacy key) +autoQueue.backfill: {"enabled": false, "maxWorkers": null, "replaceAutoSubs": false, "order": "newest", "snoozeUntil": null, "held": false} +/operations/diarization: Speaker diarization Off · 679 reachable · 74,046 no media · 1.86% of 76,138 + Auto-backfill: Runner stopped · 0 in flight +``` + +After: + +``` +backfill: {"concurrency": 1, "allowRedownload": false} (legacy `enabled` dropped by the writeSettings round trip — expected) +autoQueue.backfill: {"enabled": false, "maxWorkers": null, "replaceAutoSubs": false, "order": "newest", "snoozeUntil": null, "held": true} +/operations/diarization: Speaker diarization Off · 679 reachable · 74,046 no media · 1.86% of 76,138 + Auto-backfill: Runner stopped · button now reads "Resume the lane" (Holding) · 0 in flight +``` + +**Pass:** `held: true`, `allowRedownload: false`, `enabled: false` — all hold. Nothing +dispatched. + +**Not done, on purpose.** The lane stays disabled. Arming it (enable → Resume) is a later, +separate act, and when it happens the expected work is the reachable **~679**, not the +~66,540 `missingInput` figure above. Two stale numbers to know about, neither changed here: +the form's hint text still says 836 (a measured figure that has aged — +`LaneSettingsForm.tsx:101`), and `plans/tools/phase1-numbers.ts` does not filter +`handling: "youtube"`, so its `missingInput` is the whole bucket.