📖About

Three Ninad asks on the Token Cost Tracker's by-service chart. (1) Bars lose the white selection outline and all bar borders, and render in slightly darker provider colours. (2) A card strip above the chart shows every service name in clearly readable text with that day's spend; selecting a card or a bar highlights that service's bar segments in a brighter shade of the same provider colours - at Ninad's direction this supersedes the earlier selection-never-recolours outline ruling for THIS chart only (the daily chart keeps its outline). (3) Completeness: the chart must catch every service's spend each day - today real metered DeepSeek spend by Orion-owned scheduled droids (the Carolopedia refreshers) is invisible because the CLI-lane exclusion rolls every droid up to its owner; the exclusion becomes lane-scoped (enumerated CLI droids + bare CLI agent ids only) so registered droids' metered spend shows under their service, and nonzero-but-tiny bars stay visible as minimum-length slivers instead of sub-pixel invisibility next to the pipeline's spend.

⚖️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)
• The by-service chart WAS catching multiple services - two things hid them: the CLI-lane exclusion rolled every droid up to its owner (so Orion-owned metered scheduled droids like the Carolopedia refreshers vanished), and non-pipeline bars were sub-pixel next to the pipeline's spend. Fixed both rather than the chart alone. (orion)
• The CLI exclusion is now LANE-scoped in one shared helper used by all three excluding endpoints (daily trend, day-by-service, service breakdown): enumerated CLI droids plus bare CLI agent ids only, no droid-to-owner rollup. Real metered spend always shows under its service; Orion's notional flat-plan rows stay excluded. (orion)
• At Ninad's direction the selection-never-recolours outline rule is superseded for the by-service chart ONLY: bars are borderless, base colours slightly darker (x0.82), the selected service a brighter shade (x1.3) of the same provider hues; the daily chart keeps its outline selection. (orion)
• Service cards above the chart show every service name in readable text with the day's spend, sorted by cost; card and bar clicks share one selection path. Tiny nonzero segments render with a 3px minimum bar length, with zero values passed as null so slivers only appear for REAL spend. (orion)
• [delivery-check] 3 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3321.py: PASS (1 passed in 0.70s) (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 by-service bars show no white outline and no bar borders, in slightly darker provider colours; the selected service is highlighted by a brighter shade of the same colours. (must_have)
• A card strip above the by-service chart names every service in clearly readable text with the selected day's spend; clicking a card or a bar selects that service and card, chart and drill-downs stay in sync. (must_have)
• Every service with real spend on a day is visible in the chart: metered spend from owner-rolled scheduled droids appears under its service, and tiny nonzero bars render as visible slivers. (must_have)