📖About

UAT rework of CAROL-INI-3125's admin screen. Fold agent mapping into Heimdall's existing User Management app (port 7302) as a feature: the all-users list gains a 'Mapped agents' column showing each user's mapped agents, and the user detail page gains an inline editor to assign/revoke agents (within the user's subscribed services). Remove the standalone agent-map page from the Access Mgmt app. A separate app is overkill (Ninad). Orion bypass.

⚖️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)
• Current state at filing (Elrond validity check): User Management app is registered and running; agent mapping access layer from CAROL-INI-3125 exists, but mapping UI remains in the standalone Access Mgmt app. Admins have no inline agent editing within User Management and the all-users list lacks a Mapped agents column. (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

• Heimdall's User Management app shows, for EVERY user, the agents currently mapped to them (an all-users -> mapped-agents overview), not a per-user picker on a separate page. (must_have)
• An admin can edit a user's agent mapping from within User Management (which agents, within the user's subscribed services), and the change persists to the user's config. (must_have)
• The standalone agent-mapping page is removed; agent mapping is a feature of the existing User Management app, not a separate app/screen. (must_have)