Archilyzer · Source

archilyzer

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

commit e4bc59181ffa629a0c7c6d4fb36383af208a3398
parent 0eb056bb29f2f8d7bd97235ec91bd2315ccf43bb
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Mon, 28 Sep 2026 12:25:25 -0400

plans: release 13 — the lows bundle, the build image, one-core Phase 5 slices 1–3 (numbered 13: a parallel session owns release 12, the source mirror)

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

Diffstat:
Aplans/release-13.md | 43+++++++++++++++++++++++++++++++++++++++++++
1 file changed, 43 insertions(+), 0 deletions(-)

diff --git a/plans/release-13.md b/plans/release-13.md @@ -0,0 +1,43 @@ +# Release 13 — the lows bundle, the build image refreshed, one-core Phase 5 slices 1–3 + +`main` at `bf6904e8`: release 11 merged in full and **cut as 0.10.0** on 2026-09-28 (editor +`24c8352e`, export `bf6904e8`), its rollout in progress (`release-11.md`, "Rollout, as done"). +Release 13 is the second half of the operator's 2026-09-28 choice of all four bundles: the lows +left by release 11, the `Dockerfile.build` image refreshed and proved, and one-core Phase 5 +([`one-core.md`](one-core.md), "Phase 5") slices 1–3, after a corrected plan doc. Rules: +`plans/tools/implementer-rules.md`, with the commit trailer this release's prompts give. + +**Why 13, not 12:** a parallel session owns **release 12** — the source mirror +(`plans/release-12.md` on `r12/paths-fix`; slices Q then R; plan +[`source-mirror.md`](source-mirror.md)). The two releases share `editor/CHANGELOG.md`'s +`[Unreleased]` and a few files (`common/bin/doctor.ts`, `common/lib/envVars.ts`, +`common/lib/paths.ts`, umtool's path defaults, the docs); whichever merges second resolves the +join, and a code conflict goes back to its slice. + +**The operator's standing choices** (2026-09-28): +- **The LM chat-only tier is closed as moot:** Legal Mindset's filter has + `includeLivestreams: true`, so the tier never changes what is kept. +- **Merging:** each slice merges to `main` after its review, `--no-ff`. No cut, no deploy and no + restart inside a slice; the parent does the one build-image rebuild, the one build-only Build all + and (at the end of Phase 5) the one umtool rebuild + restart. +- **Worktrees:** the seven `r11-*` worktrees stay until release 12's worktrees are gone. Ports are + index-based, and removing them would move `r12-paths-fix`'s block while that session runs. + Release 13's worktrees are named `r13-*`, so they sort after it. + +## The slices + +| Slice | Branch | What | Owns | +|---|---|---|---| +| W1 | `r13/lows-editor` | Diagnostics cards keep their retry log when a retry empties the bucket; the `transcript-source.spec.ts:76` flake; `/sites` "built <when>" refreshes when a homepage build ends; `/jobs` labels for the four hub/homepage kinds; a queued-cancel writes its final sidecar status; doctor's worker engine binary from `paths` (L7); an `editor/package.json` `test` script | `editor/app/channels/[slug]/components/stages/**`, `editor/app/sites/components/{JobLane,HomepageBuildButtons}.tsx`, `common/jobs/{jobKinds,registry}.ts`, `common/lib/streamCommand.ts`, `common/bin/doctor.ts` (L7 only), the two specs | +| W2 | `r13/lows-export` | `ChartView` reaches `--chart-6` through `seriesColor(i)`; an export unit `test` script (named in the rules and CONTRIBUTING); O5's wording lows; the 2origin stage guard; `no-data.spec` skips on `workers > 1`; the mcp docs move to `archilyzer mcp` | `common/components/charts/ChartView.tsx`, `export/package.json`, `umtool/report-to-video/{svg-faces.mjs,README.md}` (comments), `export/playwright.2origin.config.ts`, `homepage/e2e/no-data.spec.ts`, `mcp/README.md`, `AGENTS.md`, `README.md`, `CONTRIBUTING.md`, `plans/tools/implementer-rules.md` | +| W3 | `r13/build-image` | `Dockerfile.build` on Node 22 and pnpm 11; the stale `--network=none` comments; `archilyzer doctor` checks the build image's presence and age | `Dockerfile.build`, `common/publish/build.ts` (comments), `common/bin/doctor.ts` (the image check) | +| P0–P3 | `r13/phase-5` | one-core Phase 5: the corrected plan doc (P0, to the operator first), then slices 1–3 stacked | per `plans/one-core-phase-5.md` | + +**Order:** W1 ‖ W2 ‖ W3, merged W1 → W2 → W3; then the parent rebuilds the build image and runs +one build-only Build all. Then Phase 5, which merges to `main` only when all three slices pass. +Then one integration gate on `main` (`r13/integration`) and the runbook +(`~/reports/release-13/MORNING.html`). + +## Record + +## Rollout