paqad-ai 1.68.0 → 1.70.0

package/CHANGELOG.md

@@ -1,5 +1,54 @@
 # paqad-ai
 
+## 1.70.0
+
+### Minor Changes
+
+- 39f86ea: Verify framework reuse claims against the version you actually have installed (#397).
+
+  A plan could already declare it was reusing a framework API — "I'll use React's `useId()`
+  instead of hand-rolling one" — but nothing checked the claim. Now paqad reads the
+  declaration files shipped inside the installed package and answers two questions before
+  the plan compiles: does that symbol exist at your installed version, and is it
+  `@deprecated`? A plan naming a removed API fails with the nearest existing symbol; one
+  naming a deprecated API fails citing the deprecation message. No AI, no network.
+
+  New: `paqad-ai index framework-api build` and `paqad-ai index framework-api query
+<package> <symbol>`.
+
+  Nothing new is installed for this. `typescript` is an optional peer dependency resolved
+  from your own project, so a Laravel, Flutter, or Python project pays nothing for a
+  JS-only check, and a project without it degrades to a visible warning rather than a
+  block. Anything paqad cannot verify statically — a dynamically-provided member, an
+  unindexed package, a missing index — warns instead of failing, because a false "this
+  does not exist" would block a perfectly good plan.
+
+## 1.69.0
+
+### Minor Changes
+
+- 09ef89f: Prove "less, better code" with per-change shape metrics (#362).
+
+  Two deterministic, diff-scoped, zero-model-token numbers are now computed for
+  every feature-development change:
+
+  - **duplication on new code** (`dup_new_pct`) — the % of the change's meaningful
+    new lines that near-duplicate existing code, folded from the #358 duplication
+    cache.
+  - **reuse rate** (`reuse_rate`) — cross-file calls from the change's new code
+    into pre-existing, untouched files per 100 changed lines, from the #353
+    code-knowledge index.
+
+  They fold over caches the completion gates already produced (no second scan) and
+  surface everywhere the developer already looks: one honest `change shape` line on
+  the end-of-change receipt, a metrics block on the feature bundle receipt, a
+  `change-metrics` row on the session ledger (which flows into the SIEM export), a
+  new **Change Shape** dashboard trend section with bands (green 0–3%, amber
+  3–10%, red >10%), and a new `paqad-ai metrics report` verb that prints the last N
+  changes offline. Either metric degrades to `n/a` when its source cache is absent.
+  Controlled by the `metrics_enabled` config knob (default on; respects the global
+  disable).
+
 ## 1.68.0
 
 ### Minor Changes