Skip to content

quest(broadcast-close): remove finish becomes a standalone quest #4173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 1 commit into from
Sep 25, 2026
+8 −6
Merged

quest(broadcast-close): remove finish becomes a standalone quest #4173

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions quest/m1/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,7 @@ transport, benchmark tooling); worktrees isolate commits, not semantics.
- [FFI shape](/quest/m1/ffi-shape/README.md) - the bindings mirror Rust's layers: net at the root, then media, json, audio, and video namespaces built from the handle below
- [Track demand](/quest/m1/track-demand.md) - Rust and JS watch a track's subscribers through `demand()` alone
- [Broadcast close](/quest/m1/broadcast-close/README.md) - `close()` is the one way to end a broadcast in every language, a permanent retraction that leaves in-flight tracks alone
- [Remove finish](/quest/m1/broadcast-remove.md) - on dev, the deprecated broadcast end APIs are gone and `closed()` carries no cause
- [Relay peer set](/quest/m1/relay-peer-set.md) - a wire consumer tells a client hop from a peer hop, and every mesh credential can mark a peer
- [CLI import clock](/quest/m1/cli-import-clock.md) - fMP4, TS, and FLV imports publish on the shared broadcast clock across restarts
- [Native clock fixtures](/quest/m1/native-clock-fixtures.md) - CI drives native capture through clock edge cases and asserts the published timestamps
Expand Down
9 changes: 3 additions & 6 deletions quest/m1/broadcast-close/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Broadcast close
# [S] Broadcast close

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 25, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Delete the completed Broadcast close quest

When this commit lands the line, all Broadcast close implementation children are already present and only landing remains, but converting its README into a sized leaf leaves completed work listed in m1. Because broadcast-remove.md requires this still-existing document, quest ready will continue to report Remove finish as blocked after Broadcast close reaches main, and agents can also re-claim the completed quest. Delete this README and its root entry, then clear the corresponding Required entry as part of completing the line. quest/CLAUDE.mdL108-L113

Useful? React with 👍 / 👎.


## Goal

Expand Down Expand Up @@ -34,11 +34,8 @@ object ended", not "the path went offline": announcements say whether a path
is live, and a path can be announced again by a new object. Caches and moq-hls
use it to tell a live object from a replaced one at the same path.

Stage the `dev` removal as the child below.

## Quests

- [Remove finish](/quest/m1/broadcast-close/remove.md) - on dev, the deprecated broadcast end APIs are gone and `closed()` carries no cause
The `dev` removal is [Remove finish](/quest/m1/broadcast-remove.md), which
waits for this line to reach `main`.

## Related

Expand Down
4 changes: 4 additions & 0 deletions quest/m1/broadcast-close/remove.md → quest/m1/broadcast-remove.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,3 +19,7 @@ This is a published API break, so it targets `dev`.
so `rs/moq-ffi/uniffi.toml` excludes it. Kotlin's `close()` releases the handle,
which ends the broadcast only once no `dynamic()` handle remains. Removing
`finish` leaves Kotlin without a forced end; decide whether it needs one.

## Required

- [Broadcast close](/quest/m1/broadcast-close/README.md) - the deprecations this removes, which must reach `main` and then `dev` first
Loading