pi-squire 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -6,6 +6,16 @@ follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.3.1] - 2026-10-03
+
+### Changed
+
+- With auto-exit on, a delegate whose run ends on a usage-limit error now
+  closes its window, as after a normal completion. The parent still gets the
+  `failed` reply and the session file stays. Other failures still leave the
+  window open. `test/harness.test.ts` now fails its run with a `400` instead
+  of a `429`, since a `429` is a usage limit and now exits.
+
 ## [0.3.0] - 2026-10-03
 
 ### Added
@@ -138,7 +148,8 @@ author's dotfiles; the changes below are against that copy.
 
 - The published file list includes `child.ts`, which `index.ts` imports.
 
-[Unreleased]: https://github.com/gvanderclay/pi-squire/compare/v0.3.0...HEAD
+[Unreleased]: https://github.com/gvanderclay/pi-squire/compare/v0.3.1...HEAD
+[0.3.1]: https://github.com/gvanderclay/pi-squire/compare/v0.3.0...v0.3.1
 [0.3.0]: https://github.com/gvanderclay/pi-squire/compare/v0.2.2...v0.3.0
 [0.2.2]: https://github.com/gvanderclay/pi-squire/compare/v0.2.1...v0.2.2
 [0.2.1]: https://github.com/gvanderclay/pi-squire/compare/v0.2.0...v0.2.1

package/README.md

@@ -353,7 +353,9 @@ The parent resolves each delegation's auto-exit from the call
   down (`ctx.shutdown()`) on the next event-loop turn, after the settle
   reply has been sent, so its tmux window closes. The session file stays, and
   `pi --session <path>` reopens it.
-- A run that ended stopped or failed never exits the delegate.
+- A run that ended stopped, or failed on anything but a usage limit, never
+  exits the delegate. A usage-limit failure is final until the quota resets,
+  so it exits like a normal completion; the parent still gets the failed reply.
 - The user taking over turns it off for the rest of the session, with a
   notice: typed or RPC input, or a run the user stopped (Esc).
 - `/auto-exit` inside the delegate turns it on again for the next normal

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-squire",
-	"version": "0.3.0",
+	"version": "0.3.1",
 	"description": "Starts a delegate Pi session in a background tmux window, sends it the task over message:*, and shows the parent its result",
 	"keywords": [
 		"pi-package",

package/src/child.ts

@@ -17,7 +17,7 @@
 // ponytail: drop the takeover once #5581 lands and the minimum Pi has it.
 import type { ExtensionAPI, ExtensionContext } from "@earendil-works/pi-coding-agent";
 
-import { type Response, recordLimit } from "./limits.ts";
+import { classify, type Response, recordLimit } from "./limits.ts";
 
 /** The launch variable that carries the parent's resolved setting. */
 export const AUTO_EXIT_ENV = "PI_DELEGATE_AUTO_EXIT";
@@ -99,7 +99,9 @@ export function registerChild(pi: ExtensionAPI, parent: string): void {
 		const stopped = last?.stopReason === "aborted" || ctx.signal?.aborted === true;
 		if (stopped) disarm(ctx);
 		if (!stopped && last?.stopReason === "error") recordUsageLimit(last, ctx, response);
-		completed = !stopped && last?.stopReason !== "error";
+		// A usage limit is final until the quota resets, so it ends the work like a completion.
+		const limited = typeof last?.errorMessage === "string" && classify(last.errorMessage) !== undefined;
+		completed = !stopped && (last?.stopReason !== "error" || limited);
 	});
 
 	pi.on("agent_settled", async (_event, ctx) => {