feat(dev): rich mock streaming scenarios (scripted thinking + tool lifecycles)

Extracted from #39. Rewrite setupMockStreaming from a flat random-token stream into a phased state machine: thinking deltas, intro text, a successful tool call (pending, in_progress, completed, with realistic input/output/preview), middle text, a scripted failing tool call, outro, complete. Exercises the full streaming pipeline including cancellation without a goose binary.

Cleanup while porting: scenario copy in #39 embeds contributor-machine Windows paths; replace with neutral examples.

**Size**: S-M | **Depends on**: #61, #65, #66 (message contract + renderers); pairs with mock mode #58 | **Tier**: 3

Look for the setupMockStreaming function in the codebase, likely in a mock or dev utilities module. Understand the current flat random-token stream implementation. Review the dependencies (#61, #65, #66) to understand the message contract and renderers. Design a state machine that produces the described phased streaming output, ensuring it exercises the full pipeline including cancellation. Replace any hardcoded Windows paths with neutral examples.

由索引模型根據 Issue 內容生成。