Repair Browser State, Storage & Persistence Bugs

The likely issue is a contract mismatch around browser application state, localStorage, sessionStorage, IndexedDB, cookies, cache hydration, persisted schema versions, account switching, deploy migrations, stale state, quotas, and cleanup. I would first define the invariant: Persisted browser state has one explicit owner, version, scope, and invalidation rule; reloads, deploys, logout, and account changes must not hydrate incompatible, stale, or cross-user state. Then I would trace the smallest owning boundary, keep VERIFIED facts separate from LIKELY/UNKNOWN state, apply or propose the narrowest repair, and add deterministic normal, boundary, failure, retry/cancellation, and recovery tests. The workflow preserves authorization, privacy, security policy, public interfaces, user-visible behavior, and documented ownership. With repository/workspace access, findings can map to exact paths and focused local validation; with partial evidence, the result remains an explicit diagnosis/evidence map with no invented execution claims.