diff --git a/.changeset/quiet-goats-shave.md b/.changeset/quiet-goats-shave.md
deleted file mode 100644
index 03d31b0..0000000
--- a/.changeset/quiet-goats-shave.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-'@cosyte/cli': patch
----
-
-Caller workflow and branch protection only, with no runtime impact: the pre-publish check now blocks a merge here instead of merely showing a red X.
-
-The shared pipeline grew a `prepublish` job on 2026-08-05, so this repo started emitting a
-`ci / prepublish` context on every pull request without a commit landing here. The branch ruleset
-did not name it, which meant a red pre-publish result reported a failure and merged anyway. That
-job is the offline manifest lint plus the pack-and-install probe, and this package is the reason
-both exist: two published versions carry local-path dependency specifiers and are permanently
-uninstallable. The context was read off a real check run first and then added to the ruleset, in
-that order, because requiring a context nothing emits strands every pull request instead of
-failing it.
-
-The banner on the caller now records the hazard it did not previously cover: a context can arrive
-in this repo with no commit in this repo, because the `uses:` reference is unpinned, and it always
-arrives unrequired.
diff --git a/.changeset/readme-lockup-link.md b/.changeset/readme-lockup-link.md
deleted file mode 100644
index c6c973c..0000000
--- a/.changeset/readme-lockup-link.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-"@cosyte/cli": patch
----
-
-The README lockup now links to cosyte.com (`ASSETS`).
-
-The `<picture>` block above the H1 is wrapped in an anchor to https://cosyte.com, per the founder
-requirement of 2026-08-06. Nothing inside the block moved: the `<source>`, the `<img>`, the alt text
-and both tile URLs are byte-identical.
-
-What the anchor does was measured on both surfaces by `fhir`, not assumed, because fourteen READMEs
-carry this shape. On GitHub the anchor works and the colour-scheme switch keeps working, because the
-`<img>` stays a direct child of `<picture>`, which is the condition the HTML spec puts on `<source>`
-applying at all. On an npm package page the anchor is lost: npm wraps a README image in its own
-anchor to the image file, a nested anchor is not representable, so the parser closes ours early and
-the image ends up linked to the image file rather than to cosyte.com. Shipped anyway by founder
-decision of 2026-08-07: on npm that is no worse than the unlinked lockup it replaces, and GitHub is
-where these READMEs are read.
diff --git a/docs-content/installation.md b/docs-content/installation.md
index 7ecca0c..c56a565 100644
--- a/docs-content/installation.md
+++ b/docs-content/installation.md
@@ -102,7 +102,7 @@ autodetector, the exit-code contract, and the value-free diagnostic types:
 ```ts runnable
 import { VERSION } from "@cosyte/cli";
 
-VERSION; // => "0.0.4"
+VERSION; // => "0.0.5"
 ```
 
 If that resolves and prints the release you installed, the install is good: head to the
diff --git a/package.json b/package.json
index eaf121a..a7ed7ee 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@cosyte/cli",
-  "version": "0.0.4",
+  "version": "0.0.5",
   "description": "The cosyte CLI: a PHI-safe developer front door over the @cosyte/* healthcare parsers. Parse HL7 v2 / FHIR from a file or stdin to typed JSON, with a documented exit-code contract.",
   "keywords": [
     "cli",
diff --git a/src/core/version.ts b/src/core/version.ts
index 6a70186..c9c1c14 100644
--- a/src/core/version.ts
+++ b/src/core/version.ts
@@ -23,4 +23,4 @@
  * console.log(`cosyte ${VERSION}`);
  * ```
  */
-export const VERSION: string = "0.0.4";
+export const VERSION: string = "0.0.5";