[SebTardif]

Summary

Align the extension with Patchloom CLI 0.37.5. The recommended version is 0.37.5. The minimum stays 0.3.0. The full MCP inventory is still 66 tools and the core pack is still 12. The Windows release zip still has patchloom.exe at the archive root.

Why

GitHub's latest Patchloom release is patchloom-v0.37.5 (2026-10-19). The extension still described 0.37.1 as current. Releases 0.37.2 through 0.37.5 change results people see from existing Quick Actions: a regex group the pattern does not contain is refused, doc move onto an existing key is already_exists, ini notes stay, padded integers are stored as strings, unquoted YAML yes/no/on/off stay strings, and upsert-bullet stops before a child heading. A TOML integer above the signed 64-bit maximum stays bare digits starting at 0.37.2.

Verification

Probed the 0.37.5 macOS arm64 release binary: tools/list returned 66 names on the full surface and 12 on PATCHLOOM_MCP_SURFACE=core. server_info reported version 0.37.5 and tool_count 66. The Windows x86_64 zip lists patchloom.exe at the archive root.

Live commands on that binary:

• replace --regex '(a)' --new '$9' is invalid_input and leaves xa unchanged. A literal replace still writes $9.
• doc move onto an existing key is already_exists and does not write.
• doc set on port = 8080 ; primary writes port = 9090 ; primary.
• doc set of 01 writes id = "01". 9223372036854775808 stays bare digits.
• doc get of unquoted YAML yes returns the string yes.
• md upsert-bullet under # List inserts - beta before ## Other.
• Two SEARCH/REPLACE matches are ambiguous. The message names --replace-all, replace_all: true, and unique: false.

npm run check: 481 passed, line coverage 92.89%, vsix packaged.

Checklist

• All commits in this pull request are signed off with git commit -s
• I ran npm run check and it passes
• I updated docs if user-facing behavior changed
• I am contributing this work under the repository license (MIT)