Qualify priority mobile planning and signed-in persistence

[sarthakagrawal927]

Current queue disposition — 11 September 2026

The Google callback, owner sign-in, bucket-list create/complete/reopen/delete with reload, and Hub continuity are verified. Current deployment succeeded. Two-account, failure-path and cross-device qualification remain broader follow-ups.

This remains an open repository backlog issue. Its outstanding acceptance criteria are not marked complete. The owner-approved minimum-use review has moved it out of the immediate project queue; the original requirements below and existing README references are preserved. To resume, remove queue: excluded and unarchive the project card.

The owner prioritized Live alongside Kith, Setline, Calorie and Anchor for immediate personal use. A guest pass does not establish signed-in owner readiness.

• Repair failed bucket-list saves: preserve the draft and await IndexedDB transaction completion. Regression proves an aborted transaction cannot report success.
• Deploy storage and canonical authentication-origin repairs. Source 054f802 was verified at 100% traffic (Worker version c4b3933a-f322-409f-9073-74c6d22107ca).
• Actual hosted mobile onboarding, aborted-save alert and retry, prior-item preservation, completion, deletion and reload pass in fresh Chromium and WebKit browsers. No onboarding fixture or API interception; synthetic local data only, no application POSTs, no horizontal overflow.
• Google handoff now returns 200 and uses the canonical callback instead of failing INVALID_ORIGIN.
• Google OAuth client must authorize https://live.significanthobbies.com/api/auth/callback/google. Actual provider screen currently rejects the request with redirect_uri_mismatch. Existing redirect entries must be retained. Owner configuration action requested; no credentials or production OAuth configuration changed.
• Real Google sign-in, personal saving, reload, account isolation and authenticated Hub continuity.
• Release and verify build-specific HTML caching. Actual /hobbies cache hits referenced six missing JavaScript assets after deployment. Repair 640c7e9 isolates HTML by Next BUILD_ID, retains query distinctions and makes browsers revalidate. Release build and full quality gate pass (593 tests); Quality 34207675150 and Browser CI 34207675287 passed; source 640c7e9 is deployed at 100% traffic (version 3e4560ff-28ce-4244-afac-6c6dde48edf5). Actual /hobbies MISS and HIT both reference 20 available scripts.
• Release cache-hit browser revalidation follow-up 9a4c9d1: hosted HIT unexpectedly raised max-age to 14400 seconds. Worker now restores the route policy; local full quality and CI 34208622633 / 34208622688 passed. Final source 9a4c9d1 is at 100% traffic (version 7b0b99fc-1e03-4cff-911d-392de6d8f272). /hobbies and /find-your-hobby MISS and HIT return max-age=0 with all scripts available; /login remains private/no-store with all scripts available. Mobile Chromium and WebKit full guest journeys passed again on this source.
• Restore GitHub deployment capability: repository Actions metadata reports CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID absent. Manual run 34205783560 failed its credential-presence gate before deployment. The checked release used the existing authenticated local CLI. No credential values were accessed or copied.

Evidence captured 8 September 2026. iPhone installation/launch and signed-in cross-device use are not implied by browser or simulator results. Keep this issue open until the remaining owner-use gates are verified.

September 10 provider recheck

Fresh isolated browser followed the real Hub sign-in button. Google returned Error 400 redirect_uri_mismatch for https://live.significanthobbies.com/api/auth/callback/google before account selection. The public directory contains five maintained apps and no Journal; Hub login retains callbackUrl=/hub. Existing OAuth client and callback entries must be preserved when adding this callback. No auth configuration, credentials or account records changed; isolated browser closed.

[sarthakagrawal927]

Fresh 9 September 2026 verification from an isolated 390px Chromium browser: the actual Continue with Google button at /login?callbackUrl=%2Fhub reaches Google and visibly fails with Error 400: redirect_uri_mismatch.

Public OAuth client identifier: 207924374505-t0nqhf0ei3ref87aeaigvvb5dafdicvd.apps.googleusercontent.com.
Required authorized redirect URI: https://live.significanthobbies.com/api/auth/callback/google.

Owner action: add that exact URI to this existing Google OAuth client's Authorized redirect URIs, preserving all existing entries. Do not change Live's stable auth identities or use an apex callback workaround. No credentials were entered or provider configuration changed. Real sign-in, account isolation, persistence and Hub continuity remain unqualified. Fresh local real-handler/auth-routing tests pass 19/19. The owning repository retains the provider screenshot and compact receipt at docs/qualification/2026-09-09/.