helix4u f38f7a3870 fix(desktop): recover stale session before stop ... Desktop already recovers from a stale runtime session id when `prompt.submit` returns `session not found` after a gateway restart or sleep/wake. The stop path did not have the same recovery: `cancelRun` called `session.interrupt` once with the stale runtime id, then surfaced `Stop failed / session not found`. This makes stop/cancel mirror the prompt recovery path. If `session.interrupt` reports `session not found` and the selected stored session id is available, Desktop resumes that durable session, updates the active runtime ref with the recovered id, and retries `session.interrupt` once against the recovered runtime id. Salvaged from #43941 — rebased onto current main, dropping the unrelated `package-lock.json` (@types/node 24.13.1->24.13.2) and `nix/lib.nix` hash churn. That bump is a local npm 11 re-resolution artifact, not a CI requirement: repo CI runs node 22 (npm 10) and main is green at @types/node 24.13.1, so the lockfile and nix hash do not need to change. Co-authored-by: helix4u <4317663+helix4u@users.noreply.github.com>		2026-06-11 11:45:08 +05:30
..
bootstrap-installer	change(tooling): typecheck in CI, update ts to 6	2026-06-10 11:59:34 -04:00
desktop	fix(desktop): recover stale session before stop	2026-06-11 11:45:08 +05:30
shared	change(tooling): typecheck in CI, update ts to 6	2026-06-10 11:59:34 -04:00