@nklisch/pi-enhanced 0.2.6 → 0.2.7

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## v0.2.7
+
+### Fixed
+
+- Rebundle `@nklisch/pi-plugins` 0.6.2 and `@nklisch/pi-subagents` 18.1.0-nklisch.4 so a blocking subagent result request cannot duplicate its completion notification in context.
+
 ## v0.2.6
 
 ### Fixed

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/CHANGELOG.md

@@ -5,6 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [18.1.0-nklisch.4] - 2026-08-27
+
+### Fixed
+
+- Prevent a blocking `get_subagent_result` call from also receiving the same background-agent completion as a delayed follow-up notification.
+
 ## [18.1.0-nklisch.3] - 2026-08-24
 
 ### Fixed

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/docs/architecture/architecture.md

@@ -243,7 +243,7 @@ Resume admission is a record-owned lease. A genuinely running or already-reserve
 
 Terminal outcomes also carry orthogonal consumption state. Foreground delivery, `get_subagent_result`, and a queued completion notification mark the outcome consumed. Records remain available for the parent session; only their heavy live child sessions are released after the configured consumed or unconsumed retention window. Released records keep their result and persisted transcript pointer but cannot resume. Release detaches the session synchronously before awaiting teardown, so it cannot race a new resume.
 
-Completion notifications are held while the parent agent run is active and flushed on `agent_settled`, rechecking consumption before enqueueing a follow-up. Child session creation shares the parent model runtime and leaves extension-tool registration open; a denylist removes disallowed built-ins and recursive orchestration tools across registry refreshes. Child teardown mirrors Pi's managed root lifecycle: it emits and awaits `session_shutdown` before `AgentSession.dispose()` revokes extension contexts, then publishes the child `disposed` event.
+Completion notifications are held while the parent agent run is active and flushed on `agent_settled`, rechecking consumption before enqueueing a follow-up. A blocking `get_subagent_result` request claims direct delivery before awaiting, so the same terminal outcome cannot also enqueue a completion follow-up. Child session creation shares the parent model runtime and leaves extension-tool registration open; a denylist removes disallowed built-ins and recursive orchestration tools across registry refreshes. Child teardown mirrors Pi's managed root lifecycle: it emits and awaits `session_shutdown` before `AgentSession.dispose()` revokes extension contexts, then publishes the child `disposed` event.
 
 ## Execution flow
 

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nklisch/pi-subagents",
-  "version": "18.1.0-nklisch.3",
+  "version": "18.1.0-nklisch.4",
   "type": "module",
   "exports": {
     ".": {

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/src/lifecycle/subagent-state.ts

@@ -66,6 +66,12 @@ export class SubagentState {
 	get consumedAt(): number | undefined { return this._consumedAt; }
 	get consumed(): boolean { return this._consumedAt != null; }
 
+	// A blocking result request has claimed the next terminal outcome for direct
+	// delivery. Completion notification observes this so it cannot enqueue the
+	// same result through Pi's asynchronous follow-up channel.
+	private _pendingResultWaits = 0;
+	get hasPendingResultWait(): boolean { return this._pendingResultWaits > 0; }
+
 	// Stats — accumulated via mutation methods, readable via getters
 	private _toolUses = 0;
 	get toolUses(): number { return this._toolUses; }
@@ -208,6 +214,16 @@ export class SubagentState {
 		this._consumedAt ??= at ?? Date.now();
 	}
 
+	/** Claim the next terminal outcome for a blocking direct-result request. */
+	beginResultWait(): void {
+		this._pendingResultWaits++;
+	}
+
+	/** Release one direct-result claim after its wait returns or is interrupted. */
+	endResultWait(): void {
+		this._pendingResultWaits = Math.max(0, this._pendingResultWaits - 1);
+	}
+
 	/** Transition to stopped state. Always valid — no guard. */
 	markStopped(completedAt?: number): void {
 		this._status = "stopped";

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/src/lifecycle/subagent.ts

@@ -127,6 +127,8 @@ export class Subagent {
 	get stoppedWhileQueued(): boolean { return this.state.stoppedWhileQueued; }
 	get consumedAt(): number | undefined { return this.state.consumedAt; }
 	get consumed(): boolean { return this.state.consumed; }
+	/** A blocking get-result call will deliver the next terminal outcome directly. */
+	get hasPendingResultWait(): boolean { return this.state.hasPendingResultWait; }
 	get toolUses(): number { return this.state.toolUses; }
 	get lifetimeUsage(): Readonly<LifetimeUsage> { return this.state.lifetimeUsage; }
 	get compactionCount(): number { return this.state.compactionCount; }
@@ -496,6 +498,21 @@ export class Subagent {
 		await settleOrAbort(run, signal);
 	}
 
+	/**
+	 * Wait for a terminal result that the caller will return directly to the
+	 * parent. The claim begins synchronously, before the first await, so a child
+	 * that settles while the tool is blocked cannot also queue a follow-up nudge.
+	 */
+	async waitForResult(signal: AbortSignal): Promise<void> {
+		if (!this.isActive()) return;
+		this.state.beginResultWait();
+		try {
+			await this.waitUntilSettled(signal);
+		} finally {
+			this.state.endResultWait();
+		}
+	}
+
 	/** Build a callback-only lifecycle bridge after the immutable child session exists. */
 	private createTurnLifecycle(
 		phase: "initial" | "resume",

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/src/observation/notification.ts

@@ -157,7 +157,10 @@ export class NotificationManager implements NotificationSystem {
   ) {}
 
   sendCompletion(record: Subagent): void {
-    if (this.disposed || record.consumed) return;
+    // A blocking get-result request has already selected direct delivery for
+    // this terminal outcome. Never enqueue the same payload as a follow-up,
+    // even if Pi's parent lifecycle currently appears idle.
+    if (this.disposed || record.consumed || record.hasPendingResultWait) return;
     if (this.parentRunActive) {
       this.pendingNudges.set(record.id, record);
       return;

package/node_modules/@nklisch/pi-plugins/node_modules/@nklisch/pi-subagents/src/tools/get-result-tool.ts

@@ -33,8 +33,10 @@ export class GetResultTool {
 		}
 
 		// A queued record is awaitable from spawn, and a resumed record republishes
-		// its live promise. Interrupting this tool stops only the wait.
-		if (params.wait) await record.waitUntilSettled(signal);
+		// its live promise. This claim is synchronous so completion cannot race the
+		// direct result with an asynchronous follow-up notification. Interrupting
+		// this tool stops only the wait.
+		if (params.wait) await record.waitForResult(signal);
 
 		// Pull delivery: only a terminal result was actually collected.
 		if (!record.isActive()) record.markConsumed();

package/node_modules/@nklisch/pi-plugins/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nklisch/pi-plugins",
-  "version": "0.6.1",
+  "version": "0.6.2",
   "private": false,
   "description": "A small filesystem-first marketplace and plugin host for Pi.",
   "license": "MIT",
@@ -63,7 +63,7 @@
   ],
   "dependencies": {
     "@nklisch/pi-mcp-adapter": "2.21.0-nklisch.2",
-    "@nklisch/pi-subagents": "18.1.0-nklisch.3",
+    "@nklisch/pi-subagents": "18.1.0-nklisch.4",
     "jiti": "2.7.0"
   },
   "devDependencies": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nklisch/pi-enhanced",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "description": "Pi, enhanced — one install for nklisch's full harness: policy-gated command review, plugin marketplace, subagents, background tasks, research tools, search, model modes, and a curated UX set.",
   "author": {
     "name": "nklisch"