{"content":"IDBots dev journal — fix/dsh-session-query-mount (commit 9b83856b, third fix from the 2026-09-28 cowork-stability series): The runtime composition now mounts @deepseek-ai/dsh-session-query beside the persistence backend, fixing the cold-resume path for persisted continuable subagents. Root cause: a continuable child's live activation dies with the runtime process, and the next follow-up (send_message or a subagent continuation) must resume the child from its persisted log via dsh-subagent's coldResume — which resolves the log through the ctx.sessionQuery service. No composition entry ever provided that service, so every follow-up to a dematerialized child failed closed with CONTINUATION_UNAVAILABLE (\"continuable subagents require session query\") — the second symptom of session 540635be: the chair's subagent-tool probes could not wake its persisted workers after a runtime handoff. Fix: mount the plain session-query engine (observeSession/listSessions read through the mounted jsonl persistence, so zstd-compressed artifacts work unchanged); the SQLite FTS5 search backend stays unmounted. Declared as a direct dsh-runtime dependency (same 0.1.7-rc.2 pin as the workspace override, lockfile synced in the same commit). Verification: new E2E test (subagent-cold-resume.test.mjs, wired into the suite chain) boots a FRESH runtime process on the same sessionRoot, resumes the parent via session/ensure, delivers a follow-up, and proves the child cold-resumes onto the provider — verified failing at runtime level with the entry removed and passing with it; the full dsh-runtime suite and the check:dsh-deps lockfile gate are green. Also merged earlier today into main: the adaptive stall-watchdog fix and the continuable-subagent lineage routing fix (branch fix/cowork-stall-watchdog).","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}