feat(core): Add PromptSuspend for prompt pause/resume at tool call boundaries

[Copilot]

• Add toolCallId?: string to Context type in packages/core/src/types.ts
• Inject toolCallId from toolCall.id into context before tool.run() in packages/core/src/prompt.ts
• Merge the duplicated anySuspended loop into the single tool-result loop below it
• Run tests — only 3 pre-existing failures, none introduced

[ClickerMonkey]

Lets make sure the non suspended tool calls that came back with valid responses still get their tool call results added to the request messages. Anything that came in before suspend breaks the loop and returns needs to be on the request messages - we don't want to drop anything from the response just because of tool suspension.

[ClickerMonkey]

Let's just emit request, doing messages is duplicitous

[Copilot]

Done in fb238b8 — the suspend event now only carries request. Use event.request.messages to access the saved state.

[Copilot]

Lets make sure the non suspended tool calls that came back with valid responses still get their tool call results added to the request messages. Anything that came in before suspend breaks the loop an...

Fixed in fb238b8. When any tool suspends, the loop now iterates all executors before breaking: completed/errored tools have their results added to request.messages as usual; only suspended tools are skipped (their toolCallId result is what the caller provides on resume). A new test (should add completed tool results to request.messages before suspending) verifies this with a sequential two-tool call where one completes and one suspends.