Refine journal search filtering

documentation/BOOTSTRAP__AI_Agent_Quickstart.md

@@ -306,6 +306,11 @@ These are real incidents — know them before you start.
    redundant on the V3 path. Both paths now pretty-print with 2-space indent.
    See `GUIDE__AE_API_V3_for_Frontend.md` → section 3C for the full explanation.
 
+12. **Broad Dexie result windows get silently clipped** — if a broad "All" view shows fewer
+   rows than a narrower filter, check for a page-level limit or an API revalidation step
+   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.
+
 ---
 
 ## 8. Source Layout (Quick Reference)

documentation/GUIDE__SvelteKit2_Svelte5_DexieJS.md

@@ -91,6 +91,7 @@ $effect(() => {
 
 ## Practical Patterns from Aether (Journals & Events)
 - 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.
 
 - Sessions / Presentations: The session page demonstrates several best practices:
     - Use `url_*` constants (derived from `data.params`) so the `liveQuery` closure captures a stable value instead of the reactive store directly.
@@ -113,6 +114,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 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.