Found during the 2026-07-25 agent-leaf live-verify (hermiq#41 deploy).
POST /api/agents/{id}/run-on-object resolves the agent via OpenRegister's AgentMapper (the oc_openregister_agents table — 13 rows). A run-on-object against a table agent uuid → 202 (works). But the hermiq /api/agents UI listing returns agents from a different store (OR objects, different uuids). So an agent uuid copied from the UI returns a clean fail-closed 404 {"error":"Agent not found"} — not a route error, but the two agent sources don't share uuids.
Impact: the run-on-object endpoint + the type:agent manifest action are correct, but a manifest author who takes an agent uuid from the hermiq UI will get a 404. Need one canonical agent store (or run-on-object to resolve against both / the same store the UI shows).
Endpoint + governed dispatch + leaf are otherwise live and verified (202 with a table agent, leaf registered in openregister.integrations.leaves).
Found during the 2026-07-25 agent-leaf live-verify (hermiq#41 deploy).
POST /api/agents/{id}/run-on-objectresolves the agent via OpenRegister'sAgentMapper(theoc_openregister_agentstable — 13 rows). A run-on-object against a table agent uuid → 202 (works). But the hermiq/api/agentsUI listing returns agents from a different store (OR objects, different uuids). So an agent uuid copied from the UI returns a clean fail-closed404 {"error":"Agent not found"}— not a route error, but the two agent sources don't share uuids.Impact: the run-on-object endpoint + the type:agent manifest action are correct, but a manifest author who takes an agent uuid from the hermiq UI will get a 404. Need one canonical agent store (or run-on-object to resolve against both / the same store the UI shows).
Endpoint + governed dispatch + leaf are otherwise live and verified (202 with a table agent, leaf registered in openregister.integrations.leaves).