The peer follow stream had no byte cap and kept a whole unterminated
frame in memory, and the MCP surface carried its own peer status table
that already disagreed with REST for peer 400.
- mcp::peers::fetch now returns proxy::PreparedResponse, so the status
comes from proxy::classify_status and the body from
proxy::prepare_response (peer byte cap, deadline, shutdown), the same
two steps REST uses. status_error, body_bytes and the local 2xx check
are gone.
- tail_journal consumes that prepared stream; a Frames cursor keeps a
partial frame from being rescanned from byte 0 on every chunk, the
entry cap truncates the result, and the end of the stream maps to the
note (entry cap, shutdown, byte cap, deadline or close).
- Prompts resolve the peer argument against the registry (unknown or
disabled peer is refused); list_peers returns the error registry()
produced; one wording for an unknown peer name.
- Tests: byte cap on an unterminated frame, entry cap, buffered body,
follow 404/500, deadline with an open stream, shutdown, frame cursor,
REST/MCP parity for peer 400/404/401/5xx, and a full golden snapshot of
the peers-off tool table. Peer scripts use the stripped path form C2
forwards.
Server instructions and the eight tool descriptions mention peers and the
untrusted-data rule only while a registry is configured. peers://status
returns the list_peers JSON and is advertised only then. diagnose_unit and
container_health_report take an optional validated peer argument.
The two status tools and the optional peer argument exist only when a
registry is configured. rmcp's disable_route hides the tools; the eight
shared schemas lose the optional peer property, and the two list tools also
lose the derived $schema key, so the peers-off list and schemas match a
build without the feature byte for byte. Both snapshot variants and the
wire-level tool list are asserted.
Peers resolve through PeerRegistry::get, the same entry point REST uses,
so the hop marker, allowlist and error mapping stay in one place. Log
tools keep the local {entries, truncated, note} shape; tail_journal
consumes the peer SSE stream. Tests cover every tool, path encoding,
error mapping and the integration path through the assembled router.