paqad-ai 1.65.0 → 1.67.0

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # paqad-ai
 
+## 1.67.0
+
+### Minor Changes
+
+- 7aaebd3: Give the review stage hard facts, and make ignoring them detectable (#360).
+
+  `paqad-ai review digest` composes `.paqad/session/review-digest.md` from what
+  paqad already computed — rule-script findings, duplication findings, the check
+  verdict, failing verification gates — alongside the frozen acceptance criteria,
+  the per-stage state, and an honest list of the blind spots no machine covers.
+  It reads cached JSON only: no subprocess, no scan, no model tokens, hard-capped
+  at 150 lines.
+
+  The review stage contract now tells the model to build and read it before
+  writing findings, and `ImplementationReviewGate` fails when a deterministic,
+  file-anchored, high-severity finding is never cited by `file:line` in the
+  recorded `review.json`. The gate re-derives those rows from the same collector
+  the digest uses, so skipping the verb does not disarm the check. A change with
+  no machine findings behaves exactly as before.
+
+## 1.66.0
+
+### Minor Changes
+
+- 87c8153: Wire the idle planning skills into the enforced stage contract (#359): four fully-built-but-never-invoked planning helpers now run when relevant, and only when relevant.
+
+  - The enforced feature-development **planning stage** gains three lane-gated instruction blocks, sourced from one shared set of constants so the default policy object and the rendered `feature-development.yaml` cannot drift: an all-lanes reuse reflex (consult the Existing surface + `index query`, follow the solution-architect Reuse / Extend / Build-new procedure), a graduated/full block that runs `diff-minimizer` before the plan compiles and `existing-doc-checker` before any new doc, and a graduated/full multi-module block that runs `cross-module-impact-scanner`.
+  - **Lane honesty:** a fast-lane change pays exactly one sentence; no skill procedure loads for it. A new `reusePlanningInstructions(lane, { multiModule })` assembler is the single source of that lane-gating logic.
+  - The #357 plan schema now accepts an optional per-step `classification` (`ac-satisfying` | `necessary-setup` | `scaffolding` | `over-build`) so a diff-minimizer verdict can ride in the compiled `plan.json`; a plan without it stays valid.
+  - No new hook and no new runtime gate — the skills feed fields the schema already checks, and the wired-vs-sidelined map in the onboarded-project overview is updated to keep it honest.
+
 ## 1.65.0
 
 ### Minor Changes