Receive durable driver support reports with scoped lookup - #476
Merged
Merged
Conversation
Constraint: Keep reports within existing account, device, and tenant diagnostic boundaries. Rejected: New notification or support-auth surface | Not required for server receipt and would expand operational scope. Confidence: high Scope-risk: narrow Directive: Deploy USER_REPORT ingestion before releasing the mobile report action. Route-less receipts are private server records, not dispatcher notifications. Tested: Contract and HTTP tests 55/55; disposable PostgreSQL integration 2/2; typecheck; changed-file lint; API build; diff check; independent review. Not-tested: Production deployment and final connected-device report scenario pending.
OziinG
force-pushed
the
codex/cc-307-driver-support-reports
branch
from
October 2, 2026 08:14
d05bb78 to
a08a35f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A driver stuck on session recovery can submit a privacy-safe support report through the existing independent diagnostic transport. The server now accepts
USER_REPORTwith the existing durable, ID-specific acknowledgement, and authenticated operators can find an exact report by routePlanId and diagnosticId after it leaves the recent 25-record window.No new database schema, notification, delivery-state mutation, or global support privilege is introduced. Route-less reports are durably stored as account-private records and are only accessible to authorized server operations through controlled support procedures; receipt must not be described as dispatch notification. Deploy this server contract before the mobile release.
Target: #473. Change control: EVNSolution/clever-change-control#307; project-start EVNSolution/clever-change-control#145. Development-linked branch: codex/cc-307-driver-support-reports. Mobile release: EVNSolution/clever-routes-app#294.
Validation: RED tests confirmed missing USER_REPORT/exact lookup behavior and the overbroad non-report lookup. Contract/HTTP 55/55 and disposable PostgreSQL integration 2/2 passed, including idempotent replay, old report lookup, tenant isolation, route-less privacy, and exclusion of old non-report records. Typecheck, scoped lint, API build and diff check passed. Independent review found no remaining release-blocking issue. Exact-head CI, production deployment and final physical-device reporting remain pending.
Concurrent Work Gate: allowed-with-non-overlap. Open #463/#460/#427/#402 do not own these diagnostic contract/query files. Single PR groups one compatible server contract and its tests/docs; it is separate from the mobile artifact rollback unit. No production delivery data changes.
Context result: apps/delivery-api/docs/api/driver-runtime-diagnostics.md documents the receiver, operator query, receipt semantics and route-less limitation. Broader service-context follow-up remains tracked in the release; do not close the release change-control until device and Play submission evidence are recorded.