claudemd-cli 0.51.1 → 0.53.0

package/CHANGELOG.md

@@ -8,6 +8,28 @@ 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.53.0] - 2026-07-24
+
+Ships spec **v6.21.0** (minor) plus the drift test that pins it. No hook, script, or command behavior changes.
+
+**What changes for users**: the §EXT §12 fallback table now covers `gs:/qa` / `gs:/qa-only`, and its Detection clause no longer assumes a missing skill announces itself by failing. Agents routed at a skill that is disabled via `skillOverrides` (or absent from the install) are told to check the session skill list first, take the documented fallback, and say which substitution they made — instead of either calling a skill that is not there or silently improvising. Manifest descriptions move to the `v6.21` family per the versioning policy above.
+
+- **spec v6.21.0** (minor): `§EXT §12` Fallback table gains `gs:/qa, /qa-only` → `gs:/browse` pass over the changed user-facing surface, report per §7 L2 evidence, repair via §12 Review-finding repair. It was the only §4 Routing primary without a fallback row while §4's `ship L2` row routes user-facing ships at it. Detection premise widened to **absent-from-listing = missing**: `skillOverrides: "off"` produces no failing call, so call-failure auto-degrade never fired for it. Trigger: 2026-07-24 `/doctor` found 6 §4 Routing primaries off in `~/.claude/settings.json#skillOverrides` (`office-hours` `freeze` `benchmark` `qa` `canary` `design-consultation`) — 5 already had fallback rows. SHOULD-level spec text: `hard-rules.json` bumps `spec_version` only, no rule added to the manifest and no hook touched.
+- **test: `§12: every §4 Routing primary has a §12 Fallback-table row`** (`tests/scripts/spec-structure.test.js`) closes the drift class rather than just the one gap — it joins the §4 Routing table's Primary column against the §12 Fallback table's Missing column, resolving family globs (`/design-*`, `sp:*-code-review`) and the `sp:TDD` / `sp:finishing` shorthands. Against the pre-change spec it fails with exactly `gs/qa, gs/qa-only`; suite 689 → 690.
+
+## [0.52.0] - 2026-07-24
+
+Fix batch from the 2026-07-24 production-readiness audit (`docs/2026-07-24-production-readiness-audit.md`) — items 1-3 and 5-10 of its action table, plus the restocked core net-delete candidate pool (C7-C12, item 4 core-side). Ships spec **v6.20.1** (patch). Minor bump: the curl-sh gate's deny surface widens (user-visible default behavior change).
+
+**What changes for users**: wrapper-prefixed fetch-to-shell commands (`sudo curl … | sh`, `nohup curl … | bash`, `FOO=1 curl … | sh`, `timeout 5 curl … | sh`, `( sudo curl … | sh )`) previously slipped past the §8 curl-sh gate and now deny. Escape hatches unchanged: `[allow-curl-sh]` token or `DISABLE_PRE_BASH_SAFETY_HOOK=1`; prior behavior = pin plugin ≤0.51.1. The deny message carries the bypass paths at the moment of impact.
+
+- **fix(§8): fetch-side wrapper/assignment prefix bypassed the curl-sh gate** (audit P1-1). Only the sink side stripped wrappers (`curl … | sudo bash` denied) while the fetch side was a bare regex anchored at command position, so `sudo curl … | sh` was allowed. Each curl-sh segment now strips leading subshell/brace openers, env-assignments and exec-wrappers via the shared `s8_strip_wrappers` (same machinery as the rm/npx gates; monotonic — stripping only exposes text to a deny-on-match regex). Hook suite 382 → 394 (+8 wrapper-deny cases, 7 pre-fix RED, + 4 FP guards; all pre-existing rows verdict-unchanged). Documented residuals: option-with-arg wrappers (`sudo -u svc curl`), wrapper after a mid-segment background `&`.
+- **spec v6.20.1** (patch, audit P1-2 + P2-14): §13 META enforcement-partition counts corrected 22/6-hook → 23/7-hook (stale since §8-curl-sh joined hard-rules.json 2026-07-13) with new drift test `hard-rules-9` pinning the prose counts to the computed manifest partition; duplicate §EXT heading ids made unique (`§7-EXT-TMP` / `§11-EXT-MEM` / `§11-EXT-MAC`), tag-syntax subsection relocated into §11-EXT-MEM, core pointers updated; `spec-coherence-audit` CHECK 1 now flags duplicate `##+ §id` headings (with the id-token regex fixed so `§4.FULL` / `§4.FULL-lite` are distinct ids, not a phantom `§4.` duplicate). v6.20.0 Recent-changes entry externalized to the spec changelog: extended headroom 1300B → 2311B (95.38% of cap, out of the §0.1 danger band).
+- **ci: shellcheck now blocking at warning+ severity** (audit P2-11; was `|| echo` warn-only) and scope extended to `scripts/*.sh` + `tests/lib/*.sh`. Baseline cleaned: `tests/lib/env-hygiene.sh` gains a `shellcheck shell=bash` directive (SC2148), dead `TRIGGER_RE` back-compat alias removed from banned-vocab-check.sh (SC2034). Info-level findings remain a visible non-blocking report.
+- **fix(mem-audit): 24h debounce sentinel now written BEFORE the scan loop** (audit P2-4). A 3s-timeout kill on a many-project install left the sentinel unwritten, so every subsequent Stop re-ran the full scan instead of debouncing.
+- **statusline: repo git calls bounded with `timeout 1`** where coreutils timeout exists (audit P2-18; hung NFS/fuse git could block the render — CC's own statusline timeout remains the backstop; macOS stock falls back to bare git).
+- **docs (audit P1-3 + P2-9/10/12)**: `ADDING-NEW-HOOK.md` now includes the drift-gate registration steps (RULE-HITS-SCHEMA + contract-test `DOCUMENTED` array + hard-rules.json + registry/toggle) — following the old doc verbatim produced a red build; stale "6th hook" / "8 shipped hooks" counts removed (install.js ×2); `ARCHITECTURE.md` documents the settings.json lock-free/idempotent posture and the guarded L1-spawns-L2 bootstrap edge; `mergeHook` annotated as test-fixture-only (not live wiring since v0.1.5).
+
 ## [0.51.1] - 2026-07-17
 
 Fix release from the 2026-07-17 four-dimension audit (`docs/comprehensive-audit-2026-07-17-v0.51.0.md`): two latent-bug closures + one CI coverage hole. No spec change (spec stays **v6.20.0**). All three are `fix:` — restoring documented/intended behavior, not new rules.

package/README.md

@@ -1,12 +1,12 @@
 # claudemd
 
-> A **personal AI-coding discipline harness**: one developer's opinionated **AI-CODING-SPEC v6.20**, encoded as Claude Code shell hooks and shipped with the plugin. Built and dogfooded on my own repos — fork and adapt, don't adopt wholesale.
+> A **personal AI-coding discipline harness**: one developer's opinionated **AI-CODING-SPEC v6.21**, encoded as Claude Code shell hooks and shipped with the plugin. Built and dogfooded on my own repos — fork and adapt, don't adopt wholesale.
 
 [![CI](https://github.com/sdsrss/claudemd/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/sdsrss/claudemd/actions/workflows/ci.yml)
 [![npm](https://img.shields.io/npm/v/claudemd-cli.svg)](https://www.npmjs.com/package/claudemd-cli)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
-claudemd plugs into the Claude Code hook system to **block commits, pushes, and bash commands** that violate AI-CODING-SPEC v6.20 — banned vocabulary in commit messages, `rm -rf $VAR` without variable validation, ship-on-red-CI, unread `MEMORY.md` entries during release flows, and more. The spec itself (`CLAUDE.md` + `CLAUDE-extended.md` + `CLAUDE-changelog.md` + `OPERATOR.md`) ships with the plugin and installs into `~/.claude/`, so the rules Claude Code reads at session start match the rules the hooks enforce. (`OPERATOR.md` is the human-only spec-maintenance handbook — Agent-loaded files are the CLAUDE trio.)
+claudemd plugs into the Claude Code hook system to **block commits, pushes, and bash commands** that violate AI-CODING-SPEC v6.21 — banned vocabulary in commit messages, `rm -rf $VAR` without variable validation, ship-on-red-CI, unread `MEMORY.md` entries during release flows, and more. The spec itself (`CLAUDE.md` + `CLAUDE-extended.md` + `CLAUDE-changelog.md` + `OPERATOR.md`) ships with the plugin and installs into `~/.claude/`, so the rules Claude Code reads at session start match the rules the hooks enforce. (`OPERATOR.md` is the human-only spec-maintenance handbook — Agent-loaded files are the CLAUDE trio.)
 
 A standalone CLI (`npx claudemd-cli`) reuses the same `banned-vocab.patterns` source for git pre-commit hooks, GitHub Actions, and other agents that don't run inside Claude Code.
 
@@ -60,7 +60,7 @@ Verify in one command (Linux): `node --version && jq --version && gh --version &
 | 16 shell hooks | `banned-vocab-check` · `pre-bash-safety-check` · `ship-baseline-check` · `residue-audit` · `memory-read-check` · `memory-prompt-hint` · `mid-spine-yield-scan` · `sandbox-disposal-check` · `session-start-check` · `session-extended-read` · `session-summary` · `session-end-check` · `transcript-vocab-scan` · `transcript-structure-scan` · `version-sync` · `mem-audit` |
 | 16 slash commands | `/claudemd-install` · `/claudemd-status` · `/claudemd-update` · `/claudemd-refresh` · `/claudemd-audit` · `/claudemd-toggle` · `/claudemd-doctor` · `/claudemd-analyze` · `/claudemd-uninstall` · `/claudemd-rules` · `/claudemd-clean-residue` · `/claudemd-sparkline` · `/claudemd-sampling-audit` · `/claudemd-bypass-audit` · `/claudemd-design-adopt` · `/claudemd-statusline` |
 | 1 standalone CLI | `claudemd-cli lint` · `claudemd-cli audit` ([npm: `claudemd-cli`](https://www.npmjs.com/package/claudemd-cli)) |
-| Spec v6.20 | `~/.claude/CLAUDE.md` · `CLAUDE-extended.md` · `CLAUDE-changelog.md` · `OPERATOR.md` (backup-before-overwrite) |
+| Spec v6.21 | `~/.claude/CLAUDE.md` · `CLAUDE-extended.md` · `CLAUDE-changelog.md` · `OPERATOR.md` (backup-before-overwrite) |
 | StatusLine (opt-out) | PS1-style line — `user@host:dir (branch) Model [ctx:N% · 5h:N% · 7d:N%]` (`dir` = cwd basename; context / 5-hour quota / weekly quota, all **used %**, read from Claude Code's `rate_limits` payload; quota segments auto-hide when the data is absent, or force-hide with `DISABLE_STATUSLINE_QUOTA=1`) — wired into `~/.claude/settings.json` on install **only when the slot is empty**; an existing statusline is left untouched. Skip entirely with `CLAUDEMD_NO_STATUSLINE=1`. Manage via `/claudemd-statusline`. |
 
 Install backs up a hand-written `~/.claude/CLAUDE.md` (any file without the `# AI-CODING-SPEC` H1) to `~/.claude/backup-<ISO>/` before overwriting (last 5 kept automatically). An already-installed claudemd spec is overwritten **without** a backup — deliberate (v0.23.11): the sole backup is always your own content, so `restore` can never return a stale spec instead. Uninstall offers `keep / restore / delete`; `delete` requires an extra confirmation.
@@ -353,7 +353,7 @@ claudemd/
 ├── commands/                 # 16 slash-command markdown files
 ├── bin/                      # standalone CLI entrypoint (claudemd-lint.js → `npx claudemd-cli` on npmjs.org)
 ├── scripts/                  # 18 Node.js scripts + scripts/lib/ (single-source registry, lint, etc.)
-├── spec/                     # shipped v6.20.0 CLAUDE*.md trio + OPERATOR.md + hard-rules.json manifest
+├── spec/                     # shipped v6.21.0 CLAUDE*.md trio + OPERATOR.md + hard-rules.json manifest
 ├── tests/                    # hook shell tests + Node.js tests + integration + fixtures
 ├── docs/                     # ADDING-NEW-HOOK.md + RULE-HITS-SCHEMA.md + superpowers/
 └── .github/workflows/        # ci.yml (ubuntu+macOS × node 20) + npm-publish.yml (tag-triggered)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudemd-cli",
-  "version": "0.51.1",
+  "version": "0.53.0",
   "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": {