📖About

The Planner execution tree lists initiatives ordered by id ascending, so actively-running work (e.g. an old low-or-high id re-running today) does not surface at the top. Change the ordering to last-activity-descending: compute each initiative's most recent step/run activity (max droid_run started_at across its executions, linked via task_id; fallback to the initiative's updated_at/created_at) and sort the tree by it, newest first, so currently-executing initiatives appear on top. Backend-only change in the planner app's execution-tree builder; restart the planner.

⚖️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)
• Planner execution tree now sorts initiatives by last activity (newest first): computed from the max droid_run started_at across each initiative's executions (linked by task_id), falling back to updated_at/created_at. Replaces the id-ascending order so currently-executing work surfaces on top. Backend-only; planner restart required to load. (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 execution tree returns initiatives sorted by last activity (most recent first); a currently-executing initiative appears at/near the top, not buried by id order. (must_have)