chore: bump version to 0.0.2 for protean 0.0.2 (#92)

- protean 0.0.2 is out; the console tag v0.0.2 marks the state verified
  against it, and the tag must match package.json, as v0.0.1 did
- the one console-facing wire change in protean 0.0.2 is the `ready` ack,
  which the console already reads (#63): its seven fields match
  StreamReady one for one; the rest of that release is MCP-only
- the changelog note still said no release was tagged, which stopped being
  true at v0.0.1; it now says what the tags mean

Author: htcom-code

CHANGELOG.md

@@ -86,7 +86,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   readable on hover in both light and dark themes.
 
 ### Notes
-- No tagged release yet (`0.0.1`). This section tracks work toward the first
-  release; move entries under a versioned heading when one is cut.
+- Version tags mark which protean release the console was verified against:
+  `v0.0.1` for protean 0.0.1, `v0.0.2` for protean 0.0.2. Entries are not yet
+  split per tag; this section still collects everything on `main`.
 
 [Unreleased]: https://github.com/htcom-code/protean-console/commits/main

package-lock.json

@@ -1,7 +1,7 @@
 {
   "name": "protean-console",
   "private": true,
-  "version": "0.0.1",
+  "version": "0.0.2",
   "license": "MIT",
   "author": "htjulia <htjulia1@gmail.com>",
   "repository": {