[Lstarsky0]

What and why

A paragraph indented under a list item renders flush left: the word wrapper drops spaces at the start of a row, so the indent never reaches the screen. Models write these often, as a bullet's second paragraph or a note after a numbered step's code block. At 60 columns, before:

● Setup:
▏
▏ 1. Install the dependencies:
▏
       npm install --save-dev typescript
▏
▏ This also writes a lockfile, which you should commit
▏ together with the change.
▏
▏ 2. Build:
       npm run build
▏ 3. Check the config:
▏
       {
         "strict": true
       }
▏
▏ - A bullet with a second paragraph.
▏
▏ The second paragraph of that bullet, indented two spaces
▏ and long enough to wrap.
▏ - Last bullet

The code under step 1 keeps its indent but the note after it doesn't, so step 1 looks finished and the note reads as top-level text. After:

● Setup:
▏
▏ 1. Install the dependencies:
▏
       npm install --save-dev typescript
▏
▏    This also writes a lockfile, which you should commit
▏    together with the change.
▏
▏ 2. Build:
       npm run build
▏ 3. Check the config:
▏
       {
         "strict": true
       }
▏
▏ - A bullet with a second paragraph.
▏
▏   The second paragraph of that bullet, indented two
▏   spaces and long enough to wrap.
▏ - Last bullet

The parser now carries whether a list is open, next to its code-fence state: a list item opens it, blank lines, code and indented paragraphs keep it open, and anything else closes it. While a list is open, a paragraph keeps its leading spaces, and render_paragraph_tagged wraps the text in the remaining width and draws the indent on every row, capped at half the width like a list item's indent (#7030); links shift with it. The decision is made when the line is parsed rather than in the renderer, because streaming renders the text between code blocks separately and a look-back there would not match the final render. Copy follows list items: the first row copies with its indent, as written, and wrapped rows strip it.

Command notes go through the same renderer, and some have indented rows that aren't under a list item, such as /status's key/value rows and part of /cost. Those render as before: I ran /status, /cost, /context, /hooks, /mcp, /skills, /tools, /memory, /doctor, /version, /usage, /agents, /workspace, /permissions, /sandbox, /todo, /goal, /diff, /stats and /profile in one session on both builds, and the screens match once the session id is masked. A first version that kept every indent did shift /status and /cost, which is why the decision follows the list.

Issue

No-Issue: a paragraph indented under a list item renders flush left; I searched and found no issue for it

How I tested it

• Ran a debug build of this change and one of main at 588426d in a pseudo-terminal at 60 columns with an empty HOME and a local mock OpenAI-compatible server replying with the steps and bullets above; the rows above come from those runs.
• Selection copy: with a throwaway test (not part of this PR) that selects 1. Install followed by an indented paragraph, and - item followed by an indented line, at 24 columns and calls selection_to_text, this change copies both as written ("1. Install\n\n alpha beta … kappa"); main copies them without the indent ("1. Install\n\nalpha beta … kappa").
• cargo nextest run -p codewhale-tui -p codewhale-tui-kit --lib: 13880 of 13886 passed, with the 427 tests whose names match markdown, paragraph, selection or transcript among them. The 6 failures (status_public_output_and_read_only_state_match_baseline, golden_turn_events_match, model_visible_prefix_bytes_match_goldens, interrupted_session_deletion_keeps_recovery_incomplete_and_can_finish, worker_compacts_past_its_context_window_and_keeps_working, reasoning_effort_uses_one_strict_alias_table_and_legacy_fallback) also fail on main at 588426d without this change.
• cargo fmt --all -- --check, cargo clippy -p codewhale-tui -p codewhale-tui-kit with CI's flags (also on 1.99), cargo check -p codewhale-tui -p codewhale-tui-kit --all-targets and cargo +1.89.0 check -p codewhale-tui -p codewhale-tui-kit: clean.

Checklist

• One focused change, on 588426d; it merges cleanly into current main
• cargo fmt --all passes, and tests cover new or changed behavior — cargo fmt passes; no new test, per AGENTS.md, so the runs above stand in for one
• 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	🔄 Running since 2026-10-29T19:33:38.513505Z	9dc506b	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.

[carloslindhstrom-code]

``

[Hmbown]

thank you!! this is great