<!--
Thanks for contributing to Vim!

Please read CONTRIBUTING.md if you have not already.  The comments below
are not shown in the pull request; delete any section that does not apply.

Write the commit message in this form:

    Short description of the problem

    Problem:  One sentence: what is wrong, from the user's point of view.
    Solution: One sentence: what this change does about it (Your Name).

    Anything longer (mechanism, benchmark numbers, why an alternative
    was rejected) goes here.

    fixes:   #number
    related: #number

For a pull request with a single commit, GitHub uses the first line as
the title and the rest as the start of this description.

For changes to runtime files the first line starts with one of:

    runtime(doc): for a documentation update
    translation(isocode): translations into language
    runtime(lang): runtime file changes for language lang
    filetype: for changes to filetype detection

Add "fixes: #number" when this fixes a reported issue, and
"related: #number" when it references another issue or pull request.
"closes: #number" is added when merging.
-->

### AI assistance

<!--
Please disclose AI involvement by adding the trailer
  "Assisted-by: AI tool".
-->

- [ ] AI involvement is disclosed in the commit message
- [ ] No AI was used

### Checklist

- [ ] The commit message follows the Problem/Solution form above
- [ ] `Signed-off-by:` trailer is present (`git commit -s`), recommended but not required

#### Tests

- [ ] Tests were added
- [ ] Existing tests cover the change
- [ ] The change cannot be tested (explain below)

#### Documentation

- [ ] Documentation under `runtime/doc/` was updated
- [ ] No documentation update is needed

### Anything reviewers should know

<!--
For example: a behavior change users may notice, a platform you could
not test on, or an assumption the change relies on.
-->