Put the setup walkthrough on the site, and stop apologising for the relay

[karngyan]

Puts the 8:51 setup walkthrough on the site, and retires the status copy that said the relay might not work.

The video

Mux, public playback, no signed tokens. Rendered with kino, the player this project's author wrote, through @karnstack/kino/mux. Accent is passed as var(--primary) rather than a literal colour: kino assigns the prop straight to --kino-accent on its own root, so the header's theme toggle moves the scrubber along with everything else.

An English subtitle track is attached to the asset itself, so captions come from Mux and cost this repo nothing.

Where it goes

Inside the existing Install section on the landing page, between the claim and the install command, and at the top of /docs/setup ahead of any instruction.

No fifth section on the landing page. The four were a considered cut down from seven, and Install is where the live objection sits: at the moment somebody is about to pipe a script into their shell, the question is whether this actually works. Every other window on that page is a drawing. This is the one artefact that is not.

What it costs

/docs/setup and / load 327 kB gzipped, up from about 101 kB. kino and the Mux streaming engine are 212 kB of that.

That is a real tripling and it is deliberate. An earlier version of this branch deferred the engine behind a poster and a play button, which cost 2 kB up front instead of 212 kB. It was removed because it made opening the video take two clicks: the first swapped the picture for the real player, the second started it, and the first bought the viewer nothing. If a video is worth putting on a page it is worth loading. If the landing page number becomes a problem, the answer is to keep the player on /docs/setup and drop it from /, not to bring the facade back.

No autoPlay, and why that matters

Passing kino's autoPlay played two audio tracks a beat apart, and the first one could not be stopped by anything on the page.

kino builds its <mux-video> inside a mount effect and sets autoplay on the element there, while its teardown calls remove(), which detaches an element without pausing it. React invokes a mount effect twice in development, so the sequence is: element created and started, element detached but still playing, second element created and attached. Patching document.createElement to count and clicking play once gave {"created": 2, "attached": 1}. The orphan was unreachable because every control talks to the provider that owned it, which had been thrown away.

Not passing autoPlay means nothing ever starts the orphan. The leak itself is kino's and is being fixed there separately. The viewer presses play, which is what they came to do.

Status copy

README.md and the Remote section of the landing page both claimed the relay had not been through its manual end-to-end gate and should be treated as ready to try rather than ready to rely on. That is no longer true, and the video on the same page disproves it: a relay deployed to a real Cloudflare account with a real token, a phone paired across a different network, and a second machine joined to the same relay.

Both now say it is released, name v0.5.1, and state that it is 0.x so commands and config can still change between versions. That last part is a plain fact rather than an apology.

Two other matches for the old wording were left alone on purpose:

• docs/RELAY.md release gate section is the standing checklist itself, which is a process and still true.
• The plan file under docs/superpowers/plans/ is a historical record.

Verification

• pnpm run lint (tsc --noEmit) clean.
• pnpm run build green: 6 routes prerendered, check-pages and check-prose pass.
• The custom element registers on import and every route here is prerendered to static HTML at build time. All six still prerender, so the static import is safe.
• Playback, both themes, both pages, confirmed in a browser.

🤖 Generated with Claude Code