Module app_server 

Provider-neutral App Server process and JSONL/JSON-RPC transport.

This module deliberately stops at lifecycle and handshake. Thread, turn, rendering, and interactive-request semantics live in the protocol adapter added by later rollout slices. No provider selects this controller yet.

Structs

AppServerLimits

Conservative resource limits at the untrusted child-process boundary.

AppServerProcess

AppServerTransport

ClientInfo 🔒

InitializeCapabilities 🔒

InitializeParams 🔒

PendingGuard 🔒

ServerResponseError

SharedState 🔒

StderrTail 🔒

WriteOutcomeTracker

Tracks, for a single tracked outbound write, whether retrying after a non-success outcome risks sending the same frame twice. A plain success/failure Result isn’t enough for this: once a frame is handed to run_writer it will be delivered independent of anything that happens afterward to the caller’s future, including that future being dropped/cancelled before it ever observes an outcome — a case a Result alone can’t represent, but which a caller’s own Drop glue can still consult here (ReAgent P1, PR #3212 6th review).

Enums

AppServerError

AppServerExit

AppServerIncoming

Outbound 🔒

RpcId

WireMessage 🔒

Constants

INITIALIZED 🔒

INITIALIZE_FAILED 🔒

INITIALIZING 🔒

Functions

classify_frame 🔒

fail_transport 🔒

parse_remote_error 🔒

read_frame 🔒

run_reader 🔒

run_writer 🔒

validate_jsonrpc_marker 🔒

Type Aliases

PendingSender 🔒