Name the handoff doc in AGENTS.md and generalise it to HANDOFF.md

A fresh session had no way to learn the handoff existed: AGENTS.md named
only docs/PLAN.md, and the filename tied the document to one piece of work.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

AGENTS.md

@@ -6,9 +6,11 @@ submodule. The
 Android app uses a thin Java activity and `android-view`; desktop uses winit.
 
 `docs/PLAN.md` is the design source of truth. Read it before structural work
-and update it when a decision changes. Working documents are pruned as work
-lands: preserve current invariants, measurements, and failed hypotheses, not a
-chronicle of completed tasks. Do not create a decisions log.
+and update it when a decision changes. `docs/HANDOFF.md` is where the work in
+flight stands; read it first in a fresh session and keep it current. Working
+documents are pruned as work lands: preserve current invariants, measurements,
+and failed hypotheses, not a chronicle of completed tasks. Do not create a
+decisions log.
 
 ## Architecture
 

docs/HANDOFF.md

@@ -1,7 +1,9 @@
-# Iris extraction handoff
+# Handoff
 
-Operational handoff for pulling Iris out of ai-app into a standalone framework.
-Not a decisions log; delete it when the extraction is done.
+Where the work in flight stands, for a session picking it up cold. Not a
+decisions log; when a piece of work finishes, replace this with the next one
+rather than accumulating both. The subject now is pulling Iris out of ai-app
+into a standalone framework.
 
 ## Where things stand
 

docs/LAYOUT.md

@@ -6,7 +6,7 @@ without reading that result does not make the parent's size depend on it.
 
 §1 and §2 have landed in Iris (#16 and #18) and the notes below have been
 brought to what shipped rather than what was proposed; §3 to §6 describe the
-same design as it stands. `docs/IRIS_EXTRACTION_HANDOFF.md` has the invariants
+same design as it stands. `docs/HANDOFF.md` has the invariants
 the code now rests on and what is still to do.
 
 ## Design