fix: make child tool, workspace and provider execution reliable

[tt-a1i]

Problem and requested behavior

Ordinary and Workflow children should be able to use parent-authorized tools, including shell/network tools, and operate in an explicitly selected working directory. A recent eight-way PR audit failed across three attempts: Cursor chat-only rejected tool calls; Codex children were stopped by OpenPI's extra 45-second progress watchdog; Seal returned account rate limits while the task/tool/cwd mismatch persisted. Private sessions and credentials are not published.

The user authorizes investigation and implementation in one PR, for review before merge.

Scope / acceptance

• Built-in role defaults support parent-authorized child-safe tools. Custom allowlists and parent-only exclusions remain enforceable; Plan Mode cannot obtain write/shell authority through a child.
• Ordinary and Workflow paths have tested explicit cross-directory operation, with target-project trust and correct worktree/replay/operator/cleanup identity.
• Cursor maps supported advertised tools to Pi's native tool lifecycle and replays results; it must not execute Cursor-native tools outside Pi. Local protocol fixtures plus bounded real acceptance distinguish proven support from uncertainty.
• Remove false 45-second child failures without weakening Pi transport error handling or bounded caller cancellation/disposal.
• Inspect related observed hot paths; add focused regressions and executable evidence rather than unrelated refactoring.
• bun run check, bun run test, independent reviews and required CI pass.
• Submit one cohesive PR; do not merge or publish a release.

Related work

• fix: Workflow dashboard blocks input by reloading history on animation ticks #420 / fix(workflows): keep history loading off dashboard animation ticks #422 fixed repeated dashboard history hydration; configured local runtime was still at c8f2c13 during diagnosis.
• Windows: bash tool in OpenPI derived sessions (subagent / Web) incorrectly invokes WSL stub; shellPath setting is ignored #419 / fix(child-sessions): preserve configured shell in headless tools #423 track configured shell propagation; inspect overlap instead of duplicating that independent work.
• perf(tui): child transcript 在 viewport 裁剪前扫描完整历史并可能二次配对 #185 / perf(tui): render child transcript by viewport window #327 track viewport transcript performance; inspect relevance before adding changes.

Repository investigation and design records will be linked from the delivery PR and this Issue.

[seekskyworld]

I am taking a focused reliability slice from this issue: align the Workflow child model-progress watchdog with Pi's effective SettingsManager.getHttpIdleTimeoutMs() value. The current code reads only raw optional settings, so an unset Pi setting (whose effective default is 300 seconds) silently falls back to OpenPI's extra 45-second timeout and can abort a healthy slow provider turn.

I will implement this as #425: preserve the bounded 45-second floor (including Pi's explicit transport-timeout 0), keep test overrides and abort/disposal unchanged, add deterministic regression tests, and update the timeout contract. This does not claim Cursor tool support or the broader workspace/allowlist work in #424.

[tt-a1i]

Implemented in #426, left open for maintainer review.

Canonical investigation: Workflow child failures and capability inheritance.

Local checks and the full test set passed (Node file concurrency 2: 1435 passed, one platform skip; Vitest 30/30). Two independent reviews found no actionable defects. Live Cursor Grok completed Pi tool/result handoff, Workflow cross-directory read plus HTTPS via Bash, and eight concurrent production-runner children (8/8 success).

The record distinguishes repaired adapter/runtime mechanisms from custom role restrictions and provider account limits. Existing user role files and the active installed runtime were preserved. Final CI on c3809e1 passed on Node 22.19.0, Node 24, and Windows: CI receipt. The PR remains open; no merge performed.