2 Commits

Include renames

Author	SHA1	Message	Date
naps62-yoloandClaude Opus 4.8	3b60f67332	fix(maestro): give CLI reqwest clients connect + request timeouts (NAP-262) ... The `RegistryClient` and the bare `reqwest::Client::new()` calls in `policy.rs` built clients with no timeouts, so `maestro list` / `maestro policy {show,reload}` would hang forever against a registry/daemon that is TCP-alive but not making forward progress (SIGSTOP, swap thrash, deadlock behind slow disk). Centralize construction in `http::build_client()`, which applies a 5s connect timeout and a 30s request timeout, and route every call site through it. Covered by a test that points the client at a peer which accepts the connection but never responds and asserts the request times out instead of hanging. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-31 19:22:58 +00:00
naps62-yoloandClaude Opus 4.7	f69c7a9eee	feat(maestro): hot-reload [daemon.policy] via SIGHUP + maestro policy CLI (NAP-237) ... `PairAttachVerifier` now stores `allow_inbound` behind `Arc<RwLock<_>>` so clones share the same set. Two triggers re-read the unified config file and swap it atomically: - SIGHUP — `systemctl --user reload maestrod`, or any `kill -HUP`. The installer's user unit now sets `ExecReload=/bin/kill -HUP $MAINPID`. - `POST /api/policy/reload` — used by `maestro policy reload`. The CLI reads `[daemon].bind_addr` from the unified config (default 7070) and POSTs to `http://127.0.0.1:<port>`. No PID lookup required. Also adds `maestro policy show [--json]` and `GET /api/policy` for "did my edit get picked up?" debugging. A broken mid-edit config logs an error and leaves the previously-effective list in place rather than locking everyone out. In-flight attaches keep their existing connection — revocation requires killing the session, as spec'd. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 09:53:19 +00:00