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

[kixelated]

Problem

The broadcast-close line (#4031) and its last child, Remove finish (#4152), block each other. A line's PR stays a draft until its Quests list is empty, but the removal is a dev break that can only land after #4031 reaches main and then dev.

Approach

• Move remove.md out of the line to quest/m1/broadcast-remove.md, ranked right after Broadcast close in m1, with the line as Required.
• The line README has no children left, so it is sized [S]. Its remaining work is to land: merge main in and mark quest(broadcast-close): Broadcast close #4031 ready.

Impact

• None (quest docs only).

Alternatives

• Landing the whole line on dev: this delays the additive close() and the deprecations that main users need.

Follow-ups

• feat(net)!: remove the deprecated broadcast finish and abort #4152 should delete quest/m1/broadcast-remove.md (the new path) when it completes, and pick up this move when it merges its base.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[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	✅ Completed 2026-09-25T18:46:33.836944Z	ec04f88	PR opened

ℹ️ 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]

MERGE

This is a clean quest-docs unblock. The broadcast-close line and Remove finish were deadlocking each other: the line stays draft until Quests is empty, but the removal is a dev break that can only land after #4031 reaches main and then dev. Pulling remove.md out as a sibling under m1, ranking it after Broadcast close, and pointing Required back at the line is the right shape.

Positive improvement: yes. The line README can go [S] with no children left, and the remaining work is honestly just landing (#4031 ready after merging main). Worth the complexity: yes; the diff is tiny and docs-only. Different approach: landing the whole line on dev would delay the additive close() and deprecations that main users need, so rejecting that is correct. Changing the empty-Quests draft rule would be heavier and the wrong place to fix it.

One follow-through to watch: #4152 should delete quest/m1/broadcast-remove.md (the new path) when it completes, and rebase onto this move when its base merges. No code impact.

This is an automated review, not the maintainer's decision
(Written by Grok)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ec04f88d8c

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

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 👍 / 👎.