paqad-ai 1.69.0 → 1.71.0

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # paqad-ai
 
+## 1.71.0
+
+### Minor Changes
+
+- b394371: Framework-native reuse now covers PHP/Laravel, Python and Java/Spring, not just JS/TS
+  (#398). Each ecosystem gets an adapter behind the same normalized schema: resolve the
+  version actually installed, read the declaration layer that ships with it, and answer
+  whether a symbol exists and whether it is deprecated — so `plan compile` checks a Laravel,
+  Django or Spring reuse claim exactly as it already checked a React one.
+
+  Laravel facades resolve through their `@method static` docblocks rather than reporting
+  `__callStatic`, and the version-pinned Laravel Upgrade Guide is folded in as a
+  `doc-derived` deprecation backstop for the deprecations Laravel documents but never tags.
+  Metaprogrammed members always read "could not verify statically", never a false "does not
+  exist".
+
+  `FRAMEWORK_PACKAGE_MAP` also gains the Spring Boot, Django, FastAPI and Rails coordinates
+  it was missing, so those projects are detected and indexed instead of silently producing
+  nothing.
+
+## 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