@raidiant/notifai 11.0.5 → 11.1.1

package/dist/skill-source/notifai/references/harness-setup.md

@@ -57,10 +57,10 @@ Installed definitions call one stable user-level adapter at
 `~/.notifai/bin/hook-adapter`. `hooks install` atomically retargets that adapter
 to the current CLI while leaving definition bytes unchanged across Node/NVM,
 package-manager, CLI-version, checkout, XDG directory, and Notifai preference
-changes. Stop definitions differ by harness: Claude Code's runs asynchronously
-with an explicit timeout above the longest answer window (POSIX hosts only — on
-Windows it blocks like the others), and Codex declares the same full-window
-timeout; prompt-submit and session-end retain fixed short limits on both.
+changes. Codex Stop runs asynchronously on every platform; Claude Code Stop
+runs asynchronously on POSIX and blocks on Windows. Both declare a timeout
+above the longest answer window so their waiters can own the complete window;
+prompt-submit and session-end retain fixed short limits on both.
 Codex SessionStart stays within the harness's built-in inline-context budget;
 Notifai does not add an output-limit override that would create a second trust
 identity. Upgrades preserve both the source file and the approved definition.
@@ -72,7 +72,7 @@ later upgrades must not require another.
 first. The current Agent Session's UserPromptSubmit observation proves that the
 exact session owns this turn. A historical Stop observation is diagnostic
 telemetry, not an admission prerequisite: the installed, trusted, current,
-singular Stop definition and its continuation owner establish that the asking
+singular Stop definition and its answer waiter establish that the asking
 turn can route the question. Ask exposes no `--session-id` override and will
 not guess one.
 When the failure includes a User-owned trust or permission `user_action`, relay
@@ -122,11 +122,12 @@ shell. Do not strip markers or borrow another Agent Session's identity to make
   UserPromptSubmit does not activate it. Codex SubagentStart uses the same
   reporting-only worker contract and explicit textual delegation rule as
   Claude. A fresh install writes the Machine layer's `~/.codex/hooks.json`, or
-  joins inline `[hooks]` when that is the layer's existing representation.
-  Upgrades preserve whichever source already owns Notifai's approved handlers
-  and keep the default SessionStart output-limit identity, because moving the
-  definition or adding identity-bearing fields creates a new Codex trust
-  identity. One install covers every project and every worktree, so there is
+  joins inline `[hooks]` when the User already keeps their own hooks there.
+  Notifai-owned inline handlers with no foreign inline neighbours are moved to
+  `hooks.json`; Codex will ask for `/hooks` approval because it keys trust by
+  source path. Foreign inline configuration is left in place. Later upgrades
+  keep the default SessionStart output-limit identity so they do not mint a
+  second trust identity. One install covers every project and every worktree, so there is
   nothing to repeat in a new checkout; a Project-scoped `.codex` hook file from
   an older Notifai is removed once the Machine copy is proven current.
 - **Cursor:** start one fresh conversation, send one prompt, and let the first
@@ -196,9 +197,16 @@ meter differs per harness:
   the successor turn in the same Agent Session without another User prompt.
   Direct inbox wake is unavailable, but it is not needed while this exact Stop
   continuation owns the answer.
-- **Codex:** the Stop hook is the waiter. It holds until the answer arrives or
-  the complete answer window ends, then continues the session by returning
-  `decision: block`.
+- **Codex:** the asynchronous Stop hook releases the turn and waits in the
+  background for the complete answer window. When an answer arrives, Notifai
+  invokes `codex queue` for the exact Agent Session in the same Codex home.
+  A live idle session starts a turn, a busy one consumes the answer after its
+  current turn, and a closed one keeps the queued answer until it is reopened.
+  Queue success proves storage, not consumption; UserPromptSubmit observes
+  consumption. Keep the original question and request identities if the route
+  fails so Notifai's journal can recover the answer. Never queue and resume the
+  same answer separately: a resume can consume the queue and the repeated
+  prompt, producing two copies.
 - **Crash recovery:** the answer journal protects an accepted answer if an
   owner process or its route fails. It is not the normal last meter for an
   unexpired question.
@@ -271,7 +279,8 @@ Those are three different controls and only the last one decides whether an
 answer is still wanted. Question Routing owns that complete window. Claude Code
 waits out of band and wakes the Agent Session on POSIX; on Windows its Stop
 stays held and returns the answer as the same Agent Session's continuation,
-like Codex. The journal is crash recovery, not the ordinary delivery path.
+while Codex queues the answer into its Agent Session's durable inbox. The
+journal is crash recovery, not the ordinary delivery path.
 
 `NOTIFAI_NO_INPUT=1` guarantees no command will ever prompt, which is what you
 want in CI or any shell with nobody at it. `NOTIFAI_CREDENTIALS=file` stores the

package/dist/ui/theme.d.ts

@@ -40,7 +40,7 @@ export declare const glyph: {
     readonly bullet: "-" | "•";
     readonly arrow: "→" | "->";
     readonly chevron: "›" | ">";
-    readonly bar: "│" | "|";
+    readonly bar: "|" | "│";
 };
 export type Tone = 'ok' | 'warn' | 'bad' | 'pending';
 /** A coloured glyph for a tone; the caller supplies the words. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raidiant/notifai",
-  "version": "11.0.5",
+  "version": "11.1.1",
   "type": "module",
   "description": "Send native device notifications from agents and local programs",
   "bin": {
@@ -12,7 +12,7 @@
   ],
   "dependencies": {
     "@clack/prompts": "^1.7.0",
-    "@raidiant/notifai-protocol": "6.1.5",
+    "@raidiant/notifai-protocol": "7.0.2",
     "commander": "^14.0.0",
     "picocolors": "^1.1.1",
     "smol-toml": "^1.4.0"