Organize Iris support files

src/android/view.rs

@@ -829,7 +829,7 @@ impl<State: AndroidAppState> AccessibilityNodeProvider for IrisViewPeer<State> {
 /// `newViewPeer` call from Java. `State`'s app crate wraps this in a
 /// concrete `extern "system" fn` (a generic function cannot be handed to
 /// `register_view_class`, which wants a plain function pointer) -- see
-/// `iris/android-app/src/lib.rs`.
+/// `app/src/android/mod.rs` and `iris/examples/*/android.rs`.
 pub fn new_peer<'local, State: AndroidAppState>(
     mut env: JNIEnv<'local>,
     view: View<'local>,

src/rsc/sense.rs

@@ -1035,7 +1035,7 @@ const FIT_COEFFICIENTS: usize = FIT_DEGREE + 1;
 pub const MAX_FLING_VELOCITY_DP_S: f32 = 8000.0;
 
 /// The numbers its tests assert on come from
-/// `iris/benches/velocity_reference.py`, an independent transcription of
+/// `iris/scripts/reference/velocity_reference.py`, an independent transcription of
 /// the same Kotlin -- not from this code, for the reason
 /// `android_fling_spline`'s doc gives at length.
 #[derive(Default)]

src/rsc/sense_tests.rs

@@ -101,7 +101,7 @@ fn a_button_over_a_list_scrolls_the_list_and_still_clicks() {
         events: EventManager::default(),
     };
 
-    // the case in IRIS_TODO.md's report.
+    // A button nested over a scrolling surface must participate in both gestures.
     let list = rsc.ui.widgets.add_strong(Rect::new(PaintId::WHITE));
     let list_weak = list.weak();
     let button = rsc.ui.widgets.add_strong(Rect::new(PaintId::RED));