📖About

Ninad (2026-08-06): both apps found dead — last launched by the estate relaunch on 2026-08-03 22:56, still alive at the 2026-08-04 08:25 pass (skipped as running), died unlogged some time after, and nothing relaunched or flagged them: their serving processes are not droid-registered so the Daily Process Sweep cannot see them, and the Azure Cost Tracker sits on port 7070 — below the 7080-7400 range the registry-derived restart lane accepts — so Radagast cannot manage it either. Scope: restart the Infra Monitor via Radagast now; move the Azure Cost Tracker onto a port inside the Carol range (registry + nginx + relaunch) so the restart lane and monitors can hold it; register both serving processes as droids with run-audit so silent death is visible next time.

⚖️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)
• [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] 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

• Carol Infra Monitor serves 200 again via the sanctioned Radagast restart (must_have)
• Azure Cost Tracker moved to a port inside the Carol managed range, nginx and registry updated, serving 200 at its public URL (must_have)
• Radagast restart_app can manage the Azure Cost Tracker at its new port (must_have)
• Both apps serving processes are droid-registered with run-audit so the Daily Process Sweep detects future death (must_have)