[WalksWithASwagger]

Transmission 001 adds a finite listening edition at /transmission-001, with three visual chapters, a creator-note detour that restores position and play/pause intent, timestamp links, and an explicit ending. A private preparation workflow now makes the existing recordings reviewable before the creator supplies a finished technical package.

Refs #73; parent #55. Reuses the provider work from #63 / #65.

Merge scope: implementation and private-proof tooling; the public edition is not release-ready. The production manifest remains {"release": null}. An authentic 15–30-second creator recording, approved transcript, final edit/artwork/credits, audible review and physical-device/listener checks remain required. The private proof does not replace these gates.

Behavior and scope

• A separate static edition entrypoint, chapter artwork, transcript, reduced-motion/static presentation, keyboard/focus behavior, clipboard fallback and one homepage navigation link.
• Opt-in single transport on the existing provider, with one audio element. Existing playlist/repeat behavior remains the default. Provider regressions cover metadata-aware seek/retry, graph initialization, buffering, OS actions and WebKit paused-return races.
• A strict media release checker measures and fully decodes recordings, checks duration/format/path boundaries and distinct bytes, and produces hashes/tool versions for review. Error-level decoder diagnostics remain failures even after a zero exit; no gate was weakened.
• pnpm prepare:transmission assembles the three local Gorgeous Ghost MP3s in catalogue order into a fresh private PCM review render. It uses decoded sample counts for chapters, checks the final sample total and decode, records hashes and preserves original sources. No trims, crossfades or normalization are applied.
• pnpm preview:transmission -- <proof-directory> validates the receipt and builds only the proof entry and receipted assets into a fresh site directory outside Git. With no directory it prepares a fresh candidate. The server binds to loopback port 4175. No unapproved media or private render is committed or uploaded.
• The proof identifies itself as unapproved, omits the missing artist-note and public-sharing controls, and uses the edition's player. Production builds exclude its entry/assets; a query parameter cannot enable it. Narrow-screen heading sizing and masthead wrapping fix overflow found at 390px with 200% CSS zoom.
• Documentation now explains preparation, editorial review and final release separately. No new dependency, lockfile update, CMS, account system, telemetry, generative content or global agent configuration is introduced.

The private candidate measured locally is 262.893458 seconds / 12,618,886 samples at 48 kHz, with chapters at 0, 70.6935 and 133.533479 seconds. Its review WAV is approximately 50 MB and is not the final delivery encoding. Its local receipt records the exact bytes; technical verification does not establish editorial approval or listening quality.

Validation

• Committed baseline f4938ca: CI passed, with 90 unit tests and 14 Chromium/WebKit browser tests. The earlier FFmpeg 6 diagnostic/encoder-padding failures and their fixes remain in the commit history.
• Private-proof follow-up: 95 unit tests pass, including real catalogue assembly, sample boundaries, repeatable output, unchanged sources, missing/corrupt inputs and tools, Git-contained output, escaping/modified assets, and a real private Vite build excluding unrelated files. The build test runs in Node because esbuild cannot run inside jsdom's typed-array realm; per-test media mock calls are cleared to keep silent-cue assertions independent.
• All 20 Chromium/WebKit browser checks pass. New checks verify advancing real proof audio, HTTP 206 byte ranges, keyboard playback, chapter seek, finite ending, receipt navigation, 390px/200% CSS zoom, reduced motion, and production isolation. Existing modern/classic and note-return checks still pass.
• Root and playground TypeScript checks, pnpm check:dist, pnpm check:package (8 required files), pnpm check:seo (3 entrypoints), script syntax and diff whitespace checks pass. No library source or generated package output changed in the proof follow-up.
• Desktop and 390px phone layouts were visually inspected in the browser, including chapter selection. The local preview server was stopped after review.
• Initial local browser startup hit sandbox EPERM; the suite ran with loopback permission. Early new browser runs exposed actual masthead/title overflow, fixed before the passing run. Existing jsdom canvas and NO_COLOR warnings remain. Package verification used a temporary npm cache for the pre-existing user-cache permission issue.
• CI at 4e0d164 passed unit/type/package/SEO checks and 19 browser tests, but Linux WebKit exposed a two-pixel heading overflow under 200% CSS zoom. A wider-font regression reproduced the same problem locally (418px content in a 390px viewport). The heading now wraps when needed; all 20 local browser checks pass with both normal and wider fonts. The original no-overflow assertion remains strict.
• pnpm check:transmission still fails for missing approved release content. Full audible review, physical iOS Safari interruption/background testing and the five-listener check have not run. No passing content gate or release readiness is claimed.

Remaining gate

CI at 1c6415c passed: unit tests, both TypeScript configurations, generated output, packaging, SEO, and the complete Chromium/WebKit suite including the font-width regression. The existing GitHub Actions runtime-deprecation warning remains outside this slice.

Review the private sequence, joins, artwork, titles and credits; supply the authentic creator recording and approved transcript. Then prepare and remeasure the approved delivery encoding, populate the production manifest, add the production content gate to CI, and attach exact-content approval/listening/device evidence. Issue #73 remains open for these requirements after this implementation merges.

The original main checkout's .gitignore edit and dist/skins.css deletion, all other worktrees, and PR #72's homepage metadata are preserved. The user explicitly authorized review and merge on 2026-09-06. No separate deployment command, force push or hosting-setting change is included. The existing GitHub/Vercel integration may create a branch preview after a normal push; private proof assets are excluded from that build.

Merge review

No blocking code findings. Fresh local review passed 95 unit tests, both TypeScript configurations and generated-output parity. The final documentation change separates implementation merge approval from content publication. Existing Chromium/WebKit CI evidence covers 20 browser checks, including keyboard, narrow-screen zoom and private-proof isolation. The strict content checker remains failing for the intentionally pending production manifest; audible, physical iOS and listener checks remain unavailable. Merge only the exact final head after its CI passes.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
winamp	Ready	Preview	Sep 6, 2026 3:32pm UTC