wire/adapters/mod.rs
1//! Adapter registries — pluggable per-category contracts so a new
2//! integration point (a host, an IdP, a plugin) is a one-file change
3//! instead of a five-file edit.
4//!
5//! Paul's direction in #92: *"It should be easy for an agent to write
6//! an adapter and wire it up to wireup. Minimal boilerplate, a clear
7//! contract, a template, and tests — author one, register it, done."*
8//!
9//! ## Categories
10//!
11//! - [`harness`] — Host adapters (Claude Code, Cursor, Claude Desktop,
12//! VS Code Insiders, GitHub Copilot CLI, Pi, OpenCode, …). Each
13//! declares its probable MCP-config file paths + the JSON shape its
14//! host expects. Consumed by `cli::cmd_setup`.
15//!
16//! Future categories (per #92, deferred to dedicated PRs since they
17//! need cross-fleet coordination):
18//! - SSO / IdP provider adapters (Google Workspace, Okta, Azure AD, …)
19//! - Plugin / extension adapters (wire-plugin marketplace, A2A bridge,
20//! `did:wire` method)
21
22pub mod harness;