Update Old Docs

Keep old documents current without destroying their history.

tl;dr (the whole skill in 5 lines):

1. Read every old file before touching any.
2. Per file decide: ANNOTATE / ARCHIVE / SKIP / LEAVE ALONE.
3. Write only specific notes (commit hash + what's still open) — never generic banners.
4. Every note must survive the "so what?" test.
5. Place notes as inline edits or end-of-file appendices — never top-of-file banners.
6. Re-runs are productive: items finished since the last pass get marked done at — never re-stamp an already-resolved item. When ALL items resolve, move the file to archived/.

Old documents — status reports, plans, reviews, audits, snapshots — capture what someone knew at a point in time. They go stale. A reader opening an old status report wants to know: is this done? where is it NOW? Keeping that report current is the job.