📖About

Ninad (2026-08-15) rich-chat arc, phase 2. (a) Live turn progress: the engine records stage transitions per turn_id; the window swaps the typing dots for honest stage lines. Needs the window contract to grow a fifth call across all chat doors - one template change, each door exposes the endpoint. (b) Threads: named conversations per sender with search, replacing the single endless scroll; store grows a thread key, clear scopes to a thread.

⚖️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=dispatcher_transition | dispatcher state change (ds-s1)
• [status-router] reviewing -> blocked | event=reviewer_verdict | bypass twin reviewer verdict != pass (CAROL-INI-2039) (orion)
• [status-router] blocked -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [arc] Rich-chat arc resequenced into FIVE phases (Ninad, 2026-08-16): 1 rich replies (3864/3865/3866) | 2 live stages + named threads (3867) | 3 the self-correcting turn + WhatsApp full-turn convergence (3873) | 4 files, charts, canvas (3868) | 5 voice + get-back-to-me (3869). — The self-correcting turn moved ahead of files/charts/canvas because it rebuilds the turn machinery and finishes the one-engine convergence (3872/3877); file grounding and canvas state plug into that turn, so building them first would wire them to a seam about to be rebuilt. Voice remains last per Ninad's standing ruling. (orion)
• [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

• While a turn runs the window shows the real current stage, not dots; stages come from the engine, never invented client-side (must_have)
• Conversations can be named, listed, switched and searched in every agent window (must_have)
• The canon byte-identity test stays green across all doors with the grown contract (must_have)