📖About

The Today / This week / This month tiles and the calls-all-time counter read the whole ledger with no CLI exclusion, while the daily chart and by-service chart on the same page already exclude the CLI lane (CAROL-INI-3002 UAT rule). One question derived twice had drifted. Fix: the tiles endpoint applies the SAME existing CLI-exclusion helpers the charts use - no second copy of the rule - and the tile sublabels say CLI excluded so the page states its own basis.

⚖️Decisions

• Auto-detected remediation target INI-999901680 from title/description scan (matched CAROL-INI-3002 -> row id 999901680 (CAROL-INI-3002-00: Token Cost Tracker: subscription-level chart, day-to-service )); 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)
• Display basis only - the CLI lane stays fully recorded — Cost truth is unchanged: every operator-lane row still lands in the ledger and on its initiative (cookbook 446). What changed is the PAGE basis - the tiles now answer the same question as the charts under them, and say so on their face. (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 Today / This week / This month tiles and the calls counter exclude the CLI lane, using the same exclusion helpers the charts already use - no duplicated rule (must_have)
• After the fix the Today tile matches the non-CLI ledger total for the day (verified against a direct ledger computation) (must_have)
• The tile sublabels state CLI excluded, matching the daily charts declared basis (must_have)
• A regression test compares the tiles endpoint to an independent non-CLI ledger sum and fails if the two ever drift (must_have)