Archilyzer · Source

archilyzer

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

commit 5ab175935155d3e2d5dc170db1414d1b7ece1aca
parent 8d53d72e5f42f9459636a3ed102052383979b582
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Thu, 24 Sep 2026 16:40:27 -0400

plans: slice 4b record — gates on the merged tip (8d53d72e)

Merge of main a9f5961e (slice 3a) as 8d53d72e: tsc clean; common 1723;
editor unit 67; test:scripts 156 + 1 skip; mcp 219; numbers diff empty;
editor and export next build green, no zod in either .next/static,
ƒ /api/view/[name] present; the plan's 34-spec editor e2e 190/190. Plus the
cause of the first export-build failure (the live editor's build-deploy job
regenerated export/public without tags.json; not this slice).

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

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

diff --git a/plans/one-core-phase-3.md b/plans/one-core-phase-3.md @@ -1074,3 +1074,24 @@ No profiling was needed. Run #2 was taken by the coordinator with the same harne | e2e editor, the plan's 34 specs, at `7c03d7c9` | **190 passed**, 0 failed, 11.1 min, exit 0 — every spec the plan named exists; none dropped | | e2e editor after the review fixes (`973e59ee`): storage-locations, channel-storage, channel-rename, sites-crud, channels, digest, availability | **63 passed**, 0 failed, 3.7 min | | e2e export: site-branding, related-sites, pwa-search, ask-chat | **33 passed**, 0 failed, 1.0 min | + +**Merged with `main` `3241fed2` (slice 3a) as `7dfd7508`** — conflicts only in this file and +`editor/CHANGELOG.md`, both sides kept, 3a first. Gates on the merged tip: + +| gate | result | +|---|---| +| `pnpm -r --workspace-concurrency=1 exec tsc --noEmit` | clean | +| common tests | **1723/1723** (1709 + slice 3a's 14) | +| editor unit | 67/67 | +| `pnpm run test:scripts` | 156 pass / 1 skip | +| mcp | 219/219 | +| `next build` editor / export | both green; `├ ƒ /api/view/[name]`; `grep -rl 'ZodError\|_zod'` over both `.next/static` prints nothing | +| numbers tool vs `main` (frozen inputs) | diff empty, 3,832 lines | +| e2e editor, the plan's 34 specs | **190 passed**, 0 failed, 12.7 min, exit 0 | + +The export build first failed on the merged tip with `ENOENT export/public/tags.json`. Not this +slice: the live editor's `build-deploy` job `01M3AADF600BDC99T2WPH1KBQB` (14:21–14:37, an +incremental build:index on the real corpus plus a Jeralyzer deploy) regenerated the primary's +`export/public/` without a `tags.json` (Jeralyzer has no curated tags), which left this +worktree's per-path symlink to it dangling. The stale link was removed and the export build +re-run green.