What
Only 1 test file exists (298 lines) for a ~1700 line daemon. Untested packages:
- socket.go (Unix socket listener and protocol)
- handlers.go (message dispatch)
- mcp_lifecycle.go (MCP server spawn/discover/invoke/kill)
- audit.go (hardware audit loop)
- wide_client.go (HTTP client to inference engine)
- config.go (configuration parsing)
Why
The daemon is the core runtime component. Low coverage means high risk of regressions in state management, message routing, and MCP lifecycle.
How
- Add unit tests for each untested file
- Add an integration test that: starts the daemon, connects via Unix socket, sends messages, and verifies responses
What
Only 1 test file exists (298 lines) for a ~1700 line daemon. Untested packages:
Why
The daemon is the core runtime component. Low coverage means high risk of regressions in state management, message routing, and MCP lifecycle.
How