📖About

Argus's scheduled regression run executes test_ini3624, whose probe picks the NEWEST live orion-filed initiative and calls the real bypass_start/bypass_end against it in the live Orion book. The leaked execution (0 checks) becomes the STANDING attempt, so the twin reviewer fails the real work as unauditable — this blocked CAROL-INI-3750 today (probe row exec 1369, 01:24). Scope: sandbox the probe (its bypass rows must land in a temp copy of the book, never the live one, and never touch a live initiative), re-attribute the leaked probe rows in the live book to this initiative so no real family carries them, and re-run the twin review on CAROL-INI-3750.

⚖️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

• test_ini3624's fresh-row probe writes to a temporary copy of the bypass book and does not name or mutate any live initiative (must_have)
• Existing probe executions in the live Orion book (title INI-3624 regression probe) are re-attributed away from the real initiatives they polluted, with the correction recorded (must_have)
• The twin review of CAROL-INI-3750 grades its real standing attempt (checks present) after the cleanup (must_have)
• A regression test proves the probe leaves the live book untouched (must_have)