@rasensio/aidlc-content 1.77.0 → 1.78.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/roadmap.md +18 -10
- package/package.json +1 -1
package/docs/roadmap.md
CHANGED
|
@@ -95,21 +95,29 @@ works the backlog may ask it what is next, but promoting stays a person's decisi
|
|
|
95
95
|
that picks has no way to write. `priority` is an ordinary extension field (a rank, 1 first) that a
|
|
96
96
|
project declares in `roadmap.item_fields`.
|
|
97
97
|
|
|
98
|
-
**Seeing the roadmap** is `aidlc roadmap view`: one self-contained HTML page, opened in the browser
|
|
99
|
-
|
|
100
|
-
marked, the latest 20 done items with the rest behind a control, the reason on each hold card —
|
|
101
|
-
each card links to its item file, its instance folder and retrospective, and its pull requests on
|
|
102
|
-
GitHub when the branch and `origin` are known. Clicking a card opens its executive summary
|
|
103
|
-
dependencies
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
98
|
+
**Seeing the roadmap** is `aidlc roadmap view`: one self-contained HTML page, opened in the browser,
|
|
99
|
+
with two tabs. **Board** has a column per status — backlog in `roadmap next` order with ranks and ready
|
|
100
|
+
items marked, the latest 20 done items with the rest behind a control, the reason on each hold card —
|
|
101
|
+
and each card links to its item file, its instance folder and retrospective, and its pull requests on
|
|
102
|
+
GitHub when the branch and `origin` are known. Clicking a card opens its executive summary, its
|
|
103
|
+
dependencies and a copy button for its next command (a triage prompt, start in a worktree, rank, or
|
|
104
|
+
`aidlc continue`); the page itself runs nothing. **Dependencies** is a zoomable map of the `depends_on`
|
|
105
|
+
chains, one labelled group per cluster of linked items, packed side by side: each item under its first
|
|
106
|
+
dependency, a link to anything not yet done drawn red and dashed, an unknown id drawn as a red dashed
|
|
107
|
+
node (a typo there silently blocks `roadmap next`), and items with no dependency hidden behind a
|
|
108
|
+
toggle. Each tab has its own status chips, presets (Active work, Needs a decision, Shipped, Parked,
|
|
109
|
+
Everything) and Ready/Blocked toggles. The Board opens on inbox, backlog and in progress, with done and
|
|
110
|
+
hold folded into rails you click to reopen; Dependencies opens on every status but hides clusters that
|
|
111
|
+
are entirely done ("Open chains only"), and dims what its filters exclude rather than removing it. The
|
|
112
|
+
tab and both tabs' filters live in the URL hash, so a reload or a shared link reopens the same view.
|
|
113
|
+
`/` focuses search, `1` and `2` switch tabs, `Esc` closes the panel or clears the search. The page
|
|
114
|
+
opens light; the header button switches to dark, and the browser remembers it across regenerations. The page is written to `<git-common-dir>/aidlc/roadmap.html` — outside every working tree, so
|
|
107
115
|
it is never committed and every worktree shares one copy — or wherever `--out` says; `--no-open` only
|
|
108
116
|
writes it. Nothing rebuilds it on a move: until 2026-10-06 every move rewrote two committed Mermaid
|
|
109
117
|
graphs, so every promotion left two shared generated files modified in whichever checkout ran it.
|
|
110
118
|
`aidlc doctor` deletes those files where they are still the generated ones, and `aidlc roadmap graph`
|
|
111
119
|
is now an alias of `view`. All item text is escaped and the page's Content-Security-Policy allows only
|
|
112
|
-
its own script, because titles here routinely carry backticks, quotes and `<`.
|
|
120
|
+
its own style and script, because titles here routinely carry backticks, quotes and `<`.
|
|
113
121
|
|
|
114
122
|
**Ranking the backlog** is `aidlc roadmap rank <item> <n>`: it puts a `backlog/` item at rank `n` and
|
|
115
123
|
renumbers every ranked backlog item 1…k in their existing order, so ranks stay unique and gap-free —
|