oh-my-opencode 4.16.0 → 4.16.2

package/.agents/skills/codex-qa/SKILL.md

@@ -70,19 +70,21 @@ Windows.
 | `scripts/tui-smoke.sh` | the real codex TUI boots in the isolated home, renders, and survives (no early exit); captures the pane |
 
 When TUI visual QA evidence is needed, follow
-`docs/reference/web-terminal-visual-qa.md` and do not stop at the raw pane. Replay the
-captured pane through the repository web-terminal helper so the PR can attach a
-stable browser screenshot:
+`docs/reference/web-terminal-visual-qa.md`: render the TUI through the real
+xterm.js web terminal - NEVER the `tmux capture-pane` frame, which degrades
+color and CJK width:
 
 ```bash
 node script/qa/web-terminal-visual-qa.mjs --title "Codex TUI QA" \
-  --from-file .omo/evidence/<slug>/codex-tui-pane.txt \
+  --command "codex" --input "{Enter}" \
   --evidence-dir .omo/evidence/<slug>/codex-web-terminal
 ```
 
-The helper writes `terminal.txt`, `terminal-ansi.txt`, `terminal.html`,
-`terminal.png`, and `metadata.json`. Use that artifact set for TUI visual QA;
-use `app-server-drive.sh --plugin` for assertion-grade hook behavior.
+The helper runs a real pty, renders it in xterm.js under Chrome, and writes
+`terminal.txt`, `terminal-ansi.txt`, `terminal.png` (true color), and
+`metadata.json` (`--from-file <capture.ansi>` replays a saved raw stream). Use
+that artifact set for TUI visual QA; use `app-server-drive.sh --plugin` for
+assertion-grade hook behavior.
 
 ## Match QA to your change scope
 

package/.agents/skills/codex-qa/references/logging-debug.md

@@ -46,17 +46,19 @@ tmux send-keys -t <sess> "/debug-config" Enter
 tmux capture-pane -t <sess> -p -S -
 ```
 
-For TUI visual QA evidence, replay that pane capture through the browser helper
-from the repository root:
+For TUI visual QA evidence, render the live TUI through the real xterm.js web
+terminal instead of scraping the tmux pane (`tmux capture-pane` degrades color
+and CJK width):
 
 ```bash
 node script/qa/web-terminal-visual-qa.mjs --title "Codex TUI /debug-config" \
-  --from-file .omo/evidence/<slug>/codex-debug-config-pane.txt \
+  --command "codex" --input "/debug-config" --input "{Enter}" \
   --evidence-dir .omo/evidence/<slug>/codex-debug-config-web-terminal
 ```
 
 Attach the resulting `terminal.png` and keep `metadata.json` with the cleanup
-receipt. The pane proves terminal text; the PNG proves the visual TUI surface.
+receipt. The tmux pane above proves the config text; this PNG proves the visual
+TUI surface in true color.
 
 ## 5. `codex debug` subcommands
 

package/.agents/skills/opencode-qa/SKILL.md

@@ -125,21 +125,21 @@ This launches the TUI under tmux in an isolated sandbox, confirms it renders
 session down, and verifies the real DB session count is unchanged.
 
 When TUI visual QA evidence is needed for a PR, follow
-`docs/reference/web-terminal-visual-qa.md` and attach a browser-rendered
-terminal artifact in addition to the tmux pane. From the repository root, replay
-the captured pane or run a short tmux-backed command through:
+`docs/reference/web-terminal-visual-qa.md`: render the TUI through the real
+xterm.js web terminal and screenshot it - NEVER the `tmux capture-pane` frame,
+which degrades color and CJK width. From the repository root:
 
 ```bash
 node script/qa/web-terminal-visual-qa.mjs --title "OpenCode TUI QA" \
