chore(release): 0.9.2

[kkdev92]

Releases 0.9.2: sharp 0.35.5 and the extension on @kkdev92/vscode-ext-kit 7.1.0. A patch — a dependency update and a backward-compatible kit update, with nothing added.

What's in it

• version 0.9.2 (npm version, so the lock's root follows).
• CHANGELOG: the [Unreleased] entries become [0.9.2] - 2026-10-04, with the compare links: sharp 0.35.4 → 0.35.5 (libvips 8.18.6 → 8.18.7), the kit ^7.0.0 → ^7.1.0, the clipshot.enabled context key no longer set, and the save-directory warning for a drive-relative path or a leading backslash.

Since v0.9.1, what reaches the VSIX is #89 (sharp) and #92 (the kit); #93 changed SECURITY.md and a comment, and the rest is development dependencies.

Verification

• npm run verify on this branch: lint, compile, typecheck:test, test:coverage (491 tests; lines 90.31%, branches 79.23%) and test:e2e (13 passing, exit code 0, VS Code 1.140.0).
• vsce package --target win32-arm64 from main in a clean worktree after npm ci, and verify-vsix.mjs win32-arm64: 116 files, sharp 0.35.5 with libvips-cpp-8.18.7.dll.
• That VSIX, installed in an isolated VS Code with a real image on the clipboard: the notice on first start that clipshot.pasteImage was added to terminal.integrated.commandsToSkipShell; Ctrl+Shift+V in a Markdown editor (the link and an 800×600 PNG), with two cursors (one image, inserted at both), and with the integrated terminal focused (the path typed, not run); JPEG and WebP resized to 400×300 through sharp; clipshot.logLevel at silent, warn and info; a configuration warning for C:images; nothing saved with clipshot.enabled off.
• The same steps on the published 0.9.1 give the same results, except the C:images warning, which 0.9.1 does not give.

🤖 Generated with Claude Code