Module session 

Session-attach data-plane wire contract.

subc has two distinct channel-0 handshakes. Module registration is the module-to-subc HELLO/HELLO_ACK handshake that registers the manifest and liveness. Session attach is the client-to-subc-to-module request/response handshake that binds one (project_root, harness, session) triple to a route channel.

Session attach is vetoed by the module: subc relays an AttachRelay to the singleton module, commits the route only after an accepted AttachRelayResponse, and returns module rejection as an ErrorBody ERROR frame. The triple binds once at attach time; subsequent data-plane frames carry only the envelope channel and opaque body bytes.

Config is forwarded as an ordered, provenance-tagged tier list. subc treats every config document as opaque text and preserves tier, source, and doc exactly from AttachRequest to AttachRelay; it never parses, merges, partitions, or relabels config in transit.

Structs

AttachAck

subc’s channel-0 response body for an accepted session attach.

AttachRelay

subc-to-module channel-0 control RPC body asking the singleton module to bind a route channel.

AttachRelayResponse

Module response body for an accepted attach relay.

AttachRequest

Client-originated channel-0 control RPC body for binding a harness session to a module route.

ConfigTier

One provenance-tagged config tier supplied during session attach.

DetachRelay

subc-to-module channel-0 control RPC body telling the module a route channel is gone after client GOODBYE or client drop.