colmugx/acp/method does not have a README file

    AcpV1Method

    pub(all) struct AcpV1Method {
    method_name : String
    direction : AcpV1MethodDirection
    kind : AcpV1MethodKind
    } derive(Eq,
    Debug
    )

    One entry in the stable ACP v1 method manifest.

    method_name is the exact JSON-RPC wire name. The direction and kind are protocol facts, not runtime capability decisions; capability gates are applied by the endpoint layer after method lookup.

    AcpV1MethodDirection

    pub(all) enum AcpV1MethodDirection {
    ClientToAgent
    AgentToClient
    Bidirectional
    } derive(Eq,
    Debug
    )

    The endpoint direction of a stable ACP v1 JSON-RPC method.

    AcpV1MethodKind

    pub(all) enum AcpV1MethodKind {
    Request
    Notification
    } derive(Eq,
    Debug
    )

    Whether a stable ACP v1 method expects a response.

    acp_v1_method_manifest

    fn acp_v1_method_manifest() -> Array[AcpV1Method]

    Return a fresh, exact manifest for the stable ACP v1 method surface.

    A fresh array on every call keeps the public value free of shared mutable state. This list follows the fixed v1 table in the implementation plan; v2 and unstable overlays are deliberately absent.

    acp_v1_unstable_method_manifest

    fn acp_v1_unstable_method_manifest() -> Array[AcpV1Method]

    Return a fresh manifest for the v1 unstable-overlay method surface this facade implements. Upstream unstable (RFD session-fork, Draft).

    This is a deliberate subset of the pinned v1 unstable overlay (spec/schema/v1/meta.unstable.json, vendored): only session/fork is implemented. Unstable overlay methods deliberately stay out of the stable manifest above and out of its exact-set drift gate against the pinned stable meta.json/schema.json bytes.

    Source Files