Archilyzer · Source

archilyzer

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

commit 927e559f62e24b56736990616b6232245dc94cae
parent db37837b04ce66384f3d55b3ffdd47cbc2384b53
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Fri,  9 Oct 2026 13:31:00 -0400

plans: release 18 — As it went: Wave 0, main merged in again, the gates and the full suite on a837bf85

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Diffstat:
Mplans/release-18.md | 16++++++++++++++++
1 file changed, 16 insertions(+), 0 deletions(-)

diff --git a/plans/release-18.md b/plans/release-18.md @@ -1556,3 +1556,19 @@ export unit ok, editor build ok, e2e (ops-api, jobs, publish) **38 passed, 0 fai `main` in the primary checkout. Owed, with the rollout, to the operator (`~/reports/release-18/RUNBOOK.html`; scripts `~/reports/release-18/scripts/r18-{build,restart,smoke,publish-now,jeralyzer-preview,hub}.sh`, guarded on `bf796701`). + +**Wave 0 (2026-10-09) — `main` `e921f82f` merged in again**, `4cffda3f`: six conflicts, both sides kept +(`jobDetail` reads a publish stage's run and a fetch-windows batch; `GET_ARG_OPTIONAL` keeps `tags`, `channels` and +`publish`; PUBLISH.md keeps the "three ways to drive it" table with main's fetch-windows row and main's two-step +reports paragraph; the changelogs release 18 first). `ac5832de`: the jobKinds invariant names fetch-windows as +drainable but not ingest (it writes only the clip cache). Gates: tsc clean; common **3465**; editor unit **159**; +`test:scripts` **677 + 3 skipped**; mcp **292**; export unit **116**; homepage unit **23**; `docs env|files --check`, +`settings example --check` clean; builds ok — editor 119 s, export 60 s (over the committed fixture compose: the +primary's `export/public` holds a cited-only compose), homepage `build:nodata` 37 s, umtool capped 67 s. **The whole +editor suite on `ac5832de`: 711 passed, 10 failed, 12 skipped, 71 min**, run while the machine sat at load 43 (three +implementers' unit suites and a peer render): six `audio-check-scenarios`, two `auto-queue`, `dashboard-answers`' +5 s budget, `undownloaded` "one-click whisper". The four specs alone: **43 passed, 2 failed** (audio-check "happy +path" and "mid-stream corruption" — the fixture's corrupt checkpoint landed before any `.good` existed); the +audio-check spec alone again: **14 passed, 1 failed** — "happy path", its first test against a cold test server +both times, green in the full run. No code on the audio-check path changed on either side of the merge. The rollout +scripts are re-guarded on `ac5832de`. Step 5 (fast-forward `main` to `r18/integration`) is still the operator's.