@rasensio/aidlc-content 1.56.0 → 1.57.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.
|
@@ -37,6 +37,14 @@ project, so there is no second version to drift.
|
|
|
37
37
|
`init` installs skills for the platforms listed in `.aidlc/config.yaml`. `update` refreshes them after
|
|
38
38
|
the framework changes, and also rewrites the managed block in `CLAUDE.md`.
|
|
39
39
|
|
|
40
|
+
**A version bump alone changes no generated file.** Each embedded skill body opens with
|
|
41
|
+
`<!-- aidlc:generated version=… sha256=… -->`, and the version is the CLI version at which that body
|
|
42
|
+
last changed, not the one that last wrote it: when the emitted body hashes to the recorded `sha256`,
|
|
43
|
+
`update` keeps the line as it is. Stamping the running version instead restamped 42–44 identical files
|
|
44
|
+
on every release, and every branch that ran `update` then conflicted with every other on files nobody
|
|
45
|
+
edited. So an older version in a marker is normal. `aidlc doctor` reports a body only when it no longer
|
|
46
|
+
matches its hash (a hand edit) or names a CLI newer than the one running (upgrade the CLI first).
|
|
47
|
+
|
|
40
48
|
**Anything you write inside that managed block is lost on the next update.** Put project instructions
|
|
41
49
|
above the start marker or below the end marker. This repo's own `CLAUDE.md` says so at the top, and the
|
|
42
50
|
"Lessons That Keep Costing Us" section sits deliberately outside the block for exactly that reason.
|