mise lock writes to wrong lockfile when mise.local.toml exists

[jstriebel]

Problem

mise lock writes the lockfile matching the highest priority config (mise.local.lock) rather than the config that defines the tools (mise.toml).

Reproduction

mkdir test && cd test

cat > mise.toml << 'EOF'
[tools]
jq = "latest"
EOF

cat > mise.local.toml << 'EOF'
[env]
FOO = "bar"
EOF

mise lock
ls mise*.lock
# Output: mise.local.lock  ← mise.lock not created

Also, when when tools are in both files, everything goes into mise.local.lock.

Why this matters

Common pattern:

• mise.toml - committed, defines shared tools
• mise.local.toml - gitignored, personal overrides

Current behavior silently writes and reads gitignored mise.local.lock, so team members never get locked versions.

Suggested behavior

One lockfile per config file - tools defined in mise.toml → mise.lock, tools in mise.local.toml → mise.local.lock. This aligns with gitignore conventions and keeps shared tools locked in a committed file.

---

tested with mise 2026.2.3 linux-x64

[cheinema]

Duplicate of #8000

[jstriebel]

Thanks for the catch, missed this one due to timing. Added context there, too, marking this one as resolved.