Miler rider app: surface system, visible design language, backend lifecycle

Design system
- MilerSurface ladder (canvas → working → raised → floating) with MilerPanel
  as layer 1; canvas moved to #DEE3EA so white separates at 1.290:1.
- Visible vocabulary applied across Home, Deliveries, Activity, Account and
  the sheets: hero heads (tabular numeral + small caption, clamped at 1.3x),
  canvas wells for anything that opens, small filled tags for shelf labels,
  demoted placeholders. Recorded in DESIGN_SYSTEM.md §6.
- One icon family: 222 Material glyphs migrated to Lucide; none left outside
  lib/xpress.
- Colour semantics corrected: amber only for what is genuinely owed, brand red
  reserved for the live stop, disabled primaries go neutral rather than pale.

Data and lifecycle
- lib/data/lifecycle.dart reads mutations for what they prove; route_order.dart
  makes admin sequence the single ordering authority; service_day.dart, and
  stop_area.dart rewritten against live Coimbatore addresses (digit-token
  stripping, city stoplist, street suffixes, stammer collapse).
- countLabel states the load once, in bags.

Testing
- 1440 tests passing; golden shot harnesses for Home, Deliveries, Activity,
  sheets and verify, with test/failures/ now gitignored (diff debris).
- New pins: home_gutter_test, stop_area_test, plus updated structural bounds.

Note: this commit also carries pre-existing working-tree deletions that were
present before this work (API_SPEC.md, README.md, demo test fixtures).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

test/route_metrics_test.dart

@@ -0,0 +1,64 @@
+import 'package:flutter_test/flutter_test.dart';
+
+import 'package:miler/views/Dashboard/pickups/route_metrics.dart';
+
+/// ── `metersToStop` measures the leg the caller is on ──
+///
+/// It always read the pickup pair, which on the delivery leg measured the
+/// ride BACK to the kitchen the rider had just left — the card's distance
+/// grew as he approached the customer's door. The leg now arrives as a flag,
+/// and these pin the three behaviours that keep both legs honest.
+void main() {
+  // Roughly Coimbatore: kitchen at RS Puram, door ~4.7 km northeast.
+  const riderLat = 11.0080, riderLng = 76.9500; // standing at the kitchen
+  const stop = <String, dynamic>{
+    'pickuplat': 11.0080,
+    'pickuplon': 76.9502, // ~20 m from the rider
+    'droplat': 11.0183,
+    'droplon': 76.9678, // ~2.2 km away
+    'kms': '9.9',
+  };
+
+  test('the default is the pickup pair — Home is untouched', () {
+    final m = RouteMetricsHelper.metersToStop(
+      stop,
+      riderLat: riderLat,
+      riderLng: riderLng,
+    );
+    expect(m, isNotNull);
+    expect(m!, lessThan(200), reason: 'he is standing at the pickup');
+  });
+
+  test('toDrop measures to the door', () {
+    final m = RouteMetricsHelper.metersToStop(
+      stop,
+      riderLat: riderLat,
+      riderLng: riderLng,
+      toDrop: true,
+    );
+    expect(m, isNotNull);
+    expect(
+      m!,
+      greaterThan(1500),
+      reason: 'the delivery leg is the ride ahead, not the counter behind',
+    );
+  });
+
+  test('a payload with no drop pair falls back to the pickup pair', () {
+    // On many hyperlocal payloads the stop IS the customer's address; a
+    // wrong-ish number beats a dash the rider cannot plan with.
+    final m = RouteMetricsHelper.metersToStop(
+      {'pickuplat': 11.0080, 'pickuplon': 76.9502},
+      riderLat: riderLat,
+      riderLng: riderLng,
+      toDrop: true,
+    );
+    expect(m, isNotNull);
+    expect(m!, lessThan(200));
+  });
+
+  test('the backend kms fallback survives the flag', () {
+    final m = RouteMetricsHelper.metersToStop({'kms': '9.9'}, toDrop: true);
+    expect(m, closeTo(9900, 0.1));
+  });
+}