v1.97.0 ·
The tutorials caught up with the product
The tutorials on this site were last touched in early September. Since then AIDLC grew autopilot, a project constitution, roadmap ranking, a console, hooks and a way to undo a task. None of that was in the tutorials. A new reader could finish the whole series and never learn the backlog can work itself.
Worse, one chapter taught something wrong. The chapter on gates said aidlc transition --override was the way past a review finding. It is not. It skips the ownership gate, the one that stops you moving work someone else has claimed, and only a person may run it. A finding is settled by its status, not by a flag.
What changed
Getting-started and the eight deep-dive chapters were checked against the current CLI and fixed where they disagreed. Getting-started now opens the console: run aidlc with no arguments and you get the dashboard. The gates chapter covers the read-only reviewer agent and task agents. The backlog chapter covers roadmap next, rank and view. The customization chapter covers aidlc hook and the constitution.
Two things did not fit any chapter, so they became recipes instead: packages/content/howto/let-autopilot-work-the-backlog.md and packages/content/howto/undo-a-task.md. Five existing recipes that no longer ran as written were fixed. On the docs pages, doctor --fix is gone, because that flag does not exist.
The terminal frames shown with each chapter were re-recorded from real runs of the built CLI in scratch projects, where the output had changed. The ones that still matched were left alone.
Why this way
I kept the series at eight chapters with the same names and order. Adding chapters would have turned a catch-up into a rewrite, and that is how a docs pass never ends.
I also did not add a new check to keep the docs current. packages/website/src/test/tutorial-drift.test.ts already fails when a tutorial names a command or flag that no longer exists. It cannot tell when shown output is stale, or when a feature is missing altogether. That gap is still open. Another gate that every future change has to pass costs more than a pass like this one every few weeks.
What it does not cover
The autopilot recipe was checked flag by flag against --help, and autopilot status was run, but a full autopilot run was not started from it. The Codex line in the cost recipe was checked against the docs, not against real Codex records. And the drift test still only catches a renamed command, so the next month of features will drift the same way unless someone reads the pages again.