@rasensio/aidlc-content 1.66.0 → 1.67.0

package/docs/roadmap.md

@@ -95,6 +95,22 @@ works the backlog may ask it what is next, but promoting stays a person's decisi
 that picks has no way to write. `priority` is an ordinary extension field (a rank, 1 first) that a
 project declares in `roadmap.item_fields`.
 
+**Seeing the roadmap** is `aidlc roadmap view`: one self-contained HTML page, opened in the browser.
+The kanban board has a column per status — backlog in `roadmap next` order with ranks and ready items
+marked, the latest 20 done items with the rest behind a control, the reason on each hold card — and
+each card links to its item file, its instance folder and retrospective, and its pull requests on
+GitHub when the branch and `origin` are known. Clicking a card opens its executive summary and its
+dependencies. Below the board, a zoomable map lays out the `depends_on` chains: each item under its
+first dependency, dashed links to the rest, an unknown id drawn as a red dashed node (a typo there
+silently blocks `roadmap next`), blocked items marked, and items with no dependency hidden behind a
+toggle. The page is written to `<git-common-dir>/aidlc/roadmap.html` — outside every working tree, so
+it is never committed and every worktree shares one copy — or wherever `--out` says; `--no-open` only
+writes it. Nothing rebuilds it on a move: until 2026-10-06 every move rewrote two committed Mermaid
+graphs, so every promotion left two shared generated files modified in whichever checkout ran it.
+`aidlc doctor` deletes those files where they are still the generated ones, and `aidlc roadmap graph`
+is now an alias of `view`. All item text is escaped and the page's Content-Security-Policy allows only
+its own script, because titles here routinely carry backticks, quotes and `<`.
+
 **Ranking the backlog** is `aidlc roadmap rank <item> <n>`: it puts a `backlog/` item at rank `n` and
 renumbers every ranked backlog item 1…k in their existing order, so ranks stay unique and gap-free —
 hand-typed ranks drift, because an item leaving the backlog leaves a hole and two items typed at one

package/package.json

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

package/skills/04-roadmap.md

@@ -145,7 +145,7 @@ 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.
+**Seeing the roadmap.** When someone asks to see the roadmap or its dependencies, run **`aidlc roadmap view`** rather than drawing a graph. It writes one self-contained HTML page — a kanban board of every item by status, and a zoomable map of the `depends_on` chains with blocked items and unknown ids marked — and opens it in the browser (`--no-open` only writes it; `--out <path>` writes it elsewhere). The page lives in the git common dir, outside every working tree, so it is never committed and nothing rebuilds it on a move; run the command again for a fresh one. `aidlc roadmap graph` is the same command.
 
 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.