release: 0.2.0

[kboshold]

What

Bumps package.json to 0.2.0.

Why

Step 1 of the release runbook. The workflow now triggers on a published GitHub Release and checks out the tag, so the version has to be on main before v0.2.0 is tagged. A tag that disagrees with package.json fails the run before it installs anything.

0.2.0 rather than 0.1.1: the default config location moved to streamctl.config.ts, which is a new feature with no removals. 0.1.0 is already taken on the registry.

Merging this does not publish. Tagging the merge commit and publishing the GitHub Release does.

[kboshold]

Superseded. The sibling repos bump with a local npm version pushed straight to main (verified: ssm-secrets 3c70167b and nuxt-auth 6daf2ad0 are single-parent, package.json-only, with zero associated PRs, and each tag points at that commit). Routing the bump through a PR also splits the bump from the tag, which npm version does atomically. Runbook corrected to match.