📖About

Follow-on to CAROL-INI-2058/2060. The Planner top lane boxes (Albus bypass / Orion bypass / Planner totals) deliberately mirror the recent card but still scope to LIMIT 10. Align them to the same rolling 7-day window: /api/exec/lane-stats filters updated_at >= datetime(now,-7 days) (fallback created_at; LIMIT 10 only if no date column), dropping the fixed 10. Keep the blocked/closed/reviewing status filter and the lane aggregation.

⚖️Decisions

• Auto-detected remediation target INI-999900291 from title/description scan (matched CAROL-INI-2058 -> row id 999900291 (CAROL-INI-2058-00: Planner recent card: rolling 1-week window instead of last 10)); 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)
• Aligned the top lane boxes to the recent cards rolling 7-day window (dropped LIMIT 10; same updated_at filter + status set). Boxes now count the full week: Orion bypass 134 (91 closed), Planner 59 (58 closed), Albus 0; sum 193. (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 Planner top lane boxes count the same rolling-7-day blocked/closed/reviewing set as the recent card (no fixed LIMIT 10). (must_have)