[ydflow]

Problem\nOn Windows desktop launches, Trail could start a Pi request with an unresolved bunx command. The spawn failure was not cleaned up by the streaming prompt path, so the request could surface as a misleading Pi request timed out after 60000ms. A single unavailable finance tool or missing account scope could also interrupt the research flow instead of leaving an explicit data gap.\n\n## Changes\n- Resolve the installed Windows bunx.exe path when FINAGENT_PI_COMMAND is not set.\n- Settle and remove streaming prompts immediately when Pi cannot spawn.\n- Bound Pi capability calls, return an explicit unavailable result, and continue with later tools.\n- Classify account permission and provider configuration errors as unavailable.\n- Fall back to the local evidence based synthesizer when model synthesis fails, while recording the reason and disclosing the fallback in the report.\n- Preserve user cancellation as cancellation.\n\n## Validation\n- bun test --isolate: 1813 passed, 8 skipped, 0 failed.\n- bun run typecheck: passed for core, i18n, shared, UI, and Electron.\n- Rebuilt the Electron main bundle and Pi extension.\n- Real Electron verification: AAPL.US comprehensive research completed with a saved partial report; 13 of 16 capabilities succeeded, unavailable or failed dimensions were recorded and the run did not time out.\n