fix(idaa): resolve ~1-year 'no meetings found' bug on recovery meetings page

Root cause: stale IDB records from prior deploys persisted indefinitely.
Fast path returned 0 (account_id mismatch), API errored silently, and the
error state showed the same message as a genuinely empty result — making
the failure indistinguishable from real data.

Fix is layered defense:
- Bump IDB_CONTENT_VERSIONS.events.event to 2 (one-time force-clear for all users)
- Add check_and_clear_idb_table() helper to store_versions.ts; wire it in
  (idaa)/+layout.svelte to catch future version mismatches on session start
- One silent auto-retry (3s) on API failure before surfacing error UI
- Distinct error state (Unable to load meetings) separate from empty state
- Escape-hatch cache-reset button after 8s when zero results + no active filters
- Document root cause and fix in README.md and BOOTSTRAP__AI_Agent_Quickstart.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

documentation/BOOTSTRAP__AI_Agent_Quickstart.md

@@ -336,6 +336,38 @@ These are real incidents — know them before you start.
     replacing the local IDB result set. For empty text searches, the full local result set
     should drive the display; server refreshes should update cache, not shrink visibility.
 
+13. **Not bumping `IDB_CONTENT_VERSIONS` when changing `properties_to_save`** — this caused
+    the IDAA Recovery Meetings "no meetings found" bug for approximately one year (2025–2026).
+
+    **What happened:** A deploy changed `properties_to_save` in `ae_events__event.ts`, but no
+    one bumped `IDB_CONTENT_VERSIONS.events.event` in `store_versions.ts`. Existing users kept
+    the old stale event records in IndexedDB indefinitely. On the Recovery Meetings page, the
+    fast path (IDB search) returned those stale records, which all failed the `account_id`
+    filter and returned 0 results. The API call then either errored silently or was filtered
+    to 0 by the secondary client-side filter. Critically, the error state and the genuinely
+    empty state showed the **same** "No meetings found" message — users and staff had no
+    indication a failure had occurred. The manual Full Reset (via the `?` help panel) always
+    fixed it, but no one knew why it worked, making the root cause impossible to track down.
+
+    **The fix (2026-05-16):** `check_and_clear_idb_table()` in `store_versions.ts` is now
+    wired in `src/routes/idaa/(idaa)/+layout.svelte` for `db_events.event`. On a version
+    match it costs one localStorage read. On a mismatch it silently clears the table; the
+    SWR pattern then repopulates from the API on next load.
+
+    **The rule going forward:**
+    - When you change `properties_to_save` in any `ae_events__*.ts` file (or any other
+      object file) in a way that makes existing cached records stale — fields added, removed,
+      renamed, or where a computed field's behavior changes — **bump the matching entry in
+      `IDB_CONTENT_VERSIONS` in `src/lib/stores/store_versions.ts`**.
+    - If the table is not yet wired, wire it first (see the wiring instructions in the
+      `IDB_CONTENT_VERSIONS` comment block in `store_versions.ts`).
+    - Currently wired: `events.event`. All other tables are not yet wired.
+
+    **Also:** Never show the same UI message for both a failed API call and a genuinely empty
+    result. Always distinguish `qry__status === 'error'` from `qry__status === 'done'` with
+    0 results in your templates. Silent failures look like data problems and are extremely
+    difficult to diagnose.
+
 ---
 
 ## 8. Source Layout (Quick Reference)