[max-sixty]

Two display features for wt list and the interactive picker, developed together because they share the column-layout and progressive-rendering machinery.

Custom columns ([list.custom-columns])

Each [list.custom-columns.<Header>] entry in user config adds a wt list column: a minijinja template rendered per row over branch, worktree_path, worktree_name, and vars.*, with optional width and drop priority. Values expand before the skeleton renders, from in-memory data only — vars come from the bulk git-config snapshot, so no subprocess runs per cell. Widths are measured from content like the Branch and Path columns; a column that is empty on every row is dropped.

Unknown variables and misspelled filters abort wt list with the available-variables hint; undefined values render as empty cells (the intended sparse-column shape). wt list --format json gains a columns map per item, and its vars field now reads from the snapshot too (the previous --get-regexp line-parse truncated multiline values). The picker shares the row renderer, so the columns appear there as well; a broken definition degrades to no columns plus a stashed warning, since collect runs while skim owns the terminal.

The key is [list.custom-columns], not [list.columns], to avoid colliding with the column-visibility toggles in #3065 (which claims [list.columns] as a flat map of built-in-column bools — a mutually exclusive serde shape for the same protected key). Namespacing here lets both land independently.

Ref #1982 — the custom-columns proposal lives in that thread. The issue's own title is a separate directory-naming request, so this doesn't close it.

Cached PR/MR numbers in the picker

The picker skips the networked CiStatus task, so until now it had no CI column at all. Cached statuses are local data, though: collect now fills rows from .git/wt/cache/ci-status/ when the task is skipped under a progressive handler, so PR/MR numbers fetched by earlier wt list --full or statusline runs render in the picker — aligned with the same MaxPrNumber ratchet width wt list uses, and with zero network access.

A valid cache entry renders as-is. An entry whose TTL passed or whose branch head moved keeps its PR/MR number dimmed: the number still identifies the PR when the pipeline color may be outdated. Expired entries without a number are dropped. The CI column is allocated only when some row had a usable entry, and rows the cache can't fill resolve to blank rather than a pending placeholder, since no task repaints them.

Key files

• src/config/expansion.rs, src/config/user/sections.rs, src/git/repository/config.rs — column resolution, the template environment, and the bulk git-config snapshot.
• src/commands/list/layout.rs, src/commands/list/render.rs — column width allocation and cell rendering.
• src/commands/list/ci_status/mod.rs — populate_from_cache, the cache-only fill.
• src/commands/picker/mod.rs — the dry-run dump (WORKTRUNK_PICKER_DRY_RUN) that makes picker row content assertable in tests.

Testing

Integration tests cover both features: custom columns (table render, JSON output, empty-column drop, invalid-template error) and the picker (cached PR numbers appear in the dry-run dump, uncached branches stay blank). Unit tests cover the cache-population logic (valid, expired-with-number, head-moved, dropped). Verified against the full cargo run -- hook pre-merge --yes gate locally.

This was written by Claude Code on behalf of max

[worktrunk-bot]

The two features are cleanly separated, the docstrings are excellent, and the test coverage is thorough — the cache-population state machine, the layout/width measurement, the vars snapshot parity, and the picker dry-run dump are all well exercised. Two things to flag before this lands.

Required test (linux) is red — two of the new snapshots are stale

test_list_custom_columns and test_list_custom_column_empty_everywhere_dropped fail in CI (and in affected tests (linux/macos, advisory) and code-coverage — same root cause; the sibling …_json and …_invalid_template tests pass). The diff is a trailing ␛[0m reset at the end of every row: the actual output emits one, the committed .snap files don't.

   4 │-…␛[1mMessage          ← committed snapshot: no trailing reset
   4 │+…␛[1mMessage␛[0m       ← actual CI output

Every existing wide list snapshot already ends each row with that reset (e.g. list_config_malformed_system_config_non_section_field.snap has …␛[2mInitial commit␛[0m), so the rendering is consistent — the two new files were just captured without it. Regenerating with cargo insta test --accept (limited to those two) should fix all four checks. Worth a glance at why the local pre-merge gate passed with these committed: it suggests the .snap files diverged from a local insta accept after a later change. Want me to push the regenerated snapshots?

[list.columns] collides with open PR #3065

#3065 (open, by @Faria22) also introduces a [list.columns] user-config section, but as a flat map of built-in-column visibility toggles (ci = false, path = false, …). This PR makes [list.columns.<Header>] a table of custom template columns. The two are mutually exclusive serde shapes for the same documented key — a user can't express both, and whichever merges second breaks the other's config examples. Since the config file format is a protected interface, it's worth deciding which design owns [list.columns] (or namespacing one, e.g. [list.custom-columns]) before either lands, rather than after.

Everything else read clean: the MaxPrNumber ratchet heals the picker's CI-column width on every render (worst case a one-render # degrade, per its docstring), the Custom(u8) 256-cap guards the index aliasing, and the column_display_index tuple change has both call sites updated.

[worktrunk-bot]

codecov/patch failed at 96.26% (project 97.44%). Per CLAUDE.md this is a merge gate. Dismissing the approval until the gap is addressed.

Most of the misses are in src/commands/list/custom_columns.rs and src/commands/list/render.rs. Three of the eight uncovered spans are testable and worth picking up; the rest are "unreachable after validation" fallbacks that read fine as-is.

Testable

• custom_columns.rs:141–151 — item.worktree_data().…unwrap_or_default(), the branch-only-item arm of the worktree-identity build. test_list_custom_columns only stresses worktree-attached rows; a template that references {{ worktree_name }} (so needs_worktree is true) rendered against a branch with no worktree would hit this.
• render.rs:321–329 — the ColumnKind::Custom(i) arm of render_skeleton_row. None of the snapshot tests render a skeleton, so this path never runs in CI even though it's the path real users see on the first ~50ms of wt list. Probably needs a WORKTRUNK_SKELETON_ONLY / pre-skeleton dump test (or extending the picker dry-run shape used in test_picker_*).
• collect/mod.rs:1069–1070 — the emit_warning(...); Vec::new() arm in match resolve_custom_columns(...) when a progressive handler is present. A picker dry-run with a deliberately invalid [list.custom-columns.X].template would exercise it, mirroring test_list_custom_column_invalid_template on the picker side.

Fine to leave

• custom_columns.rs:115–117 and :172 — parse-after-validation fallback (unreachable in practice, per the inline comment) and its matching None-template render arm.
• columns.rs:46 — ColumnKind::Custom(_) => "" in header(); layout substitutes the resolved name, so the bare arm is structural.
• ci_status/mod.rs:628,634 — populate_from_cache early returns (repo_path error, branch missing).
• git/repository/config.rs:211 — values.last() empty fallback in all_vars_from_snapshot.

Happy to push a commit adding the three tests if useful.

codecov/patch failed — see follow-up review for testable gaps