Archilyzer · Source

archilyzer

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

commit 296dbe81fe4e41f33c00f0d982254f9c2d319fcf
parent b6316a160f3a4d7e1c27ddd24b78a9a30a168946
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Mon, 14 Sep 2026 16:37:42 -0400

plans: the /channels rack lands on main; Phase 3 slice 1 is next

Fast-forward of editor-channels-rack (7811b9d -> b6316a1) onto c9461ec. tsc
clean across the workspace; the 533/533 e2e ran on the identical tree. The
worktree and branch are deleted. The rollout continues in parallel; the
channel moves go through the merged deck.

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

Diffstat:
Mplans/STATE.md | 20++++++++++++++++----
1 file changed, 16 insertions(+), 4 deletions(-)

diff --git a/plans/STATE.md b/plans/STATE.md @@ -3,7 +3,7 @@ The working memory for the local-AI derived-corpus work. Rewritten at the end of every session, before context is cleared. See [`README.md`](README.md) for the protocol. -**Last updated:** 2026-09-13 — **gate A passed and `main` moved; the interlude shipments and one-core Phase 2 are all merged +**Last updated:** 2026-09-14 (the rack landed; see the Next block) — 2026-09-13: **gate A passed and `main` moved; the interlude shipments and one-core Phase 2 are all merged on one branch**, `integrate/2026-09-storage-priority`, tip **`bd3d4ec`**, unmerged. Off `e74f005`: `relocate-channel-media` (from `storage/relocate-media`), then `channel-priority` (from `channel-priority/s5`), then Phase 2's five slices in the order their reviews cleared — @@ -327,7 +327,19 @@ branch and worktree is deleted; what remains is `one-core/phase-1` (the primary until it switches to `main`), `one-core/s0-pause` (parked for the next release), `diet-series`, `p1-e2e` and `worktree-duplicates-page`. -**Next:** the **O2–O9 rollout**, editor stopped. **The migration script only exists on +**The `/channels` rack shipped 2026-09-14** and `main` is fast-forwarded to **`1bc8765`** +(`64b5573` → `1bc8765`, forked from `a1058d0`; tsc clean, common 1159, editor e2e **533/533** +on the identical tree — the fast-forward got a `tsc --noEmit` smoke, not a second 25-minute +suite). One deck, a sticky rack and a meter bridge; the record is +[`editor-channels-rack.md`](editor-channels-rack.md). The worktree and branch are deleted. +It merged BEFORE the rollout's channel moves on purpose: those go through the `/channels` +bulk deck, which the rack rewrote, so the operator does them on the merged page. **Next, in +parallel:** the rollout below (operator-physical), and **one-core Phase 3 slice 1** — +`common/views/` — planned in [`one-core-phase-3.md`](one-core-phase-3.md), decided with the +operator 2026-09-14 as slice 1 only. Phase 3 slice 3 rewrites `ChannelsTable.tsx` again; +landing the rack first keeps that a rebase-free rewrite of one file. + +**The rollout:** the **O2–O9 rollout**, editor stopped. **The migration script only exists on `main`**, so the checkout switches first; the rule is "migrate before the first BOOT", not before the switch. Done 2026-09-13: `git switch main`, then the migration for real — 67 channels (one fewer than the 68 planned), 27 entries, 14 ranked, 14 `sync=paused`, no focus, @@ -347,8 +359,8 @@ pauses — transcription, downloads and digests come up running and the backfill held. Boot this release once, confirm all four `held` keys are in the live `settings.json`, then take it. -**Then one-core Phase 3** — views in the core, editor as shell, four slices -([`one-core.md`](one-core.md) §Phase 3). Read `common/architecture.test.ts`'s allow-list +**Then the rest of one-core Phase 3** — views in the core, editor as shell, four slices +([`one-core.md`](one-core.md) §Phase 3); slice 1 is already in flight (above). Read `common/architecture.test.ts`'s allow-list first: it is the shortest accurate statement of what is still tangled. Phase 2 left it at **eleven entries, byte-identical to the base**, while ADDING `"components"` to `FORBIDDEN.lib` — the forbidden list grew and the debt ledger did not.