Receiving release: preserve store receiving flows and startup improvements

[dt2patel]

Store teams must be able to receive the contents of a selected box, save partial progress, complete later receipts, and trust the quantity and time shown across sessions. This consolidates the Receiving fixes and startup improvements into one PR against main, including the return status/list fixes and a reproducible shared-wrapper build contract.

• Keep selected-box bulk/per-item quantities bounded; retain successful snapshots during partial refresh errors, wait for receiving settings and reject incomplete login setup.
• Apply saved timezone changes immediately and send other tabs to Login after same-session logout, clearing receiving drafts/cache without submitting inventory.
• Initialize return transitions for fresh direct detail links; show only receivable statuses in Open, excluding Cancelled and Received. Preserve backend pagination and search.
• Retain focused shared imports, deferred routes/optional SDKs, embedded startup preloads and eager bundle guards.
• Pin AccxUI to immutable 69dc97e9988d35e0c0e87f4091a17360d3d5de13 in release, merge-build and PR build paths. The PR and merge workflows own the checkout steps because the existing shared workflows cannot accept a wrapper ref. No shared source is copied into the app. No merge or deployment is performed by this PR update.

Closes #750. Tracks #749: linked return inventory reconciliation fails and approval-before-receipt remains blocked; no frontend stock workaround has been introduced. Includes all commits from superseded PR #746.

Validation:

• Node20/22 CI passes at 2e55d0397f4be0e9255c3d65e9249e4faf1f18ce, with clean dependency installation, production build and 86 unit tests: https://github.com/hotwax/receiving/actions/runs/37834820082
• Real in-app Browser on test-maarg: candidate M110864 selected boxes3/2 then7/4 completed10/6; backend QOH60/39->70/45. Cross-tab logout/re-login clears unsaved drafts with no receipt POST. Saved timezone changes history12:46PM NY->9:46AM LA without reload.
• Candidate M110865 Fulfill And Receive: shipped5/2 over two shipments, seven-unit bulk receiving, repeated confirmation creates exactly one batch/two receipt rows; QOH70/45->75/47.
• Open Returns now returns ten Created/Shipped fixtures and excludes the Cancelled fixture, using the deployed endpoint's comma-separated status contract. Direct detail initialization regression fails before and passes after.
• Final compiled candidate M110866:129 distinct lines across three43-unit boxes, two Save Progress sessions then final completion. Backend129 unique receipt rows/129 units in three batches, all129 items/header complete, sample QOH101->102; Completed UI read-only.
• Final compiled return direct detail works after fresh logout/login. Shipment/external/order-name/order-ID/tracking and negative searches pass.
• Release assembly rehearsal validates candidate root/versioned UAT bundles and all referenced assets; retained Receiving v4.1.0 builds against declared AccxUI v1.3.0 after a fresh frozen pnpm9 install through Node22. v4.2.2 is only a rehearsal path; no release tag or deployment was created.

Release remains NO-GO for unrestricted Gorjana rollout. Complete linked return fixture QAR261008RET (sales order, ReturnHeader/Items and ReturnItemShipment links) becomes Received with3/2 accepted, but QOH75/47 remains75/47 rather than78/49; shipment inventory history is empty. Separate valid M100409 approval returns400 and remainsRequested before receipt. Live transitions permit RETURN_ACCEPTED while local approval source requests RETURN_APPROVED; exact deployed cause is unproven. See issue749 validation. No frontend stock workaround. Further compiled Browser check: Shipped P10 is offered receiving but the actual POST400 explicitly rejects PURCH_SHIP_SHIPPED (readback0 accepted); Created P09 POST200 body{} becomesReceived/accepted1 without QOH increase75->76. Actual requests use BROOKLYN. Additional contract validation.

Physical iPad/HID/camera/POS, restricted roles/facility denial, exact Gorjana receiving preferences, external Shopify/NetSuite results and installed-PWA upgrade remain unverified. Earlier route-content mismatch was not reproduced in three final compiled repetitions. Fresh fixture-time shipment metadata needed reload; cause/steady-state repeatability unproven. Combined QA evidence is32 Pass/1 Fail/13 Partial/6 Blocked, with inherited main and fresh candidate results distinguished. This is not blanket certification of every Gorjana flow.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.