@caupulican/pi-adaptative 0.81.27 → 0.81.29

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [0.81.29] - 2026-07-10
+
+### Fixed
+
+- Updated capability, fitness, and regression coverage for the artifact and delegation companion tools and plain-text worker results.
+
+## [0.81.28] - 2026-07-10
+
+### Fixed
+
+- Added bounded recovery for locally unexpired OAuth credentials rejected with an initial Codex 401, including locked reload/refresh and rotated-token persistence.
+
+- Made delegated workers session-owned background jobs with non-blocking starts, explicit local-foreground queuing, bounded `delegate_status` retrieval, and safe read-only plain-text result handling.
+
 ## [0.81.27] - 2026-07-10
 
 ### Added

package/dist/core/agent-session.d.ts

@@ -112,6 +112,11 @@ export type AgentSessionEvent = Exclude<AgentEvent, {
     type: "routing_start";
 } | {
     type: "routing_end";
+} | {
+    type: "delegate_workers";
+    active: number;
+    completedSinceFlush: number;
+    failedSinceFlush: number;
 };
 /** Listener function for agent session events */
 export type AgentSessionEventListener = (event: AgentSessionEvent) => void;
@@ -379,6 +384,7 @@ export declare class AgentSession {
     private readonly _bash;
     private readonly _profileFilter;
     private readonly _toolGate;
+    private readonly _toolSelection;
     private _extensionRunner;
     private _turnIndex;
     private _currentForegroundEnvelope?;
@@ -740,8 +746,9 @@ export declare class AgentSession {
      * Also rebuilds the system prompt to reflect the new tool set.
      * Changes take effect on the next agent turn.
      *
-     * artifact_retrieve is auto-activated as a companion whenever grep or find ends up
-     * in the resulting active set and artifact_retrieve is registered (i.e. not excluded/
+     * artifact_retrieve is auto-activated as a companion whenever an artifact-producing tool
+     * (grep, find, or run_toolkit_script) ends up in the resulting active set and artifact_retrieve
+     * is registered (i.e. not excluded/
      * blocked/outside an allowlist -- the registry itself is built with that same filter,
      * so registry presence already tracks "allowed"). This is enforced here, not just in
      * the settings/profile refresh flow, because this method is a public, extension-