@llblab/pi-kit 0.36.0 → 0.36.1

package/BACKLOG.md

@@ -2,10 +2,6 @@
 
 Package pins, resource order and bundled runtime ownership remain authoritative in `package.json`. Release outcomes belong in [CHANGELOG.md](./CHANGELOG.md).
 
-## Automatic-update operations
-
-- **First changed-cohort smoke:** After the first live automatic pin update, confirm the four-file main commit, explicit `workflow_dispatch` to `publish-pi-kit.yml`, matching expected commit, and final npm/tag/GitHub Release identities. No-update runs and local bare-repository tests do not prove this hosted changed-cohort path. Do not fabricate an update or weaken branch protection for a smoke test; inspect the real run or disable the updater on failure.
-
 ## Carried checks
 
 - **Installed 0.35.4 Telegram smoke (operator-owned):** After separately authorized kit installation/reload of every Pi process together, run `/telegram-new` in one follower instance and confirm the same Thread is reused with a new letter slot and title, with no second tab and no orphan left behind. Then restart that instance, open a new session in the same folder, and confirm it adopts the retained Thread instead of provisioning another. Do not erase accepted work or replay uncertain input. Packed validation does not certify installed clients.

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 All notable changes to `@llblab/pi-kit` are documented here.
 
+## 0.36.1: Bundled Package Updates (2026-10-22)
+
+- `Exact pins`: `@llblab/pi-state-flow` 0.26.4 → 0.26.5.
+- `Packaging`: Synchronizes the lockfile, bundle aliases and README inventory. Package membership and resource order remain unchanged; packed validation does not certify extension safety or installed-client behavior.
+
 ## 0.36.0: Bundled Package Updates (2026-10-21)
 
 - `Automatic updates`: Replaces the dependency PR/approval step with validated direct-to-main adoption of stable same-major patch/minor releases. Exact pins, bundle aliases, lockfile, README and kit version remain synchronized; preparation stays read-only and a fresh data-only writer rejects unsafe payloads and concurrent main changes.

package/README.md

