📖About

Keep the dispatch queue in lock-step with the sprint plan. Today only the Sprint Builder droid refreshes the dispatched set (it calls build_sprint then dispatch_today as two separate steps), and the refresh only ADDS today-sprint items - it never RETRACTS an initiative left stuck in dispatched after a rebuild moves it out of todays sprint. Fix: fold the dispatch refresh INTO build_sprint so EVERY sprint update syncs the queue, and make it bidirectional - retract planner-mode initiatives stuck in dispatched that are no longer in todays sprint (back to planned), then dispatch todays current items. All status changes via the status router. Follow-on to CAROL-INI-1962/1939.

⚖️Decisions

• Auto-detected remediation target INI-999900185 from title/description scan (matched CAROL-INI-1962 -> row id 999900185 (CAROL-INI-1962-00: Elrond prioritises system incidents over transformation work:)); override by setting remediates_initiative_id explicitly at bypass_start. (system-auto-detect)
• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Every sprint rebuild refreshes the dispatch queue automatically (the refresh is intrinsic to build_sprint, not a separate caller step). (must_have)
• The refresh is bidirectional: planner-mode initiatives stuck in dispatched but no longer in todays sprint are retracted to planned; todays current items are dispatched. (must_have)
• All dispatch/retract status changes go through the status router (no raw status writes). (must_have)