Implement Agent Registry adapter for participant identity, grants, sessions, and revocation

[mdheller]

Agent work order

@copilot @codex please implement this after PR #1 lands or by branching from seed/agentterm-chatops-core if instructed.

Goal

Add a live Agent Registry adapter so AgentTerm cannot enable or address non-human participants from local config alone.

Context

SocioProphet/agent-registry is the authority for agent specs, identities, sessions, memories, tool grants, revocation, and runtime authority. AgentTerm is only the terminal operator surface and event log.

Required invariant

Every non-human AgentTerm participant must resolve through Agent Registry before enablement. This includes Hermes, Codex, Claude Code, OpenCLAW, Matrix bots, GitHub bots acting as agents, CI bots acting as agents, MCP tools, local process agents, and future SourceOS agents.

Required scope

• Add an Agent Registry adapter behind the AgentTermAdapter boundary.
• Add identity resolution events for requested participants.
• Add registration validation before participant enablement.
• Add tool-grant request and revocation-check event shapes.
• Fail closed when registry status is unknown, missing, or revoked.
• Add tests using a fake registry backend; do not require a live registry service in CI.
• Preserve agent_id, agent_registry_ref, agent_spec_version, session_id, tool_grant_ids, revocation_check_at, runtime_authority, adapter_key, and policy references where available.

Non-goals

• Do not move Agent Registry schemas into this repo.
• Do not allow local config to bypass Agent Registry.
• Do not enable process-backed agents in sensitive contexts without registry resolution and Policy Fabric admission.

Validation

ruff check .
pytest