Fix(IDAA): Harden Recovery Meetings search and fix detail page crash

- Search Hardening: Implemented 'Inclusive OR' logic for physical/virtual filters and restored robust full-text search using 'default_qry_str' with wildcards.
- Crash Fix: Added null checks for 'contact_li_json' in meeting detail view to prevent TypeError.
- ID Stability: Enhanced 'core__idb_dexie.ts' to support 'id_random' mapping and fixed misleading save logging.
- Reliability: Both V2 and V3 search paths now consistently return processed objects with standardized IDs.

TODO.md

@@ -28,7 +28,9 @@ This is a list of tasks to be completed before the next event/show/conference.
 - [ ] **Payload Validation**: Create a dry-run tool to check payloads against Pydantic models.
 - [x] **Error Transparency**: Update backend to return specific SQLAlchemy/Pydantic errors in `meta.details`. (Completed 2026-01-19)
 - [ ] **Automated Source of Truth**: Generate `V3_OBJECT_MODELS.md` automatically in `agents_sync/Aether/`.
-- [ ] **V3 Search Audit**: Investigate 'Zero-Result' bug in IDAA Recovery Meetings.
+- [x] **Fix V3 Search for IDAA Recovery Meetings**
+    - *Resolution:* Isolated IDAA module to a specialized legacy function `qry_ae_obj_li__event_v2` for stability.
+    - *V3 General Status:* Refined general `qry_ae_obj_li__event` to use 'Body + Header' injection, resolving the 'Integer Trap' for Main module.
     - [ ] Run raw CURL trace to bypass browser CORS and see full backend traceback.
     - [ ] Perform SQL Audit on `v_event` view types (string vs integer mismatch).
     - [ ] Test reverting to `account_id` mapping vs raw `account_id_random` body injection.