# Frontend Agent Task List > Use this file to track steps for complex features or bug fixes. > **Status:** � Stable — ongoing development. ## 📋 Open: Security - [x] **PUBLIC_AE_API_SECRET_KEY Audit:** Completed 2026-03-11. Key is `PUBLIC_*` by design (always in client bundle). Highest-risk anonymous path now uses limited-permission `PUBLIC_AE_BOOTSTRAP_KEY`. Full server-side migration would require a major API proxy refactor — not justified given JWT + account_id auth layers. `manifest.webmanifest/+server.ts` is a minor cleanup candidate (could use bootstrap key instead), but no security urgency. Current state is acceptable. ## 🚧 Upcoming High Priority ### [Launcher] Active features (identified 2026-03-06) - [x] **Font size cycler (Launcher sidebar):** Font size cycler and light/dark toggle added to new `menu_launcher_controls.svelte` component; wired into `launcher_menu.svelte`. Visibility toggles (All Files / All Sessions) moved to same component and restyled to `preset-tonal-tertiary`. (2026-03-11) - **Minor Svelte warning:** `slct_event_location_id` prop in `menu_location_list.svelte` is not `$bindable()` but `bind:value={slct_event_location_id}` is used. Functionally fine since `onchange` writes directly to `$events_slct.event_location_id`. ### [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`. ### [Badges] Remaining badge work before first live event - **Badge print controls UX polish:** Scott has improvements in mind — TBD next session. File: `ae_comp__badge_print_controls.svelte`. ### [Leads] Exhibitor Lead Scanning — NEXT MAJOR FEATURE QR code scan at exhibitor booth → capture attendee badge data. Gated by `allow_tracking` on the badge. Check if `documentation/MODULE__AE_Events_Leads.md` exists for full spec. Key questions before starting: which routes, does the Electron app scan, what does the lead record look like in the DB? ### [DevOps] Remaining deployment items - [x] **Wire AE_APP_REPLICAS:** `docker-compose.yml` line 147 already has `scale: ${AE_APP_REPLICAS:-1}`. (verified 2026-03-11) - [x] **Archive ae_env_node_app:** Archived as tar.gz under `~/OSIT_dev/backups/`; old history/docs moved to `~/OSIT_dev/for_reference_only/`. (2026-03-11) - [x] **Build Optimization:** Current state finalized. Local Gitea instance stood up at `git.dgrzone.com` (Docker, home server) — future: migrate repos from Bitbucket, verify Backblaze/restic backups cover Gitea data. (2026-03-11) ### [General] - **Temp Cleanup:** Auto-removal of native `.tmp` files older than 24h. - **`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. - **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.) ### [UX] Session Expired & Access Denied (identified 2026-03-10) Two related UX gaps to handle together: **1. Session Expired banner (API 401/403 mid-session):** - `flag_expired` in root `+layout.svelte` is declared but never set — it was always intended for this - Add a small writable store or custom event (e.g., `ae_auth_error` in `ae_stores`) that API helpers (`api_get_object.ts`, `api_post_object.ts`, `api_patch_object.ts`) can fire when they get a 401 or 403 - Root layout watches the store and sets `flag_expired = true` - Render a non-blocking dismissible banner (not full-screen): "Session expired. Please sign in again." with a link to the sign-in control - Especially relevant for Launcher (event staff on tablets may not notice silent failures) **2. Standardize Access Denied UI (non-IDAA routes only — IDAA layout is intentionally custom):** - Currently inconsistent across the app: - Root layout: full-screen `flag_denied` (site access key gate — keep this, it's correct) - `/core` layout: silent redirect to home — should show a brief message instead - `/events/[event_id]/settings`: inline raw text string — should use a consistent banner component - `/events/.../badges/.../review`: inline `