tui: replace debug/test-only crate features with debug_assertions

## Why

The remaining `vt100-tests` and `debug-logs` features in `codex-tui` were only selecting debug and test-only behavior. Those are exactly the cases where this repo already accepts `#[cfg(debug_assertions)]` as the Cargo-free substitute.

## What changed

- delete `vt100-tests` and `debug-logs` from `codex-tui`
- gate the VT100 integration tests with `debug_assertions` instead of a Cargo feature
- gate the textarea debug log site with `debug_assertions`
- shrink the manifest verifier allowlist again so only the remaining real feature exceptions stay permitted
This commit is contained in:
Michael Bolin
2026-04-01 10:21:29 -07:00
parent c31efbef25
commit 8fa00a0be7
6 changed files with 4 additions and 10 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
// Single integration test binary that aggregates all test modules.
// The submodules live in `tests/suite/`.
#[cfg(feature = "vt100-tests")]
#[cfg(debug_assertions)]
mod test_backend;
#[allow(unused_imports)]
+1 -1
View File
@@ -1,4 +1,4 @@
#![cfg(feature = "vt100-tests")]
#![cfg(debug_assertions)]
#![expect(clippy::expect_used)]
use crate::test_backend::VT100Backend;
@@ -1,4 +1,4 @@
#![cfg(feature = "vt100-tests")]
#![cfg(debug_assertions)]
use crate::test_backend::VT100Backend;
use ratatui::layout::Rect;