📖About

Rework the User Management app so the user's stable id is the primary identifier and email is just one attribute. Reduce the landing page to a clean, readable set of columns keyed on id, and move all other information (email, type, dates, mapped agents, visit history, bio) into a per-user drill-down opened by id. Keep the agent-mapping editor and visit history working on the detail view.

⚖️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 -> executing | event=operator_put | UAT refinements: exclude Carol (agent), remove a spam visitor, bump landing font (orion)
• Handover-watchdog: planner-pending nudge for phase 2 (auto-invoked Elrond planner). (elrond)
• Handover-watchdog: planner-pending nudge for phase 2 (auto-invoked Elrond planner). (elrond)
• [status-router] executing -> reviewing | event=dispatcher_transition | dispatcher state change (ds-s1)
• [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

• The User Management landing page uses the user's id as the primary identifier for each user (id shown and used as the drill-down link), not the email (must_have)
• The landing page shows a reduced, clean set of columns per user; email is no longer a landing column but moves into the detail view (must_have)
• Each user has a drill-down detail page reached by user id that shows all additional attributes including email, name, role, type, dates, mapped agents and visit history (must_have)
• The existing agent-mapping editor and visit history still work on the detail page (must_have)
• The User Management landing page uses the user's id as the primary identifier for each user (id shown and used as the drill-down link), not the email (must_have)
• The landing page shows a reduced, clean set of columns per user; email is no longer a landing column but moves into the detail view (must_have)
• Each user has a drill-down detail page reached by user id that shows all additional attributes including email, name, role, type, dates, mapped agents and visit history (must_have)
• The existing agent-mapping editor and visit history still work on the detail page (must_have)