fix: Report initial status and terminal status message (if saved)

[jirispilka]

Summary

Make actor-run progress and abort notifications reliable end-to-end.

• Abort actually aborts. callActorGetDataset awaits the abort API call before returning on notifications/cancelled, so the run is aborted rather than fire-and-forget. The polling tracker is also stopped on the cancel path.
• First progress arrives immediately. Initial actor-run status is reported before waitForFinish, so clients don't wait for the polling interval to see the first update.
• Last progress is guaranteed and accurate. After waitForFinish resolves, the tracker is stopped and the run is re-fetched once (in parallel with dataset/build) to capture the actor's final statusMessage — the platform may write it just after the status flip. A terminal notification is then emitted explicitly so the client always sees SUCCEEDED/FAILED/etc., even if polling never ticked at terminal.
• Status format is terminal-aware. formatRunStatusMessage always leads with the run status (apify/foo: SUCCEEDED — Done). At terminal status, the actor's statusMessage is only appended when explicitly marked terminal (isStatusMessageTerminal === true); otherwise it's omitted to avoid showing stale in-progress text.
• No duplicate emissions. Three sources of duplicates closed:
  • Polling dedup state is seeded with the initial run, so the first poll tick doesn't re-emit the same state already sent at start.
  • A stopped flag in ProgressTracker prevents in-flight polling ticks from emitting after stop() is called.
  • updateProgress dedups consecutive identical messages, so a polling tick that catches the terminal state doesn't double up with the explicit final emit.
• PROGRESS_NOTIFICATION_INTERVAL_MS lowered 5s → 2s for snappier updates.

All tests are passing now

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Improves reliability of Actor-run progress and cancellation behavior so clients consistently receive early and terminal status updates and cancellations actually abort the run before returning.

Changes:

• Add terminal-aware Actor run status formatting and strengthen ProgressTracker to avoid duplicate emissions (seeded initial state, stopped guard, consecutive-message dedup).
• Update callActorGetDataset to await abort requests on cancellation, emit an initial progress update immediately, and emit a final terminal update from a refreshed run snapshot.
• Reduce progress polling interval from 5s to 2s and expand unit test coverage for the new behaviors.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/tools/core/actor_execution.ts	Await abort on cancellation; emit initial + final progress messages; refresh run snapshot after completion.
src/utils/progress.ts	Introduce formatRunStatusMessage; add dedup/stopped protections; seed polling dedup state.
src/const.ts	Lower progress polling interval to 2 seconds.
tests/unit/tools.actor_execution.test.ts	Add coverage for cancellation awaiting abort and for initial/final progress emission behavior.
tests/unit/utils.progress.test.ts	Add coverage for dedup, seeded initial state, and stop-while-in-flight behavior; add formatter tests.
tests/integration/suite.ts	Update commentary to reference the polling interval constant.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.