@ngockhoale/ukit 2.2.10 → 2.2.11

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 All notable changes to UKit are documented here.
 
+## 2.2.11 - 2026-08-29
+
+Same-day follow-up to 2.2.10. The two premises that release shipped as unverified were checked
+against omp's own installed TypeScript source (`@oh-my-pi/pi-coding-agent` v18.0.10, not a live
+session — omp still was not run) and both hold:
+
+- **`steer` after a compaction is accepted, not dropped.** `session-maintenance.ts` fires
+  `session_compact` only after `agent.replaceMessages()`/`rebaseAfterCompaction()` already ran, so
+  the session is idle at that point, and `agent-session.ts`'s `sendCustomMessage()` non-streaming
+  branch appends the message to the live context regardless of `deliverAs`.
+- **`display: true` does trigger a visible re-render.** `extension-ui-controller.ts`'s
+  `applyCustomMessageDisplay()` calls `rebuildChatFromMessages()` for the non-streaming case (the
+  streaming case renders via the `message_end` event instead).
+
+`templates/.omp/hooks/pre/ukit-bridge.js`'s two `TODO(verify)` comments (PLAN.md §3 D3, D4) are
+updated to record this — from "unverified, additive, worst-case-unchanged" to "source-confirmed,
+one rung below a live repro." No runtime behaviour changes; both delivery paths (`steer` +
+`nextTurn`, and the `finalNotice` fallback) stay in place as defense in depth either way. A stale
+local `.omp/hooks/pre/ukit-bridge.js` install artifact in this repo — untracked, regenerated by
+`ukit install`, and out of sync with `templates/.omp/` since before 2.2.10 shipped — was also found
+and resynced; that file is never part of the published package.
+
 ## 2.2.10 - 2026-08-29
 
 User report: long omp (Oh My Pi) sessions go idle roughly 15 minutes into a task — no output, no

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngockhoale/ukit",
-  "version": "2.2.10",
+  "version": "2.2.11",
   "description": "Install/update an index-first AI workspace for Claude Code, OpenAI Codex, OpenCode, and omp (Oh My Pi).",
   "license": "MIT",
   "type": "module",

package/templates/.omp/hooks/pre/ukit-bridge.js

@@ -470,8 +470,12 @@ export async function runSessionCompact(pi, event, { projectRoot, context: exten
   const metadata = runtimeMetadata(event, extensionContext);
   const payload = buildHookPayload('SessionStart', { ...metadata, source: 'compact' });
   const result = await runScriptChain(pi, HOOK_EVENT_MAP.session_start, payload, { projectRoot });
-  // TODO(verify) PLAN.md §3 D3: whether omp still accepts a 'steer' message after a compaction
-  // is unverified. If it drops steer, the 'nextTurn' copy below preserves prior behavior.
+  // VERIFIED (2026-08-29, source read of omp v18.0.10 pi-coding-agent/src) PLAN.md §3 D3:
+  // session_compact fires only after agent.replaceMessages()/rebaseAfterCompaction() already
+  // ran (session-maintenance.ts), i.e. the session is idle here, and agent-session.ts's
+  // sendCustomMessage() non-streaming branch appends the message to the live context
+  // regardless of deliverAs — so 'steer' is accepted right after a compaction. Not a live
+  // repro, so the 'nextTurn' copy below stays as defense in depth.
   sendContext(pi, result.context, 'steer');
   sendContext(pi, result.context, 'nextTurn');
   return undefined;
@@ -499,9 +503,12 @@ export async function runSessionStop(
         `[UKit] Stopping with unfinished work: ${evaluation.missingEvidence.join(', ')}.`,
         evaluation.reason,
       ].filter(Boolean).join(' ');
-      // TODO(verify) PLAN.md §3 D4: whether omp honours display:true on a sendMessage payload
-      // is unverified (omp is not installed). If display is ignored, the finalNotice
-      // continuation below (the model's own message) is the channel guaranteed to render.
+      // VERIFIED (2026-08-29, source read of omp v18.0.10 pi-coding-agent/src) PLAN.md §3 D4:
+      // display:true on a non-streaming sendMessage payload triggers
+      // extension-ui-controller.ts's applyCustomMessageDisplay() -> rebuildChatFromMessages(),
+      // a real immediate TUI re-render (the streaming case renders via the message_end event
+      // instead). Not a live repro, so the finalNotice continuation below (the model's own
+      // message) stays as a second guaranteed channel.
       sendContext(pi, [notice], 'nextTurn', { display: true });
     }
     return undefined;