paqad-ai 1.70.0 → 1.72.0

package/CHANGELOG.md

@@ -1,5 +1,56 @@
 # paqad-ai
 
+## 1.72.0
+
+### Minor Changes
+
+- 12acee3: New **Site Map** capability — the deterministic core (P1), behind an OFF-by-default `site_map`
+  flag (env `PAQAD_SITE_MAP`). With the flag off nothing changes; when on and the coding capability
+  is active, `paqad-ai sitemap run` maps the application — its surfaces (pages, screens, endpoints,
+  CLI commands), transitions, guards, and areas — reconciles them against a canonical
+  `docs/instructions/site-map/app-map.yaml`, runs Tier-A verification (evidence resolution,
+  cross-reference integrity, graph invariants), and publishes a token-budgeted `index.md`, a
+  deterministic Mermaid overview, and screen/API registries. Zero model tokens: the engine mirrors
+  the codebase-health pattern (injectable gatherer → pure assemble → exit-code-as-verdict).
+
+  This release wires the capability into the framework:
+
+  - **Routing**: `site-map` and `site-map-retest` are routed workflows (mirroring
+    codebase-health / health-retest). Verb-qualified triggers keep a literal `sitemap.xml` feature
+    request on the feature-development path.
+  - **Skills, roles, and rules**: the `site-map` / `site-map-retest` workflow rules, the
+    `app-cartographer` and `journey-designer` agent roles, and the fine-grained skills (readiness,
+    extraction, modeling, transition-tracing, guard-inference, assembly, verification, gap-analysis,
+    publication, maintainer, retest, and journey-synthesis). Journeys are proposed by
+    `journey-synthesis`/`journey-designer` and become `confirmed` only through human sign-off.
+  - **Freshness gate**: a feature-development change that drifts the map cannot reach "Safe to
+    merge" while a published view is stale — inert unless the flag is on.
+  - **Retest**: `paqad-ai sitemap retest` replays a prior report by stable `SM-` id (never invents a
+    finding, never lowers severity, never calls the absence of proof a fix).
+
+  The React dashboard Site map area and the human journey-curation UI (confirming a proposed journey)
+  are deferred to a follow-up.
+
+## 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