claudemd-cli 0.65.0 → 0.65.2

package/CHANGELOG.md

@@ -8,6 +8,26 @@ All notable changes to the `claudemd` plugin. This changelog tracks plugin artif
 - **Canonical spec version source**: `spec/CLAUDE.md` top-line title (`# AI-CODING-SPEC vX.Y.Z — Core`) + `spec/CLAUDE-changelog.md` top `##` entry.
 - **Plugin semver vs spec semver** are independent: plugin patch (0.2.0 → 0.2.1) may ship when spec is unchanged (this release); plugin minor (0.1.9 → 0.2.0) ships when spec minor updates (v0.2.0 shipped spec v6.10.0).
 
+## [0.65.2] - 2026-07-28
+
+The v0.65.0 red leg has an explanation, and the guidance v0.65.1 left behind was wrong. No shipped **code** changed: the tarball delta is the version field and this changelog entry (`CHANGELOG.md` is itself the largest shipped file, so "byte-identical apart from the version" — the first draft of this sentence — would have been self-falsifying). No hook, script, command or spec changed. It is released so the correction carries a version and reaches the marketplace channel, which serves the whole repository.
+
+- **fix: `contract.test.sh` splits `grep`'s exit-code spectrum.** The C-direction membership test collapsed exit 1 ("no match") and exit ≥2 ("failed to run" — fork / ENOMEM / signal) into a single else branch, so a transient runner spawn failure was reported as documentation drift. Exit ≥2 is now an explicit infrastructure fault. Same class as the repo's own recorded lesson that `grep` exit 2 is an error, not a zero-match — the gate had stepped on a rule this project already wrote down.
+- **Retraction: v0.65.1's "if the assertion flakes again, the awk extraction is the next suspect" was wrong — do not start there.** The load-bearing evidence is the re-run: attempt 1 (failure) and attempt 2 (success) of the identical v0.65.0 commit ran on the **same runner version and the same image** (`macos-26-arm64 / 20260720.0258.1`) and disagreed. Identical code, identical image, different outcome — that alone excludes every deterministic cause, and it also means v0.65.1's hardening was not what fixed it.
+- Two weaker arguments were used at first and are recorded here as *weaker*, not as co-equal proof: the failing leg parsed the same **47** documented pairs and ran the same **46** assertions as every passing leg (45 PASS + 1 FAIL, `110/111`), and the pair carries no regex metacharacter. The 47 is counted **before** the `sort -u`, so it cannot by itself exclude a collation drop; and the collision check was run on glibc, which is not the collator that was on trial. The re-run is what settles it.
+- v0.65.1's two hardenings (`LC_ALL=C` on the dedups, `grep -Fqx` for the lookup) stay: BSD `sort -u` deduplicating by collation and a literal compared as a BRE are real portability hazards on their own merits. They were simply not the cause, and the earlier entry now says so.
+- **What is proven, and what is not.** Proven: the gate could not distinguish "not found" from "did not run", and the failure is non-deterministic on a fixed image. Not proven: that a spawn failure actually occurred on that runner — GitHub does not log it, so the transient-fault account is inferred, not observed. Every mechanism *we enumerated* (parse, extraction, collation, pattern interpretation) is excluded; that is not the same as closure over an unenumerable space. The fix removes the conflation rather than asserting the fault.
+- The new branch is verified by a three-arm control rather than assumed reachable: a hit reports PASS, a miss reports drift, and a stub `grep` exiting 2 reports an infrastructure fault — three distinct outcomes.
+
+## [0.65.1] - 2026-07-28
+
+Hotfix for a red `ci@main` leg on the v0.65.0 push. No hook, script or spec behavior changes — the failing assertion is in a test, and the released artifact is not affected.
+
+- **fix: `contract.test.sh` pins the two locale-sensitive operations in its (event, emitter) comparison.** BSD `sort -u` removes lines that *collate* equal rather than lines that are byte-equal, so under a UTF-8 locale it can silently drop a distinct pair; the membership test also used `grep -qx`, treating a literal pair as a basic regex. Both are now `LC_ALL=C`, and the lookup is `grep -Fqx`.
+- **Correction (2026-07-28, after this version shipped): a defect that explains the failure was found, and this entry's closing guidance was wrong.** (The *mechanism* on the runner remains unproven — see v0.65.2.) Re-running the identical v0.65.0 commit — without the hardening below — passed, so the hardening is not what fixed it and the failure is not deterministic. The failing leg parsed the same **47** documented pairs and ran the same **46** assertions as every passing leg; no collation collision exists among those 47 under `C` or `en_US.UTF-8`; the pair contains no regex metacharacter. That exonerates the awk extraction this entry named as "the next suspect" — **do not start there.** What remains is that the C-direction membership test collapsed `grep` exit 1 ("no match") and exit ≥2 ("failed to run") into one branch, so a transient runner spawn failure was reported as documentation drift. Same class as the repo's own recorded lesson that grep exit 2 is an error, not a zero-match. The exit-code spectrum is now split. The two hardenings below remain — they are real portability hazards on their own merits — but they were not the cause.
+- **Mechanism not established at the time, and the comment said so.** v0.65.0's `ci@main` leg failed `C emitted 'fail-open' by 'ship-baseline' is NOT documented` on macos-latest/22 while **the same commit passed on the tag run** (all four legs), on both Linux legs, and on macos-latest/20. It did not reproduce locally across repeated runs or under `C` / `en_US.UTF-8` / `C.UTF-8`. A "the table row got too long" theory was checked and discarded — the `bypass-escape-hatch` row is 1691 chars against fail-open's 1102 and parses fine. So this hardens two real portability hazards rather than claiming a root cause. If the assertion flakes again, the extraction itself is the next suspect, not the collation.
+- Worth stating plainly: v0.65.0's tag run passed all four matrix legs and `npm-publish` succeeded, so **0.65.0 on npm is not broken** — no deprecate. The red run is the duplicate `ci@main` run that the atomic ship flow fires on the same commit.
+
 ## [0.65.0] - 2026-07-28
 
 The fail-open instrumentation could not report the failure it was built for. Fixes from the 2026-07-28 four-dimension audit (`docs/comprehensive-audit-2026-07-28-v0.64.1.md`), whose starting taxonomy was deliberately moved outside the detection-coverage family the previous five rounds sampled — lifecycle, entropy, dependency degradation, adoption.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudemd-cli",
-  "version": "0.65.0",
+  "version": "0.65.2",
   "description": "Standalone CLI for §10-V banned-vocab + transcript scanning. Companion to the claudemd Claude Code plugin (github.com/sdsrss/claudemd) for use in git pre-commit hooks, GitHub Actions, and other agents.",
   "type": "module",
   "bin": {