@hraness/message-like-me 0.8.3 → 0.8.4

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog
 
+## 0.8.4 (2026-09-06)
+
+- Make the exact public `@hraness/message-like-me@0.8.4` npm package the
+  supported default install, with the same reviewed bytes mirrored in the
+  immutable GitHub Release. The product is unchanged from 0.8.3.
+- Let the GitHub Release writer wait briefly for its freshly created draft
+  instead of failing on the first inventory read, so an automated release no
+  longer needs a manual rerun.
+- Fetch the release tag with one more commit of history than the admitted
+  workflow range and prove the production commit is its ancestor before the
+  leased fast-forward, so Git attributes the push instead of reporting a forced
+  update. Every job after promotion path selection carries an explicit
+  skip-aware condition, and a terminal admission fails unless verification and
+  provider admission both succeeded.
+
 ## 0.8.3 (2026-09-06)
 
 - Let Beeper users bring a finished private Wrench bundle into the same local

package/README.md

@@ -43,7 +43,7 @@ Message Like Me requires Bun 1.3.14 or newer. Install the exact public npm
 package, then install both bundled Agent Skills:
 
 ```sh
-bun add --global @hraness/message-like-me@0.8.3
+bun add --global @hraness/message-like-me@0.8.4
 messagelikeme skill install
 ```
 

package/dist/cli.js

@@ -6214,7 +6214,7 @@ class LocalStore {
 }
 
 // src/version.ts
-var MESSAGE_LIKE_ME_VERSION = "0.8.3";
+var MESSAGE_LIKE_ME_VERSION = "0.8.4";
 
 // src/x-archive.ts
 import { createHash as createHash4 } from "crypto";

package/docs/publishing.md

@@ -727,6 +727,15 @@ the same checked explicit-lease fast-forward and requires one new provider
 outcome. A baseline-preserving range uses the frozen v1 no-digest receipt; a
 workflow-changing range requires the exact independently reviewed v2 digest and
 recomputes its old-through-current-workflow-source inventory before authority.
+The sterile writer fetches only the exact verified tag, with one more commit of
+history than the admitted workflow range, and proves the expected production
+commit is its ancestor before pushing. Missing ancestry or a non-fast-forward
+target fails before the ref can move; the push receipt must still report one
+ordinary fast-forward rather than a forced update. Because exactly one of the
+advance and already-exact jobs is intentionally skipped, every job after path
+selection has an explicit skip-aware status condition. The final public
+admission runs as a terminal sentinel and fails unless verification and provider
+admission both succeeded, so a skipped tail cannot make the workflow green.
 If the ref is already exact, the baseline marks advancement false, skips the
 entire `production-ref-writer-key` job, and mints no App token. A separate
 read-only job accepts only the unique latest exact-SHA Production deployment in

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hraness/message-like-me",
-  "version": "0.8.3",
+  "version": "0.8.4",
   "description": "A local-first CLI and Agent Skill for studying private messaging history and drafting messages that sound like you.",
   "license": "MIT",
   "type": "module",