tui: keep inaccessible apps out of mentions

[canvrno-oai]

Summary

Fix the TUI $ app mention paths so App Directory rows that are not accessible are not treated as usable apps.

This includes the core preservation fix from #24104, but expands it to the other app mention paths:

• preserve app-server is_accessible flags when partial app/list/updated snapshots reach the TUI
• require apps to be both accessible and enabled when resolving exact $slug mentions
• require restored/stale app://... bindings to point at accessible, enabled apps before emitting structured app mentions
• remove the now-unused codex-chatgpt dependency from codex-tui, which addresses the cargo shear failure seen on tui: keep inaccessible apps out of the mention picker #24104

Root Cause

The app server already sends merged app snapshots with accessibility computed. The TUI handled app-server app list updates as partial app loads and re-ran the old accessible-app merge path. That path treated every notification row as accessible, so App Directory entries with isAccessible=false could appear in $ suggestions.

Regression source: #22914 routed app-list updates through the app server while reusing the old TUI partial-load handling. Related precursor: #14717 introduced the partial-load path, but #22914 made it user-visible for app-server updates.

Issues

Fixes #24145
Fixes #24205
Fixes #24319

Validation

• just fmt
• git diff --check
• just bazel-lock-update
• just bazel-lock-check
• just argument-comment-lint -p codex-tui
• just test -p codex-tui chatwidget::tests::popups_and_settings::apps_notification_update_excludes_inaccessible_apps_from_mentions chatwidget::tests::composer_submission::submit_user_message_ignores_inaccessible_app_mentions_from_bindings chatwidget::skills::tests::find_app_mentions_requires_accessible_enabled_apps_for_bound_paths chatwidget::skills::tests::find_app_mentions_requires_accessible_enabled_apps_for_slugs

[canvrno-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 870d93f248

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[fcoury-oai]

Smoke tested with $app and the difference is obvious. Code looks very straightforward.

Approved 👍