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.
B1/B2 are merged, so `real_transport` builds the `ReqwestTransport` with the
configured limits and deny list instead of bailing. Binary tests now probe a
real loopback server: ok with latency, rejected credential, unreachable peer
and an unknown name, none of which may print the token.
The peer-less `--print-config` output is now compared against the committed
pre-peers text plus the default `[peers]` block, and a config with a peer
must leave everything before that block byte-identical. New binary tests
cover `--print-config`, `peer list`, `token create|list` with an unreadable
token file, and `serve` refusing to start while naming the peer.
Land the shared peer contracts: types, error mapping, transport trait,
fake transport and fixtures, registry/proxy/health skeletons, the
AppState.peers and Config.peers seams, the ping and peers route stubs,
and unit plus integration tests. No loops, no network, feature off by
default.
Probe the served cert with a non-verifying client and wait on the server log
instead of fixed sleeps, so a not-yet-processed SIGHUP no longer panics.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>