📖About

Ninad spec 2026-07-04 (CLI-023), amended: keep the chart view exactly as it is - same daily buckets, same drill-down - and (1) stack each bar into 3 mode segments (planner, Albus bypass, Orion bypass) in slight shade variations of the same colour; (2) y-max = 120 percent of the total of the max-count bar summed across the 3 modes. Backend: the closed-daily endpoint additionally returns per-mode count/tokens/cost per day (existing fields untouched). Frontend: 3 stacked Chart.js datasets in purple shades with a legend; selection highlight adapts to the stack.

⚖️Decisions

• 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)
• Ninad amendments applied in-flight (CLI-023): keep the existing chart view (daily buckets) - only stack the bars per mode; y-max = 120 percent of the total of the max-count bar across the 3 modes (independent of which mode filters are ticked). The earlier weekly-bucket draft was discarded unrun. (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> executing | event=operator_signoff | CLI-023 extension (Ninad): the initiative listing should also show the mode (planner / Albus bypass / Orion bypass). (orion)
• Handover-watchdog: planner-pending nudge for phase 3 (auto-invoked Elrond planner). (elrond)
• [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

• The initiatives chart looks the same as before (same buckets, same click-to-drill, same filters) except each bar is now a stack of three shade-varied segments of one colour family - planner, Albus bypass, Orion bypass - with a small legend naming them (must_have)
• The y-axis tops out at 120 percent of the busiest bar's TOTAL across all three modes, so the tallest stack fills five-sixths of the chart (must_have)
• The mode filter checkboxes hide and show their segments without changing the 120 percent scale rule (must_have)
• The initiatives chart looks the same as before (same buckets, same click-to-drill, same filters) except each bar is now a stack of three shade-varied segments of one colour family - planner, Albus bypass, Orion bypass - with a small legend naming them (must_have)
• The y-axis tops out at 120 percent of the busiest bar's TOTAL across all three modes, so the tallest stack fills five-sixths of the chart (must_have)
• The mode filter checkboxes hide and show their segments without changing the 120 percent scale rule (must_have)
• Every row in the tracker's initiative listing shows its mode - Planner, Albus bypass or Orion bypass - as a labelled chip matching the chart's shade for that mode (must_have)