Repository navigation
quest: move viewer-side composition to m2 behind publish-independently - #97
Conversation
Quest-Claim: 3570705f9a7b3a34
… a source track Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Pick (/quest-complete, maintainer away under /afk, recommended option): ✅ Move the compose epic to m2, with "Published independently" ( (Written by Claude Opus 5.5) |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
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 42 minutes. 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. |
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head b4184149722beaf0dfabd088e8f28dad072f2ea0 against base a461c842511aa3664af049ff78209854e28378cf.
No actionable findings. The prerequisite chain is acyclic: layout requires independent publication, browser/server require layout, and controls require browser. The publication quest's backlink is only Related. Local source-track publication supports the stated dependency, and the reference-picture redesign was already deferred at base. The moved documents' links resolve; no old quest/m1/compose paths remain in the quest tree or user README.
Direction: keeping composition behind fetchable source tracks avoids implementing an unusable layout, while preserving the explicit replan before implementation.
Verification: GitHub-only static review of all nine changed documents, surrounding quest hierarchy, publication source and history. Repository guidance and pinned quest context were read as source; no quest context, quest check, builds or tests were executed.
(Written by review (OpenAI))

Replans Layout track: the viewer-side composition epic moves to m2, behind Published independently.
Summary
Since 2026-11-04 (moq-dev/studio#21, moq-dev/studio#30), the program is the default and no source's track reaches the relay.
rs/moq-scene/src/publish.rskeeps every source track in a local broadcast the studio never announces. A source reaches viewers only once Published independently ships, and that quest is in m2. So nothing in m1 can fetch a track a layout names, and the browser, server, and controls quests have nothing to compose.Changes:
quest/m1/compose/moves toquest/m2/compose/. Links in the m0, m1, and m2 READMEs and inpublish-independently.mdfollow it. The epic leaves m1's Required list and joins m2's, after Published independently.layout.md: Published independently becomes its first Required. The Plan records the decision and the rejected options, and says the quest is replanned around the epic's reference picture once that lands. The## Waitingitem is cleared.browser.mdandserver.mdneed fetchable source tracks, but both already Require the layout.controls.mdRequiresbrowser.md. All three now wait on Published independently through the layout, so they don't repeat the link. The epic README says so.Decisions
git mvplus link rewrites).quest mvrefuses to move a quest its own open claim names, and this PR is that claim. After merge the quest lives atquest/m2/compose/layout.md, and this branch name no longer matches it.Public API and wire impact
None: quest files only.
Validation
quest check --base origin/main: 37 documents ok.quest unblocked quest/m2/compose/layout.mdandquest unblocked quest/m2/compose/browser.md: both are blocked, through Published independently and the layout.just check/just testnot run: the diff touches only quest Markdown. Merged origin/main (a461c84) without conflicts.Review
quest review), gpt-6.1-sol, medium effort.b4184149722beaf0dfabd088e8f28dad072f2ea0, round 1.(Written by Claude Opus 5.5)