lefarcen b8cfee0c60 fix(diagnostics): capture daemon/web logs in packaged bundles (#3126) ... Packaged diagnostics bundles never contained the daemon or web `latest.log` — the very logs that hold the agent/critique run flow — so support exports could not explain "sent prompt to the agent, then nothing happened" reports. Root cause: the sidecar `base` means different things per launch path. tools-dev passes the pre-namespace source root, so `resolveNamespaceRoot(base, namespace)` is correct. But the packaged orchestrator launches every child with `base = <namespaceRoot>/runtime` (apps/packaged/src/{paths,sidecars}.ts) while logs live a level up at `<namespaceRoot>/logs`. The diagnostics builders re-appended the namespace and resolved every log to `<namespaceRoot>/runtime/<namespace>/logs/...` → ENOENT. renderer.log only survived by accident: the desktop main process wrote it to the same wrong path the reader looked in. Add `resolveRuntimeNamespaceRoot(runtime, contract, runtimeMode)` to `@open-design/sidecar` which walks up out of the `runtime/` dir in packaged (runtime-mode) launches and falls back to the dev layout otherwise. Route the desktop renderer-log path and both diagnostics exporters (desktop IPC + daemon HTTP) through it so writer and reader stay in lockstep and renderer.log lands next to the desktop log dir. Tests: sidecar unit specs for both layouts; a daemon export spec that writes a real `<namespaceRoot>/logs/daemon/latest.log` and asserts the bundle captures its contents (red on main → ENOENT placeholder, green here). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-27 14:48:14 +00:00
..
index.test.ts	fix(diagnostics): capture daemon/web logs in packaged bundles (#3126)	2026-05-27 14:48:14 +00:00