release: 0.1.1

Stamps `## Unreleased` as `## 0.1.1 — 2026-07-19` and re-arms the
changelog with a fresh, empty `## Unreleased` above it — both halves in
this diff, per CONTRIBUTING's ceremony (#113/#114; heavy-duty/rig#66).

Bumps package.json and package-lock.json 0.1.1-dev -> 0.1.1. Patch is
correct: the shipped section carries only `### Fixed`.

This is the first cast release to go through the merge door. 0.1.0 could
not — the interlock refused it (run 29698017907) because cast had said
`0.1.0` since its first commit, so there was no `-dev` transition to
detect, and it shipped by the manual tag path. main now genuinely reads
`0.1.1-dev`, so release.yml's decide step sees bare-and-changed: the
ceremony state.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

CHANGELOG.md

@@ -7,6 +7,8 @@ actually cutting it, and this file starts there.
 
 ## Unreleased
 
+## 0.1.1 — 2026-07-19
+
 ### Fixed
 
 - **The release ceremony re-arms the changelog, and CI notices when it

package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "cast",
-  "version": "0.1.1-dev",
+  "version": "0.1.1",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "cast",
-      "version": "0.1.1-dev",
+      "version": "0.1.1",
       "dependencies": {
         "yaml": "^2.5.0",
         "zod": "^3.25.76"

package.json

@@ -1,6 +1,6 @@
 {
   "name": "cast",
-  "version": "0.1.1-dev",
+  "version": "0.1.1",
   "type": "module",
   "private": true,
   "engines": { "node": ">=22.12.0" },