📖About

New Clara-owned app via the add-new-app skill: services-first landing with task counts and status, drill-down per service to tasks grouped by track then agent with budget vs actual cost and time per day, reading only the shared task accessor; Carolopedia updated.

⚖️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)
• [status-router] executing -> reviewing | event=bypass_work_complete | CAROL-INI-3608 bypass work complete; Reviewer closes per cookbook 20 (orion)
• [delivery-check] 4 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] reviewing -> blocked | event=reviewer_verdict | bypass twin reviewer verdict != pass (CAROL-INI-2039) (orion)
• [status-router] blocked -> reviewing | event=false_block_restored | CAROL-INI-3608: twin review re-graded PASS (standing attempt, 7 checks, 0 failing) after the check results were recorded; the earlier fail was 'no checks recorded = unauditable', cured by recording the real checks. Operator revives on the verdict per rule 717; parks for UAT. (orion)
• Orion remediated: INI-999902521 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999902521 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)
• [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

• App registered, Clara-owned, standard format, services-first landing (must_have)
• Drill-down service to tasks by track then agent with budget vs actual cost and time (must_have)
• All numbers from the shared task accessor plus cost ledger (must_have)
• Passes add-new-app review contract; Carolopedia page and concept live (must_have)