@rasensio/aidlc-content 1.77.0 → 1.79.0

package/docs/lifecycle.md

@@ -86,8 +86,9 @@ Two gates are worth knowing because they block real work:
   This one has an override, and the honest observation from the retrospectives is that having the
   override meant it got waved through by reflex on every phase.
 
-`aidlc menu`, or bare `aidlc`, opens a picker of the common commands if you would rather not
-remember them.
+Bare `aidlc`, or `aidlc menu`, opens the console if you would rather not remember the commands:
+`/help` lists them, `/doctor` runs one, plain words go to your agent, and autopilot changes print
+as they happen.
 
 **When requirements move after their phase closed**, `aidlc amend <instance>` is the way back. The
 gates check that artifacts exist, not that they still agree with each other, so editing

package/docs/roadmap.md

@@ -95,21 +95,29 @@ 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
+**Seeing the roadmap** is `aidlc roadmap view`: one self-contained HTML page, opened in the browser,
+with two tabs. **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, its
+dependencies and a copy button for its next command (a triage prompt, start in a worktree, rank, or
+`aidlc continue`); the page itself runs nothing. **Dependencies** is a zoomable map of the `depends_on`
+chains, one labelled group per cluster of linked items, packed side by side: each item under its first
+dependency, a link to anything not yet done drawn red and dashed, an unknown id drawn as a red dashed
+node (a typo there silently blocks `roadmap next`), and items with no dependency hidden behind a
+toggle. Each tab has its own status chips, presets (Active work, Needs a decision, Shipped, Parked,
+Everything) and Ready/Blocked toggles. The Board opens on inbox, backlog and in progress, with done and
+hold folded into rails you click to reopen; Dependencies opens on every status but hides clusters that
+are entirely done ("Open chains only"), and dims what its filters exclude rather than removing it. The
+tab and both tabs' filters live in the URL hash, so a reload or a shared link reopens the same view.
+`/` focuses search, `1` and `2` switch tabs, `Esc` closes the panel or clears the search. The page
+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
 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 `<`.
+its own style and 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 —

package/package.json

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