Prune the docs of work already done: 18,252 -> 7,567 lines

Iris: "the documentation is also pretty crazy too. Can you go through it
and remove everything that's already done and decided? There's entire md
files iirc for projects already complete. And many with checkboxes already
ticked off that just fill up context."

  docs/RUST.md        8503 -> 905    the framework bake-off (options,
                                     recommendation, twelve closed
                                     experiment boxes) and two superseded
                                     "where things stand" sections, out;
                                     what the experiments settled kept as
                                     one line each
  docs/IRIS_TODO.md   1383 -> 229    fifty closed items and six
                                     phone-report sections whose defects
                                     are all fixed
  docs/LAYOUT.md      1116 -> 829    the pre-implementation framing: the
                                     old trait, the checklist, the
                                     migration list, the pass conditions
  docs/TEXTURES.md     496 -> 240    the prior-art survey, the proposal
                                     and its review, all implemented
  docs/REVIEW-*.md     673 -> 0      two completed review passes; the two
                                     findings left open on purpose (mask
                                     hit-testing, the phone's font set)
                                     moved into RUST.md

What survives a prune is what cannot be cheaply re-derived: measurements
(the APK-size table, the phone bench reports), dead ends, invariants and
their reasons, and the design of what exists now rather than the route to
it. AGENTS.md now says that, so the next session prunes as it goes rather
than appending; docs/IRIS_TODO.md's header says items are deleted when
they land rather than ticked.

Deleting the two review files left eighteen citations dangling in code
comments that state their reason inline and cited the file for provenance
only — those now read "(review, 2026-09-06)" and carry no dead pointer.
The emulator's measured GPU capabilities moved to the this-machine-android
skill, where machine facts belong. IRIS.md and DECISIONS.md are dated
records and were not rewritten; each gained one note that paths in older
entries predate the 2026-09-08 crate merge, pointing at the mapping.

Not touched, deliberately: docs/DECISIONS.md's entries (that file *is* the
queue of things for Iris to review, so deleting decided items would remove
what it exists for) and iris/readme.md and iris/TODO, which are hers.

Verified: ./run-tests.sh and `cd iris && cargo test` green, clippy and fmt
clean in every workspace, and every remaining docs/*.md cross-reference
resolves.

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

src/widget/position/lazy_span.rs

@@ -1053,8 +1053,8 @@ impl LazySpan {
         // `prev_slot`/`next_slot`, which already check existence -- but
         // that invariant is enforced by convention across three call
         // sites, not by this function, which would otherwise fail with a
-        // bare "index out of bounds" and no context (docs/
-        // REVIEW-2026-09-06.md finding 2). `slot_widget`, called from
+        // bare "index out of bounds" and no context (review,
+        // 2026-09-06). `slot_widget`, called from
         // here, is what actually indexes/`.expect`s on it. Stays a
         // `debug_assert!` under R1's rule: this runs once per row placed
         // per frame, and its release failure is the `.expect` below rather
@@ -1995,9 +1995,9 @@ mod tests {
     /// its sibling below ever asserts the *evicted* key's own bookkeeping
     /// is actually gone -- both replace row 4 with another row also keyed
     /// `4`, so `heights.remove(&old.key)` removing and re-inserting the
-    /// same key would pass either test even if it did nothing (docs/
-    /// REVIEW-2026-09-06.md finding 10; this is `Selection`'s finding 1
-    /// class of bug -- a stale handle outliving what it points to --
+    /// same key would pass either test even if it did nothing (review,
+    /// 2026-09-06; the same class of bug -- a stale handle outliving what
+    /// it points to --
     /// production-tested from `LazySpan`'s own side). Replacing with a
     /// **different** key is what actually exercises the removal.
     #[test]