feat(06-08): the ?drive= fixture-replay knob — the D-16 browser leg's fix source

- ?drive=<name> replaces navigator.geolocation with a replay source
  streaming a committed drive fixture (web/test/fixtures/drives/*.json)
  through the LIVE shell: the real pump arms the real
  createGuidanceWatch against it — no test-only bypass of validation
- the replay clock starts lazily at the first watchPosition arm (the
  route draw — nothing emitted before a consumer exists) and plays
  REAL-TIME: the machine's grace/storm clocks read wall time
- window.__ARAHARAH_DRIVE = { pause(), resume(), name }: pause freezes
  emission mid-stream (the capture legs' freeze for scripted taps and
  the REROUTING window), resume continues; the machine's wall clock
  keeps running across a pause (documented harness semantics)
- unknown drive name -> one honest token (ARAHARAH-DRIVE
  state=unknown) + the default geolocation stays — never a crash,
  never arbitrary data (T-06-08 Tampering mitigation); slug guard on
  the name, defensive fixture shape check
- import.meta.glob pattern is ROOT-ABSOLUTE (/test/fixtures/drives/*.json
  — Vite 8's importGlob matches no relative pattern escaping src/,
  verified by the dev-server probe); fixtures inline into the harness
  bundle only — production tree-shake verified clean in BOTH directions
- BA5 posture held: production scan clean, harness bundle carries the
  replay; 147/147 web tests, typecheck clean

web/index.html

@@ -9,7 +9,7 @@
 <body>
   <div id="app"></div>
   <script type="module">
-    /* D-11 Mock-Telegram profile: ?mock=android|ios|tdesktop|macos|web  +  ?scheme=light|dark  +  ?pin=1  +  ?locale=en|ms  +  ?fixdelay  +  ?sessiondelay  +  ?dest=<id>  +  ?fixpair=<pair-id>
+    /* D-11 Mock-Telegram profile: ?mock=android|ios|tdesktop|macos|web  +  ?scheme=light|dark  +  ?pin=1  +  ?locale=en|ms  +  ?fixdelay  +  ?sessiondelay  +  ?dest=<id>  +  ?fixpair=<pair-id>  +  ?drive=<fixture-name> (06-08: the drive replay is read inside the mock module — installMockWebApp replaces navigator.geolocation with the committed fixture's stream)
        Harness-only: served from web/dist-harness, never deployed.
        The WHOLE block below is inside `if (__ARAHARAH_HARNESS__)` — Vite's `define`
        replaces that identifier with `false` in the production build, so the branch is