📖About

Ninad ruling 2026-08-12 (CLI-245): the Agent Chat service (id whatsapp) holds ONLY the three per-agent chat tracks. Move agent-resources-leo/carol/sam-chat into it (keys never change). Dissolve WhatsApp + Serving Engine tracks INTO Carol Chat - a Carol conversation bills the Carol track whatever channel carried it (whatsapp reply, web reply incl. anonymous per 3780 superseded-in-part, engine work, availability/product/quality tasks move with their owners and payer attributions intact). Retire Web Chat + the superseded agent_chat_reply task. Budgets 2/2/2 Leo/Carol/Sam (Leo 6 to 2); channel-track allocations zeroed and disabled. All four layers move together per the track law (row, work units incl. source_spec payer, blocks, budget allocation).

⚖️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 -> parked | event=bypass_blocked|pipeline_stopped_park_3044 | pipeline stopped (operator OFF or budget-paused) - parked instead of blocked so the stop does not strand live work (CAROL-INI-3044); resumes on turn-ON (or-bx-01)
• Bypass session failed — initiative blocked (exec 1416) — bypass_end called with success=False for exec 1416, run 3163 (shared.bypass.bypass_end)
• [status-router] parked -> 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)
• Orion remediated: INI-999902731 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999902731 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

• The Agent Chat service lists exactly three tracks - Leo Chat, Carol Chat, Sam Chat - and Agent Resources lists none of them; track keys unchanged. (must_have)
• Every task from the dissolved WhatsApp/Serving Engine/Web Chat tracks either serves Carol Chat (keys, owners and source_spec payers intact) or is retired with zero droids left behind; reference counts match the before-picture. (must_have)
• (must_have)
• A real resolver check shows a serving-engine droid resolving through Carol Chat to its declared lane, and the next real Carol conversation books against the Carol Chat track. (must_have)