📖About

Ninad 2026-07-15 item 1: the Initiatives Tracker (port 7178) must count initiatives as done when closed OR when reviewing+uat-pending (both). The done-filter exists in three endpoints; verify EVERY endpoint/chart uses it (no closed-only leftovers), fix divergences, and verify the LIVE app serves the rule (bounce via Radagast if the in-memory code is stale).

⚖️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 Initiatives Tracker app is registered and live, but it is not confirmed that all endpoints count done as closed OR reviewing+uat-pending. No recent closed initiative addresses this specific done-filter change. The live app may still have a closed-only filter in some endpoints. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• CAROL-INI-2812 verified + locked: the Initiatives Tracker already counts done as closed OR reviewing+uat-pending. — Audit of every endpoint in the tracker app: the combined rule (CAROL-INI-2315 ext) is present in all three initiative endpoints (_close_days, closed-daily, closed-on); no closed-only filter exists anywhere; the other endpoints are activity-based (no initiative-status filter). LIVE verification: closed-on for 2026-07-14 returns 37 items including reviewing+uat-pending rows 999901439/41/42/43; the running process (started Jul-11) is newer than the file, so no bounce needed. NEW regression shared/test_ini2812.py (3/3) locks the rule in source AND against the live app. No code change was required — the ask was already implemented; this initiative converts it into a verified, regression-locked contract. (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

• Every Tracker endpoint and chart counts done as closed OR reviewing-with-uat-pending; no closed-only filter remains in the app. (must_have)
• The live app (not just the file) serves the rule: an API response includes a known reviewing+uat-pending initiative in the done counts. (must_have)
• Regression: a new test locks the done-filter; runner reports zero NEW FAILURE. (must_have)