@@ -17,7 +17,7 @@ Package links lead to the owning repositories for usage, documentation, issues,
 | [`@llblab/pi-clean-room`](https://github.com/llblab/pi-clean-room) | `0.3.0` | Isolated nested Pi TUI with named npm extensions and compatible model selection |
 | [`@llblab/pi-codex-usage`](https://github.com/llblab/pi-codex-usage) | `0.13.1` | OpenAI/legacy Codex subscription quota and Business credit status, with persistent priority Fast toggle mirrored in Telegram |
 | [`@llblab/pi-grow-loop`](https://github.com/llblab/pi-grow-loop) | `0.9.0` | Visible continuation scheduling and bounded worker Skills through compiled, manifest-owned resources |
-| [`@llblab/pi-state-flow`](https://github.com/llblab/pi-state-flow) | `0.26.4` | Scoped context/memory compiler with step-independent current memory, stable Passive/Active modes and visible blocked-state status |
+| [`@llblab/pi-state-flow`](https://github.com/llblab/pi-state-flow) | `0.26.5` | Scoped context/memory compiler with step-independent current memory, stable Passive/Active modes and visible blocked-state status |
 | [`@llblab/pi-telegram`](https://github.com/llblab/pi-telegram) | `0.57.3` | Telegram companion with per-prompt Steer, queued controls, Reroute/Restore, recoverable connections, previews, follower Threads, files, and voice |
 | [`@llblab/skills`](https://github.com/llblab/skills) | `1.15.0` | Portable workflows for engineering, review, design, context maintenance, and other focused tasks |
 
@@ -25,7 +25,7 @@ Versions are exact by design. An upstream release does not change an installed k
 
 ## Install
 
-Requires **Pi 1.0.0+** and **Node.js 22.19.0+**. State Flow requires its canonical checkpoint/tail storage format and does not convert unsupported stores in place. Preserve existing stores and consult the [owning package's storage guidance](https://github.com/llblab/pi-state-flow/blob/v0.26.4/docs/usage.md#moving-a-store-and-supported-formats) before changing installations.
+Requires **Pi 1.0.0+** and **Node.js 22.19.0+**. State Flow requires its canonical checkpoint/tail storage format and does not convert unsupported stores in place. Preserve existing stores and consult the [owning package's storage guidance](https://github.com/llblab/pi-state-flow/blob/v0.26.5/docs/usage.md#moving-a-store-and-supported-formats) before changing installations.
 
 From npm:
 

package/node_modules/@llblab/pi-state-flow/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 > Each release keeps at most 8 outcome records of at most 512 characters.
 
+## 0.26.5: Telegram Mode Receipt Hotfix
+
+- `Telegram mode controls`: Passive now refreshes the selected button on the first accepted click after Off, including existing-memory restoration and write-fence recovery during an active run. Accepted controls retain their renewed presentation receipt instead of being mistaken for canceled work; later mode choices, branch changes and shutdown still suppress obsolete updates. Memory storage and mode semantics are unchanged; no migration is required.
+
 ## 0.26.4: Passive Compaction Continuity
 
 - `Passive continuation`: After idle Stop, native compaction can replace the later user anchor with a summary. Passive now retains that summary, the available tool calls/results and later refinements instead of reducing requests to a frozen handoff. Reload/resume preserve the same continuation; discarded raw history is not reconstructed. Native compaction, memory scopes and stored state are unchanged; no migration or configuration change is required.

package/node_modules/@llblab/pi-state-flow/dist/lib/extension.js

@@ -1214,11 +1214,11 @@ export default function stateFlowExtension(pi, options = {}) {
                 });
             if (!modePersistenceError) {
                 appendCheckpoint();
-                return { ok: true, message: `State Flow ${selectedMode}` };
+                return { ok: true, message: `State Flow ${selectedMode}`, signal: sharedInspectionLifetime.signal };
             }
             const message = conciseDiagnostic(`State Flow ${selectedMode}; memory writes paused: ${modePersistenceError}`);
             notifyProblem(ctx, message, "warning");
-            return { ok: true, message };
+            return { ok: true, message, signal: sharedInspectionLifetime.signal };
         };
         let accepted = false;
         try {
@@ -1291,10 +1291,11 @@ export default function stateFlowExtension(pi, options = {}) {
                 const operation = selectMode(activeContext, mode);
                 if (mode === "active")
                     return operation;
-                // Inactive choices revoke older presentation at once; the receipt belongs to the new lifetime.
+                // Native-only outcomes use the selected lifetime; async acceptance may renew and return its own receipt.
                 const signal = sharedInspectionLifetime.signal;
                 try {
-                    return { ...await operation, signal };
+                    const result = await operation;
+                    return { ...result, signal: result.signal ?? signal };
                 }
                 catch (error) {
                     return { ok: false, message: diagnosticText(error), signal };

package/node_modules/@llblab/pi-state-flow/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-state-flow",
-  "version": "0.26.4",
+  "version": "0.26.5",
   "license": "MIT",
   "private": false,
   "description": "Incremental scoped state/context/memory compiler for Pi, inspired by SKILL.state",

package/node_modules/@llblab/pi-state-flow/docs/compatibility.md

@@ -138,7 +138,7 @@ The optional adapter presents one Off | Passive | Active row and uses the same m
 - Inspection returns coherent state plus matching revisions, without publication.
 - Controls and inspections acknowledge callbacks before waiting, suppress revoked results and escape late failures in the current menu.
 - Synchronous mode-selection ports are supported.
-- A first Passive selection may install a read-only shared cache without invalidating its own success receipt. Later controls, branch changes and cancellation still revoke obsolete presentation.
+- Passive acceptance returns its current presentation receipt after any internal restoration or lifetime renewal, including existing-memory reacquisition after Off and write-fence recovery. The adapter preserves that accepted receipt, so the first click refreshes the button in both busy and idle sessions. Pre-runtime shared-cache loading also retains its receipt. Later controls, branch changes and shutdown still revoke obsolete presentation, including a change away and back to the same mode while callback acknowledgement waits.
 
 Adapter tests establish these contracts with isolated transport fixtures; they are not a live Telegram smoke test. Missing or unready transport remains fail-open and cannot change core memory behavior.
 

package/node_modules/@llblab/pi-state-flow/docs/usage.md

@@ -211,6 +211,7 @@ When `pi-telegram` is available, its main-menu section shows `State Flow: active
 
 - A horizontal radio row presents `Off | Passive | Active`. The selected option uses 🟣, 🟡 or 🟢 respectively; each inactive option uses ⚫️.
 - Telegram Active requested during a run waits for settlement; Passive and Off apply immediately.
+- The first accepted Passive click refreshes the selected button after memory restoration or write-fence recovery, including while the agent is busy. A later mode or branch selection still suppresses an obsolete menu update.
 - Ordinary successful controls add no redundant mode receipt; diagnostic outcomes stay visible.
 - Off exposes neither tool nor State Flow model context.
 

package/node_modules/@llblab/pi-state-flow/lib/extension.ts

@@ -1200,11 +1200,11 @@ export default function stateFlowExtension(pi: ExtensionAPI, options: StateFlowE
 			});
 			if (!modePersistenceError) {
 				appendCheckpoint();
-				return { ok: true, message: `State Flow ${selectedMode}` };
+				return { ok: true, message: `State Flow ${selectedMode}`, signal: sharedInspectionLifetime.signal };
 			}
 			const message = conciseDiagnostic(`State Flow ${selectedMode}; memory writes paused: ${modePersistenceError}`);
 			notifyProblem(ctx, message, "warning");
-			return { ok: true, message };
+			return { ok: true, message, signal: sharedInspectionLifetime.signal };
 		};
 		let accepted = false;
 		try {
@@ -1272,10 +1272,11 @@ export default function stateFlowExtension(pi: ExtensionAPI, options: StateFlowE
 				if (!activeContext) throw new Error("State Flow is not attached to an active session yet");
 				const operation = selectMode(activeContext, mode);
 				if (mode === "active") return operation;
-				// Inactive choices revoke older presentation at once; the receipt belongs to the new lifetime.
+				// Native-only outcomes use the selected lifetime; async acceptance may renew and return its own receipt.
 				const signal = sharedInspectionLifetime.signal;
 				try {
-					return { ...await operation, signal };
+					const result = await operation;
+					return { ...result, signal: result.signal ?? signal };
 				} catch (error) {
 					return { ok: false, message: diagnosticText(error), signal };
 				}

package/node_modules/@llblab/pi-state-flow/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-state-flow",
-  "version": "0.26.4",
+  "version": "0.26.5",
   "license": "MIT",
   "private": false,
   "description": "Incremental scoped state/context/memory compiler for Pi, inspired by SKILL.state",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-kit",
-  "version": "0.36.0",
+  "version": "0.36.1",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -49,7 +49,7 @@
     "@llblab/pi-clean-room": "0.3.0",
     "@llblab/pi-codex-usage": "0.13.1",
     "@llblab/pi-grow-loop": "0.9.0",
-    "@llblab/pi-state-flow": "0.26.4",
+    "@llblab/pi-state-flow": "0.26.5",
     "@llblab/pi-telegram": "0.57.3",
     "@llblab/skills": "1.15.0"
   },