[kixelated]

Problem

Operators need to distinguish redundant publishers from redundant routes without making independent importers share a broadcast epoch.

Approach

Add a general Setup guide next to Production covering same-path publisher switching, subscriber choice on separate paths, same-publisher route recovery, and where hitless protection belongs. Link it from the CLI and clustering pages and remove the completed quest.

Impact

• Public API: unchanged.
• Wire format and runtime behavior: unchanged.

Validation

• nix develop --command just ci passed, including documentation TypeScript checks, 114 documentation tests, VitePress builds, and repository checks.
• quest check passed for 426 documents; completed quest references were removed.
• Built the current CLI and checked the HLS publisher and TS --stitch --linger examples against --help.
• Checked recovery claims against origin routing, player restart following, and TS follower code and existing regression tests.
• Branch merges cleanly with latest origin/main.

Alternatives

Kept this general instead of adding a TS-only section. The CLI links to the guide rather than duplicating its switching explanation.

Follow-ups

None identified. No open decisions.

(Written by GPT-6)

[kixelated]

Completed the redundant ingest guide quest. The Setup page covers independent publishers on one path or separate paths, same-publisher route continuity, restart behavior for players and exports, and hitless protection at the boundaries. Sidebar, CLI, and cluster links are in place, and the completed quest and its references are removed.

just ci, quest check, CLI example --help validation, and the merge-conflict check passed. No public API or wire changes, open decisions, or follow-ups were identified. Left this PR in draft for maintainer review.

(Written by GPT-6)

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 9 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 248008d8-c9da-433a-adee-ffa5483e9406

📥 Commits

Reviewing files that changed from the base of the PR and between eecb86c and 153be1c.

📒 Files selected for processing: 6

• doc/.vitepress/config.ts
• doc/bin/cli.md
• doc/bin/relay/cluster.md
• doc/setup/redundancy.md
• quest/m1/README.md
• quest/m1/redundant-ingest-guide.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-20T22:28:42.108421Z	153be1c	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[kixelated]

Merging: adds the redundant ingest and route failover guide and retires its quest. Docs and quest checks pass; Codex reviewed 153be1c7 with no findings. The only local just check failure is the known bench/relay.test.py readiness flake, tracked by quest/m1/test-flakes-2/relay-bench-holder.md in #6083.

(Written by Claude Opus 5.5)