paqad-ai 1.63.4 → 1.64.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +10 -0
- package/dist/cli/index.js +1384 -1067
- package/dist/cli/index.js.map +1 -1
- package/dist/feature-evidence/adoption.js.map +1 -1
- package/dist/index.d.ts +9 -1
- package/dist/index.js +314 -200
- package/dist/index.js.map +1 -1
- package/dist/kernel/gate.js +105 -86
- package/dist/kernel/gate.js.map +1 -1
- package/dist/rule-scripts/index.js.map +1 -1
- package/dist/stage-evidence/live-writer.js.map +1 -1
- package/dist/stage-evidence/marker-parse.js.map +1 -1
- package/dist/stage-evidence/narration.js.map +1 -1
- package/package.json +1 -1
- package/runtime/AGENT-BOOTSTRAP.md +3 -0
- package/runtime/capabilities/coding/rules/feature-development.md +33 -0
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,15 @@
|
|
|
1
1
|
# paqad-ai
|
|
2
2
|
|
|
3
|
+
## 1.64.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- f99e23e: Plans must now declare reuse (issue #357). `paqad-ai plan compile` requires a `reuse` section recording what existing code was consulted, what the plan will reuse, and why anything new is justified — so a plan can no longer quietly rebuild something the project already has.
|
|
8
|
+
|
|
9
|
+
The enforcement is deterministic schema validation inside the existing compile verb, costing zero model tokens. First-party reuse claims are cross-checked against the code-knowledge index (an unknown symbol fails with a nearest-match suggestion), and framework-native claims are cross-checked against the resolved stack snapshot. Every check degrades gracefully: a missing index or stack snapshot downgrades the check to a warning rather than blocking, and a project with no detected framework carries no new burden.
|
|
10
|
+
|
|
11
|
+
The end-of-change receipt's planning line and the per-feature HTML report now surface the declared reuse counts. Existing `plan.json` files stay valid and readable — the section is required on the compile-input side and optional in the stored schema.
|
|
12
|
+
|
|
3
13
|
## 1.63.4
|
|
4
14
|
|
|
5
15
|
### Patch Changes
|