release 0.1.0-beta.3

v0.1.0-beta.2 was tagged but never published: the release workflow failed on the
windows-x64 build, so no release object and no artifacts exist under that tag.
The fix is in df5f9f8. Burning the version is cheaper than moving a tag that is
already on the remote.

ROADMAP records what happened, and development.md now says plainly that a green
local `bun run release` is not proof — the Windows host takes a different branch
from the Ubuntu runner CI releases from.

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

ROADMAP.md

@@ -49,10 +49,15 @@ 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
+### 0.1.0-beta.3
 
 Fourteen built-in tools, up from six, with sets so the schema cost stays controllable.
 
+`v0.1.0-beta.2` was tagged and never published: `bun build --compile
+--target=bun-windows-x64` rejects `--windows-title` unless the host is Windows, and CI
+releases every target from one Ubuntu runner. It passed locally and failed on the last of
+five builds. The version was burned rather than moving a published tag.
+
 **Visible process** — reasoning streams to a collapsed panel with an estimated token count,
 `ctrl-r` expands it, and it leaves with the turn since it is progress rather than the answer.
 The tool in flight is named from `tool-input-start`, before its arguments have finished

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.2). Bump the version or retag.
+tag v9.9.9 does not match src/version.ts (0.1.0-beta.3). Bump the version or retag.
 ```
 
 A binary reporting the wrong version is worse than a failed release.
@@ -133,11 +133,16 @@ To cut one:
 
 ```bash
 # bump src/version.ts and package.json to the same value
-git commit -am "release 0.1.0-beta.3"
+git commit -am "release 0.1.0-beta.4"
-git tag v0.1.0-beta.3
+git tag v0.1.0-beta.4
 git push --follow-tags
 ```
 
+Cross-compilation is the part that only breaks in CI. `bun run release` on Windows
+takes a different branch from the Ubuntu runner — `--windows-title` is accepted on a
+Windows host and rejected everywhere else — so a green local release is not proof.
+`buildArgs()` is unit-tested for both hosts because of exactly that.
+
 `.github/workflows/release.yml` then runs typecheck and tests, cross-compiles all five
 targets on one Ubuntu runner, asserts the built binary reports the expected version, and
 publishes a GitHub release with the binaries and `SHA256SUMS`. A tag containing `-` is

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.2  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.3  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.2",
+  "version": "0.1.0-beta.3",
   "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.2';
+export const VERSION = '0.1.0-beta.3';
 
 /** What `--version` prints: enough to identify a build from a bug report. */
 export function versionLine(): string {