Summary

• Follow-up to fix(mothership): report a Copilot workflow tool whose paused run settles after a resume or cancel #9290 from the v0.9.31 release review.
• finalizePausedCancellationForTerminalRun runs when a cancel of a paused run loses the race to another writer that already made the run terminal. That writer may never report the Copilot tool bound to the execution: the stale-execution sweep, or a resume worker killed after its log write. The tool then waits out the Copilot client wait.
• It now reports through reportCopilotToolForSettledPause, the same as completePausedCancellation. The reporter is idempotent: it does nothing unless the log is terminal, a CAS lets only a running row claimed by this execution through, and it never throws. A report the winner already made is therefore a no-op.

Type of Change

• Bug fix

Testing

• workflow-client-settlement.integration.ts: 13/13. New: a paused execution whose cancel lost the race to a run that failed unreported is delivered to the waiting Copilot turn. It goes red without the call.
• Unit: human-in-the-loop-manager plus lib/execution (1306 pass). check:test-patterns and biome pass. Full type-check and check:audits run in CI.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)