Organize Iris support files

app/src/android/mod.rs

@@ -23,7 +23,7 @@ mod enrollment;
 mod transcript_client;
 
 /// The app's `View` subclass, matching the Java side's package --
-/// `app/src/main/java/dev/iris/android/demo/IrisView.java`.
+/// `app/android-project/app/src/main/java/dev/iris/android/demo/IrisView.java`.
 const VIEW_CLASS: &str = "dev/iris/android/demo/IrisView";
 
 #[cfg(not(feature = "bench"))]

app/src/client/log_ring.rs

@@ -262,8 +262,7 @@ fn is_own_target(target: &str) -> bool {
         || target.starts_with("ai_app::")
 }
 
-/// This is the one filter docs/IRIS_TODO.md's "logs way too big" entry
-/// asked for, applied once here rather than at each `debug!` call site:
+/// Applied once here rather than at each `debug!` call site:
 /// Info and above always ring, from anything, because a real warning or
 /// error from a dependency is worth keeping. Debug and Trace ring only
 /// from this app's own targets, and only while tracing is switched on --

app/tests/input_log_roundtrip.rs

@@ -103,7 +103,7 @@ fn tracing_is_silent_off_and_round_trips_the_flick_on() {
     let report = input_lines.join("\n");
     let script_path = concat!(
         env!("CARGO_MANIFEST_DIR"),
-        "/../iris/benches/report_to_touch.py"
+        "/../iris/scripts/report_to_touch.py"
     );
     let mut child = Command::new("python3")
         .arg(script_path)

app/touch/flick-120hz.touch

@@ -1,6 +1,5 @@
 # A finger flick the shape Iris's phone delivers one, from
-# docs/bench/iris-phone-v2-2026-09-06.md and docs/IRIS_TODO.md's
-# "From the phone, 2026-09-06, 22:16": at 120Hz a flick reaches the app
+# docs/bench/iris-phone-v2-2026-09-06.md: at 120Hz a flick reaches the app
 # as DOWN, one or two MOVEs and UP inside a few frames, with the
 # intermediate positions batched inside those MOVEs as historical
 # samples (~4ms apart, the touch digitiser's own rate) rather than