daemon.json → socket-only migration (finish what #1803/#1804 started)

[rgbkrk]

Finish migrating off the daemon.json sidecar file. #1803 added the GetDaemonInfo socket request; #1804 switched user-facing Tauri and MCP callers to it.

Status

Phase 1 — Migrate readers: Done.
All callers now use socket-first query_daemon_info(). No callers of the old get_running_daemon_info() remain.

Remaining work

Phase 2 — Stop writing the file and remove compatibility shims.

1. Delete the write_info() call in crates/runtimed/src/daemon.rs (~line 758) and the DaemonLock::write_info / Drop cleanup in crates/runtimed/src/singleton.rs.
2. Remove the daemon.json fallback in query_daemon_info() (crates/runtimed-client/src/singleton.rs).
3. Remove get_blob_paths_sync/async() fallback reads from crates/runtimed-client/src/daemon_paths.rs.
4. Delete daemon_info_path(), read_daemon_info(), get_running_daemon_info(), DaemonInfo (file-shaped), and cleanup_stale_daemon_info + its callers.
5. Remove the one-release fallback in Tauri get_blob_port added in feat(runtimed-client): query_daemon_info helper prefers socket #1804.
6. Clean up remaining daemon.json references in CLI tooling (crates/runt/src/main.rs).

Keep daemon.lock + flock — still the singleton guard.

Related

• feat(protocol): add GetDaemonInfo to replace daemon.json sidecar #1803 (merged) — GetDaemonInfo protocol
• feat(runtimed-client): query_daemon_info helper prefers socket #1804 (merged) — first round of readers migrated