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.
Documentation index
Root files: README.md (install and usage), ARCHITECTURE.md (design, decisions, verification), TODO.md (work tracking), AGENTS.md (guidance for AI coding agents). Plans for the next big phase go in plan/.
Reference
| Doc | Contents |
|---|---|
api.md |
Full REST route table, MCP tools/prompts/resources, client setup, Origin and Host checks |
tls.md |
Native TLS: configuration, self-signed example, SIGHUP rotation, ACME and sops paths |
Workstream records (archived)
Archived. The files in
workstreams/are historical records of how the project was built (scope, owned files, design notes, logs). They are not maintained. Current design is inARCHITECTURE.mdand open work is inTODO.md.
| Card | Phase | Depends on |
|---|---|---|
| P0 Foundation | 0 | none |
| WS-A systemd | 1 | P0 |
| WS-B journal | 1 | P0 |
| WS-C docker | 1 | P0 |
| WS-D auth + DB | 1 | P0 |
| WS-E REST | 2 | A, B, C, D |
| WS-F MCP | 2 | A, B, C, D |
| WS-G OTel | 2 | A, B, C |
| P3 Integration | 3 | E, F, G |
| WS-I TLS | 4 | P3 |
| WS-H NixOS | 4 | P3, WS-I (gate result pending) |
Dependency order: P0, then A to D in parallel, then E to G in parallel, then P3, then WS-I, then WS-H.