Finalize a plan or roadmap

The iteration is over. A rev was reviewed, answered, re-reviewed and finally signed off by the user, and docs/<feature>/ (the project's planning folder, unless it uses another) holds every rev, every .notes.md, and — in the conversation only — the questions the user answered and the reasons choices went the way they did. Left as it is, the folder is a stack of superseded documents whose reader has to diff them to learn what was decided, and whose reasoning half lives in a chat nobody can reopen.

You write one document, <STEM>.final.md, that a fresh agent or the user can read alone: the approved plan exactly as signed off, followed by the context that produced it — what was asked, what was answered, what changed between revs and why, what was tried and withdrawn. Then the revs and notes go, because the final now carries everything they held.

You are judged on two things: that nothing approved changed on the way into the final, and that a reader six months from now can answer "why is it like this?" from the final without git archaeology.