paqad-ai 1.40.0 → 1.41.1

package/CHANGELOG.md

@@ -1,5 +1,43 @@
 # paqad-ai
 
+## 1.41.1
+
+### Patch Changes
+
+- 2137219: Rule-script whole-tree scan now respects `.gitignore`. Previously the scanner
+  enumerated the working tree with a fixed ignore list (`node_modules`, `dist`,
+  `.paqad`, `build`) and never consulted the project's `.gitignore`, so gitignored
+  build output, vendored dependencies, and generated code were still scanned —
+  producing `deterministic` findings on files the developer cannot hand-fix and
+  blocking the strict `rule_compliance` gate. The scan now drops git-ignored paths
+  via a batched `git check-ignore` (falling back to the static list when git is
+  unavailable), and adds `vendor/` to that fallback list.
+
+## 1.41.0
+
+### Minor Changes
+
+- 7d3bed0: Analytics v2 (#279): turn analytics instrumentation into a tracking-plan-as-code.
+
+  When `analytics_instrumentation` is on, paqad now makes the per-event docs tree the single
+  source of truth for what a project tracks, and governs every event through the normal PR:
+
+  - The #241 `paqad.analytics-tag` ledger is removed (redundant with the docs); the flag,
+    detection, classify-time gate, and conflict decision-pause categories stay.
+  - A `docs/instructions/stack/analytics.md` tracking-plan doc is generated from provider
+    detection (OFF stays silent).
+  - Framework analytics rules are compile-time gated on the flag (`<!--gate:-->` frontmatter),
+    so zero analytics bytes reach the model when off.
+  - A per-event docs tree `docs/modules/{module}/analytics/{feature}/{event}.md` (one doc per
+    event, a section per provider, normalized-slug filenames that collapse casing variants) is
+    generated by the documentation workflow and the doc-sync stage.
+  - Every new event opens an `analytics.new_event` Decision Pause packet (who/why), and the
+    feature-development stages inject analytics instructions when the gate resolves to instrument.
+  - One `AC-TRACK` per event flows through spec freeze and traceability (an unproven event is a
+    `TR-UNTESTED-PROMISE`), gated by doc existence with a new `analytics_strictness` knob
+    (off | warn | strict, default warn).
+  - A new `analytics-instrumentation` skill writes the doc + emits the provider snippet.
+
 ## 1.40.0
 
 ### Minor Changes