[kixelated]

Problem

moq-dev/moq#6522 renamed or removed CLI flags, environment variables, and GStreamer properties with no aliases. The quest tracked moving each downstream deployment that pins moq at a commit past it, so the next release cut does not break their invocations.

Approach

Audited both consumers the API-audit epic names, at their current main, for every spelling #6522 renamed or removed: --backoff-*, --goaway-*, MOQ_BACKOFF_*, MOQ_GOAWAY_*, MOQ_LISTEN_TLS_* / MOQ_SERVER_TLS_* / --tls-* on export hls, --passthrough on import fmp4/hls, --max-delay on export rtmp, moqsrc versions=, moqsink linger, and <moq-publish linger>.

• The moq.pro submodule pin is already 83 commits past refactor(cli,gst,publish)!: align flags and drop the publisher linger opt-ins #6522's merge, and its pin bump migrated the invocations (--connect-backoff-timeout, MOQ_CONNECT_BACKOFF_TIMEOUT, --connect-version). No old spelling remains.
• The moq.dev submodule pin is 77 commits before refactor(cli,gst,publish)!: align flags and drop the publisher linger opt-ins #6522, but it passes none of the affected spellings: it consumes only the JS packages and never set the unreleased linger attribute. Its next routine pin bump needs no migration for this rename, so this PR does not bump it.
• --backoff-healthy from moq-dev/moq#6529 landed as --connect-backoff-healthy / MOQ_CONNECT_BACKOFF_HEALTHY; neither consumer uses it.

The quest's Done condition (no pinned consumer passes a renamed or removed spelling) holds, so this deletes the quest and its epic link.

Notes for review:

• The quest said MIGRATE.md's ## Unreleased held the full list. It does not: per moq-dev/moq#6610, the notes are written at the breaking cut, and refactor(cli,gst,publish)!: align flags and drop the publisher linger opt-ins #6522's PR body carries them.
• The quest said to drop moqsink linger; moq-dev/moq#6636 since reintroduced linger as a duration in milliseconds (default 30000). Neither consumer sets it.

Impact

• Public API and wire: none. Quest files only.

Validation

• just check passed (markdown, gh, quest, shell lint); quest check --base origin/main passes.
• Searched both consumers' main trees (excluding vendored checkouts and node_modules) for each old spelling, and confirmed the new spellings are in use where the flags appear.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[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 10 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: 6532c1a7-b0bf-4426-9ded-48ac5093930d

Commits

Reviewing files that changed from the base of the PR and between 67bf4e5 and d063c9a.

Files selected for processing: 2

• quest/m1/api-audit/README.md
• quest/m1/api-audit/cli-flags-consumers.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	🔄 Running since 2026-10-25T06:55:19.171377Z	d063c9a	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]

Automated review by review (OpenAI)

Reviewed commit: d063c9a

No actionable bugs found in the two-file documentation change. Removing the completed quest together with its epic link is a minimal, coherent cleanup; no runtime, API, wire or build behavior changes.

Verification limits: inspected the complete diff and surrounding epic in moq-dev/moq. I did not independently verify downstream repository audits described in the PR, and did not run tests or quest/lint checks.