📖About

Two defects on the Daily Spend (last 14d) stacked-by-subscription chart. (1) The chart canvas is 240px tall; with the current spend scale the stacked bars are too small to read - double the height to 480px (daily chart only, service chart unchanged). (2) The initiatives-worked line reads 0 for almost every previous day. Root cause: the trend endpoint filters worked families to planner mode only (comment cites CAROL-INI-3138) - since the fleet moved to the bypass lanes the line flatlined while 15-58 real families/day had spend and recorded work (measured 2026-08-10 via the shared day-count source). Cure: count worked families across all three lanes (planner, albus bypass, orion bypass) from the shared worked-modes source, and update the legend/tooltip and the registered metric definition to match.

⚖️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)
• [delivery-check] 5 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• UAT r1 (Ninad, 2026-08-10): 480px height did not give the desired readability. (ninad)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [delivery-check] 5 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [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 line counts distinct worked FAMILIES per day across ALL execution lanes (planner + albus bypass + orion bypass), still from the shared day-count source with no app-local counting logic (must_have)
• Previous days with real bypass work show non-zero counts on the live API (e.g. days that measured 15-58 worked families no longer read 0) (must_have)
• Chart legend/tooltip wording and the registered metric definition reflect the all-lanes semantics (must_have)
• Change is live: the running app serves the new chart height and corrected counts (must_have)