commit b2ee9c4e402801b3e3df4fe07063d209ac3f9fed
parent 482fc437fe4287e1e0e24ed12b2da7111f8ba84c
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Mon, 28 Sep 2026 13:18:31 -0400
plans: release 13 — W2's fix round in its record (S1 --silent, Q1 the Use with AI page, Q2 the editor bullet, L1/L2 left)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Diffstat:
1 file changed, 56 insertions(+), 0 deletions(-)
diff --git a/plans/release-13.md b/plans/release-13.md
@@ -185,4 +185,60 @@ in the homepage's docs content or in scripts; what it found and left is under "F
- **`main` moved to `e6c5d2e3` during the slice** (release 12's changelog fix). Not merged: the
rules say merge `main` again only when the parent asks.
+#### Fix round (review: SHIP AFTER FIXES, `w2-review.md`)
+
+The review found one should-fix and answered the two questions above; the first and fifth
+found-and-left bullets are therefore closed.
+
+- **S1 — `pnpm archilyzer mcp` was not a clean JSON-RPC stream on pnpm 9 and 10.** `pnpm
+ archilyzer` is a `pnpm run`; pnpm 9 and 10 print its banner (a blank line, `> <pkg>@<ver>
+ archilyzer <dir>`, `> <command>`, a blank line) to STDOUT before the server starts; only pnpm
+ 11 prints `$ …` to stderr, which is all this slice had checked. 9.15.4 is what the Dockerfiles
+ install, and nothing pins the version. Every example is now `pnpm --silent -C … archilyzer mcp`
+ (the long spelling: `claude mcp add` has its own `-s`) — AGENTS.md, README.md (three), mcp/README.md
+ ("Run it" three, "Add to Claude Code", the `mcp.json` args), PUBLISH.md — and the five claims that
+ stdout is clean now say it is `--silent` that makes it so. Measured with an initialize request
+ and an empty `--local` dir: stdout is exactly one line, the answer, on **9.15.4, 10.18.0 and
+ 11.26.0** (`w2-fix-mcp-*-stdout.txt`); without `--silent` 9.15.4 gives 5 lines, the banner first
+ (`w2-fix-mcp-9-nosilent-stdout.txt`). FACTS' release 11 entry ("a clean MCP registration") is
+ amended. `CONTRIBUTING.md:157`'s `pnpm archilyzer mcp` stays: it lists the CLI's commands for a
+ person at a shell, not a registration.
+- **Q1 — the public "Use with AI" page moved too.** The snippet is built by
+ `export/app/use-with-ai/mcpSnippet.ts` (pure): keyed **`archilyzer`** on every site and the hub
+ (a site-id key breaks `/ask` and `/sweep`, whose tool names embed the key), `"args":
+ ["--silent", "-C", "/path/to/yt-dlp-transcript-browser", "archilyzer", "mcp"]`, the site's
+ `TRANSCRIPT_SITE_URL` or the hub's `TRANSCRIPT_HUB_URL` line kept, values JSON-escaped. A line
+ under it says why the name matters. The built page (`export/out/use-with-ai/index.html`) shows
+ exactly that. `mcpSnippet.test.ts` (3) parses the snippet; **with the page's old template put
+ back in the module (uncommitted), all 3 fail** (`w2-fix-bite-snippet.log`). Its own
+ `[Unreleased]` bullet in `export/CHANGELOG.md`.
+- **Q2 — `editor/CHANGELOG.md`** gets a new `## [Unreleased]` above `[0.10.0]` with one bullet: a
+ site's Charts tab gives a sixth series its own colour. The only `editor/**` file W2 touches; W1
+ adds its own `[Unreleased]` block, for the parent to join.
+
+| sha | what |
+|---|---|
+| `84992e73` | `docs:` `--silent` on every `archilyzer mcp` example; the stdout claims say why; FACTS |
+| `48d2df8e` | `export:` `use-with-ai/mcpSnippet.ts` + test (3); the page uses it, keyed `archilyzer`; `[Unreleased]` bullet |
+| `8995d635` | `editor:` `[Unreleased]` — the Charts tab's sixth series colour |
+| _this_ | `plans:` this fix round |
+
+**Gates:** tsc clean (`w2-tsc-5.log`); export unit **101/101** (98 + 3); common **2,116/2,116**;
+`pnpm --filter export exec next build` ok, 97 s, no dangling links before or after; e2e
+`responsive.spec.ts` alone (the one spec that visits `/use-with-ai/`, for phone overflow): **10
+passed, 0 failed, 56 s**.
+
+**Found and left in the fix round** (the review's lows):
+- **L1 — pnpm 11 may install before it runs, and prints that to stdout even with `--silent`.** In
+ a checkout with no install (and, the reviewer infers, one whose lockfile changed since the last
+ install) pnpm 11.26 installed before both `run` and `exec` and printed `Already up to date` /
+ `Done in …` to stdout. It hits the old `exec` form equally, so it is not W2's regression;
+ AGENTS.md and mcp/README.md now say "on an installed checkout" / "run `pnpm install` first".
+- **L2 — `README.md:114` says `corepack enable` makes "the pinned pnpm version" used; nothing is
+ pinned** (`package.json` has no `packageManager`; `Dockerfile:234-236` says so and installs
+ 9.15.4). The unpinned version is what made S1 reachable. For a later slice: pin, or reword.
+- L3 (series 7+ hues) is the bullet above; the two nits (N1: `no-data` also skips when it is the
+ only file in a `--workers=2` run; N2: `5a4ec2fd` alone is red until `babd4b75`) are left as the
+ review says.
+
## Rollout
