Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a clear, informative header comment to all mise generated lockfiles. This change aims to prevent unintended manual modifications by both automated agents and human users, by explicitly stating that the files are auto-generated and should not be edited. This improves the maintainability and reliability of mise projects by ensuring lockfiles are treated as machine-managed artifacts.

Highlights

• Lockfile Header: A header comment was added to all generated mise lockfiles to explicitly state they are auto-generated and should not be manually edited.
• Test Updates: End-to-end tests were updated to assert the presence of the new lockfile header in the generated files.

Greptile Summary

This PR prepends a 4-line comment block to every generated mise.lock file explaining that it is auto-generated and should not be edited manually, targeting both AI agents and human contributors who might otherwise modify it by hand.

Key changes:

• src/lockfile.rs — After TOML serialization and formatting, the save() function prepends the header string via format!() before the atomic write. Placement after format() is intentional and correct: the toml_edit-based formatter would not strip top-level comments, but inserting before ensures the comment always leads the file regardless of TOML tooling.
• e2e/assert.sh — A shared LOCKFILE_HEADER variable is defined once and reused across all test scripts (sourced before every test by run_test).
• e2e/cli/test_use_latest and e2e/lockfile/test_lockfile_use — All 7 exact-match (assert "cat mise.lock") assertions are updated. The remaining tests in the broader e2e suite (which use assert_contains / assert_not_contains) require no changes.
• Backward-compatible: TOML's native #-comment support means Lockfile::read() parses files with or without the header without any code changes. Existing lockfiles without a header will acquire it on the next mise use or mise lock run.

Confidence Score: 5/5

• This PR is safe to merge — the change is purely additive, backward-compatible, and well-tested.
• The implementation is straightforward: a fixed string is prepended to the file content before writing, after all TOML processing is complete. TOML's native comment syntax means the parser requires zero changes. All exact-match e2e tests were correctly updated, and every other lockfile test in the suite uses substring matching which is unaffected by the new header. No logic paths, error handling, or public APIs are altered.
• No files require special attention.

Sequence Diagram

sequenceDiagram
    participant User as User / Agent
    participant CLI as mise CLI
    participant Lockfile as Lockfile::save()
    participant FS as mise.lock (file)

    User->>CLI: mise use / mise lock
    CLI->>Lockfile: save(path)
    Lockfile->>Lockfile: Build TOML table (tools, conda-packages)
    Lockfile->>Lockfile: toml::to_string_pretty()
    Lockfile->>Lockfile: format() — sort keys, inline platform tables
    Lockfile->>Lockfile: Prepend header comment block
    Note over Lockfile: "# This file is auto-generated by mise.\n# It is not intended to be edited manually.\n..."
    Lockfile->>FS: Atomic write (temp file → rename)

    User->>CLI: mise install / mise ls
    CLI->>Lockfile: Lockfile::read(path)
    Lockfile->>FS: Read file contents
    FS-->>Lockfile: content (with header comments)
    Lockfile->>Lockfile: toml::from_str() — TOML ignores # comments natively
    Lockfile-->>CLI: Parsed Lockfile struct

_{Last reviewed commit: d2cf116}

Okay, I didn't shellcheck. You caught me. (One sec.)

Suggestion: simplify the header to a single line with @generated (which GitHub and AI agents recognize as machine-generated):

# @generated - this file is auto-generated by `mise lock` https://mise.jdx.dev/dev-tools/mise-lock.html

This comment was generated by Claude Code.

Oh, interesting! There might be some other cool GitHub stuff we can do with linguist to improve how these lockfiles are rendered in the repo web UI: https://github.com/github-linguist/linguist/blob/d403bc76daf1d83d97f7ee40cd64957cadc33706/lib/linguist/generated.rb#L53-L59