[dsfbug]

Release preparation

• Bump package.json and both root lockfile versions from 0.1.1 to 0.1.2.
• Update CHANGELOG.md for the macOS/VS Code path fix (Fix VS Code installation path detection on macOS #4), Linux/Windows/macOS CI and tests (Add VS Code extension CI and dependency updates #9), action runtime updates (build(deps): bump the actions group with 3 updates #10), and security dependency fixes (build(deps): bump picomatch from 2.3.1 to 2.3.2 #5, build(deps-dev): bump js-yaml from 4.1.1 to 4.3.2 #6, build(deps-dev): bump flatted from 3.3.3 to 3.4.4 #7, build(deps-dev): bump brace-expansion from 1.1.12 to 1.1.21 #8).
• Update README.md with macOS troubleshooting, remaining real-install caveats, and the manual master branch build command: npm ci, npm test, npm run package.

Validation

Clean install, compile, all four tests and VSIX packaging passed locally on the release content atop master 7afaf47. The generated package reports version 0.1.2 and includes the updated changelog. Hosted PR checks will run after creation.

Scope

Publishing stays manual: no Marketplace upload, GitHub release/tag, token, or automatic publishing workflow. Please review before merging, then pull master (the repository's default branch) and build the VSIX.

PR #11 is excluded: its grouped TypeScript 7/typescript-eslint 8 upgrade fails peer dependency resolution (TypeScript must be below 6.1). No forced install or major dependency upgrades are included.

Issues #1 and #3 stay open until the updated extension's background installation is tested on real macOS. The path regression tests do not prove actual install permissions or a full runtime fix.