paqad-ai 1.63.2 → 1.63.4

package/CHANGELOG.md

@@ -1,5 +1,46 @@
 # paqad-ai
 
+## 1.63.4
+
+### Patch Changes
+
+- f2128be: Make feature-development stage narration visible on Claude Code Desktop (#409).
+
+  The stage hooks narrate on Claude's `{systemMessage}` channel, which the Desktop app
+  records as a hook attachment and never renders in the chat. A verified six-stage run
+  emitted eleven `▸ paqad` stage lines and the developer saw none of them, while the
+  evidence bundle was complete — recorded but unnarrated, the inverse of #389.
+
+  The narration contract now tells the Claude Code agent to speak its own stage lines and
+  the one end-of-change receipt in visible assistant text, placed in the turn's final
+  message, and carries a per-surface table of which channels actually render instead of
+  the previous single wrong assumption. A new deterministic backstop reads the turn
+  transcript and reports any stage recorded this turn with no matching visible narration,
+  advising the model to relay the receipt. The check is advisory: it never turns a passing
+  verdict into a failing one and never blocks a turn.
+
+## 1.63.3
+
+### Patch Changes
+
+- eb1fa9a: fix(#401): spec freeze now runs the spec-quality review it always claimed to require
+
+  `paqad-ai spec freeze` told you, in both the rule pack and the workflow contract, that
+  freezing enforces "no critical spec-review defects". It never did: the CLI evaluated the
+  freeze with no review attached, so that clause was enforced nowhere. Agents closed the gap by
+  hand-running `compliance review`, which left a stray `.paqad/compliance/<slug>/spec-review.json`
+  behind that was neither part of the change's evidence bundle nor git-ignored.
+
+  Freeze now runs the review itself and blocks on a critical defect like any other blocker, so
+  there is no second command to run and no stray artifact. On a clean freeze the defect summary
+  is folded into the bundle's `specification.json`, so the review evidence travels with the spec
+  of record. Non-critical findings never block.
+
+  Two related fixes: `spec freeze` and `compliance review` now reject a spec file that resolves
+  outside the project root and record `spec_file` as a project-relative posix path, and the
+  managed `.paqad/.gitignore` covers `compliance/` so a compliance artifact can never surface as
+  an untracked, committable file.
+
 ## 1.63.2
 
 ### Patch Changes