Pages fall away downward, the pickup comes back, and a real icon set

── Navigation ──

Pages arrived from the right and left to the right. Right is the direction
the system back gesture drags, so a page leaving under a button press read as
a swipe nobody made — and every push in this app is a layer over the one
before it, which arrives from below. The axis is vertical now: the incoming
page rises and covers, the page underneath stays put and dims, and back drops
the top page off the bottom. Full travel rather than the old 14% nudge, which
is what makes the direction nameable. test/page_transition_test.dart holds it.

── Home ──

The pickup pill is back under the greeting. It was cut on the argument that
the form below already carried the pickup; the form is four hundred points
down the screen, and a location you can only see by scrolling to a form is a
location you do not trust. It shows the locality while the form keeps the
door, so the screen answers one question once, and it now has a resolving
state — it used to print the last place you were, confidently, while the fix
was still in flight.

The sphere's caption was falling off the screen. Adding the pill pushed it out
of the scroll viewport, silently, with no overflow warning — the fourth time
Home growing has clipped something under the sphere. DmBookOrb.field is no
longer a constant: the glow gives way to whatever is left, the sphere never
does.

── 74 points of dead canvas, on every root ──

Home, Orders and Account each cleared the floating tab bar by
`MediaQuery.paddingOf(context).bottom + 74`, on the reasoning that the inset is
the home indicator and 74 is the bar above it. Scaffold with extendBody
replaces the body's bottom padding with the bar's whole laid-out height —
measured, a 34pt inset and this bar hand the body 106. They were clearing the
bar, then clearing it again. One helper now, dmTabBarClear().

── One journey, one vocabulary ──

Review said ORIGIN/DESTINATION; Home's form and tracking say PICKUP/DROP.
Three screens a customer walks in order. The tracking card had already written
down the argument; the booking screen hadn't followed.

The rail's first milestone read "Booking created" directly above "Order
created" — down the rail: created, created, in transit. It is "Pickup booked",
which is what JourneyStage.milestoneLabel has called that stage all along on
Orders and on Home's live row.

── The launcher icon ──

tool/icons.py renders all twenty-eight files from one master, because the
failure mode of exporting by hand is nineteen replaced and nine left on the
old mark, at the density nobody checks.

The master is a bare mark on a field, so it cannot be dropped into Android's
adaptive canvas whole: crimson is the background, the white mark is the
foreground, and it is sized by its reach from the canvas centre so a round
mask cannot take the arrow tip. Measured on the built file: 63.7dp against a
66dp safe zone. A real monochrome layer replaces the colour foreground that
was standing in for one — the system tints by alpha, so that themed as a blob.
ic_launcher_round.png exists at last; minSdk is 24 and android:roundIcon had
nothing to resolve to below API 26.

The artwork is flattened (the source vignettes over ten values of red) and its
horizontal offset is placed deliberately rather than inherited — geometric
centring made the mark lean, because the arrow carries the bounding box right
while contributing almost none of the ink.

── Bundle ──

pubspec declared assets/images/ as a folder, which shipped the 974 KB icon
master to every customer for a file no code opens. Named explicitly now.

lib/data/models.dart

@@ -97,9 +97,9 @@ enum JourneyStage {
   /// What a status pill should say.
   ///
   /// Deliberately **not** [CustomerMilestone.of]. The rail collapses the whole
-  /// pickup visit into "Booking created", which is right for a journey read
+  /// pickup visit into "Pickup booked", which is right for a journey read
   /// over days — but a pill on Orders, or the live row on Home, is answering
-  /// "what is happening to my parcel *now*", and "Booking created" is a poor
+  /// "what is happening to my parcel *now*", and "Pickup booked" is a poor
   /// answer while a named Miler is two kilometres from the door. The two
   /// surfaces want different granularity from the same stage, so they get
   /// their own vocabulary.
@@ -151,11 +151,24 @@ enum JourneyStage {
 /// rest of the journey — the part measured in days — the other three.
 ///
 /// The rail's job is the shipment. Everything before the order exists is
-/// **Booking created**; the moment the Miler creates the order the parcel is a
+/// **Pickup booked**; the moment the Miler creates the order the parcel is a
 /// consignment with a tracking number, and the four milestones after that are
 /// the ones a customer checks back for over the following days.
+///
+/// ── Why the first one is not "Booking created" ──
+///
+/// It was, and it sat directly above "Order created". Two rows, one word
+/// apart, both past-tense creations of something the customer cannot
+/// distinguish — a booking and an order are the same parcel to them, and the
+/// rail's whole job is to show movement. Read down the rail it said: created,
+/// created, in transit.
+///
+/// "Pickup booked" is not a new coinage either. [JourneyStage.milestoneLabel]
+/// has called this stage exactly that all along, on Orders and on Home's live
+/// row, so the rail was the one surface using a different word for the state
+/// the rest of the app had already named.
 enum CustomerMilestone {
-  booked('Booking created'),
+  booked('Pickup booked'),
   orderCreated('Order created'),
   inTransit('In transit'),
   outForDelivery('Out for delivery'),