fix(nushell/windows): Fix $env.PATH getting converted to a string

[zackyancey]

This addresses the issue in discussion #5472.

Mise on nushell on windows doesn't properly convert the path to a nushell-native list. Most of the time this works fine, as long as the path stays a string. However, if anything else adds a value to the path (like manually activating a python venv), you end up with a list of 2 items: the big, ; delimited string that was $env.PATH, and one entry for whatever was just added (now the only valid item in the path list).

The problem comes from this function in the activate script:

def --env "update-env" [] {
     # ...
     if $var.name == 'PATH' {
        $env.PATH = ($var.value | split row (char esep))
     } else {
    # ...
}

$env.PATH is case-insensitive in nushell 1 (actually, all environment variables are, regardless of OS 2). Mise matches whatever capitalization is in use at run time 3, which for windows is Path. For the sake of the update hook though, in case something changes the capitalization of $env.PATH between activating mise and some later run of the hook, it's probably just better to do this comparison in a case-insensitive way.

[Copilot]

Pull Request Overview

This PR fixes an issue where mise's nushell integration on Windows doesn't properly handle the PATH environment variable when it has different capitalization. The fix ensures that PATH comparison is case-insensitive by converting the variable name to uppercase before comparison.

• Implements case-insensitive PATH comparison in the nushell update-env function
• Updates both the source code and corresponding test snapshot

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/shell/nushell.rs	Updates the PATH comparison to be case-insensitive using str upcase
src/shell/snapshots/mise__shell__nushell__tests__hook_init.snap	Updates test snapshot to reflect the case-insensitive PATH comparison

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}