release 0.1.0-beta.2

Bump src/version.ts and package.json together; release.ts refuses to build if
they disagree, or if the git tag disagrees with either.

Also updates the version shown in the README and MCP sample headers, and the
example in development.md so it points at the next release rather than this one.

README.md

@@ -46,7 +46,7 @@ from the models that endpoint actually reports. Settings land in
 `~/.shiro-neko/config.json`. Run `/provider` any time to change them.
 
 ```
-shiro-neko 0.1.0-beta.1  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.2  openai/gpt-5  session 0193ab2c
 agent: default  thinking: medium
 cwd: /home/you/project
 skills: debug, refactor, review, test

ROADMAP.md

@@ -49,7 +49,7 @@ reported rather than fatal.
 **Distribution** — five-platform cross-compiled binaries, checksums, install scripts, CI on
 three operating systems, tag-driven releases.
 
-### 0.1.0-beta.2 (unreleased)
+### 0.1.0-beta.2
 
 Fourteen built-in tools, up from six, with sets so the schema cost stays controllable.
 

docs/development.md

@@ -124,7 +124,7 @@ disagrees with either:
 
 ```
 $ GITHUB_REF_NAME=v9.9.9 bun run release
-tag v9.9.9 does not match src/version.ts (0.1.0-beta.1). Bump the version or retag.
+tag v9.9.9 does not match src/version.ts (0.1.0-beta.2). Bump the version or retag.
 ```
 
 A binary reporting the wrong version is worse than a failed release.
@@ -133,8 +133,8 @@ To cut one:
 
 ```bash
 # bump src/version.ts and package.json to the same value
-git commit -am "release 0.1.0-beta.2"
-git tag v0.1.0-beta.2
+git commit -am "release 0.1.0-beta.3"
+git tag v0.1.0-beta.3
 git push --follow-tags
 ```
 

docs/mcp.md

@@ -54,7 +54,7 @@ one tool for the session.
 A server that fails to start is reported and the session continues:
 
 ```
-shiro-neko 0.1.0-beta.1  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.2  openai/gpt-5  session 0193ab2c
 mcp: 4 tools
 mcp db failed: spawn python ENOENT
 ```

package.json

@@ -1,6 +1,6 @@
 {
   "name": "shiro-neko",
-  "version": "0.1.0-beta.1",
+  "version": "0.1.0-beta.2",
   "type": "module",
   "private": true,
   "bin": {

src/version.ts

@@ -5,7 +5,7 @@
  * fails inside the shipped binary. A constant is compiled in and always correct.
  * `scripts/release.ts` checks it against the release tag so the two cannot drift.
  */
-export const VERSION = '0.1.0-beta.1';
+export const VERSION = '0.1.0-beta.2';
 
 /** What `--version` prints: enough to identify a build from a bug report. */
 export function versionLine(): string {