Skip to content

quest: plan rollout confidence for the lite-07 route layer - #9110

Merged
kixelated merged 3 commits into
mainfrom
quest-plan/rollout-confidence
Nov 18, 2026
Merged

kixelated merged 3 commits into
mainfrom
quest-plan/rollout-confidence

Conversation

@kixelated

@kixelated kixelated commented Nov 18, 2026 •

Copy link
Copy Markdown
Collaborator

Plans four quests for confidence in the lite-07 route layer before a deployment rolls its cluster links onto it. No code changes.

Quests

Quest Size Milestone Why there
A relay counts what its route layer does M m2, blocks the cut The mesh replay reads them, and the release a deployment rolls onto lite-07 carries them
Real relays replay a mesh and its faults L m2, blocks the cut A wire flaw found on a real mesh after the cut would wait for lite-08
Nightly races the route layer across threads M m3 Tests code, not the wire
Track replacement under Bun finishes every run M m0 Flakes join the open flake epic

Decisions

Decided 2026-11-18 (maintainer, in the coordinating session, from a survey of the moq.pro deployment):

  • ✅ Plan the mesh replay, the route counters, and the mixed mesh and hang work (rejected: leaving any of the three out).
  • The staging and canary work offered beside them was not picked and is not planned here.
  • The mixed-version roll is a case of the mesh replay rather than a quest of its own, since both need the same harness.
  • ✅ The mesh replay and the route counters it requires block the lite-07 cut, under the multicast epic (rejected: m3, starting now without the cut waiting on them).
  • The lite-07 auth/waiting bench hang is not planned: moq-dev/moq#9039 fixed it.

What already covers this

  • just test wire-compat and the cut's two-relay smoke pair one released relay with one from this checkout. Neither runs a mesh mid-roll.
  • The session tests cover mixed lite-06 and lite-07 rings in one binary (mesh_withdraw.rs).
  • Random fault schedules and the relay soak are m4 and cover one relay or the simulated clock.

Open for the maintainer

Nothing. The threaded stress stays in m3 and the Bun hang in m0, as the agent placed them.

(Written by Claude Fable 5.2 with high effort)

🤖 Generated with Claude Code

Review

Rewritten by quest review after each round.

  • Head: 77274d7

  • Base: origin/main at f1df3c3

  • Risk: medium, the base has no RISK.md to name what is always high or customer-facing, so every change is medium

  • Classified: medium by default

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

  • Session: 01a1f07e-f660-7360-a095-6a0c618c3989, round 2

  • Score: 10/10, The incremental changes consistently make route counters and mesh replay prerequisites for the lite-07 cut, with updated links and no actionable defects.

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

  • Findings: none

Four quests from a survey of a downstream deployment: route counters in
a relay's stats and metrics, a real-process mesh replay with a mixed
roll, a threaded stress of the route layer, and the track replacement
hang under Bun.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@kixelated
kixelated marked this pull request as ready for review November 18, 2026 21:11
@coderabbitai

coderabbitai Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

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 3 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

  • 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: c17ee1f1-a2b7-455f-814f-de91d80ddb1a
Commits

Reviewing files that changed from the base of the PR and between 383b52c and c220a72.

Files selected for processing: 4

  • quest/m0/test-flakes-3/track-replacement-bun.md
  • quest/m3/mesh-replay.md
  • quest/m3/route-counters.md
  • quest/m3/route-race-stress.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

pullfrog[bot]
pullfrog Bot previously approved these changes Nov 18, 2026

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Approach: sound — docs-only quest plans, each scoped with goal, plan, and dependencies.

Reviewed changes

  • track-replacement-bun.md — m0 flake quest under the test-flakes-3 epic.
  • mesh-replay.md — m3 quest for a real-relay mesh replay with faults and a mixed-version roll.
  • route-counters.md — m3 quest for per-label route-layer stats and metrics.
  • route-race-stress.md — m3 quest for a seeded multi-threaded route stress.

All relative quest links resolve to existing files, and the Required/Related links between the new quests are consistent.

Pullfrog  | View workflow run | Using claude-sonnet-5-5 | 𝕏

kixelated and others added 2 commits November 18, 2026 14:00
Maintainer decision on #9110: both move under the multicast
epic in m2, since a wire flaw found on a real mesh after the cut would
wait for lite-08.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@kixelated

Copy link
Copy Markdown
Collaborator Author

Maintainer decision (2026-11-18, in the coordinating session):

  • ✅ Merge.
  • ✅ The mesh replay blocks the lite-07 cut, with the route counters it requires (rejected: m3, starting now without the cut waiting on it). Both moved under quest/m2/multicast/ on the new head; each quest's Plan records it.

(Written by Claude Fable 5.2 with high effort)

@kixelated

Copy link
Copy Markdown
Collaborator Author

Answered: the decision above is recorded in #9110 (comment) and nothing else waits on the maintainer here.

(Written by Claude Fable 5.2 with high effort)

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes since the prior review, the delta from c220a72 to 77274d7:

  • Moved quests to the multicast epic — mesh-replay.md and route-counters.md now live under quest/m2/multicast/.
  • Recorded the maintainer decision — both quests block the lite-07 cut, and the replaced m3 "agent's choice" bullets are removed.
  • Updated the epic README — quest/m2/multicast/README.md lists the counters and replay as cut blockers. All cross-links resolve to existing files.

Pullfrog  | View workflow run | Using claude-sonnet-5-5 | 𝕏

@kixelated
kixelated added this pull request to the merge queue Nov 18, 2026
Merged via the queue into main with commit 71c6209 Nov 18, 2026
8 of 9 checks passed
@kixelated
kixelated deleted the quest-plan/rollout-confidence branch November 18, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant