@salesforce/sfdx-agent-harness-claude 0.81.0 → 0.83.0

package/CHANGELOG.md

@@ -3,6 +3,15 @@
 All notable changes to `@salesforce/sfdx-agent-harness-claude` are documented in this file.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [0.83.0] - 2026-09-17
+
+### Fixes
+- **agent-sdk,harness-mastra**: classify aborted turns as finishReason 'cancelled' at the pre-stream sites @W-23749670@ ([#830](https://github.com/forcedotcom/agentic-dx/pull/830))
+
+## [0.82.0] - 2026-09-16
+
+_No changes — released alongside dependent packages._
+
 ## [0.81.0] - 2026-09-16
 
 _No changes — released alongside dependent packages._

package/README.md

@@ -218,9 +218,10 @@ When `StreamOptions.abortSignal` fires during an active turn with approval gatin
 
 - All pending permission Promises reject with an `AbortError`.
 - The underlying Claude subprocess is killed (existing `AbortController` wiring).
-- The single per-turn `eventStream` ends with an `error` event (`code: 'aborted'`, `error.name === 'AbortError'`)
-  followed by a `finish` event (`finishReason: 'error'`). The `'error'` finish reason is used because the SDK's
-  `FinishReason` type has no `'aborted'` value; the preceding `error` event carries the abort identity.
+- The single per-turn `eventStream` ends with an `error` event (`code: 'cancelled'`, `error.name === 'AbortError'`)
+  followed by a `finish` event (`finishReason: 'cancelled'`). The canonical `'cancelled'` code and finish reason are
+  uniform across the Claude, Mastra, and OpenAI harnesses (W-23559264), so consumers distinguish a user cancel from a
+  genuine failure without branching on harness-specific codes — a cancelled turn never surfaces `finishReason: 'error'`.
 
 If the signal is already aborted when `stream()` is called, `stream()` throws synchronously (existing
 `AbortSignal.throwIfAborted()` behavior — unchanged).