Why

Markdown tables with a long path-heavy column could allocate almost all available width to that column and collapse neighboring prose columns to only a few characters. In rollout summaries this made Unit and What It Adds difficult to read, even though the long Files values were the content best suited to wrapping.

The affected example also specified Files as right aligned in its markdown delimiter (---:). This change preserves that requested alignment while improving how width is distributed.

Before	After

What Changed

• Classify table columns as narrative, token-heavy, or compact during width allocation.
• Shrink token-heavy path and URL columns before shrinking narrative prose, while preserving compact counts and short labels longest.
• Use readable soft floors for narrative and token-heavy content before falling back to tighter layouts.
• Add snapshot coverage for a rollout-shaped table containing right-aligned file paths and prose columns.

How to Test

1. Render a markdown table with Unit, right-aligned Files, Adds, Removes, and What It Adds columns at a constrained terminal width.
2. Put long repository paths in Files and sentence-length content in Unit and What It Adds.
3. Confirm that Files remains right aligned but wraps before the narrative columns become unreadable.
4. Confirm that the compact numeric columns remain easy to scan.

Targeted tests:

• just test -p codex-tui markdown_render

Validation note: just test -p codex-tui was also attempted and reached two existing unrelated failures in app::tests::update_feature_flags_disabling_guardian_*; the markdown rendering regression test passes in the targeted run.