[kixelated]

Summary

moq keeps what a large live-media platform would use; mesh networking moves to Kixel, which plans and builds it in kixel-ai/kixel.ai (decided by the maintainer 2026-11-14). Kixel's coordinator already has its own certificate-based enrollment contract and uses nothing from moq_auth::mesh, so the module has no consumer left.

• Removes moq_auth::mesh (contract types, Client, Coordinator, the Signer trait), Server::with_mesh, and Error::Mesh/MeshState.
• Removes moq auth mesh and every --mesh-* flag and [mesh] setting on moq auth serve.
• Removes the mesh enrollment section of doc/bin/relay/auth.md and the mesh bullet in doc/lib/rs/moq-auth.md.
• Deletes the quests that move to Kixel: the m3 mesh epic (relay node, Endpoint, address hints, sparse overlay, status track, certificate credentials), the m2 mesh contract quests, the parked mesh guide, JS enrollment, ICE, and keys quests, the teleop questline, link quality, the certificate challenge, and the stored signing key quest. Also the teleoperation use-case guide and its moq-json example.

AGENTS.md says to ask before planning or building work a large live-media platform would not use, which belongs to Kixel (approved by the maintainer).

LAN cluster discovery (--cluster-lan), outbound federation, and the MoQ Boy and CARLA demos stay.

Supersedes moq-dev/moq#8746, moq-dev/moq#8748, and moq-dev/moq#8750, which change the removed module.

Impact

Public API: breaking. moq_auth::mesh and Server::with_mesh are gone, and moq-cli loses moq auth mesh and --mesh-url, --mesh-listen, --mesh-key, --mesh-relay, --mesh-state, and --mesh-token-ttl. None of it is on release, so no published user migrates. The release cut should drop the Unreleased rs/moq-auth/MIGRATE.md note about moq_auth::mesh::EndpointId, which the MIGRATE check keeps edits out of until then. Wire: none.

Validation

• just check in the dev shell passes on the combined branch (Rust lint and 14092 Rust tests, JS, docs, quest, nix, and the rest of the changed modules).

• quest check: 484 documents ok.

• A grep outside quest/ for moq_auth::mesh, moq auth mesh, and mesh-enrollment finds only the MIGRATE.md note above.

• the_secret_guards_every_route used the mesh admin route; it now checks the same secret handling on POST /.

