fix(cli): refresh runtime detection accurately

[nguyenha935]

Updates CLI runtime detection across the status API, batch cache, shared runtime service, and dashboard hook. The previous cached detection could report stale or incomplete tool state; this change refreshes and propagates runtime status consistently and adds unit/integration coverage for the affected paths. Validation note: the branch contains targeted tests, but the full omniroute-patch test gate was not rerun during this publication step.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[diegosouzapw]

Thanks for this — verified locally: gh pr diff shows this is byte-identical to #7505 except for the changelog fragment filename, and this PR already targets the correct base (release/v3.8.49), so we'll merge this one and close #7505 as a duplicate/subsumed by this PR (crediting you the same either way).

Ran the full test surface in an isolated probe worktree against the release tip: tests/unit/cli-runtime-detection.test.ts + tests/unit/batch-status-cache.test.ts (28/28), tests/integration/all-statuses-route.test.ts (9/9, including your new refresh=true case), and tests/unit/ui/useToolBatchStatuses.test.tsx via vitest (7/7) — all green, no lint issues on the touched files. The checkRunnable() version field and the .continue/config.yaml path already existed elsewhere in the codebase (tool-detector.ts), which corroborates the Continue-detection fix. Looks solid — merging as-is.