feat: leads re-enable flow — detect removed leads on scan + Remove/Restore buttons

- QR scanner (single + multi): detect previously-removed leads via IDB enable flag;
  route to 'reenable' state instead of duplicate error; offer Re-activate button
- API fallback: if create fails and no IDB record, search API for disabled tracking
  record by event_exhibit_id + event_badge_id (adds qry_badge_id param to
  search__exhibit_tracking)
- Lead detail page: Replace raw enable checkbox with Remove Lead (two-click confirm,
  navigates back after) and Restore Lead card (shown when enable is falsy)
- Fix flash of disabled records in leads list: filter !enable in both filtered_lead_li
  derived and local IDB fast-path in handle_search_refresh
- eslint.config.js: disable svelte/no-navigation-without-resolve (no base path configured)
- Also includes _random field annotation cleanup (db_events, ae_types), iframe layout
  fixes, badge view tweaks, test updates, and doc updates from prior session

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

documentation/MODULE__AE_Events_Badges.md

@@ -535,8 +535,8 @@ Button has `data-testid="badge-print-btn"` and shows loading/done/error states w
 **Indexed Fields:**
 ```typescript
 badge: `
-  event_badge_id_random, event_badge_id, id,
-  event_id, event_id_random,
+  event_badge_id, id,
+  event_id,
   full_name, full_name_override, email, email_override,
   affiliations, affiliations_override,
   badge_type, badge_type_code, badge_type_code_override, badge_type_override,

documentation/MODULE__AE_Events_Exhibitor_Leads.md

@@ -132,7 +132,7 @@ One exhibitor's presence at an event.
 
 | Field | Purpose |
 |---|---|
-| `event_exhibit_id` / `event_exhibit_id_random` | Primary / URL-safe ID |
+| `event_exhibit_id` | Primary / URL-safe ID |
 | `name` | Exhibitor display name |
 | `code` | Booth number |
 | `staff_passcode` | Shared sign-in code |
@@ -232,4 +232,4 @@ Guard in [ae_tab__manage.svelte](src/routes/events/[event_id]/(leads)/leads/exhi
 - `license_max` controls how many licensed staff slots an exhibit can have
 - Export endpoint: `GET /v3/action/event_exhibit/{id}/tracking_export` — requires `leads_api_access`
 - Custom questions are stored per-exhibit in `leads_custom_questions_json` (not global)
-- The exhibitor landing page link format: `/events/[event_id]/leads/exhibit/[exhibit_exhibit_id_random]/`
+- The exhibitor landing page link format: `/events/[event_id]/leads/exhibit/[exhibit_exhibit_id]/`

documentation/PROJECT__Use_AE_API_V3_CRUD_upgrade.md

@@ -106,7 +106,7 @@ V3 returns detailed error metadata in the `meta.details` object.
 **Symptom:** Providing a string ID in a search body that the backend maps to an integer can result in **Zero Results** if the underlying view expects a string.
 
 **Final Solution (Body + Header Injection):**
-1.  **Body:** Inject the raw field name (e.g. `account_id_random`) into the `search_query.and` array to bypass automatic backend mapping.
+1.  **Body:** Inject the raw field name (e.g. `account_id`) into the `search_query.and` array to bypass automatic backend mapping.
 2.  **Headers:** Pass `headers: { 'x-account-id': ... }` manually to provide context for Auth validation.
 3.  **Isolation (IDAA):** Due to specific bugs in the IDAA module, it has been temporarily isolated to a legacy V2 search function (`qry_ae_obj_li__event_v2`) using `default_qry_str` for text searching, while the main module continues to use the V3 implementation.