docs: document service worker fix, events sort encoding, and slct account_id pattern

BOOTSTRAP__AI_Agent_Quickstart.md:
- Mistake #15 addendum: events/session modules use legacy tmp_sort_1 encoding
  (priority=true→'1'), not build_tmp_sort — requires descending sort until migrated
- Mistake #16 (new): service worker without skipWaiting+clients.claim silently serves
  stale code to long-lived tabs; explains the "can't reproduce in dev" pattern that
  likely caused the IDAA recovery meetings issue for months

CLIENT__IDAA_and_customized_mods.md:
- New "Sort Encoding" section: table of legacy vs build_tmp_sort modules with
  correct comparator direction for each
- New "Search Trigger" section: explains why $slct.account_id not $ae_loc.account_id

TODO__Agents.md:
- IDB Sort: added ae_events__event migration task + legacy encoding warning
- DevOps: marked service worker fix complete; replaced nginx caching item with
  proxy buffer tuning task

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

documentation/CLIENT__IDAA_and_customized_mods.md

@@ -457,6 +457,32 @@ filtered) replaces it after the background refresh completes. The IDB path does
 - Add `contact_li_json_ext` to the IDB fast-path filter in `search__event()` and the recovery
   meetings page so contact matches appear instantly from cache, not only after API refresh.
 
+### Sort Encoding — Events Use Legacy (Not `build_tmp_sort`)
+
+`ae_events__event.ts` builds `tmp_sort_1` with the **legacy encoding**: `priority ? 1 : 0`
+(priority=true → `'1'`). This is the **opposite** of `build_tmp_sort` (priority=true → `'0'`).
+
+| Module | Encoding | Correct comparator |
+| --- | --- | --- |
+| `ae_events__event.ts` (Recovery Meetings) | Legacy: `priority=true→'1'` | **Descending** `b.localeCompare(a)` |
+| `ae_events__event_session.ts` | Legacy: `priority=true→'1'` | **Descending** `b.localeCompare(a)` |
+| `ae_events__event_presentation.ts` | `build_tmp_sort` (overrides legacy in `specific_processor`) | **Ascending** `a.localeCompare(b)` |
+| Journals, Posts, Archives | `build_tmp_sort` | **Ascending** `a.localeCompare(b)` |
+
+**Do not apply the `build_tmp_sort` ascending rule to raw event or session sorts** until
+`ae_events__event.ts` is migrated (tracked in TODO__Agents.md under IDB Sort rollout).
+
+### Search Trigger — Use `$slct.account_id`, Not `$ae_loc.account_id`
+
+The recovery meetings search `$effect` gates on `$slct.account_id` (set only by the bootstrap
+Sync Effect, non-persisted). Do NOT change this back to `$ae_loc.account_id`.
+
+**Why:** `$ae_loc` is a persisted store that hydrates from localStorage on page load. Its
+`account_id` may be stale from a previous session (e.g., a dev/demo account_id left behind).
+Using it as the gate fires the API call with the wrong account before bootstrap has run,
+producing either a 403 or wrong-account data. `$slct.account_id` is null until bootstrap
+sets it — a reliable gate. See mistake #14 in `BOOTSTRAP__AI_Agent_Quickstart.md`.
+
 ### My Meetings (Favorites)
 
 Members can star meetings to build a personal "My Meetings" list. The star toggle appears:
@@ -873,4 +899,4 @@ ae_loc.idaa_loc = { novi_uuid: 'test-uuid-value', ... };
 ---
 
 **Document Status:** ✅ Current
-**Last Verified:** 2026-05-19 — Access Gate: documented new `verify_error_type` error-handling states and retry/reset UI; Search Architecture: corrected contact-search status (now works via `default_qry_str` in API path — two root causes fixed 2026-05-18/19); noted IDB fast-path gap as remaining enhancement
+**Last Verified:** 2026-06-03 — Recovery Meetings: documented legacy `tmp_sort_1` encoding for events (requires descending sort, not ascending); documented `$slct.account_id` gate pattern for search trigger; noted service worker `skipWaiting`/`clients.claim` requirement for long-lived IDAA iframe sessions (root cause of user-reported loading failures that could not be reproduced in dev)