fix: update docs/todos after v1 edit form retirement + v2 rename

- Update CLIENT__IDAA_and_customized_mods.md: remove v1 entry and v2 suffix
- Update tests/README.md: rename _v2 reference to canonical filename
- Update TODO__Agents.md: mark all state_referenced_locally warnings resolved;
  document remaining 23 CSS @apply warnings as harmless language-service noise

documentation/CLIENT__IDAA_and_customized_mods.md

@@ -81,8 +81,7 @@ src/routes/idaa/
 │   │   ├── ae_idaa_comp__event_obj_li.svelte           # Individual list item card
 │   │   ├── ae_idaa_comp__event_obj_qry.svelte          # Query/filter bar
 │   │   ├── ae_idaa_comp__event_obj_id_view.svelte      # Meeting detail (read-only)
-│   │   ├── ae_idaa_comp__event_obj_id_edit.svelte      # Meeting edit form (v1, legacy — do not touch)
+│   │   ├── ae_idaa_comp__event_obj_id_edit.svelte   # Meeting edit form (active)
-│   │   ├── ae_idaa_comp__event_obj_id_edit_v2.svelte   # Meeting edit form (v2, active)
 │   │   └── [event_id]/
 │   │       ├── +page.svelte    # Meeting detail page — renders view OR edit based on session flag
 │   │       └── +page.ts
@@ -96,7 +95,7 @@ src/routes/idaa/
 > 2. **Direct page** (`[event_id]/+page.svelte`) — navigating to `/idaa/recovery_meetings/<id>` renders
 >    the same view/edit components gated by `$idaa_sess.recovery_meetings.edit__event_obj`.
 >
-> Both patterns use `ae_idaa_comp__event_obj_id_edit_v2.svelte`. The edit form clears **both**
+> Both patterns use `ae_idaa_comp__event_obj_id_edit.svelte`. The edit form clears **both**
 > `show__modal_edit` and `edit__event_obj` on save/cancel so it works correctly from either entry point.
 
 ---

documentation/TODO__Agents.md

@@ -23,7 +23,7 @@ Related: `src/lib/stores/store_versions.ts` is the new home for version constant
 - [x] **Minor Svelte warning:** `slct_event_location_id` in `menu_location_list.svelte` — prop already has `$bindable(null)`; stale comment in file updated. (2026-03-11)
 
 ### [Svelte] State reference warnings
-- **42 `state_referenced_locally` warnings remain** in `recovery_meetings/ae_idaa_comp__event_obj_id_edit.svelte` and `..._v2.svelte`. Same pattern as the 10 fixed on 2026-03-09 — move reactive reads into `onMount`.
+- [x] **`state_referenced_locally` warnings resolved** — all 42 warnings fixed. v1 edit form retired; v2 renamed to canonical name. Remaining 23 warnings in `ae_idaa_comp__event_obj_id_edit.svelte` are CSS `@apply`/`@reference` warnings from the svelte-check CSS language service not understanding Tailwind v4 at-rules — harmless, build works fine, not fixable without a full `<style>` block refactor. (2026-03-11)
 
 ### [Badges] Remaining badge work before first live event
 - **Badge print controls UX polish:** Scott has improvements in mind — TBD next session.

src/routes/idaa/(idaa)/recovery_meetings/[event_id]/+page.svelte

@@ -36,7 +36,7 @@
         idaa_prom
     } from '$lib/stores/ae_idaa_stores';
 
-    import Event_obj_id_edit from '.././ae_idaa_comp__event_obj_id_edit_v2.svelte';
+    import Event_obj_id_edit from '../ae_idaa_comp__event_obj_id_edit.svelte';
     import Event_obj_id_view from '.././ae_idaa_comp__event_obj_id_view.svelte';
     import Help_tech from '$lib/app_components/e_app_help_tech.svelte';
 

tests/README.md

@@ -91,7 +91,7 @@ console.log(bad.map(el => el.name || el.id));
 
 **Cause:** In Svelte 5, `value={someReactiveExpr}` on an uncontrolled `<input>` or `<select>` is a **one-time set at mount**. If the backing reactive store (`$ae_loc`, `liveQuery`, etc.) is empty when the component first renders, the field gets `value=""` and stays that way — even after the store updates.
 
-**Specific instance fixed:** The `[name="timezone"]` field in `ae_idaa_comp__event_obj_id_edit_v2.svelte` has two branches:
+**Specific instance fixed:** The `[name="timezone"]` field in `ae_idaa_comp__event_obj_id_edit.svelte` has two branches:
 ```svelte
 {#if $ae_loc?.lu_time_zone_list?.length}
     <select name="timezone" required value={...}>  ← renders with value ✓