Warn when current GPS outruns server-confirmed route results

[OziinG]

Closes #212

Change control: EVNSolution/clever-change-control#265

Outcome

• derives raw mismatch evidence only from server-owned operationalState: in-progress lifecycle, fresh/reliable position, server-evaluated proximity threshold, nearest stop sequence, and authoritative server progress
• maps that evidence through the canonical operational-state presentation and reuses its Alert, GPS, Server, Gap, and Sync Pills
• keeps Gap strictly Device-to-server; when Device evidence is absent, the warning shows Gap unknown
• preserves GPS as location evidence only; it never marks a stop delivered
• suppresses warnings for stale/unreliable GPS, server threshold false, missing legacy evidence, terminal routes, and the next unresolved stop

Kitchener regression

The 1/11 server-results versus GPS-near-Stop-11 case renders canonical evidence including:

• Alert warning
• GPS fresh
• GPS Stop 11 nearby
• Server 1/11
• Gap unknown when Device evidence is absent
• Sync unknown

The warning states that at least nine earlier planned stops have no result and that GPS proximity does not confirm delivery.

Verification

• focused route tracking and operational-state tests: 55/55
• full Shopify tests: 616/616
• lint: pass, zero warnings
• build: pass
• typecheck: pass
• public URL guard: pass
• Shopify Polaris App Home component validation: pass
• git diff --check: pass
• control-plane preflight: ready

The current node:test harness has no JSX transform or DOM renderer. Accessibility is therefore covered by the closest available source contract for role="alert", the warning banner heading, the evidence group label, and canonical Pill wiring; no new test dependency was added.

Release boundary

This PR is source-only. It does not merge or deploy.

[OziinG]

Implementation verification is complete for head 1ec12f2811e77997b1d109a0a992a1057c40095d.

• GitHub CI run 32785157691: success
• focused tracking: 41/41
• full Shopify: 613/613
• lint, build, typecheck, public URL guard, compose validation, and diff check: pass

Independent code-reviewer and architecture review remain required before merge. This implementation lane has not approved, merged, or deployed the PR.

[OziinG]

HOLD remediation is now on exact head 04691aac3f87d7fdf7106be9c07e42c7fa957336.

• Removed Shopify-owned 100m/coordinate proximity logic.
• Raw mismatch evidence now requires server operationalState: IN_PROGRESS, FRESH, reliableForProximity=true, withinProximityThreshold=true, nearestStopSequence, and authoritative serverProgress counts.
• Missing legacy state/progress stays unknown and suppresses the warning; no missing count is coerced to zero.
• Canonical operational-state.js now owns the alert presentation and reuses its Alert/GPS/Server/Gap/Sync Pills.
• Gap remains Device-to-server and is Gap unknown when Device evidence is absent.
• Server-resolved SKIPPED/CANCELLED terminal outcomes are represented by authoritative resolvedStopCount; the conservative earlier-unresolved lower bound prevents false warnings at the next unresolved stop.
• Added Kitchener, stale/AGING, unreliable, threshold-false, missing evidence, SKIPPED/CANCELLED, Device-absent, malformed mismatch, accessibility wiring, and no-separator regressions.

Fresh local evidence: focused 55/55; full Shopify 616/616; build, typecheck, lint, public URL guard, Polaris component validator, diff check, and control-plane preflight all pass.

Accessibility test gap: this repository node:test harness has no JSX transform or DOM renderer. The closest available contract asserts role="alert", banner heading, evidence aria label, canonical Pill wiring, and no middle-dot/bullet separator without adding a new dependency.

No merge or deployment was performed.