show-backloglisted

# show-backlog Someone wants to see the work state. The repository already renders it: `generate-dashboard` projects the pool, the sprints, the timeline, the records and the changelog into one page from the committed files. Reading `backlog.md` aloud into chat is a second, worse rendering of a thing that renders itself - slower, lossy, and stale the moment it is written. So: build the page, hand over the link, and say the two or three numbers that answer the question actually asked. Do not paste the backlog. ## Steps 1. **Find the generator.** It is an optional entry, so a repo may not have it. Look for `scripts/generate-dashboard/index.mjs` (the manifest path; `self-verify` knows whether this repo took the entry). If it is not there, go to "No dashboard in this repo" below. 2. **Find how this repo runs it.** Do not assume a package manager or a script name. Read `package.json` (or the equivalent task file) and look for a script whose command mentions `generate-dashboard`; if one exists, run it with the package manager this repo's lockfile implies. If none exists, run the generator directly - Node is already a prerequisite of the shipped guards, so this always works: ``` node scripts/generate-dashboard/index.mjs --serve ``` `--serve` builds the page and serves it on `http://localhost:9675`, rebuilding when a source file changes. Without `--serve` it writes `_dashboard/index.html` and exits, which is the right call when the user wants