docs: update badge module docs — verify completed items, close stale TODOs

- MODULE__AE_Events_Badge_Templates.md: mark style_href, duplex, and
  badge_back suppression as done; correct v1→v2 component references
- PROJECT__AE_Events_Badges_Review_Print.md: update project status
- TODO__Agents.md: close debug-outlines, style_href, duplex TODOs;
  mark window.print() wiring as done

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

documentation/TODO__Agents.md

@@ -42,16 +42,19 @@ Axonius (mid-April). See `documentation/PROJECT__AE_Events_Zebra_Hardware_Test_D
 for the full checklist and prep plan.
 
 **Pre-test work (do before printer arrives):**
-- [ ] **Remove debug outlines** from `print/+page.svelte` print CSS (lime/blue/red/orange/purple/cyan)
+- [x] **Debug outlines are gated** — `print/+page.svelte` prints nothing; outlines live in
+  `static/ae-print-badge.css` behind `html.debug_outlines` class (toggled by the "Show debug
+  outlines" checkbox in the controls panel, trusted-only). Won't appear in print unless explicitly
+  enabled. No action needed. (verified 2026-03-18)
 - [ ] **Zebra ZC10L Linux driver** — install CUPS driver package ahead of time; verify card prints
   before burning rental time on driver setup. Check Zebra's site for Linux/CUPS driver.
-- [ ] **Wire `style_href`** via `<svelte:head>` in `print/+page.svelte` — needed so client-specific
-  CSS loads from the template's `style_href` field. Currently tracked as pending in MODULE doc.
-- [ ] **Confirm `duplex=0` hides badge back in print** — `duplex` field not yet on backend;
-  verify badge_back is suppressed for single-sided PVC. May need a manual print CSS rule until
-  the backend field lands and `properties_to_save` is updated.
+- [x] **`style_href` wired** — `print/+page.svelte` already loads `style_href` via `<svelte:head>`
+  and it's in `properties_to_save`. (verified 2026-03-18)
+- [x] **`duplex=0` hides badge back** — `duplex` is in `properties_to_save`; v2 badge render
+  gates `{#if show_badge_back}` on `duplex != null && !!duplex`. Set `duplex=0` on the template
+  to suppress the back section for single-sided PVC. (verified 2026-03-18)
 - [ ] **Set up test event + PVC template** in dev DB with `layout: badge_3.5x5.5_pvc`,
-  a few badge records with varied name lengths, HTML in fields, different badge_type_codes.
+  `duplex=0`, a few badge records with varied name lengths, HTML in fields, different badge_type_codes.
 - [ ] **Test data set:** include edge cases — very long name, HTML markup in name/affiliations,
   badge with no affiliations, badge with all ticket/option codes set.
 
@@ -98,7 +101,7 @@ Full audit: `src/routes/events/[event_id]/(leads)/` and `src/lib/ae_events/ae_ev
 
 ### [General]
 - [x] **Temp Cleanup:** `cleanup_tmp_files` wired in `launcher_background_sync.svelte`; called at launcher startup. Confirmed working. (2026-03-11)
-- **`window.print()` for badge print button:** Wire the existing `handle_print_badge()` to trigger `window.print()`. Browser print works well across Chrome/Chromium/Firefox — no Electron needed.
+- [x] **`window.print()` for badge print button:** Wired in `ae_comp__badge_print_controls.svelte` — increments count, fires `window.print()`, redirects to badge search. (done)
 - **Input Field Audit:** Several input fields are missing `name`/`id` attributes or `data-testid`. Known examples: badge override fields in `ae_comp__badge_obj_view.svelte`; template name input in `ae_comp__badge_template_form.svelte`. Matters for: accessibility, autofill, label associations, and test targeting. (For tests, use `getByLabel()` rather than `input[value*=...]` which only checks the HTML attribute, not the Svelte-bound DOM property.)
 
 ## ✅ Completed (2026-03)