feat(agent): sdk-core 0.3.3 com notification, title da ferramenta e README do mode (#123)

CHANGELOG.md

@@ -2,6 +2,27 @@
 
 All notable changes to this project are documented in this file.
 
+## 0.3.3
+
+Needs the box and the Copilot that send and record it (mitra-sandbox#782, mitra-copilot#552), and
+goes out before them: 0.3.0 to 0.3.2 read a `NOTIFICATION` row as the agent's text.
+
+- Background work that ended (a command, a subagent, a monitor left running past the turn) reaches
+  the session as T3 reports it: a `notification` event (`AgentNotification`: `source`, `outcome`,
+  `summary`, `detail`, with `itemId`, `sequence` and `turnId`) and a `notification` item in
+  `history`, live from the box's `notification` frame and reloaded from the Copilot's
+  `NOTIFICATION` row. Values pass as they come; `source.kind` is what T3 sends on the wire
+  (`background_command`, or `background_task` with `work: "subagent"`). `AgentTimelineItem` gains
+  the `kind: "notification"` member, with `payload` and no `text`: TypeScript code that reads
+  `text` in a catch-all branch has to handle it.
+- Tool events and `tool` history items carry `title` when the box sends it: on a subagent's call,
+  its name as T3 shows it, which the history row already had and the item left out. New optional
+  field `AgentToolEvent.title`.
+- README: a `send` without `mode` while a turn runs goes into that turn (steer); the queue is only
+  for `mode: "queue"`. Also documented: `backgroundTasks`, the running turn the box sends again
+  after the replay (mitra-sandbox#782), and `reason: "interrupted"` on the history row a Stop
+  closed (mitra-copilot#552).
+
 ## 0.3.2
 
 - `providerUsage` carries `provider` when the box sends it: the provider the reading is of, with

contracts/README.md

@@ -24,6 +24,10 @@ publishes.
 
 ## Versions
 
+- `0.3.3` is the `0.3.2` parity surface with the agent session's `notification` event and history
+  item and the tool's `title`, which the parity cases do not cover. Same parity cases; the version
+  exists so a consumer pinning the package can pin a corpus with the same number.
+
 - `0.3.2` is the `0.3.1` parity surface with `provider` on the `providerUsage` reading and a fix
   in the agent session: a message still on its way when the session closes goes to the Copilot
   over REST. Same parity cases; the version exists so a consumer pinning the package can pin a

contracts/manifest.json

@@ -1,6 +1,6 @@
 {
   "contract": "SDK-PARITY-001",
-  "current": "0.3.2",
+  "current": "0.3.3",
   "versions": [
     {
       "version": "0.1.0",
@@ -145,6 +145,11 @@
       "version": "0.3.2",
       "path": "v0.3.2/sdk-parity.json",
       "sha256": "0b66f731c16aef358fd944b322b31bf8568ddc3d000b6ad9ad401e63f89a81b6"
+    },
+    {
+      "version": "0.3.3",
+      "path": "v0.3.3/sdk-parity.json",
+      "sha256": "784919ec6dae6893c6c2807b0893963a9db6c8380081841159f263e188452597"
     }
   ]
 }