feat: Remove legacy files and fix first svelte/no-at-html-tags error\n\n- Moved legacy files from src/routes/legacy to backups/legacy/src/routes/legacy.\n- Removed the empty src/routes/legacy directory.\n- Fixed a svelte/no-at-html-tags error in src/routes/idaa/(idaa)/archives/[archive_id]/+page.svelte by replacing '{@html ?.name ?? 'Archive'}' with '{?.name ?? 'Archive'}'.\n- Addressed a misidentified '{@html}' tag in src/lib/ae_core/ae_comp__hosted_files_clip_video.svelte by removing commented-out code that might have caused false positives.

TODO.md

@@ -19,6 +19,7 @@ This is a list of tasks to be completed before the next event/show/conference.
 
 ## Big Picture Goals
 
+- Everything needs to work with Svelte 5.x and SvelteKit 2.x.
 - Able to cache data and mostly work offline.
 - The new Events Launcher must be able to work offline and query the API for changes to data.
 - The new Events Launcher must be able to run inside an Electron app and have access to local files and OS shell commands and applications. This includes loading a special library that only works in Electron.
@@ -87,6 +88,7 @@ These functions are frequently used and critical to the application's data flow.
     - **Why:** These functions transform API data for the frontend and are a common source of bugs and inconsistencies.
     - **Cleanup:** Standardize their structure across all modules, ensure they are pure functions, and add unit tests for correctness.
     - **Update 2025-11-13 (Temporary Rollback):** The previous refactoring of these functions has been temporarily rolled back due to an `InternalError`. `ae_core_functions.ts` has been restored. The new plan is to refactor these functions module by module, ensuring stability at each step. The generic CRUD functions in `core__crud_generic.ts` were simplified to remove data processing and caching, delegating those responsibilities to the module-specific functions. The deprecated `process_ae_obj__props` function in that file was left in place but is no longer used by the generic CRUD functions.
+    - **Update 2025-11-20 (Successful Refactor):** The `event_badge` module has been successfully refactored to use the new "API Function -> Processor -> DB Save" pattern. The `process_ae_obj__event_badge_props` function now handles inconsistencies in the API search results (i.e., a missing `event_id`) by accepting the `event_id` as a parameter and injecting it. This serves as a successful proof-of-concept for this architectural pattern.
 
 4. **Usage of `liveQuery` from Dexie**
     - **Why:** `liveQuery` is powerful for reactive UIs, but current usage suggests complexity and potential issues.