• 2026-11-15 merge of main (redoing the land fixer's unpushed resolution): kept this PR's deletions of quest/m3/mesh/README.md, quest/m3/mesh/endpoint.md, quest/m5/mesh-ice.md, and rs/moq-json/examples/teleop.rs over main's edits; took main's deletion of quest/m1/stream/README.md (byte streams moved to Kixel); merged the quest/m2/README.md and quest/m3/README.md prose, keeping main's finished fences and dropping links to deleted quests. just check passes on the merge.

• cargo test -p moq-json --doc fails on main: snapshot::Producer::mutate's example still passes None for the Timestamp that feat(moq-net)!: address groups by their start #8638 made required. Fixed here (one line), since this PR changes moq-json.

Decisions

Taken while the maintainer was away, each undoable by a later review:

• ✅ Merge main keeping this PR's deletions (rejected: restoring the mesh quests main edited), per the land fixer's recommendation.
• ✅ Fix the pre-existing moq-json doctest in this PR (rejected: a separate PR), since no open PR fixes it and this PR's moq-json change would otherwise run it.

Follow-ups

None. moq-crypto's serde feature now has no user in the workspace; it stays, since downstream may still enable it.

Models

Size: M
Implementer: Claude Code, claude-opus-5-5, medium effort (iterate, M)

🤖 Generated with Claude Code

(Written by Opus 5.5)

Review

Rewritten by quest review after each round.

• Head: 082fdb6

• Base: origin/main at 52732a0

• Risk: high, Removing the mesh library API can break downstream consumers that depend on it, requiring them to migrate or revert the removal.

• Classified: medium by default

• Reviewer: Codex, gpt-6.1-sol, high effort

• Session: 01a1dedf-1d75-71c3-80d1-6b1c642b4d7f, round 1

• Score: 9/10, The removal is internally consistent with no actionable regressions or blocking defects identified, though builds and tests were not run as instructed.

• Rounds: 1; first round 0; findings 0: fixed 0, refuted 0, open 0

• Findings: none

• Reviewer: Codex, gpt-6.1-sol, medium effort, shadow

• Session: 01a1dedf-1d75-7a40-81f3-ecb2e8d5a648, round 1

• Score: 9/10, Source review found no actionable regressions or blockers, with mesh removal consistent across the library, CLI, and documentation, but builds and tests were not run as instructed.

• Raised the risk to high: Removing the mesh library API can break downstream consumers that depend on it, requiring them to migrate or revert the removal.

• Rounds: 1; first round 0; findings 0: fixed 0, refuted 0, open 0

• Findings: none

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The change removes mesh enrollment from moq-auth, including its public API, client, coordinator, server routes, and CLI settings and commands. It deletes related mesh plans and documentation, with planning notes identifying Kixel as the destination for mesh work. It also removes teleoperation documentation and a moq-json example, and updates a snapshot producer documentation example to pass a timestamp.

Merge Risk: Minimal · up to 082fd

This PR removes mesh enrollment from moq-auth and moq-cli and fixes a doctest. No merge-blocking risk was found. The public API removal is intentional and is described as a breaking change.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: removing mesh enrollment from moq-auth and moving mesh plans to Kixel. The changeset deletes the moq_auth::mesh module, Server::with_mesh, the moq auth mesh command an…
Description check		The description states the purpose and scope: moving mesh networking to Kixel, removing moq_auth::mesh, Server::with_mesh, Error::Mesh/MeshState, the moq auth mesh command and --mesh-* flags, the mesh…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: removing mesh enrollment from moq-auth and moving mesh plans to Kixel. The changeset deletes the moq_auth::mesh module, Server::with_mesh, the moq auth mesh command and its flags, and the mesh quests and docs, so the title matches the primary change. The title is a single line of 69 characters and uses a conventional-commit prefix with a breaking-change marker, which fits the breaking public API removal.

Full details: Description check

Explanation

The description states the purpose and scope: moving mesh networking to Kixel, removing moq_auth::mesh, Server::with_mesh, Error::Mesh/MeshState, the moq auth mesh command and --mesh-* flags, the mesh doc sections, and the related quests and teleoperation guide. It also covers the breaking API impact, the moq-json doctest fix, and validation. This directly describes the changeset.

Finishing Touches

Simplify code

• Commit to this branch
• Create a new PR

• 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

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8c6d5693-a96d-4ef7-8a93-d47e20ad29d0

Commits

Reviewing files that changed from the base of the PR and between e9700c7 and 082fdb6.

Files selected for processing: 13

• Cargo.toml
• doc/bin/relay/auth.md
• nix/Cargo.nix
• quest/m2/README.md
• quest/m3/README.md
• quest/m3/cluster-routing/README.md
• quest/m3/mesh/README.md
• quest/m3/mesh/endpoint.md
• quest/m5/mesh-ice.md
• rs/moq-auth/Cargo.toml
• rs/moq-auth/src/lib.rs
• rs/moq-json/examples/teleop.rs
• rs/moq-json/src/snapshot/producer.rs

Files with no reviewable changes: 6

• quest/m3/cluster-routing/README.md
• quest/m3/mesh/README.md
• quest/m3/mesh/endpoint.md
• quest/m5/mesh-ice.md
• rs/moq-auth/src/lib.rs
• rs/moq-json/examples/teleop.rs

Files skipped from review as they are similar to previous changes: 3

• Cargo.toml
• quest/m2/README.md
• quest/m3/README.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

[pullfrog]

ℹ️ No code issues. One wording fix in the quest record, inline.

Reviewed changes

I reviewed both commits: the removal of moq_auth::mesh and its CLI surface, plus the quest and doc moves to Kixel.

• moq_auth::mesh removed. src/mesh/, Server::with_mesh, Error::Mesh/MeshState, and the serde features on moq-crypto/url are gone. fs::write_private becomes private. The secret-guard test now covers only POST /.
• moq auth mesh and --mesh-* removed. MeshServe, MeshSettings, coordinator(), the mesh listener, and the [mesh] file settings are deleted. restart_only now compares only the listener and its secret.
• Teleoperation removed. The use-case page, its sidebar and index entries, the moq-json teleop example with its [[example]] entry, and the MoQ Boy aside are deleted.
• Quests moved to Kixel. The m2 mesh contract quests, the m3 mesh epic, m4 cert-challenge/crypto-key-load, and the m5 mesh/teleop/link-quality quests are deleted. Inbound links now read as prose.

Checks I ran on this head:

• cargo check -p moq-auth --all-targets --all-features and cargo check -p moq-cli --bin moq --tests both pass with no warnings.
• A git grep for the deleted quest slugs, use-case/teleoperation, examples/teleop, moq_auth::mesh, with_mesh, auth mesh, and mesh-url finds only the rs/moq-auth/MIGRATE.md note the Impact section already flags.
• js/auth has no mesh counterpart to remove.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

[pullfrog]

✅ No new issues found. The earlier wording fix is in.

Reviewed changes

This run covered the commits since 3b7e4b4: the applied quest wording fix and a merge of main.

• Fixed the quest/m3/README.md record. It now says only the mesh libraries left for Kixel, and byte streams stay in m1. The text matches the suggestion exactly.
• Merged origin/main. The only change in this PR's files is in quest/m2/README.md, where the first-publish-versions link is gone. main had already removed it, and the file no longer exists.

A grep at a09b65a for the deleted quest slugs, use-case/teleoperation, examples/teleop, moq_auth::mesh, and with_mesh still turns up only the rs/moq-auth/MIGRATE.md note the Impact section mentions, plus the prose in quest/m2/README.md.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

[pullfrog]

✅ No new issues found. The new commit is only a merge of main.

Reviewed changes

This run covered the changes since a09b65a.

• Merged origin/main. main (#8702) had already deleted quest/m5/teleop-{robot,arbitration,mavlink,proof}.md and the teleoperation link in the mesh README, so those deletions drop out of this PR's diff.

A git grep at 843f72b for the deleted quest slugs, use-case/teleoperation, examples/teleop, with_mesh, and moq_auth::mesh finds two things. One is the rs/moq-auth/MIGRATE.md note, which the Impact section already mentions. The other is the prose in quest/m2/README.md.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

[moq-bot]

quest land watch: the merge queue removed this pull request at 843f72b because it conflicts with main (merge_conflict).

The land fixer works on it in the background, and the watcher re-enqueues it at the back of the queue once it is fixed or judged flaky, or hands it back here with what it needs.

(written by quest land watch)

[pullfrog]

✅ No new issues found. The new commit only merges main.

Reviewed changes

This run covered the changes since 843f72b.

• Merged origin/main. main deleted quest/m2/usage-derive-settings.md, so the merge turned the link to it in quest/m2/README.md into plain text.

A git grep at c259c3f finds no leftover references to the deleted quests, docs, or example. moq_auth::mesh still appears only in the rs/moq-auth/MIGRATE.md note, which the PR's Impact section already mentions.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

[moq-bot]

codex, gpt-6.1-sol, medium effort land fixer note:

The failure log, lines 6–8, reports:

Auto-merging quest/m2/README.md
CONFLICT (content): Merge conflict in quest/m2/README.md
Automatic merge failed; fix conflicts and then commit the result.

Commit a5fcdcd874e2509d4466a9775b7d3f5608c43539 on pr-8756 merges base and preserves both the PR's mesh-removal text and base's removal of the completed usage quest link. The conflict resolution changes no behavior and makes no additional protected-path edits.

Ran git diff --check and nix develop --command just ci base. Cargo plan verification, Rust checks and all 14,120 Rust tests, Python checks and tests, C and C++ checks, OBS checks, and Biome passed. The gate selected the full suite because it started before the merge commit. It then reported:

ci: flake's NixOS VM tests need KVM, but /dev/kvm is missing; run them on a KVM host, as CI does

Stopped the remaining validation after this environment blocker. The fix remains committed locally, but complete validation requires a KVM-enabled runner.

(written by codex, gpt-6.1-sol, medium effort)

[moq-bot]

quest land watch: the land fixer's result for 843f72b was not applied: its head moved to c259c3f while the fixer ran, and a push by anyone but the land fixer ends the pick.

(written by quest land watch)

[moq-bot]

quest land watch: the merge queue removed this pull request at c259c3f because it conflicts with main (merge_conflict).

The land fixer works on it in the background, and the watcher re-enqueues it at the back of the queue once it is fixed or judged flaky, or hands it back here with what it needs.

(written by quest land watch)

[pullfrog]

✅ No new issues found. The new commit only merges main.

Reviewed changes

This run covered the changes since c259c3f.

• Merged origin/main. main deleted quest/m2/auth-key-validation.md, quest/m2/api-capture-fences.md, and quest/m1/stream/rust.md. The merge turned their links in quest/m2/README.md into plain text, and the deleted mesh quests no longer link to them.

A git grep at e9700c7 finds no leftover references to the deleted quests, docs, or example. moq_auth::mesh still appears only in the rs/moq-auth/MIGRATE.md note, which the Impact section already mentions.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}

[moq-bot]

codex, gpt-6.1-sol, medium effort land fixer note:

Failure log lines 5–8 report:

CONFLICT (content): Merge conflict in quest/m2/README.md
CONFLICT (modify/delete): quest/m3/mesh/README.md deleted in c259c3f and modified in HEAD. Version HEAD of quest/m3/mesh/README.md left in tree.
CONFLICT (modify/delete): quest/m3/mesh/endpoint.md deleted in c259c3f and modified in HEAD. Version HEAD of quest/m3/mesh/endpoint.md left in tree.
Automatic merge failed; fix conflicts and then commit the result.

Merged base and resolved these mechanically in f097672a9c4902bc33e3ff825026426019f281f1 on pr-8756. The resolution keeps the mesh plan deletions and combines the mesh removal notes with base's reference cleanup. Protected paths retain the automatic merge result.

Validation command: nix develop --no-update-lock-file -c just ci base. The flake check reports: ci: flake's NixOS VM tests need KVM, but /dev/kvm is missing; run them on a KVM host, as CI does. This prevents reporting the PR as fixed; rerun the full gate on a KVM host.

The gate completed: all other selected checks passed, including Biome, the generated Cargo plan, documentation, quest validation, repository tooling tests, and Rust checks and tests (14,134 passed, 159 skipped). The command exited 1 solely because the flake VM check requires KVM.

(written by codex, gpt-6.1-sol, medium effort)

[moq-bot]

quest land watch: the land fixer's result for c259c3f was not applied: its head moved to e9700c7 while the fixer ran, and a push by anyone but the land fixer ends the pick.

(written by quest land watch)

[moq-bot]

quest land watch: the merge queue removed this pull request at e9700c7 because it conflicts with main (merge_conflict).

The land fixer works on it in the background, and the watcher re-enqueues it at the back of the queue once it is fixed or judged flaky, or hands it back here with what it needs.

(written by quest land watch)

[moq-bot]

codex, gpt-6.1-sol, medium effort land fixer note:

The failure log reports:

CONFLICT (modify/delete): quest/m3/mesh/README.md deleted in e9700c7 and modified in HEAD. Version HEAD of quest/m3/mesh/README.md left in tree.
CONFLICT (modify/delete): quest/m5/mesh-ice.md deleted in e9700c7 and modified in HEAD. Version HEAD of quest/m5/mesh-ice.md left in tree.
Automatic merge failed; fix conflicts and then commit the result.

Commit 8746584ee113443a20fbc2bc934ba524bc386415 merges base and preserves both deletions: base only removed obsolete P2P references from those files. No behavior changes were added. The required gate, nix develop --command just ci base, reports: ci: flake's NixOS VM tests need KVM, but /dev/kvm is missing; run them on a KVM host, as CI does. Full verification needs a KVM host.

The gate finished with only the KVM-dependent flake step failing. All other selected checks passed, including Rust lint/build/docs and all 13,810 Rust tests, JavaScript type checks/tests and documentation build, generated Cargo metadata, CARLA checks/tests, and repository tooling checks.

(written by codex, gpt-6.1-sol, medium effort)

[moq-bot]

codex, gpt-6.1-sol, medium effort land fixer: Re·solved the modify/delete conflicts, but `nix develop --command just ci base` cannot complete: ci: flake's NixOS VM tests need KVM, but /dev/kvm is missing; run them on a KVM host, as CI does. Recommendation: Use conflict-resolution commit 8746584ee113443a20fbc2bc934ba524bc386415 on pr-8756 and rerun `nix develop --command just ci base` on a KVM host before landing.

CONFLICT (modify/delete): quest/m3/mesh/README.md deleted in e9700c7c4854a35b573474b895fed194354b6e96 and modified in HEAD.  Version HEAD of quest/m3/mesh/README.md left in tree.
CONFLICT (modify/delete): quest/m5/mesh-ice.md deleted in e9700c7c4854a35b573474b895fed194354b6e96 and modified in HEAD.  Version HEAD of quest/m5/mesh-ice.md left in tree.
Auto-merging rs/moq-auth/Cargo.toml
Auto-merging rs/moq-auth/src/lib.rs
Automatic merge failed; fix conflicts and then commit the result.

(written by codex, gpt-6.1-sol, medium effort)

[pullfrog]

✅ No new issues found. The new commits merge main and fix one doc example.

Reviewed changes

This run covered the changes since e9700c7.

• Merged origin/main. main deleted quest/m1/stream/ and quest/m4/p2p/. The merge turned links to them in quest/m3/README.md, quest/m3/cluster-routing/README.md, and the deleted mesh quests into plain text. quest/m2/README.md now takes main's list of fences.
• Fixed the mutate doc example. The snapshot::Producer::mutate example now passes a moq_net::Timestamp, which matches mutate(f, at: moq_net::Timestamp).

A git grep at 082fdb6 finds no leftover references to the deleted quests, docs, or example. moq_auth::mesh still appears only in the rs/moq-auth/MIGRATE.md note the Impact section mentions and in the prose in quest/m2/README.md.

  ^{｜ View workflow run ｜ Using claude-opus-5-5 ｜ 𝕏}