[linghengqian]

Fixes #737: these are the last two unticked items of the issue (section 5, smaller items).

A real Nushell in CI

The vfox.nu that vfox generates was only checked as text. Whether vfox env sees the __VFOX_ORIG_PATH that the script records shows only in the order of PATH that a real session ends up with.

TestNushellSessionUsesTheBaselineItRecorded builds vfox, generates the configuration the documented way (vfox activate nushell $nu.default-config-dir), starts nu on it, and checks the PATH of the session when it starts and after a directory was put in front and the prompt hook ran, for the default (baseline) and for the legacy mode. Deleting the line that records the baseline, or moving it behind the first env call, makes it fail.

The new nushell job installs Nushell 0.117.0 from its release archive and checks the SHA-256 of the archive first (the digest is listed on the release page; bump both together). The test skips when nu is not installed, and the job sets VFOX_TEST_NUSHELL=1 so that an installation that went wrong fails instead of skipping.

If #720 lands, this job runs its template change against a real nu.

The CLI tests on Windows

cliFixture skipped on Windows, so the junction, .cmd and PATH separator cases had no end-to-end coverage. It runs there now:

• USERPROFILE is set (os.UserHomeDir reads it, not HOME), commands are .cmd files (Windows only runs files with a PATHEXT extension), PATH is spelled the way each shell gets it (; natively, /c/... for the bash hook), links are junctions and hard links (no privilege needed), the short name in TEMP is resolved, and directories are named with os.MkdirTemp instead of the clock.
• Selecting an SDK globally writes the user's PATH in the registry on Windows, so the fixture runs there only with VFOX_TEST_WINDOWS_REGISTRY=1, which the build job sets. Someone who runs go test ./... on a Windows machine skips these tests, as before.
• Two tests are new: the PowerShell spelling of PATH (all platforms), and a baseline in the two forms that Git Bash hands to a native program (Windows only; the situation of [BUG]: On Windows, vfox use java@X doesn't change java when a JDK is in the system PATH and a global SDK is set #732).
• TestInstallCommandUseOnShellWithoutHookSaysWhatFailed is skipped on Windows: without a hook use falls back to the global scope and opens a shell.

AGENTS.md says how to write CLI tests that work there.

Verification

• Linux: go test ./cmd/commands with Nushell 0.117.0 on PATH, also with -race and with -shuffle=on -count=3.
• CI on a fork branch with this commit: every job passes, the new nushell job included (run). In its Windows build job cmd/commands took 13.9 s at 52.3% coverage (Linux: 1.9 s at 54.5%).
• What ran on windows-latest, from a throwaway fork branch (verbose run, which fails on purpose after printing every test; the real exit code was 0): 192 tests and subtests, 179 passed, 13 skipped, none failed. The skips are the Unix-only environment fixture in env_test.go, the no-hook install -u test, and the Nushell test. That branch carries the same tests. It differs in that the gate of the fixture also opens under GITHUB_ACTIONS (it could not carry the workflow change) and in an extra file that prints the tests. Its plain runs of cmd/commands took 10.6 s and 14.6 s, both at the same 52.3% coverage.

Not covered: Nushell runs on Linux only, so the Path and ; branch of the template for Windows is not exercised.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.21%. Comparing base (4754dfd) to head (e5ddf26).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #753   +/-   ##
=======================================
  Coverage   56.21%   56.21%           
=======================================
  Files         115      115           
  Lines        8576     8576           
=======================================
  Hits         4821     4821           
  Misses       3291     3291           
  Partials      464      464           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[linghengqian]

CC @version-fox/vfox-committers @version-fox/vfox-maintainers . Please help review it.