pi-delegation-policy 0.22.0 → 0.22.1

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 0.22.1 - 2026-10-22
+
+### Fixed
+
+- The footer no longer keeps a stale `D:ERR` from session start when an ordinary model becomes
+  available only after this extension's `session_start` handler. Another extension may fill the model
+  catalog in its own start handler, and the host then emits `resources_discover`; a read-only runtime
+  refresh there repaints the footer with the existing validation. This adds one configuration/branch
+  read and footer refresh per session bind or reload, returns no resource paths, makes no network
+  call, and leaves the configuration-change notice reference alone, so a pending change is not lost.
+  A model that is genuinely missing or unusable still reports `D:ERR`. The fix relies on the public
+  post-start discovery order, verified in Pi `0.87.1` and `1.1.0`; availability changes after that
+  event still refresh on the next request or menu action.
+
 ## 0.22.0 - 2026-10-21
 
 ### Added

package/README.md

@@ -6,7 +6,7 @@ general subagent runner. Only explicit tools can request reader work or Advisor
 the authorized host executor; hooks never launch children.
 
 > **Docs:** [yivas.github.io/pi-delegation-policy](https://yivas.github.io/pi-delegation-policy/).
-> Version **0.22.0** requires Pi `0.87.1` or later (`>=0.87.1`); it re-applies its marked policy block in the final provider payload.
+> Version **0.22.1** requires Pi `0.87.1` or later (`>=0.87.1`); it re-applies its marked policy block in the final provider payload.
 > Version `0.14.1` supports Pi `0.84.3` or later (`>=0.84.3`).
 >
 > Independent Advisor mode and its companion file are available from version `0.17.0`.
@@ -15,7 +15,7 @@ the authorized host executor; hooks never launch children.
 ## Install
 
 ```bash
-pi install npm:pi-delegation-policy@0.22.0
+pi install npm:pi-delegation-policy@0.22.1
 # restart Pi, or run /reload
 ```
 
@@ -190,6 +190,10 @@ example `advisor-mode=with-delegation (global); A:OFF` and `thinking-advisor=uns
 `D:OFF`, `D:NORM`, `D:AGG`, and `D:ORCH` describe delegation; `A:OFF`, `A:ON`, `A:PART`, and `A:ERR` describe
 Advisor. None of them proves that a launch happened or that another system followed the guidance.
 
+The footer also revalidates after all session-start handlers finish. If another extension makes a
+configured model available later in startup, the earlier `D:ERR` is replaced with the current status
+without waiting for a message or menu action. A model that remains invalid still reports `D:ERR`.
+
 ### Configuration change notice
 
 Available from `0.22.0`. The declared Pi peer remains

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-delegation-policy",
-  "version": "0.22.0",
+  "version": "0.22.1",
   "private": false,
   "description": "A Pi extension for configurable delegation intensity and exact subagent role model references.",
   "type": "module",

package/src/index.ts

@@ -896,6 +896,14 @@ export function createPiDelegationPolicy(options: PiDelegationPolicyOptions = {}
       advisorContext = undefined;
       startConfigBaseline(await refreshRuntime(ctx));
     });
+    // The host emits this after every `session_start` handler has run, so a model catalog another
+    // extension fills during its own start handler is visible here and the footer stops reporting an
+    // error that no longer applies. It only re-reads the runtime and repaints: no resource paths, no
+    // network, no new validation rules, and the notice reference stays as the start left it, so a pending
+    // change is not lost.
+    pi.on("resources_discover", async (_event, ctx) => {
+      await refreshRuntime(ctx);
+    });
     pi.on("input", async (event) => {
       // The host emits this for every submitted input immediately before the prompt it belongs to,
       // and `before_agent_start` follows only for a fresh prompt. Attribution therefore depends on