Repository navigation
chore(quest): delete MoQ on rind, finished in moq-dev/moq#8250 - #520
Merged
Merged
Conversation
Quest-Claim: a679e7a25b866af5
MoQ's rind epic is gone from moq-dev/moq's quest tree: its last work, dropping aws-lc-rs and ring and shipping an armv7 moq-cli, landed there, and every child merged before it. Its waiting item is removed, and the epic's Plan links to moq-dev/moq's migration epic, a file that no longer exists, so it names the PR that finished the switch instead. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
kixelated
marked this pull request as ready for review
November 9, 2026 07:04
|
Warning Review limit reachedYou'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 15 seconds. View limit details
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. |
There was a problem hiding this comment.
ℹ️ No critical issues — one wording-precision suggestion inline.
Reviewed changes
- Wait-only quest deleted:
quest/m1/moq/moq-on-rind.mdis gone along with itsRequiredbullet inquest/m1/moq/README.md, which keepsquic-path(the file exists) so the section isn't empty. - Dead link replaced: the epic README's link to MoQ's
quest/m1/rind/README.md, deleted upstream, now points at merged moq-dev/moq#8250 and records that the switch finished. - Upstream claims verified: moq-dev/moq#8250 is merged (2026-11-09) and its body confirms it was the epic's own work — aws-lc-rs and ring out of the workspace, a CI guard against C crypto, the armv7 moq-cli release — and that finishing it deletes the epic. moq's
maintree (untruncated recursive listing) contains noquest/m1/rind/and exactly one rind quest left,quest/m5/rind-instant-acme.md, which is new m5 feature work (instant-acme 0.9 / relay ACME), not this epic's remains. - Tree consistency checked by hand:
quest checkisn't runnable on this runner, so consistency was verified manually — no stalemoq-on-rindreferences or links into moq's quest tree remain anywhere in this repo,quest/m1/README.md's still-openrind covers MoQentry correctly needs no change, and the epic Goal prose was updated in step with the dropped bullet.
glm-5.3 | 𝕏
rind-instant-acme's quest in moq-dev/moq (m5, relay ACME) still waits on rind publishing that crate, so "no MoQ area waits on rind" overreached. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Deletes the wait-only quest
quest/m1/moq/moq-on-rind.mdand its link inquest/m1/moq/README.md. The condition holds.Verification
quest/m1/rind/README.mddoes not exist on moq-dev/moqmain. The only rind quest left there isquest/m5/rind-instant-acme.md.transport.md,cpu-error.md,rtc.md) were removed by merged feature commits, and the workspaceCargo.tomldeclares no aws-lc-rs or ring.rind-instant-acmeis not the epic's remaining work. The epic's Plan removed relay ACME on 2026-11-03 and deferred its return to m5, so that quest tracks a new feature, not this epic.Changes
quest/m1/moq/moq-on-rind.md, and drop itsRequiredentry fromquest/m1/moq/README.md. The epic keepsquic-path, so itsRequiredis not empty.quest/m1/moq/README.mdwith a link to chore(rind): drop aws-lc-rs, guard against C crypto, and ship moq-cli for armv7 moq#8250, and scope its "no MoQ area waits on rind" sentence to the switch.quest/m1/README.mdneeds no change: itsrind covers MoQentry is still open.Decisions
quest/m1/moq/README.md:14(pullfrog, AI-attributed): accepted. moq'squest/m5/rind-instant-acme.mdstill waits on rind publishingrind-instant-acmefor relay ACME, so the unscoped sentence overreached. ✅ scope it to the switch, with the reviewer's wording (rejected: keep the unscoped sentence).Public API
None. Quest files only.
Checks
quest check --base origin/main: 147 documents ok.just check: exit 0.Models
Size: XS
Implementer: Claude, claude-haiku-5-5, high effort
Implementer: Claude Code, claude-haiku-5-5, high effort (iterate, XS)
🤖 Generated with Claude Code
(Written by Haiku 5.5 with high)
Review
Rewritten by
quest reviewafter each round.01a1c2b1-6171-7c92-a203-86dc5dcaf3c6, round 1The scoped diff only updates migration tracking documentation and removes the completed quest, with no executable code changes or actionable defects identified.