refactor(core): thin the CLI — move parsing/resolution into ant-core, route all daemon calls through the client

[Nic-dorman]

Summary

Five mechanical fixes from the CLI-architecture audit (the "CLI should be a thin adapter" contract in CLAUDE.md), one commit per finding:

• PortRange parsing (audit docs: comprehensive API documentation for data, wallet, devnet, and library usage #7): impl FromStr for PortRange in ant-core next to the type; CLI uses .parse() instead of its own parse_port_range.
• Env vars (audit fix: resolve HRTB lifetime issue in stream closures #8): AddNodeOpts::parse_env_vars owns KEY=VALUE parsing; CLI helper removed.
• Bootstrap resolution (audit fix: migrate NAT-friendly quote selection and process exit fix #4): explicit > devnet manifest > bootstrap_peers.toml priority (with manifest-peer filtering) moved to ant_core::config::resolve_bootstrap_peers; no-source case is now typed Error::NoBootstrapPeers.
• Daemon calls (audit Migrate from saorsa-node to ant-node 0.6 #3): node add/node reset no longer hand-roll reqwest against the daemon — new daemon::client::add_node / client::reset matching every other endpoint.
• Registry race (audit Unify all clients into ant-client #2): node start/stop --service-name resolved the node ID by reading node_registry.json directly while the daemon (the registry owner) was running. New client::resolve_node_id_by_name goes through GET /nodes/status; the CLI no longer touches the registry file at all.
• Progress reporters (audit chore: bump version to 0.1.1 #9): the two near-identical ProgressReporter impls (CliProgress in add.rs, CliUpdateProgress in update.rs) collapsed into one progress::CliProgress on stderr. Side fix: ant node add --json no longer interleaves download progress with the JSON result (NoopProgress in JSON mode, matching ant update).

Behavior notes

• Parse/lookup error texts are preserved (No node found with service name '…', Expected KEY=VALUE, port-range messages near-identical).
• Daemon-error surfacing for add/reset changes from Daemon returned error: {body} to HTTP request error: {body} (the shared daemon-client convention).
• node add download progress moves stdout → stderr, consistent with the rest of the progress UI.

Testing

• cargo test --workspace: 443 passed (new unit tests for PortRange::from_str, parse_env_vars, resolve_bootstrap_peers priority).
• clippy -D warnings clean, fmt clean.
• Live smoke against a running daemon (empty registry): name-miss and name-hit resolution for start/stop, reset --force --json no-op, add --json full round-trip with a stub binary (then dismissed), client-side parse failures for inverted port range and malformed --env — all outputs byte-compatible with the old CLI.

🤖 Generated with Claude Code

[Nic-dorman]

Superseded by #157 — the head branch was renamed and GitHub detached this PR's head ref, closing it. All commits and discussion context live on in #157.