WIP: a widget's region stays put and its placement moves in it

The protocol split: `region` is the box a parent gives a widget -- what a
fraction it declares or reports is a fraction of, and the coordinates
every region it writes composes within -- and it is the same box on the
ask that measures and the ask that places. `placement` is what of that
region the drawing takes, chosen by the parent per axis or by the
widget's own answer and alignment.

That is what stops a fraction being resolved twice: the placing ask no
longer hands the widget its own answer as its box, so nothing under it
re-resolves against a box that came from its own report. `reports_of`
and `decided` are gone, folded into the two regions; `box_of` is gone;
`declared_box` becomes `ask_box`, which gives a rule the region's length
and takes the position from the placement.

84 of 92 suite tests pass. Five text and region-node cases still diverge
warm against cold, and three count a second widget draw where a span's
measuring ask and its placing ask give different placements.

core/src/ui/active.rs

@@ -9,12 +9,16 @@ use crate::{
 #[derive(Debug)]
 pub struct ActiveData {
     pub id: WidgetId,
-    /// The box its drawing is in, in `parent_move`'s coordinates.
+    /// The box its parent gave it, in `parent_move`'s coordinates: what it
+    /// was asked about, and what a fraction under it is a fraction of. A
+    /// local redraw asks here.
     pub region: UiRegion,
-    /// The box its parent gave it, in the same coordinates: what it was
-    /// asked about, before its own answer placed its drawing inside it.
-    /// `region` is that placement, and a local redraw asks here.
-    pub given: UiRegion,
+    /// Where its drawing sits inside that box, in the box's own coordinates.
+    pub placement: UiRegion,
+    /// Whether its drawing read that placement, which is what says whether
+    /// moving it within the region is a redraw or only a different claim on
+    /// the same drawing.
+    pub reads_placement: bool,
     /// The same box as lengths of its parent's box, which is the one route
     /// to a box in pixels: a draw threads these down a level at a time, and
     /// [`crate::UiRenderState::redraw`] takes the same steps back up.