release 0.1.0-beta.4

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>

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.3  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.4  openai/gpt-5  session 0193ab2c
 agent: default  thinking: medium
 cwd: /home/you/project
 skills: commit, debug, refactor, review, test, verify

ROADMAP.md

@@ -95,7 +95,7 @@ fails with a message saying the command did not finish and its effects are unkno
 model takes its next step from there. The kill takes the whole process tree, because killing
 `cmd /c` alone leaves the real command holding both pipes open and the read never returns.
 
-### 0.1.0-beta.4 (unreleased)
+### 0.1.0-beta.4
 
 **Compaction no longer stops the loop.** The beta.2 repair dropped any assistant part whose
 reasoning item pruning had removed. On a reasoning model that is every tool call, so past the

docs/development.md

@@ -128,7 +128,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.3). Bump the version or retag.
+tag v9.9.9 does not match src/version.ts (0.1.0-beta.4). Bump the version or retag.
 ```
 
 A binary reporting the wrong version is worse than a failed release.

docs/mcp.md

@@ -67,7 +67,7 @@ one tool for the session.
 A server that fails to start is reported and the session continues:
 
 ```
-shiro-neko 0.1.0-beta.3  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.4  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.3",
+  "version": "0.1.0-beta.4",
   "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.3';
+export const VERSION = '0.1.0-beta.4';
 
 /** What `--version` prints: enough to identify a build from a bug report. */
 export function versionLine(): string {