chore(daemon): read status through transport layer

[jackwener]

Summary

• route passive daemon/profile/doctor status reads through daemon-transport instead of daemon-client
• keep daemon-client focused on command dispatch while preserving its existing re-exports
• update daemon and doctor tests to mock the lower-level transport boundary

Verification

• npm run typecheck
• npm test -- --run src/commands/daemon.test.ts src/doctor.test.ts
• npm run build

Note: I also tried npm test -- --run src/commands/daemon.test.ts src/doctor.test.ts src/cli.test.ts. The cli tests showed pre-existing environment-sensitive failures because this machine has a default Browser Bridge profile configured, so BrowserBridge.connect received a contextId the assertions do not allow. I did not change those assertions in this cleanup PR.