Seed AgentTerm SourceOS control surface

[mdheller]

Summary

This PR turns the fresh agent-term repository from a README stub into a runnable seed implementation for a Matrix-first, terminal-native SourceOS ChatOps control surface.

It adds:

• Python package scaffold and agent-term CLI entry point.
• SQLite-backed local event log.
• Canonical AgentTerm event model.
• SourceOS plane registry covering Matrix, Agent Registry, Sociosphere, Prophet Workspace, Slash Topics, Memory Mesh, New Hope, Holmes, Sherlock Search, legacy Sherlock, MeshRush, cloudshell-fog, AgentPlane, and Policy Fabric.
• Adapter contract surface for SourceOS planes plus Hermes, Codex, Claude Code, OpenCLAW, GitHub, CI, MCP, and local process participants.
• Governance-preserving CLI commands for agent identity, workroom, topic, memory, semantic, investigation, search, graph, and shell events.
• Matrix-first and SourceOS-control-surface architecture docs.
• Agent Registry boundary doc so AgentTerm cannot enable non-human participants from local config alone.
• Holmes boundary doc so AgentTerm does not redefine or desecrate Holmes semantics.
• Example configuration, AGENTS.md, Copilot instructions, tests, and CI.

Boundary decisions

• Matrix is canonical ChatOps transport; Slack/Discord are bridge targets.
• AgentTerm is the operator surface and local event log, not a monolith.
• Agent Registry remains the authority for agent specs, identities, sessions, memories, tool grants, revocation, and runtime authority.
• Every non-human AgentTerm participant must resolve through Agent Registry before enablement.
• Policy Fabric remains the admission/evidence authority for side effects and sensitive context release.
• AgentPlane remains the execution authority for validate/place/run/replay/evidence.
• cloudshell-fog remains the shell/session authority for OIDC, placement, TTL, PTY attach, and audit.
• Holmes is treated conservatively: AgentTerm may request, display, correlate, and audit Holmes-owned work, but does not define Holmes behavior.
• New Hope is separate from Holmes/Sherlock: it is the semantic runtime for message/thread/claim/citation objects.

Validation

Added CI:

ruff check .
pytest

I did not run the suite locally through the connector; the PR CI should be the first execution gate.

Follow-up lanes

After this seed lands, implementation should fan out into focused PRs for:

1. Matrix adapter and E2EE posture handling.
2. Agent Registry identity/grant/session/revocation adapter.
3. Policy Fabric admission stub.
4. Sociosphere and Prophet Workspace adapters.
5. Slash Topics, Memory Mesh, New Hope, Sherlock Search, Holmes, and MeshRush adapters.
6. cloudshell-fog and AgentPlane adapters.
7. Hermes, Codex, Claude Code, OpenCLAW, GitHub, CI, MCP participants gated by Agent Registry.
8. Textual TUI for rooms, threads, agents, grants, workrooms, topics, memory, semantic objects, investigations, graphs, approvals, and evidence.