Prune commentary and stale Rust port notes

app-rust/tests/fence_fling.rs

@@ -1,22 +1,7 @@
-//! Layer 1 for Iris's 2026-09-08 "flinging doesn't work in horizontal
-//! scroll areas": a real markdown fence in the real transcript screen,
-//! flicked sideways, has to keep moving after the finger leaves.
-//!
-//! The fence is pushed here rather than hunted for in the bench fixture,
-//! so the test knows which row it is pressing and where. The `ScrollArea` it
-//! asserts on is found by walking what is actually drawn -- there is no
-//! handle to it from the outside, and a coordinate would only prove that
-//! *something* moved.
-
 use ai_app::ui::fixture::{PHONE_FRAME_MS, PHONE_SCALE, phone_size};
 use iris::harness::{Harness, TouchAction};
 use iris::prelude::*;
 
-/// The horizontal scroll area drawn inside `top..bottom`, with the box
-/// it was drawn at -- a fence is the only thing in a transcript that pans
-/// sideways. Found by walking what is actually drawn, because there is no
-/// handle to a fence's own `ScrollArea` from the outside and a bare
-/// coordinate would only prove that *something* moved.
 fn fence_scroll_in(h: &Harness, top: f32, bottom: f32) -> Option<(WidgetId, PixelRegion)> {
     h.render
         .active
@@ -86,12 +71,8 @@ fn a_flick_across_a_code_fence_keeps_moving_after_the_finger_leaves() {
         .expect("the pushed fence draws a horizontal scroll area of its own");
     assert_eq!(amt(&h, fence_scroll), 0.0, "a fence opens at its start");
 
-    // Down the middle of the fence's own box, so the press is on the
-    // text inside the scroll area rather than on the row's sender label.
     let y = (box_.top_left.y + box_.bot_right.y) / 2.0;
 
-    // A flick sideways: four samples 8ms apart, accelerating, then the
-    // finger leaves.
     h.touch(TouchAction::Down, Vec2::new(900.0, y), 200);
     for (i, x) in [860.0, 800.0, 720.0, 620.0].into_iter().enumerate() {
         h.touch(TouchAction::Move, Vec2::new(x, y), 208 + 8 * i as u64);
@@ -104,7 +85,6 @@ fn a_flick_across_a_code_fence_keeps_moving_after_the_finger_leaves() {
         "the flick itself must have panned the fence, got {at_release}"
     );
 
-    // Frames for the next half second, with nothing touching the screen.
     let mut t = 240;
     while t <= 740 {
         h.frame(t);
@@ -116,7 +96,6 @@ fn a_flick_across_a_code_fence_keeps_moving_after_the_finger_leaves() {
         "the fence stopped dead at the release: {at_release} -> {coasted}"
     );
 
-    // ...and it settles rather than running forever.
     let settled = coasted;
     while t <= 4_000 {
         h.frame(t);
@@ -132,19 +111,6 @@ fn a_flick_across_a_code_fence_keeps_moving_after_the_finger_leaves() {
     assert_eq!(last, amt(&h, fence_scroll), "the fling never settled");
 }
 
-/// Iris's 2026-09-08 report: "if I try to scroll vertically while a
-/// horizontal scroll animation is still active, it stays locked to the
-/// horizontal scroll. It should let it keep going and instead only affect
-/// vertical scrolling."
-///
-/// Her own diagnosis was the right one -- "tapping outside of something
-/// that a fling is currently active for should have no code in common
-/// with the fling that could influence it" -- and
-/// `sense_tests::a_press_does_not_reach_a_widget_the_pointer_has_just_left`
-/// is the mechanism in isolation. This is the same thing over the real
-/// screen, which is where it was found: the finger goes down on an
-/// ordinary row 500px above a coasting fence, and what must move is the
-/// list, while the fence carries on coasting untouched.
 #[test]
 fn a_drag_away_from_a_coasting_fence_scrolls_the_list_and_leaves_it_coasting() {
     use ai_app::client::transcript_fold::{TranscriptItem, TranscriptRow};
@@ -179,7 +145,6 @@ fn a_drag_away_from_a_coasting_fence_scrolls_the_list_and_leaves_it_coasting() {
         .expect("the pushed fence draws a horizontal scroll area of its own");
     let y = (box_.top_left.y + box_.bot_right.y) / 2.0;
 
-    // Flick the fence sideways and let go, exactly as above.
     h.touch(TouchAction::Down, Vec2::new(900.0, y), 200);
     for (i, x) in [860.0, 800.0, 720.0, 620.0].into_iter().enumerate() {
         h.touch(TouchAction::Move, Vec2::new(x, y), 208 + 8 * i as u64);
@@ -191,10 +156,6 @@ fn a_drag_away_from_a_coasting_fence_scrolls_the_list_and_leaves_it_coasting() {
         "the fence has to still be coasting for this to be the reported case",
     );
 
-    // A row well clear of the fence, taken by its own extent rather than
-    // by a coordinate: the gaps between rows are pointer-transparent, so a
-    // y picked by hand lands on nothing often enough to make a green run
-    // meaningless.
     let probe = box_.top_left.y - 500.0;
     let row = (screen.list)(&mut h.rsc)
         .key_at(probe)