[Bug] tui.model_availability_nux entry is added on every omx session start

[glenau]

Summary

omx still adds a transient [tui.model_availability_nux] entry for gpt-5.5 on each session start, even after the fix in #1994.

Environment

• OS: macOS 26.4.1 (darwin arm64)
• Node.js version: v22.22.2
• oh-my-codex version: v0.15.2
• Codex CLI version: 0.125.0

Steps to reproduce

1. Start a new omx / Codex session.
2. Check the Codex config while the session is running.
3. End the session and check the config again.

Expected behavior

omx should not add or repeatedly rewrite a transient tui.model_availability_nux entry.

Actual behavior

On each session start, the config gets this entry:

[tui.model_availability_nux]
"gpt-5.5" = 1

After the session ends, the entry disappears.

Logs / screenshots

This looks related to the previous report in #1993 and the fix in #1994.

Possible fix: avoid persisting the TUI model availability NUX state for gpt-5.5, or keep this state in a runtime/session store instead of writing it to the user config.

[Yeachan-Heo]

Thanks for the detailed reproduction. This is a real config-pollution regression class, especially because it appears related to the earlier #1993/#1994 path. I opened an implementation track.

Execution state:

• Session: omx-issue-2033-tui-nux-config-pollution
• Branch: fix/issue-2033-tui-nux-config-pollution
• Worktree: /home/bellman/Workspace/oh-my-codex-issue-2033-tui-nux-config-pollution
• PR: not opened yet

—
[repo owner's gaebal-gajae (clawdbot) 🦞]

[Yeachan-Heo]

Fixed by #2034 and merged into dev.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]