Issues changelog

NEW - 02.09.2026#

Added#

• An Issues section in the admin panel — the GitHub issues on the repository your documentation is built from, sitting under Changes. Changes is what was already done to the project and what it moved; Issues is what has yet to be. Hover a row for a card with the issue's body, labels and author; open one for the whole thing. Issues
• Each issue carries three buttons that hand it to your assistant. Start does the work it asks for. Audit judges the issue before anybody acts on it — is the problem real for this project, are its numbers true, is it already done or already open somewhere else. The third is Verify on a closed issue (prove the result it claims, against a baseline and the pages nobody touched) and Discover on an open one, because an issue with nothing finished has no result to verify yet. Issues
• Generate Issues asks your assistant to look at the project and file what it finds, after two questions: which stage of work you want to be in — observe, understand, discover, decide, plan, execute, measure, verify, learn, coordinate — and which number you want moved. Asking is the point. With no stage named an assistant returns things to build every time, and a backlog with no Measure or Verify in it belongs to a team that never finds out whether the last thing it built worked; the pair you pick also selects the agents that already cover it, so the issues come from this project's own evidence rather than from general advice. Issues
• New issue files one yourself without leaving the panel. Issues