11 Commits
Author SHA1 Message Date
ari 3f017725f8 H: correct the peer gauge gating in the docs Name otel.enabled plus otel.export_unit_metrics, and state that disabled peers have no series 2026-10-20 16:14:19 -04:00
ari 97c81f899c H: deny IPv6 link-local and metadata addresses by default Add fe80::/10, ::/128 and fd00:ec2::254/128 to the default deny_cidrs and sync config.example.toml, README and docs/consolidator.md 2026-10-20 16:13:25 -04:00
ari 39c1c91695 H: merge token loaders and peer helpers One loader in secrets.rs (header validity, canonicalised credentials dir) is used by the client; the deny-CIDR parser, loopback test and plain-http warning live once in config.rs 2026-10-20 16:10:24 -04:00
ari f82b78bad5 F: say what the proxy forwards instead of 'it is stripped'
The caller's /api/v1 prefix is dropped during validation and the peer
path is built with it, so the old sentence described half of it.
2026-10-20 15:04:09 -04:00
ari 04992e202d F: correct the peers docs against the finished behaviour
docs/consolidator.md: the Testing section described the pre-feature test
(no tests/peers.rs, the old tests.<system>.peers attribute, a note about
assertions failing by design) and is rewritten for both layers, the
module's eval check included. A shutdown subsection backs the README's
promise, the agenix examples say why a consolidator would bind 0.0.0.0
(remote callers; peers need no inbound port), and the VM test asserts
the chained-request status is exactly 400 as documented. README: token
rotation on NixOS also needs a reload for the LoadCredential copy.
2026-10-20 15:04:09 -04:00
ari dde6a12ce4 F: try every resolved peer address instead of the first
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.
2026-10-20 15:04:09 -04:00
ari 4d83c2eff5 F: F4 peers docs, agenix example and tool-count note
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.
2026-10-20 15:04:09 -04:00
ari 5edbd388d1 T: docs: interactive dev-test lives inside devenv shell; module-mode notes
AGENTS.md said the same command works in an interactive shell, which only
holds inside devenv shell or direnv (the script is on PATH there).
docs/consolidator.md now says the filter cache sits at the repo root and that
a failing check raises a catchable error instead of closing the session.
2026-10-19 22:37:08 -04:00
ari b476ac2b0c T: rename runner to dev-test 2026-10-19 22:37:08 -04:00
ari 6dade6239d T: review round 1 fix runner argv, filter cache, and the test builtin 2026-10-19 22:37:08 -04:00
ari 40cf1073f4 T: T7 nushell test runner, devenv test script, command lists, docs testing section 2026-10-19 22:37:08 -04:00