paqad-ai 1.58.0 → 1.59.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # paqad-ai
 
+## 1.59.0
+
+### Minor Changes
+
+- deb1cb9: Make the end-of-change verdict visible, honest, and enforced (#368). The completion backstop now surfaces the one end-of-change receipt to the developer whether the verdict passes, fails, or is inconclusive — a failing "Needs your attention" verdict can no longer be hidden on stderr while a PR ships. A hard-failing feature-development change now blocks the turn at the Stop seam via the documented `decision:block` channel (exit 2 is a no-op there), bounded by the stop-hook loop guard. A feature-development change with no real `paqad-ai checks run` report reads as Inconclusive and shows its `checks` stage as unverified rather than done. The `checks.block_on_failure` escalation stays script-enforced; `review_findings` / `stale_docs` are documented as agent-raised and Decision-Pause-enforced rather than falsely claiming script enforcement. The cross-provider verdict tiering (hook-surfaced on Claude, agent-narrated on Codex/Gemini/advisory) is documented so the promise is truthful per host.
+
+  Also (AC-D2, from the second reproduction on the #355 session): the evidence receipt's `verification_result` is now three-way — `FAILED` only on a genuine failure, `INCONCLUSIVE` when a measure could not run (a `blocked` ratchet from unwired/absent tooling) or could not be judged, and `PASSED` when every row passed. A couldn't-verify is no longer reported as a failure, so an unwired quality-ratchet measure can no longer manufacture a false `FAILED` on the attestation.
+
 ## 1.58.0
 
 ### Minor Changes

package/dist/cli/index.js

@@ -8443,6 +8443,17 @@ function renderDefaultFeatureDevelopmentPolicyYaml() {
   return `# Feature Development Stage Policy
 # This file customizes how the built-in feature-development workflow behaves in this project.
 # The framework still owns routing, phase order, and mandatory safety stages.
+#
+# Enforcement tiers (issue #368) \u2014 an escalation is honoured on one of two tiers, and
+# this contract never claims script enforcement it does not have:
+#   - SCRIPT-ENFORCED (deterministic): checks.block_on_failure and the mandatory-stage
+#     completeness gate. \`paqad-ai checks run\` exits non-zero on any red command and the
+#     completion backstop reads its report; a feature-dev change with no report reads
+#     Inconclusive, never a vacuous pass.
+#   - AGENT-RAISED -> DECISION-PAUSE-ENFORCED: review.escalation.review_findings and
+#     documentation_sync.escalation.stale_docs need model judgment to raise, so no script
+#     detects them; once raised as a \`stop\`, the Decision-Pause gate holds edits until the
+#     packet resolves. Not a false "a script proves this" promise.
 schema_version: "1"
 merge_mode: append
 
@@ -30327,7 +30338,7 @@ init_cancelled_error();
 init_events();
 
 // src/index.ts
-var VERSION = "1.58.0";
+var VERSION = "1.59.0";
 
 // src/cli/commands/audit.ts
 init_esm_shims();