@rasensio/aidlc-content 1.62.0 → 1.63.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/docs/lifecycle.md +3 -1
- package/package.json +1 -1
package/docs/lifecycle.md
CHANGED
|
@@ -147,7 +147,9 @@ instance changed the same requirement first, its revision no longer matches the
|
|
|
147
147
|
completion is not recorded, and nothing is written. That is the whole conflict rule — a requirement is
|
|
148
148
|
never silently overwritten. `aidlc spec fold <instance> --dry-run` runs the same check any time before.
|
|
149
149
|
An instance with no delta completes exactly as before; nothing was back-filled, so the corpus starts
|
|
150
|
-
empty and grows.
|
|
150
|
+
empty and grows. A `## Spec delta` section that holds only prose — "None." and the reason — counts as
|
|
151
|
+
no delta. One with nothing in it, or whose only block headings sit inside a code fence or at the wrong
|
|
152
|
+
level, is still an error, because that is a delta someone meant to write.
|
|
151
153
|
|
|
152
154
|
**Before code is written**, `aidlc cross-check <instance>` reads `requirements.md`, `design.md` and
|
|
153
155
|
`tasks.md` side by side. `aidlc review` reads one artifact at a time, so a criterion design forgot, or a
|