fix(list): keep [list] columns out of the --format json plan

[worktrunk-bot]

Closes the [list] columns half of #3787, per the call in this comment: JSON always emits the same shape, and list.columns only affects the actual columns.

Before, --format json planned all_columns (source Default) unioned with the selection's forced-on columns, so the selection reached JSON in one direction only — it couldn't narrow the emitted fields, but a listed ci did force the forge fetch on without --full. That made a presentation setting decide whether a machine-readable call talks to GitHub, which is the thing the Neovim plugin in #3787 had to pin --config-set 'list.columns=[…]' against. Now the JSON branch plans all_columns alone; --full is the only switch for the gated data, and it's the one a caller controls.

The table and the wt switch picker are untouched — a listed ci still renders the CI column without --full, and the picker still unions the selection in so its table matches wt list's.

Only ci and summary are affected: every other column is ungated, so full_plan() already covered them, and custom columns require no background task.

For the release note — this changes schema 1 too. A caller with [list] columns = […, "ci"] and no --full used to get the ci object in schema-1 JSON and now won't; schema 1 has no collected envelope to say why. The schema-1 ci row already documented `--full` only, so the docs get more accurate, but the observable output changes for anyone who was relying on the forcing path. Schema 2 reports the same narrowing through collected.ci.

Docs updated in after_long_help (the [list] columns section plus the schema-2 pr, summary, and checks rows — summary now names --full alongside [list] summary = true, and checks names the --full gate it shares with pr), with the generated mirrors, dev/config.example.toml, and the --help snapshots regenerated. The CLAUDE.md network inventory and the collect planning comment now record the exemption too.

Test

test_list_json_columns_selection_does_not_force_ci in tests/integration_tests/list_config.rs asserts schema 2's collected.ci across three configs: unset (false), columns = ["branch", "ci"] without --full (false — the regression this fixes), and the same with --full (true). collected records what the plan requested rather than what a fetch returned, so the test needs no forge and no gh on PATH. It sits next to test_list_json_ignores_columns_selection, which owns the narrowing direction, and test_list_config_listed_column_overrides_full_gate, which owns the table's forcing behaviour and still passes unchanged.

Ran locally: full cargo test --test integration and cargo test --lib --bins, plus cargo clippy --all-targets and cargo fmt --check. One unrelated failure, test_copy_ignored_preserves_file_executable_permissions, is a umask artifact of this sandbox (expects 0644, the runner's umask 002 produces 0664); it touches no code in this diff.

The docs-row follow-up in df5c238 re-ran cargo test --test integration -- test_help test_docs_are_in_sync (48 passed) and cargo fmt --check.

[worktrunk-bot]

The planning change itself is tight — the new three-way fork is behaviour-identical to the old prune_to_selection boolean everywhere except the JSON-with-a-selection case it means to change, required_tasks_for_render returns a HashSet so the picker's extend still dedups, and the layout (which is still computed with selected: Some(...) while tasks is now the unnarrowed full_plan()) is only read behind progressive_table/progressive_handler guards, so JSON can't observe the mismatch. wt list statusline builds its own plan through CollectOptions::for_columns, so it's untouched.

One doc gap left in the table this PR is tightening, plus a note below.

Worth calling out for the release note: this also changes schema 1. A caller with [list] columns = [..., "ci"] and no --full used to get the ci object in schema-1 JSON and now won't, and schema 1 has no collected envelope to say so. The schema-1 ci row already documented `--full` only, so the docs get more accurate — but the observable output changes for anyone who was relying on the forcing path.

[max-sixty]

this could we 50% as long

[worktrunk-bot]

Cut it entirely in 51c8121 — the scope now lives in the columns definition at the top of the section: "columns selects and orders the columns the wt list table and the wt switch picker render; --format json ignores it and always emits every field."

Net against the PR base, this section is 4 lines shorter than it was before the PR.

[max-sixty]

way way too verbose, all this section

[worktrunk-bot]

Trimmed in 51c8121. The [list] columns annotations are gone from every row — the rows now only name --full, which is the gate a JSON caller actually controls:

row	now
pr	collected with --full
checks	collected with --full
summary	needs --full, [list] summary = true, and a [commit.generation] command

pr is shorter than it was before the PR; summary gains the two gates it was missing (a caller who set only [list] summary = true got no field).

[max-sixty]

there is no need to list this everywhere, just say in the columns defn that it's for the wt list output; the docs should get simpler

[worktrunk-bot]

Done in 51c8121 — the caveat is stated once, in the columns definition, and removed from everywhere else it had spread to.

The definition now opens with the scope:

columns selects and orders the columns the wt list table and the wt switch picker render; --format json ignores it and always emits every field.

Removed: the six-line paragraph at the end of the columns section, the "[list] columns doesn't reach JSON" parentheticals on the pr and summary rows, and the trailing sentences in CLAUDE.md and the two module comments. Net −40 lines against the previous push, and both doc sections are now shorter than they were before this PR.

The code change is unchanged; test_docs_are_in_sync, test_help, list_config, and clippy pass locally.

CI on 51c81211: test (linux), test (macos), fast-checks, check-docs, lint, code-coverage, and codecov/patch all pass. test (windows) (required) was still running when my poll budget ran out — unverified.

[worktrunk-bot]

One gap left, in the doc this PR is most about.

Collected's doc comment in src/commands/list/model/item.rs still names the gate this PR removes — "Fact families whose collection is gated (--full, [list] summary, a listed ci/summary column)". Collected is built only from tasks (collect/mod.rs), and the JSON plan is now full_plan() alone, which passes ColumnSource::Default — so listed is always false there and a listed column can no longer set collected.ci/collected.summary.

That comment isn't internal: schemars ships it verbatim into docs/static/schema/list-v2.json, which test_docs_are_in_sync regenerates from wt list --print-schema and which after_long_help points JSON consumers at ("A JSON Schema for the envelope is published at worktrunk.dev/schema/list-v2.json"). So the published machine-readable contract currently advertises the exact forcing path #3787 asked to remove — to the same audience the PR is for.

The fix is to drop the clause rather than explain it, which is also a line shorter. Pushing that now, with the schema mirror.

Everything else checks out: the three-way fork is behaviour-identical to the old prune_to_selection boolean in all three unchanged cases (empty selection still lands on full_plan(), since listed_plan() over an empty selection is the empty set), CiStatus and Summary really are the only gated columns (Url's gate is data-source, identical under either source), and JSON's display.columns comes from columns_map(custom_columns, …) rather than the layout, so the "always emits every field" claim holds for custom columns too.