Log entry for the round and the hook-check port noted in the dated
Handoff, so the orchestrator knows why four files outside the F list
changed and what is left for the fold.
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.
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 test nodes declare peers through the first-class module options, so
LoadCredential and RefreshOnReload come from the module. Every node binds
:: because the test network resolves node names to IPv6 first. poll()
raises with the last observed status JSON.
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.
Proxied journal/unit values now use the local unit-name helper instead of a
second, stricter check, so escaped units pass through as text, %5C or %5c.
The peer status table is one function shared with the transport, and the
segment/encoding cases left untested get allowlist and rejection cases.