claudex-setup 1.16.1 → 1.16.2

package/CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## [1.16.2] - 2026-04-03
+
+### Changed
+- bumped the local release line to `1.16.2` so the next publish does not overwrite the already-live `1.16.1` npm release
+- synchronized README, docs, launch copy, and proof-facing state to distinguish clearly between public npm latest (`1.16.1`) and local release prep (`1.16.2`)
+
+### Fixed
+- release-truth drift across package metadata, docs, and public-facing proof references
+
+## [1.16.1] - 2026-04-03
+
+### Added
+- `feedback` command validation on the public npm package line
+- stronger secret detection coverage for Anthropic-style keys
+- deep-review sanitization and secret redaction hardening
+- watch-mode resilience improvements across recursive and non-recursive platforms
+
+### Changed
+- increased verified check count from `84` to `85`
+- proof-backed product copy and case-study traceability improvements
+
 ## [1.10.3] - 2026-04-02
 
 ### Added

package/README.md

@@ -51,7 +51,7 @@ Tested on 4 real projects — not demos:
 
 Most common gaps found: missing secrets protection, no deny rules, no mermaid diagram, no hooks in settings.
 
-> Scores measured with claudex-setup@1.10.3 on 2026-04-03. Current npm latest: 1.16.0, so exact scores may differ slightly on the newer release.
+> Scores measured with claudex-setup@1.10.3 on 2026-04-03. Current npm latest: 1.16.1, so exact scores may differ slightly on the newer release.
 >
 > Canonical proof artifacts: [Index](https://github.com/DnaFin/claudex/blob/main/research/proof-artifacts/README.md) | [CLAUDEX trace](https://github.com/DnaFin/claudex/blob/main/research/proof-artifacts/claudex-self-dogfood-proof-trace-2026-04-03.md) | [VTCLE trace](https://github.com/DnaFin/claudex/blob/main/research/proof-artifacts/vtcle-proof-trace-2026-04-03.md) | [Social trace](https://github.com/DnaFin/claudex/blob/main/research/proof-artifacts/social-proof-trace-2026-04-03.md) | [Polymiro trace](https://github.com/DnaFin/claudex/blob/main/research/proof-artifacts/polymiro-proof-trace-2026-04-03.md)
 >
@@ -129,8 +129,6 @@ That prints a compact top-3 quick scan with one clear next command.
 | `npx claudex-setup deep-review` | **Deep Review** - AI-powered config analysis (Claude Code or API key, selected config only) |
 | `npx claudex-setup insights` | **Insights** - View community aggregate stats |
 
-> Note: the `feedback` command is currently validated on the main working tree for the next release. If your installed npm build does not expose it yet, use the rest of the trust-first flow and pick it up on the next publish.
-
 ### Options
 
 | Flag | Effect |
@@ -266,8 +264,6 @@ npx claudex-setup feedback
 
 Feedback stays under `.claude/claudex-setup/outcomes/` and is used only as a local ranking signal. Recommendations with repeated positive outcomes get a measured boost; recommendations with repeated negative or rejected outcomes get pushed down.
 
-If your currently installed npm build does not expose `feedback` yet, treat this as next-release behavior rather than current npm-latest behavior.
-
 `watch` uses native `fs.watch` with recursive directory watches where the platform supports them, and an expanded directory fallback elsewhere. That keeps nested `.claude/` and `.github/` changes visible on Linux too, while staying zero-dependency. Native filesystem watch semantics can still be noisier on very large repos or network filesystems, so the command is best treated as fast local feedback rather than a CI-grade signal.
 
 ## Use Inside Claude Code
@@ -331,7 +327,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: DnaFin/claudex-setup@v1.16.0
+      - uses: DnaFin/claudex-setup@v1.16.1
         with:
           threshold: 50
 ```

package/content/launch-posts.md

@@ -17,7 +17,7 @@ Use these links as the canonical sources behind public claims:
 Measured-result boundary to preserve:
 
 - before/after scores were measured with `claudex-setup@1.10.3` on `2026-04-03`
-- current npm latest is `1.16.0`
+- current npm latest is `1.16.1`
 - current product surface is `85 checks`
 
 ## Post 1: Reddit r/ClaudeAI
@@ -175,7 +175,7 @@ Case studies:
 
 **Tweet 5:**
 Measured results were captured on `claudex-setup@1.10.3` on `2026-04-03`.
-Current npm latest is `1.16.0`, so exact scores can move slightly, but the proof packet is explicit about that boundary.
+Current npm latest is `1.16.1`, so exact scores can move slightly, but the proof packet is explicit about that boundary.
 
 **Evidence anchor:** proof artifact index + per-repo traces
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudex-setup",
-  "version": "1.16.1",
+  "version": "1.16.2",
   "description": "Score your repo's Claude Code setup against 85 checks. See gaps, apply fixes selectively with rollback, govern hooks and permissions, and benchmark impact — without breaking existing config.",
   "main": "src/index.js",
   "bin": {