📖About

Found while building CAROL-INI-3693 (CLI-234). The regression check that guards the Model Subscriptions consumption chart was written on 2026-08-02 and asserts DeepSeek as a live subscription: it expects 8 declared subscriptions, asserts 'deepseek is present', asserts DeepSeek's committed limit and basis for a named month, and then CRASHES with StopIteration reaching into the subscription list for a DeepSeek row that is no longer there. DeepSeek was retired on 2026-08-05 by Ninad's ruling (CLI-233 / CAROL-INI-3692, cookbook 1211), so the check is asserting a world the estate deliberately left. Verified NOT caused by 3693: the identical three failures and the identical crash occur against the pre-change files. The failure mode is the one the induction names - a check that could not run is not a pass - and it is worse than a plain red, because the crash aborts the remaining assertions in the file, so everything after the DeepSeek line is currently UNAUDITED rather than passing. Scope: bring the check to the post-retirement truth (the live subscription list, a usage-based lane that still exists standing in for the DeepSeek-specific cycle and limit assertions, and the several-subscriptions-consuming threshold re-derived rather than re-tuned to go green), and confirm no assertion after the former crash point was silently wrong all along.

⚖️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)
• Current state at filing (Elrond validity check): The model-subscriptions app is registered and live, and DeepSeek was retired per CLI-233/CAROL-INI-3692, but the consumption check written before that retirement still asserts 8 subscriptions including DeepSeek and crashes with StopIteration. CAROL-INI-3693 (summary boxes) is done but the filing verified the identical failures pre-date that change, so the check remains broken and every assertion after the DeepSeek line is unaudited. No recently closed initiative addresses this check. (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)
• [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 Model Subscriptions consumption check runs to completion with no exception, so every assertion in the file is actually evaluated rather than abandoned at the DeepSeek line. (must_have)
• No assertion in the check names DeepSeek or any other retired subscription as live; the declared-subscription assertion is derived from the registry's live rows, so the next retirement or addition does not make it stale again. (must_have)
• (must_have)
• Any assertion that sat after the crash point is confirmed to pass on its own merits, and any that does not is reported rather than adjusted to go green. (must_have)
• The threshold on how many subscriptions consume in a full month is re-derived from what the ledger actually shows, never lowered to make the check pass. (must_have)