Commit Graph
11 Commits
Author SHA1 Message Date
Eric Traut 6d4a02fd4f codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut e76ebc7adc codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut 946cece56e codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut 4e16d58565 codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut 952738858e codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut bf5c0455a4 codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut f1128497f6 codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut bb1f2cacec codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut 8b1505b299 codex: address PR review feedback (#20179) 2026-04-29 13:56:17 -07:00
Eric Traut 5776844377 Extend TUI boundary guard to core protocol imports 2026-04-29 13:56:17 -07:00
Eric Traut 66e13efd9c TUI: enforce core boundary (#17399)
Problem: The TUI still depended on `codex-core` directly in a number of
places, and we had no enforcement from keeping this problem from getting
worse.

Solution: Route TUI core access through
`codex-app-server-client::legacy_core`, add CI enforcement for that
boundary, and re-export this legacy bridge inside the TUI as
`crate::legacy_core` so the remaining call sites stay readable. There is
no functional change in this PR — just changes to import targets.

Over time, we can whittle away at the remaining symbols in this legacy
namespace with the eventual goal of removing them all. In the meantime,
this linter rule will prevent us from inadvertently importing new
symbols from core.
2026-04-10 20:25:31 -07:00