BITESIZE READING LIBRARY V4.3.6 — RESOURCE PERSISTENCE FIX

What was fixed
- Imported resource records now persist in IndexedDB rather than relying on localStorage.
- Large cover images can no longer silently push the imported-resource list over the browser localStorage quota.
- Resource ZIP storage is verified after installation; a failed save now produces a visible error instead of appearing to succeed temporarily.
- The app requests persistent browser storage where supported.
- index.html now redirects to START_READING_LIBRARY.html so both common launch routes use the same canonical app page/storage context.
- Existing imported-resource metadata from the previous localStorage system is migrated into the new IndexedDB metadata store on startup.

Expected behaviour
1. Add a resource ZIP.
2. Close Reading Library completely.
3. Reopen using START - WINDOWS.cmd (or START - CHROMEBOOK.html).
4. The added resource should still appear in My Library and its packaged files should remain available.

Important
Keep using the starter files supplied with Reading Library and keep the application folder in the same location. Browser storage is local to the device/browser profile.
