fix(nix): give the devShell every tool the test suite shells out to

[max-sixty]

devShells.default listed bash, zsh, fish under a # For shell integration tests comment, but that feature drives two more shells and shells out to jq. So nix develop could not run --features shell-integration-tests, which is what the repo's own gate runs (.config/wt.toml → cargo insta test … --all-features). This adds nushell, powershell and jq.

The same dependency claim was stated, wrongly, in three other places. All four now name the real set:

Where	Was	Now
flake.nix devShell	bash, zsh, fish	+ nushell, powershell, jq
Cargo.toml feature comment	bash, zsh, fish	+ nu, pwsh, jq
tests/CLAUDE.md	bash/zsh/fish + PTY	+ nushell, pwsh, jq
docs/content/faq.md	bash, zsh, fish, nushell	+ pwsh, jq

flake.nix also referenced a CLAUDE.md → "Shell/PTY Integration Tests" heading that exists nowhere in the repo; it now points at the section that does.

Verification

There is no nix on the machine this was written on, so the two claims were checked separately rather than by entering the shell.

Is the list right? A symlink farm modelling a devShell's PATH — nixpkgs stdenv's own tools plus the candidate list, and nothing else — with the full --all-features suite run under it. configure_pty_command propagates the test process's PATH into PTY children, so this reaches the shell tests.

Runs (the control is what makes the failures attributable)

PATH	Result
Full ambient PATH (control)	4572 passed, 0 failed
stdenv + every tool the suite needs	4572 passed, 0 failed
…minus pwsh	3 shell_powershell tests fail
…minus jq	test_worktree_remove_hook_skips_path_holding_no_worktree fails
…minus python3 / lsof / ps	6 failed: 2 for_each/post_start (python3), 1 remove::test_remove_reap_kills_process (lsof), 3 pgid/process-probe (ps)

The control run matters: it establishes that every failure above is caused by the withheld tool rather than by a local flake.

The last row is about what the suite needs, not what the shell was missing — see the correction below.

Does the flake still evaluate? nixos/nix in a container, evaluating devShells.<system>.default for all four systems flake-utils covers, against unmodified main as a control. All four evaluate, and every tool resolves on each.

Not verified: nothing here was built, only evaluated, so a package that evaluates but fails to build would not have been caught. The nightly nix-flake job runs nix flake check on PRs touching flake.nix, which covers that on x86_64-linux.

A correction: python3/procps/lsof were never missing

The first version of this PR also added python3, procps and lsof, claiming the shell could not run a plain cargo test. That was wrong, and worktrunk-bot caught it.

craneLib.devShell sets inputsFrom = builtins.attrValues checks ++ inputsFrom, and mkShell folds each inputsFrom derivation's nativeBuildInputs into its own. checks includes worktrunk-tests, whose nativeBuildInputs already carry git, python3, procps and lsof — so the devShell inherited all four. Evaluating the unmodified main tree confirms it: its x86_64-linux devShell derivation already contains python3, procps and lsof, and contains no nushell, powershell or jq.

The symlink farm could not have caught this: it modelled stdenv plus the literal packages list, so crane's inherited inputs were invisible to it by construction. The experiment established what the suite needs; it said nothing about what the shell already had.

Those three lines are dropped. git remains listed in both places — pre-existing, and left alone here.

A guard I added and then removed

powershell first went in behind lib.meta.availableOn, because nixos-unstable's PowerShell has no x86_64-darwin source. Testing that guard against nixpkgs HEAD showed the actual cause: nixpkgs 26.11 dropped Intel macOS wholesale, so the entire flake fails to evaluate there regardless of the guard. On every system nixpkgs still supports, PowerShell has a build — the guard protected against nothing, and its comment justified it with the wrong mechanism. Removed; powershell is listed plainly with the other shells.

Notes

task setup-web checks for bash zsh fish nu and not pwsh/jq — the same gap in a different environment, left alone here since its install mechanics are unrelated.

This was written by Claude Code on behalf of max-sixty

[worktrunk-bot]

The shell and jq additions check out: shell_powershell.rs is #![cfg(feature = "shell-integration-tests")], the jq-piping hook test at tests/integration_tests/config_show.rs is under the same gate, and the tests/CLAUDE.md → "Feature Flags, Not Runtime Skipping" heading the flake now points at exists. One note on the other three packages, inline.