📖About

Two cosmetic changes. (1) Midas Service Catalogue (services-catalogue app): render each services team as a clickable profile photo + name (avatar from Carolopedias agent portraits), linking to the org profile. (2) Carolopedia service pages: add an Apps section listing the apps owned by the services team agents (owner + supporting + service_agents + agents.service), each hyperlinked to its Carolopedia app page.

⚖️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 -> active | event=bypass_active | bypass transition (or-bx-01)
• Midas Service Catalogue renders each service team member as a clickable circular profile photo + name (avatar sourced from Carolopedias agent portraits, broken images hidden), linking to the org profile. — Ninad: show the service team as clickable profile photo and name. (orion)
• Carolopedia service pages add an Apps section listing apps owned by the services team agents (owner + supporting + service_agents + agents.service), each hyperlinked to its Carolopedia app page. — Ninad: detail the apps associated with the service via agent teams + app ownership, with hyperlinks. (orion)
• [status-router] active -> 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

• Midas Service Catalogue shows each service team member as a clickable profile photo and name (must_have)
• Each Carolopedia service page lists the apps owned by its team agents, hyperlinked to the app pages (must_have)