Closes #69. Broadcast was the last call site left on `validateFeed` — latest-only by design, the right API for documents this kit writes and the wrong one for a feed somebody else published and this tool merely reads. A valid 0.4 feed came back invalid over its `specVersion` alone, and because an invalid feed stops everything before any destination, Broadcast refused to publish a healthy feed outright. Being behind inside the support window is a notice, never a defect. `validateDocument` now picks the version. The notices it returns render above `#main` instead of in place of it, with their links as links rather than a bare URL mid-sentence — the feed still broadcasts, which is the entire point. The tracker predicted `runCli` would have to become async here as it did in the three exporters; it did not. `boot()` was already async, so the change is the call and the notice rendering. One consequence that was not predicted: `validateDocument` can reach any published version's validators, and `apps/publish` bundled to a single `outfile`, so esbuild inlined all of them and `main.js` went 464 KB → 1.3 MB. They sit behind a dynamic import precisely so a bundler can split them, which `apps/validator` already relies on. Same `splitting`/`outdir` config here takes `main.js` to 122 KB — smaller than before this change, since the latest version's validators are now a chunk too. Checked by hand, per CONTRIBUTING.md: a 0.4 feed broadcasts with the notice shown, and an invalid feed still shows its errors and no console. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Commits

Commits on Nov 4, 2026

fix(publish): judge a feed by the version it declares