refactor(mcp): type cost and daemon config services

[Shooksie]

Summary

• route cost decisions and budget reads/writes through typed in-process application services
• share one daemon-configuration service between CLI, daemon config MCP, and budget mutation
• accept structured notification configuration while retaining mutually exclusive JSON/file compatibility inputs
• document the management-only ownership boundary for global fleet state

Validation

• cargo fmt --all
• git diff --check
• cargo check -p orchestrator-cli --tests --locked
• cargo clippy --workspace --all-targets --locked -- -D warnings
• cargo animus-lint
• cargo test -p orchestrator-cli --locked -- --test-threads=1 (1,430 unit tests plus all integration suites)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
animus-docs	Ready	Preview	Jul 29, 2026 10:03pm

[animus-launchapp-gitprovider]

VERDICT: CHANGES REQUESTED

1. crates/orchestrator-cli/src/services/operations/ops_mcp/daemon_inproc.rs:notification_config_from_input — std::fs::read_to_string(path) now resolves notification_config_file against the MCP server process working directory. The previous subprocess path ran the daemon-config command with the selected project_root, so a documented project-relative input such as .animus/notification-config.json resolved inside that project; the in-process migration silently changes that behavior whenever the server cwd differs from project_root. REQUIRED CHANGE: pass the resolved project root into notification_config_from_input, and for a relative notification_config_file, join it to that root before reading (preserve absolute paths unchanged); resolve the root once in daemon_config_set_inproc and use the same resolved value for both file loading and daemon_config_application. Verification: add an MCP in-process test that creates <temp project>/.animus/notification-config.json, keeps the test process cwd elsewhere, calls daemon_config_set_inproc with notification_config_file: Some(".animus/notification-config.json"), and asserts the call succeeds and /result/notification_config equals the file content; then run cargo test -p orchestrator-cli daemon_config --locked -- --test-threads=1 with an expected pass.

The typed cost/budget service extraction, management-only authorization boundary, mutual-exclusion validation, and documentation updates are otherwise well-scoped and thoughtfully tested.