📖About

Replace every hardcoded reference to /home/caroladmin/dev and the various DB paths across the planner, dispatcher, reviewer, Albus, Argus, Forge and shared modules with calls to the project registry helper. Carol stays the default so existing flows are unaffected.

⚖️Decisions

• Follow-on to parent INI 999900546 (orion)
• Scope inherited verbatim from parent INI 999900546 per CAROL-INI-361. (elrond.initiative_author)
• Validator round 2 still flagged 1 items — operator review needed (CAROL-INI-509). (elrond.initiative_validator)
• [status-router] planned -> dispatched | event=dispatch | RSI: auto-promoted bypasses depth limit (CAROL-INI-2198) (spb-01)
• [status-router] planned -> dispatched | event=dispatch | RSI: auto-promoted bypasses depth limit (CAROL-INI-2198) (spb-01)
• [status-router] dispatched -> blocked | event=stuck_10min_no_activity | Elrond safety net: initiative has had no activity for 10+ minutes. Blocking under the parallel safety mechanism. (el-watchdog)
• Elrond safety net blocked initiative: no activity for 10+ minutes. Parallel mechanism (twin of handshake). (el-watchdog)
• Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol. Albus was supposed to wake for step 0 (cause=albus_no_show) but did not respond. Cause: albus_no_show. Reason: Elrond safety net: initiative stranded 10+ min. Albus wake failed or produced no useful result. (el-s1)
• Orion remediated: Albus RSI group diagnosis (via INI 999900519): [procedural, confidence high] The initiative became blocked because Elrond's safety net triggered after 10 minutes of inactivity during the executing phase. The execution history shows a pattern of 'Idle close' failures and the initative was repeatedly stalled at the pre-verify gate due to slot cancellations, eventually proceeding to dispatch and execute but then receiving no further step activity. The root cause is a procedural pipeline deadlock: after dispatch, the executor (likely Albus) never woke to perform step 0, leaving the initi (orion)
• [status-router] blocked -> closed | event=operator_put | PUT /api/initiatives (operator)
• [rsi-group-cure] Cured by the group diagnosis on INI 999900519 (shared cause stuck_10min_no_activity); retriggered as INI 999900935. Root cause: [procedural, confidence high] The initiative became blocked because Elrond's safety net triggered after 10 minutes of inactivity during the executing phase. The execution history shows a pattern of 'Idle close' failures and the initative was repeatedly stalled at the pre-verify gate due to slot cancellations, eventually proceeding to dispatch and execute but then receiving no further step activity (elrond.rsi_loop)

✅Success criteria

• When a pipeline droid is invoked with project=carol, it behaves exactly as today. When invoked with project=glover, it reads paths from the glover row of the projects table instead of Carol's hardcoded ones. (must_have)