fix: make IndexedDB storage self-initializing to prevent startup failures

[Copilot]

All storage operations (getAll, put, etc.) threw "Database not initialized" because init() was never called reliably before first use. Route loaders and page components each called storage.init().catch(...) independently, but useStore and feedService — the primary consumers — did not, and init() wasn't idempotent anyway.

Changes

• src/lib/storage.ts: Every storage method now calls ensureInit() before accessing IndexedDB, making the class self-initializing
  • init() caches its promise in initPromise, so concurrent/repeated calls are safe
  • On failure, the cached promise is cleared to allow retry
• Fixed broken JSDoc — unclosed /** block before bulkPut
• Added 7 tests covering auto-init without explicit init(), concurrent init safety, and feed subscription integration without manual initialization

Before/After

// Before: every caller had to remember this, and many didn't
await storage.init().catch(() => {});
const feeds = await storage.getAll('feeds'); // throws if init() lost the race

// After: storage methods auto-initialize
const feeds = await storage.getAll('feeds'); // just works

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[netlify]

✅ Deploy Preview for rss-reader-pwa ready!

Name	Link
🔨 Latest commit	ac14d9a
🔍 Latest deploy log	https://app.netlify.com/projects/rss-reader-pwa/deploys/69a86222db29ff00080f7ad4
😎 Deploy Preview	https://deploy-preview-27--rss-reader-pwa.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.