chore(release): publish 0.5.0

Author: timrichardson

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased
+## 0.5.0
 
 - move installation and upgrade guidance near the top of the README and recommend explicit release versions because `@latest` does not update an existing installation
 

README.md

@@ -6,21 +6,21 @@
 
 ## Install / upgrade
 
-The current release is `0.4.1`. The same npm package supports OpenCode V1 and OpenCode V2: V1 loads the package root, while V2 selects the native `./server` export.
+The current release is `0.5.0`. The same npm package supports OpenCode V1 and OpenCode V2: V1 loads the package root, while V2 selects the native `./server` export.
 
 ### Support OpenCode V1 and V2 together
 
 Install or upgrade the pinned release globally with OpenCode V1's plugin installer:
 
 ```bash
-opencode plugin opencode-planner@0.4.1 --global --force
+opencode plugin opencode-planner@0.5.0 --global --force
 ```
 
 This writes the singular V1-compatible field to the global `opencode.json(c)`. You can configure the same entry manually:
 
 ```json
 {
-  "plugin": ["opencode-planner@0.4.1"]
+  "plugin": ["opencode-planner@0.5.0"]
 }
 ```
 
@@ -32,7 +32,7 @@ If you no longer use OpenCode V1, use only the plural V2 field:
 
 ```json
 {
-  "plugins": ["opencode-planner@0.4.1"]
+  "plugins": ["opencode-planner@0.5.0"]
 }
 ```
 
@@ -68,7 +68,7 @@ When you no longer need OpenCode V1, rename the singular `plugin` field to the p
 
 ```json
 {
-  "plugins": ["opencode-planner@0.4.1"]
+  "plugins": ["opencode-planner@0.5.0"]
 }
 ```
 

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-planner",
-  "version": "0.4.1",
+  "version": "0.5.0",
   "description": "OpenCode plugin emulating Experimental Planning Mode and sending plan to configured editor for acceptance or editing",
   "type": "module",
   "main": "./index.js",