Treat network failures, non-success responses, unreadable or oversized receipts, and receipt mismatches as unknown upload outcomes. Bound receipt reads and signal that callers must reconcile with the original idempotency key, rather than assuming a failed request was not committed. Input validation still rejects invalid documents before any request.
Local Next.js build passed with an existing copied dependency tree; CI verifies the locked build.
This change classifies uncertain outcomes; the durable reconciliation workflow and customer route are not yet wired.
## Change
Treat network failures, non-success responses, unreadable or oversized receipts, and receipt mismatches as unknown upload outcomes. Bound receipt reads and signal that callers must reconcile with the original idempotency key, rather than assuming a failed request was not committed. Input validation still rejects invalid documents before any request.
## Validation
- Focused client tests: 9 passed; full suite: 1,247 passed, 190 skipped; typecheck passed.
- Local Next.js build passed with an existing copied dependency tree; CI verifies the locked build.
- This change classifies uncertain outcomes; the durable reconciliation workflow and customer route are not yet wired.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Change
Treat network failures, non-success responses, unreadable or oversized receipts, and receipt mismatches as unknown upload outcomes. Bound receipt reads and signal that callers must reconcile with the original idempotency key, rather than assuming a failed request was not committed. Input validation still rejects invalid documents before any request.
Validation