Repository navigation

Prepare Driver 0.2.0 with verified UI and explicit release gates - #67

Draft

OziinG wants to merge 31 commits into

devfrom

cc-315-driver-policy-candidate

Draft

Prepare Driver 0.2.0 with verified UI and explicit release gates#67
OziinG wants to merge 31 commits into
devfrom
cc-315-driver-policy-candidate

Commits on Sep 10, 2026
- Let drivers record the actual completion time with proof
  OziinG
  committed
  06b88d5
- Guide drivers to the approved password recovery path
  OziinG
  committed
  2c2a936
- Show the final-stop ETA without inventing completion time
  OziinG
  committed
  791ff7c
- Prepare the combined Driver feature release after 0.1.14
  OziinG
  committed
  b01162e
Commits on Sep 11, 2026
- Meet Play optimization requirements in generated Android releases
  OziinG
  committed
  13e2c46
- Preserve the 8 GB Android build incident as an operational guardrail
  OziinG
  committed
  bc1ad55
Commits on Oct 6, 2026
- Keep saved delivery times stable while proof uploads recover
  OziinG
  committed
  a7959e5
- Keep driver actions bound to current server authority
  OziinG
  committed
  c39acfa
Commits on Oct 7, 2026
- Preserve driver input until notification navigation is safe
  OziinG
  committed
  d5094bf
- Keep integration installs separate from driver operations
  OziinG
  committed
  ac1e688
- Keep isolated device checks connected to loopback
  OziinG
  committed
  d9740e5
- Record the isolated Driver integration boundary
  OziinG
  committed
  889e35d
- Prevent isolated Android state from reaching release builds
  OziinG
  committed
  7c11922
- Enable device tap evidence without enabling isolated FCM
  OziinG
  committed
  ae3229e
- Allow synthetic report input only inside the isolated device fixture
  OziinG
  committed
  47825ad
- Keep protected notification actions inside the device safe area
  OziinG
  committed
  1075507
- Record device evidence before DSV release decisions
  OziinG
  committed
  6e2db49
- Preserve approved completion while operational notifications defer navigation
  OziinG
  committed
  40eb21c
- Preserve one delivery result when accepted responses are lost
  OziinG
  committed
  eb9264b
- Keep isolated device evidence distinct from release readiness
  OziinG
  committed
  456ffbf
- Keep completed cleanup and audit evidence current for review
  OziinG
  committed
  aee38f8
- Keep completion retries safe when rejection follows an unknown result
  OziinG
  committed
  a1d6dd2
- Recheck assignment before continuing an uncertain completion
  OziinG
  committed
  e37122e
- Keep completion recovery reachable on device screens
  OziinG
  committed
  f560952
- Keep the final device evidence tied to the reviewed candidate
  OziinG
  committed
  047d57f
Commits on Oct 8, 2026
Commits on Oct 11, 2026

Commits

Commits on Sep 10, 2026

Commits on Sep 11, 2026

Commits on Oct 6, 2026

Commits on Oct 7, 2026

Commits on Oct 8, 2026

Commits on Oct 11, 2026