-  --from-file .omo/evidence/<slug>/opencode-tui-pane.txt \
+  --command "opencode" --input "{Enter}" \
   --evidence-dir .omo/evidence/<slug>/opencode-web-terminal
 ```
 
-This writes `terminal.txt`, `terminal-ansi.txt`, `terminal.html`,
-`terminal.png`, and `metadata.json` so the PR can attach a stable TUI visual
-screenshot plus the cleanup receipt. Use `--command "<cmd>"` only for short
-ad-hoc terminal checks; the isolated `scripts/tui-smoke.sh` remains the
-canonical OpenCode TUI smoke.
+This runs a real pty, renders it in xterm.js under Chrome, and writes
+`terminal.txt`, `terminal-ansi.txt`, `terminal.png` (the true-color artifact),
+and `metadata.json` with a cleanup receipt (`--from-file <capture.ansi>` replays
+a saved raw stream). The isolated `scripts/tui-smoke.sh` remains the canonical
+OpenCode TUI boot smoke (tmux), separate from this visual evidence.
 
 Honest verdict: tmux is fine for SMOKE (did it boot, render, accept a key) but
 fragile for asserting conversation output (the TUI is a 60fps full-screen app).

package/.agents/skills/opencode-qa/references/tui-tmux.md

@@ -16,20 +16,22 @@ Launching the real TUI would create sessions in the real ~/.local/share/opencode
 
 ## Browser-rendered TUI visual evidence
 
-For PR evidence or any TUI visual QA claim, keep the tmux transcript and add a
-browser-rendered screenshot using the repository helper:
+For PR evidence or any TUI visual QA claim, render the live TUI through the real
+xterm.js web terminal - NEVER the `tmux capture-pane` frame, which degrades
+color and CJK width:
 
 ```bash
 node script/qa/web-terminal-visual-qa.mjs --title "OpenCode TUI QA" \
-  --from-file .omo/evidence/<slug>/opencode-tui-pane.txt \
+  --command "opencode" --input "{Enter}" \
   --evidence-dir .omo/evidence/<slug>/opencode-web-terminal
 ```
 
-The helper replays the terminal frame into `terminal.html`, captures
-`terminal.png` with Chrome when available, writes `metadata.json`, and records
-the cleanup receipt. This is the required TUI visual evidence pattern when the
-review needs to see the screen, while `scripts/tui-smoke.sh` remains the
-isolation/smoke authority.
+The helper runs a real pty, renders it in xterm.js under Chrome, captures
+`terminal.png` (true color), writes `terminal.txt` + `metadata.json`, and
+records the cleanup receipt (`--from-file <capture.ansi>` replays a saved raw
+stream). This is the required TUI visual evidence pattern when the review needs
+to see the screen, while `scripts/tui-smoke.sh` remains the isolation/smoke
+authority.
 
 ## Manual tmux recipe (fenced) - for ad hoc smoke
 

package/dist/cli/codex-ulw-loop.d.ts

@@ -1,3 +1,11 @@
+/**
+ * Sentinel forwarded to every delegated ulw-loop child. A delegation chain is
+ * expected to terminate in ONE hop (component bin or cached component CLI).
+ * Without it, a broken install (missing component CLI) made the legacy `omo`
+ * wrapper re-enter this resolver: wrapper -> omo CLI -> wrapper -> ... which
+ * fork-bombed thousands of live processes and exhausted system RAM.
+ */
+export declare const ULW_LOOP_DELEGATION_SENTINEL = "OMO_ULW_LOOP_DELEGATED";
 export type CodexUlwLoopCommand = {
     readonly executable: string;
     readonly argsPrefix: readonly string[];

package/dist/cli/get-local-version/types.d.ts

@@ -5,7 +5,7 @@ export interface VersionInfo {
     isLocalDev: boolean;
     isPinned: boolean;
     pinnedVersion: string | null;
-    status: "up-to-date" | "outdated" | "local-dev" | "pinned" | "error" | "unknown";
+    status: "up-to-date" | "outdated" | "local-dev" | "pinned" | "pinned-mismatch" | "error" | "unknown";
 }
 export interface GetLocalVersionOptions {
     directory?: string;