Fix IDAA recovery meetings auto search

documentation/BOOTSTRAP__AI_Agent_Quickstart.md

@@ -149,6 +149,12 @@ subscribes to the **entire store**. This means unrelated writes to `$ae_loc`
 what you read from these stores inside `$effect` blocks. See `PROJECT__Stores_Svelte5_Migration.md`
 for the long-term fix plan.
 
+For search pages specifically, this usually means:
+- keep true user preferences in persisted local state
+- keep transient triggers, loading flags, and last-executed search keys in session state when possible
+- let the page effect schedule the search, but put the duplicate-execution guard inside the search executor so page-load auto-search still runs after hydration
+- if the search text or filters are mirrored from localStorage on mount, expect that mount-time writes can re-trigger the effect unless the executor has its own guard
+
 ### `{#await}` blocks
 ```svelte
 {#await somePromise}

documentation/GUIDE__SvelteKit2_Svelte5_DexieJS.md

@@ -89,7 +89,7 @@ $effect(() => {
 
 - When you have chains (presentations depend on session; presenters depend on presentation.person_id), make the dependent liveQuery explicitly wait for the upstream ID and log inside each query to verify the order — adding a small `await Promise.resolve()` or `await 0` inside the `liveQuery` is sometimes useful during debugging to ensure the JS microtask queue has a chance to settle after DB writes.
 
-## Practical Patterns from Aether (Journals & Events)
+## Practical Patterns from Aether (Journals & Events & IDAA Recovery Meetings)
 - Journals: The journaling pages use SWR-style background refreshes but reliably render because either (a) the page `+page.ts` blocks to populate DB for critical views, or (b) components accept `data.initial_*` fallback values until `liveQuery` emits. This hybrid approach avoids the "refresh twice" problem while keeping navigation snappy.
 - Journals broad views: if text search is empty, let the local IDB result set drive the visible list. The API can revalidate the cache in the background, but it should not replace a broad "All" view with a limited slice that hides valid rows.
 
@@ -98,6 +98,12 @@ $effect(() => {
     - Provide `initial_session_obj` from `+page.ts` as a first-draw fallback to child components.
     - Use `$derived.by(() => liveQuery(...))` for presentation lists so the observable instance is stable across renders and recreated only when `event_session_id` or `search` changes.
 
+- Search pages with persisted filters or saved query text should keep the auto-search trigger in a page-level `$effect`, but the duplicate guard should live inside the actual search executor. That preserves the first page-load search while blocking repeated identical reruns from localStorage-backed rerenders. In practice:
+    - derive a single `qry_key` from the search inputs
+    - debounce in the `$effect`
+    - compare `qry_key` against a `last_executed_key` inside `handle_search_refresh()`
+    - keep transient loading flags and trigger counters in session state when the value is only used to force a refresh, not as a persisted preference
+
 Example (presentation list pattern):
 ```typescript
 let lq__event_presentation_obj_li = $derived(
@@ -114,6 +120,7 @@ let lq__event_presentation_obj_li = $derived(
 - Add a small `console.log` inside each `liveQuery` closure to confirm when it runs and what `id` it sees.
 - Verify that `+page.ts` either `await`s critical loads or returns `initial_*` payloads for first-render hydration.
 - Confirm that dependent store values (selected IDs) are assigned before components subscribe — use `untrack` to prevent extra reactive cycles.
+- If a search page stops auto-loading after a localStorage change, check whether the duplicate guard was placed in the `$effect` instead of the executor. Guarding too early can suppress the initial search; guard at execution time instead.
 - If a broad Dexie-backed list shows fewer rows than a narrower filter, look for a limit or revalidation step overwriting the local IDB result set. Broad views should stay unbounded unless the user is actually narrowing by text.
 - Ensure your `liveQuery` closures return quickly and do not throw; any exception inside the query can stop updates.
 - If a dependent query appears stale, temporarily add `await 0` in the upstream query or an explicit `Promise.resolve()` after the IDB write to force the microtask queue to flush during debugging.