📖About

Today there is no UI surface anywhere in Carol that shows what an agent or droid is actually instructed to do. Agent identity (character, roles, rights, duties) is exposed via /api/employee/{id} (port 7147) and rendered on /employee/{id}, but the actual system prompts that govern behavior — Elrond identity.md, ip-s1 _PROMPT, el-s1 _STANCE_PROMPT, ir-s1 close-decision prompt, al-sh-01 verdict prompts, every Forge/Argus/Sage prompt, etc. — are buried in .py files reachable only via SSH+grep. This makes prompt review (e.g. checking that Elrond carries the no-sudo Hard Rule) effectively invisible to Ninad and to anyone auditing pipeline behavior. Add a Prompts tab to /employee/{id} that lists the agent identity prompt and every owned-droid prompt, with copy + diff + change-tracking via prompt hashes.

⚖️Decisions

• Follow-on to parent INI 999941 (orion)
• Scope inherited verbatim from parent INI 999941 per CAROL-INI-361. (elrond.initiative_author)
• [status-router] planned -> dispatched | event=dispatch | dispatcher queued (ds-s1)
• [status-router] dispatched -> planned | event=dispatch_retract | No longer in the top-3 dispatch window (CAROL-INI-1972). (spb-01)
• [status-router] planned -> dispatched | event=dispatch | dispatcher queued (ds-s1)
• [status-router] dispatched -> planned | event=dispatch_retract | No longer in the top-3 dispatch window (CAROL-INI-1972). (spb-01)
• [status-router] planned -> closed | event=superseded | superseded sibling closed by Author (ia-s1)
• Superseded by INI 999900481 (CAROL-INI-0055-02: Surface agent + droid prompts on Org employee profile (Prompts tab)) per CAROL-INI-401. Closed by Author (was status=planned). (Author)

✅Success criteria

• curl http://localhost:7147/api/employee/agt_011/prompts returns Elrond identity.md content + el-s1/ir-s1/ip-s1/dp-s2/bg-s1/dp-s1/pm-s1 prompts each with non-empty sha256 (must_have)
• Open /employee/elrond in a browser — Prompts tab visible, displays 1 identity prompt + at least 5 droid prompt cards (must_have)
• Coverage check: /api/prompts/audit returns a row for every active agent in registry.db (count matches) and every owned droid is either prompt-resolved or marked no-prompt-found (must_have)
• Sha256 changes when the underlying file is edited (verify by touching identity.md and re-querying) (must_have)
• No regression on existing /employee/{id} rendering or /api/droids/{agent_id} response shape (must_have)