@rasensio/aidlc-content 1.52.0 → 1.53.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.52.0",
+  "version": "1.53.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills/04-roadmap.md

@@ -145,6 +145,8 @@ For a `hold/` item, show whether it is **parked or declined**, with its reason,
 
 **`aidlc roadmap next`** is the deterministic answer to "what next?": the `backlog/` item with the lowest `priority` among those whose `depends_on` are all `done`, unranked items last, ties by file name (`--explain` shows the order and what was skipped and why; `--json` for scripts). It is read-only and never promotes — promoting stays a person's decision. `priority` is an ordinary extension field a project declares in `roadmap.item_fields`; a rank, where 1 is first. Where it is declared, `--explain` also lists every unranked backlog item, so one sitting last is visible rather than silently last. **`aidlc roadmap rank <item> <n>`** is the one way to change a rank: it puts the item at `n` and renumbers every ranked backlog item 1…k, so ranks stay unique and gap-free.
 
+**Dependency graphs.** `.aidlc/roadmap/graph-backlog.mmd` (backlog items and the `depends_on` edges between them) and `.aidlc/roadmap/graph-full.mmd` (every status, one subgraph each, every edge) are Mermaid files generated from the items — never edit them. Every CLI move rebuilds them. **After moving, adding or deleting an item by hand, run `aidlc roadmap graph`** and commit the graphs with the move; nothing else can see a hand move. When someone asks to see the dependencies, point them at these files rather than drawing a graph.
+
 The frontmatter-only rule holds for browsing, which is a list and must stay cheap enough to run over the whole roadmap. **Triage** below is the one flow allowed into the body, and only as far as the executive summary.
 
 A filename appearing in two status directories is an error: report it rather than guessing which one is current.