From be6f4cac9e6ccb33fcd03eaa2c87116883f79c73 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 5 Aug 2026 11:24:48 +0000
Subject: [PATCH] @aliou/pi-processes@0.10.3

---
 .changeset/wake-agent-on-process-success.md | 11 -----------
 CHANGELOG.md                                | 12 ++++++++++++
 package.json                                |  2 +-
 3 files changed, 13 insertions(+), 12 deletions(-)
 delete mode 100644 .changeset/wake-agent-on-process-success.md

diff --git a/.changeset/wake-agent-on-process-success.md b/.changeset/wake-agent-on-process-success.md
deleted file mode 100644
index 2e2aae4..0000000
--- a/.changeset/wake-agent-on-process-success.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-"@aliou/pi-processes": patch
----
-
-Default `notify.onSuccess` to `turn` so a finished process wakes an idle agent.
-
-Under v0.9.5 the flat `alertOnSuccess: true` boolean was clear enough that the agent set it on almost every start, so a completed build, test run, or encode always got a turn. The 0.10 rewrite replaced it with `notify.onSuccess`, defaulting to `context`, and the agent stopped opting in. `context` only reaches the agent if it happens to still be streaming when the process ends; an idle agent is never woken, so long one-shot commands finished silently and the user had to prod the agent.
-
-Servers and watchers that should not interrupt on a clean exit can still pass `notify.onSuccess: "context"`.
-
-The tool descriptions, prompt guidelines, and skill now state plainly that only `turn` reaches an idle agent, instead of claiming every exit notification brings the agent back.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index a90e4ae..69a1230 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,17 @@
 # @aliou/pi-processes
 
+## 0.10.3
+
+### Patch Changes
+
+- 7031d86: Default `notify.onSuccess` to `turn` so a finished process wakes an idle agent.
+
+  Under v0.9.5 the flat `alertOnSuccess: true` boolean was clear enough that the agent set it on almost every start, so a completed build, test run, or encode always got a turn. The 0.10 rewrite replaced it with `notify.onSuccess`, defaulting to `context`, and the agent stopped opting in. `context` only reaches the agent if it happens to still be streaming when the process ends; an idle agent is never woken, so long one-shot commands finished silently and the user had to prod the agent.
+
+  Servers and watchers that should not interrupt on a clean exit can still pass `notify.onSuccess: "context"`.
+
+  The tool descriptions, prompt guidelines, and skill now state plainly that only `turn` reaches an idle agent, instead of claiming every exit notification brings the agent back.
+
 ## 0.10.2
 
 ### Patch Changes
diff --git a/package.json b/package.json
index 1bdb3b6..c7a0cd3 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@aliou/pi-processes",
-  "version": "0.10.2",
+  "version": "0.10.3",
   "license": "MIT",
   "type": "module",
   "private": false,
-- 
2.51.2