feat(cli): add Oh My Pi (omp) as 44th client surface

[DavidHLP]

Summary

• Add Oh My Pi (omp) as a STABLE, auto-detected client surface with full four-layer integration: MCP server registration, durable instructions, skill installation, and three direct-MCP tiered subagent profiles (Scout/Verify/Auditor)
• Register OMP's MCP configuration at ~/.omp/agent/mcp.json using the standard mcpServers JSON path with type: "stdio"
• Add OMP-specific profile rendering with mcp__codebase_memory_mcp_ tool names, exact-source reads (read-summarize: false), and automatic loading of the codebase-memory skill
• Update the supported-surface count from 43 to 44 across the main README, npm README, website, llms.txt, and CLI help

Refs #649.

ℹ️ Scope note for maintainers: This PR covers the OMP client-integration side of #649. The resources/list protocol compatibility issue described there was addressed separately in #958.

---

Install / Uninstall

OMP is detected automatically when its command or ~/.omp/agent marker is present.

# Install all detected client integrations, including OMP
codebase-memory-mcp install

# Preview without writing files
codebase-memory-mcp install --dry-run

# Remove managed client integrations
codebase-memory-mcp uninstall

# Preview uninstall
codebase-memory-mcp uninstall --dry-run

The OMP integration manages:

~/.omp/agent/mcp.json
~/.omp/agent/AGENTS.md
~/.omp/agent/skills/codebase-memory/
~/.omp/agent/agents/codebase-memory-scout.md
~/.omp/agent/agents/codebase-memory.md
~/.omp/agent/agents/codebase-memory-auditor.md

---

Test plan

• make -f Makefile.cbm test — 6224 passed, 1 skipped
• make -f Makefile.cbm lint-ci — CI linters passed (cppcheck, clang-format, NOLINT whitelist)
• make -f Makefile.cbm security — all security checks passed (75 files)
• git diff --check — no whitespace errors
• New OMP client, profile, registry, schema, and documentation contracts are covered by tests

---

Changes (13 files)

File	Change
src/cli/agent_clients.h	Add CBM_AGENT_CLIENT_OMP
src/cli/agent_clients.c	Add the stable client profile, detection marker, MCP path, JSON editing, and type: "stdio" schema
src/cli/agent_profiles.h	Add CBM_GRAPH_DIALECT_OMP
src/cli/agent_profiles.c	Add direct-MCP OMP profile rendering and tool-prefix rules
src/cli/cli.c	Add managed OMP install/uninstall paths, legacy migration content, and registry routing
src/main.c	Update the supported-client count and CLI help
tests/test_agent_clients.c	Cover OMP stability, capabilities, paths, JSON schema, and foreign-entry behavior
tests/test_agent_profiles.c	Cover direct-MCP profiles, tool names, read-summarize, skill autoloading, and handoff behavior
tests/test_cli.c	Update registry and documentation consistency contracts
README.md	Add OMP to the support matrix and update counts
pkg/npm/README.md	Add OMP and update counts
docs/index.html	Add OMP and update counts
docs/llms.txt	Add OMP and update counts

Design notes

• OMP is direct-MCP capable: runtime ablation testing confirmed its subagents can call mcp__* tools directly
• No HOOK capability is added because OMP's tool_call context event is advisory and does not provide a safe augmentation channel
• read-summarize: false keeps Tier 2/3 evidence grounded in exact source rather than structural summaries
• autoloadSkills: [codebase-memory] is required because OMP subagents start without parent conversation history
• The integration preserves foreign MCP entries and only removes content managed by codebase-memory-mcp

---

Checklist

• Every commit is signed off (git commit -s) — DCO present on f80b3c2
• Tests pass locally (make -f Makefile.cbm test)
• Lint passes (make -f Makefile.cbm lint-ci)
• New behavior is covered by tests

[DeusData]

Thanks for the comprehensive integration work. Before product-direction approval, the current head has two concrete configuration risks: it hardcodes ~/.omp/agent, ignoring named profiles and PI_CODING_AGENT_DIR, and it writes a global AGENTS.md whose OMP precedence can shadow existing user safety/custom instructions. The tests cover rendered strings and registry entries but not named/relocated profiles, install-plan/dry-run/uninstall, or instruction precedence. Please pause implementation while we decide whether OMP should be auto-installed at all; if accepted, profile resolution and a non-shadowing instruction policy are required.

[DavidHLP]

Thanks — understood. I’ll pause implementation until the product direction on OMP auto-installation is decided.

If the integration is accepted, I’ll revise it to:

• resolve the effective OMP agent directory instead of assuming ~/.omp/agent, including named profiles and PI_CODING_AGENT_DIR;
• use an instruction-installation policy that cannot shadow or replace existing user safety/custom instructions; and
• add behavioral coverage for relocated/named profiles, install planning, dry-run, uninstall, preservation of user-managed content, and instruction precedence.

I won’t push further implementation changes until that direction is confirmed. Thanks for calling out these risks.

[DeusData]

Thanks, and sorry for the slow first response. Queued for review.

Mechanically clean: MERGEABLE with 28 green checks across +139/-29 in 13 files.

Being straight with you about the review question: adding a 44th client surface is a scope decision rather than a correctness one. The implementation being clean does not by itself settle whether the project wants another integration target to maintain, and that call is the maintainers rather than mine to make in triage. Mentioning it now rather than after a long silence.

[DavidHLP]

@DeusData
Thanks for the update and for explaining the situation. I understand that this is a decision for the maintainers, and I’m happy to wait for their review. Thanks again for taking the time to look at the PR.