build.rs builds the string (git, or SLINUXM_* env for builds without .git)
and the lib exposes it as VERSION. --version, /healthz, /api/v1/ping, MCP
server info and OTel service.version use it; OpenAPI info.version stays on
the semver so docs/openapi.json does not change per commit. The flake passes
the commit date and short rev to the package.
Require the child's own listening line for the probed port before it is
signalled; a 200 from /healthz proves liveness only, since another slinuxm
answers it too. Retry a lost bind race instead of signalling a dead child,
and add a squatter that answers 200.
Peer::spawn and Consolidator::start repeated the bind, pool, migrate,
mint and serve_listener sequence; serve(config, tls, prepare) does it
once and returns the handle, the token and whatever the caller prepared,
so the registry is installed before the router is built. The local
TempDir copy is gone in favour of peers::testing::TempDir, which already
does unique scratch dirs and mode-controlled writes.
The redirect test waited on a fixed sleep and a status that starts false;
it now waits for the health loop's own http_302 verdict before asserting
the Location target saw no connection. The peer cap asserts the message
rather than the bare number, and a chunked response (no Content-Length to
precheck) proves the byte count refuses an oversize body end to end.
The hand-written listener now distinguishes a complete reply, SSE headers
followed by a held socket and headers followed by one body byte every
300 ms. shutdown_ends_a_proxied_follow uses the held socket instead of a
real peer, so only shutdown can end the stream, and a new trickle case
proves the request deadline ends a slow-loris peer (503 timeout) rather
than the peer's goodwill. The silent-peer bound drops from 10 s to 4 s so
a missed 1 s deadline cannot hide inside it.
A peer whose name resolves to both families but which listens on only one
of them was reported unreachable, which the documented 0.0.0.0 binding
produces on a dual-stack LAN and in the NixOS test network.
resolve_target now returns the whole address set (still refusing the name
if any address is denied), the HTTP client pins it with
resolve_to_addrs so the connector falls through to the next address, and
tcp_check tries each address in order with a per-attempt share of the
remaining deadline. ClientKey keys on the set.
Regression cover: a client test that resolves localhost against a
single-family listener, a tests/peers.rs case declaring the peer as
http://localhost:<port>, and the VM test's TLS peer gamma now binds
0.0.0.0 (IPv4 only) while alpha and beta stay dual stack. Docs and the
contracts section 10 address note describe the new behaviour.
The proxy validated the route without its API prefix and handed the
transport "/systemd/units", which a peer answered with 404. Validation
still works on the bare route; the transport now gets
"/api/v1/systemd/units". Un-ignoring the two acceptance tests
(a_plain_peer_serves_its_own_data_through_the_proxy and
shutdown_ends_a_proxied_follow) is the check for that fix; the unit
tests in api/, mcp/ and the registry script their fakes on the peer's
real paths again.
README peers section, docs/consolidator.md (threat model, tokens, firewall,
worked agenix example, reload/restart), the MCP tool count in both tables,
and config.example.toml commentary.
Real registry and transport against in-process peers and hand-written
listeners: plain, TLS with an rcgen CA, a wrong CA, redirects, oversize
bodies, a silent peer, the 64-peer cap and shutdown mid-follow. Two proxy
cases are ignored: the proxied path is missing its /api/v1 prefix.
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.
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>