[Lstarsky0]

What and why

The transcript's markdown parser trims each line before it looks for a list marker and keeps only the marker and the text, so a nested list renders flat. A reply with

- Top level item
  - Second level, indented two spaces
    - Third level, indented four spaces, long enough to wrap at forty columns
- Another top level item

1. Step one
   - detail a under step one
   - detail b under step one
2. Step two

renders at 80×24, before:

▏ - Top level item
▏ - Second level, indented two spaces
▏ - Third level, indented four spaces, long enough to wrap at forty columns
▏ - Another top level item
▏
▏ 1. Step one
▏ - detail a under step one
▏ - detail b under step one
▏ 2. Step two

After:

▏ - Top level item
▏   - Second level, indented two spaces
▏     - Third level, indented four spaces, long enough to wrap at forty
▏       columns
▏ - Another top level item
▏
▏ 1. Step one
▏    - detail a under step one
▏    - detail b under step one
▏ 2. Step two

Before, the details under "1." read like siblings of the numbered steps. ListItem now records the source line's leading whitespace and the renderer paints it before the bullet, so wrapped rows still hang under the item's text. The indent is capped at half the width so a pathological line can't push the text out of the pane. Lists without leading whitespace render as before.

What it doesn't do: a list item's own continuation line in the source (- item then an indented line of prose) is still a paragraph and renders flush left, and a tab counts as one column. A top-level list the model indents by one to three spaces now shifts right by that much, since the renderer paints what was written.

Issue

No-Issue: nested markdown lists render flat in the transcript; I searched and found no issue for it

How I tested it

• Ran a debug build in a pseudo-terminal with an empty HOME against a local OpenAI-compatible mock that streams a canned reply, with this change and with a build from before it. The screens above are from the nested reply at 80×24; 40×12 shows the same indentation. A reply whose lists all start at column 0 (-, *, 1. to 10., with wrapped items) renders the same list rows before and after at 80×24 and 40×12. In a longer reply, - nested bullet under 2. Second item now sits under "Second item", with its wrapped path row under it.
• Checked that nothing outside crates/tui/src matches on ListItem.
• cargo fmt --all -- --check, cargo clippy -p codewhale-tui --all-targets --all-features with CI's flags, and cargo check -p codewhale-tui --all-targets: clean. Clippy also on 1.99, plus cargo +1.89.0 check -p codewhale-tui.
• cargo nextest run -p codewhale-tui --lib: 15347 passed, none failed, including the markdown render tests and the incremental-vs-full reparse test, whose corpus has a nested list.

Checklist

• One focused change, on cc4b96d; it merges cleanly into current main
• cargo fmt --all passes, and tests cover new or changed behavior
• If this adds or changes a user-facing feature, I updated its docs and its row in docs/features.toml (cargo test -p codewhale-tui --test feature_registry checks it) — n/a

[claude]

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-20T16:07:50.345675Z	d4b54cc	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Hmbown]

🤖 This reply is from Claude Opus 5.5, an AI agent working on behalf of the Codewhale maintainers. It is posted through @Hmbown's account, but Hunter did not write it.

Thanks @Lstarsky0. You traced the flat nested lists to the parser trimming each line before it looks for a list marker. Recording the source indent on ListItem and painting it before the bullet keeps wrapped rows hanging under their item, and the half-width cap stops a pathological indent from pushing the text out of the pane. Details under a numbered step no longer read like sibling steps. Thanks as well for listing what it doesn't cover (continuation prose, tabs as one column, the shift for 1 to 3 space top-level lists). Merged in ccd8d97 for 0.10.2, which hasn't shipped yet.