moq-lite-05: add broadcast Epoch and rename ANNOUNCE messages

[kixelated]

What changed

New Epoch field on ANNOUNCE_BROADCAST (a varint, placed before the Hop ID list):

• An opaque, application-defined value that orders instances of a broadcast — moq-lite requires only that a newer instance carries a larger value (a timestamp works, but any monotonic counter does).
• Origin-assigned and forwarded unchanged by relays (unlike the Hop ID list).
• Subscribers resolve duplicate active advertisements of the same broadcast by largest Epoch wins; total path length now only breaks ties between equal epochs. For ended, the epoch identifies which instance ended, so a subscriber already on a newer instance can ignore a stale ended. 0 means unassigned (resolved by path length alone).
• A non-normative note suggests a recent reference point (e.g. seconds since 2020) if deriving from a timestamp, to keep the value within a 4-byte varint.

Renamed the Announce messages:

• ANNOUNCE_INTEREST → ANNOUNCE_REQUEST (the subscriber's request to receive announcements)
• ANNOUNCE → ANNOUNCE_BROADCAST (the publisher's per-broadcast advertisement)
• ANNOUNCE_OK unchanged.

Why

Without an explicit ordering signal, a subscriber facing a reconnecting publisher has to wait for the old session to time out before it can safely route to the new one. The Epoch lets it switch immediately. The rename makes the trio ANNOUNCE_REQUEST → ANNOUNCE_OK → ANNOUNCE_BROADCAST self-describing (the request asks for announcements; the broadcast advertisement says what is announced).

Reviewer notes

• Changelog updated under moq-lite-05. Draft builds clean (make draft-lcurley-moq-lite.txt).
• Out of scope here: draft-lcurley-moq-hang.md still references the old ANNOUNCE message name (lines 71, 77–85). Those cross-references are now stale against the rename — left for a follow-up unless reviewers prefer they be updated in this PR.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@kixelated, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 18 minutes and 10 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e5f4f353-5abb-4a48-b974-04ea54ec5a6a

📥 Commits

Reviewing files that changed from the base of the PR and between 0a66e5c and e751465.

📒 Files selected for processing (1)

• draft-lcurley-moq-lite.md

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/lucid-gates-9d286c

---

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 and usage tips.}