Expand description
mcpmesh-local-api: the mcpmesh-local/1 seam (mcpmesh §6.1) — protocol types (always) plus,
behind the client feature, the family NDJSON codec + a no-iroh UnixStream client.
The client feature is the D-A extraction: a non-net mcpmesh-local/1 client (kb’s
self-registration, the host shell) links this WITHOUT pulling iroh via mcpmesh-net.
Re-exports§
pub use principals::principal_set;pub use protocol::API_NAME;pub use protocol::API_VERSION;pub use protocol::AuditSummaryResult;pub use protocol::BackendKind;pub use protocol::BackendSpec;pub use protocol::BlobFetchResult;pub use protocol::BlobPublishResult;pub use protocol::BlobScopeList;pub use protocol::Hello;pub use protocol::InviteResult;pub use protocol::OrgJoinResult;pub use protocol::PairResult;pub use protocol::PeerInfo;pub use protocol::PresencePeer;pub use protocol::RecentPairing;pub use protocol::Request;pub use protocol::RosterInstallResult;pub use protocol::RosterStatus;pub use protocol::ScopeInfo;pub use protocol::ServiceInfo;pub use protocol::StatusResult;pub use protocol::method_of;
Modules§
- principals
- THE principal-set expansion (mcpmesh §5): the ONE definition of a resolved caller’s flat
authorization identity —
groups ∪ {petname} ∪ {user_id}, empty components skipped, default-deny (no identity ⇒ empty set ⇒ nothing matches). - protocol
- mcpmesh-local/1 protocol types (spec §6.1). Shared vocabulary between the daemon and its clients (porcelain, connect proxy, later the host shell). Wire framing is the family NDJSON codec — carried by the caller, not defined here (D-A).