📖About

The Albus Bypass Runner (al-bx-01) opens one initiatives-store connection at the top of a run, then performs a ladder pickup whose retrigger runs ~90s of fleet calls plus validation, and later an Albus build call that can run minutes. The store's writer daemon closes idle client sockets after 60s, so the runner's connection is dead by the time it writes the post-retrigger decision (and again after the build) -> BrokenPipe -> the run crashes BEFORE Albus builds anything. Reproduced twice on the 2818 rename. Fix: reopen the runner's store connection after the retrigger and after the build call, so the lane can complete an autonomous ladder pickup end to end. Found while testing the Albus bypass lane on the parked Planner-to-Initiative-Audit rename (family 2818).

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

• A ladder pickup by the Albus bypass lane no longer crashes after the retrigger; the run proceeds to Albus's build step. (must_have)
• After the build call the runner can still record its verdict and end its bypass, instead of dying on a broken pipe. (must_have)