paqad-ai 1.62.0 → 1.63.1

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # paqad-ai
 
+## 1.63.1
+
+### Patch Changes
+
+- 2d4f101: fix(#403): back-fill the generic `change-<ULID>` bundle slug from the plan title. When `plan compile` writes a titled plan into a feature whose dir was minted by a bare `paqad:stage planning start`, the bundle is renamed to its descriptive `[<issue>-]<slug>-<ULID>` name — same ULID, every `_session` control repointed, stage-evidence artifact paths rewritten and re-stamped. The feature-development rule pack now tells the agent to include the change title in the plan template.
+
+## 1.63.0
+
+### Minor Changes
+
+- 9008ec6: Keep the feature evidence bundle rigid-only, and give the review stage a real artifact.
+
+  A feature bundle directory is meant to hold only rigid, script-owned artifacts, but
+  nothing enforced that. The `review` stage owned no bundle file at all, so its evidence
+  was an agent-authored markdown file written wherever the model chose — and the HTML
+  report actively went looking for one, which is how a stray `review-notes.md` and a
+  duplicate copy of the spec ended up sitting beside the rigid JSON.
+
+  - New `paqad-ai review record <template.json>` writes a rigid, schema-validated
+    `review.json` into the active feature's bundle, the review stage's counterpart to
+    `plan compile` and `spec freeze`. A `review` stage-end that names anything else now
+    records inconclusive.
+  - No stage may prove itself with a non-rigid file written inside a bundle directory,
+    and `paqad-ai feature export` reports any stray files it finds.
+  - `paqad-ai spec freeze` now deletes its transient spec markdown on success (pass
+    `--keep-input` to keep it) and refuses a spec authored inside a bundle directory.
+  - The feature report renders the review from `review.json` instead of reading a
+    free-written markdown file.
+
 ## 1.62.0
 
 ### Minor Changes