paqad-ai 1.78.1 → 1.80.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # paqad-ai
 
+## 1.80.0
+
+### Minor Changes
+
+- 3067adb: Feature bundles are now provably complete. A finished feature-development change must leave every required file in its evidence bundle, and a missing one now fails the change instead of passing silently (issue #511):
+
+  - `feature.json` finally has a writer — seeded when a feature opens and updated on rename / lane / spec-freeze / close, so a bundle records what it is instead of only its directory name.
+  - `delivery.json` is seeded at open with the branch and base, so the first commit on a branch links; it also records a `commit_decision` (committed / declined / never asked) and reconciles from git at end-of-change.
+  - A single declarative manifest states, per bundle file, when it is required and who writes it, guarded by a test so a future file cannot ship without declaring its expectation.
+  - A new fail-closed `bundle-completeness` gate runs at end-of-change: under `bundle_completeness=strict` (the default) a required-but-missing/empty/invalid file reads "Needs your attention", naming the file and its writer, and blocks via the Stop hook. `warn` surfaces it without blocking; `off` falls back to the deprecated `evidence_existence_gate`. A cache-backfilled file is reported, never passed off as clean; non-feature / no-bundle / CI turns skip the gate.
+
+- 018aac8: Spec pipeline (#512), Part A: every `spec freeze` now writes a human-readable
+  `specification.md` beside the canonical `specification.json` in the feature bundle.
+
+  - `specification.md` is a derived, read-only projection rendered from the frozen
+    `FeatureSpec` on every freeze, so it can never drift and is never a second source of
+    truth (the input-markdown deletion of #402 is unchanged).
+  - Like `report.html` (#371) it is a non-member sibling: it is not a `FEATURE_BUNDLE_FILES`
+    member, the exporter never parses it, and it is git-ignored by the managed `ledger/` line.
+  - The fail-closed bundle-completeness gate (#511) now pairs the two: a bundle carrying
+    `specification.json` must also carry `specification.md`, or the change fails closed under
+    strict mode (surfaces as inconclusive under warn).
+  - The `FeatureSpec` type and schema gain an optional, tolerant `non_goals` field (additive;
+    specs authored without it still validate and freeze unchanged).
+
+## 1.79.0
+
+### Minor Changes
+
+- dce2fc6: Rebuild the site-map workflow so it earns the trust it reports. The engine drafts the map
+  skeleton from proven extraction instead of the model hand-typing it, detects navigation links
+  from the code, records run progress so a new session resumes instead of restarting, batches every
+  preflight question into one interruption, and reports an honest verdict (Safe to merge / Needs
+  your attention / Inconclusive) when a map is absent or records no links. The dashboard gains a
+  full-screen map, a readable zoom floor, and live run progress. As the first step, the compiled
+  rule store is now recompiled automatically when it goes stale on the per-turn refresh path, and
+  `paqad-ai doctor` reports rule-store freshness, so the agent is never served a rule that no longer
+  matches the authored rules.
+
 ## 1.78.1
 
 ### Patch Changes