[talakbairam]

What

Release 0.2.0: raises the version to 0.2.0 in package.json and package-lock.json, and adds the [0.2.0] - 2026-10-21 section to CHANGELOG.md.

The section covers everything that is in develop and not yet in master:

• the Settings page and the Tags & Categories page, and the move of the webview pages to webview/ (Add Settings and Tags & Categories pages and move webview pages to webview #10)
• Copy as Encrypted Text and Decrypt Text from Clipboard (Add Copy as Encrypted Text and Decrypt Text from Clipboard #9)
• the development tool updates (eslint, typescript-eslint, prettier, vsce, @types/node)

Why

release.yml runs when develop is merged into master. It stops when the tag for the version in package.json exists already (v0.1.0 does) and when CHANGELOG.md has no dated section for that version. This PR makes both true before the merge into master. New features, no breaking change: minor version (0.2.0).

Testing

Only the version and the changelog change, so there is no code to run. The version was raised with npm version 0.2.0 --no-git-tag-version, so the lockfile matches. The release workflow has not been run; it runs after develop is merged into master.

Impact

• No code, setting or command changes.
• After the merge into master, release.yml creates the tag v0.2.0 and attaches the .vsix to the release. It does not publish to the Marketplace.

Notes

• Files: CHANGELOG.md, package.json, package-lock.json.
• Next step after this PR: a PR develop → master.