3 Commits

Author	SHA1	Message	Date
Scott Idem	7c6f264266	docs: clarify Electron scope, update badge test lessons, all badge tests passing ... - AE__Architecture.md: Add section 7 -- Runtime Environment: Browser vs Electron. Electron is ONLY for Events Pres Mgmt Launcher. Badge printing (and everything else) works via standard browser window.print(), no Electron needed. - MODULE__AE_Events_Badges.md rev 3: Update print section to browser-first approach, remove Electron from print workflow, add two new test lessons (flat API URLs, CSS attribute vs DOM property), mark all tests passing. - TODO__Agents.md: Add completed data integrity test fixes item, add window.print() wiring to upcoming tasks, expand input field audit note.	2026-02-26 18:10:08 -05:00
Scott Idem	908b4dbef9	docs(badges): clarify badge types vary by Event/Template	2026-02-26 16:26:44 -05:00
Scott Idem	ed7542b5dc	docs(badges): comprehensive module documentation ... COMPLETE DOCUMENTATION: - Override fields pattern (*_override) and sync behavior - External system integration (iMIS, Zoom, Novi, Impexium, Confex, Cvent) - Cron sync safety rules (override fields NEVER overwritten) - Access level permissions (Authenticated → Super) - Search/filter capabilities (fulltext, badge type, print status, affiliations) - Quick edit implementation details - Database schema and API functions - Component architecture - Testing status and known issues - Development guidelines KEY CONCEPTS DOCUMENTED: 1. Override fields protect staff/attendee edits from automated syncs 2. Data flow is pull-only (read from external systems, never push back) 3. Display priority: override field → regular field → fallback 4. Access-based editing (currently placeholder, future JSON config) 5. All 7 override fields explained with examples SYNC BEHAVIOR CLARIFIED: - Cron jobs CAN update regular fields - Cron jobs CANNOT touch override fields - Manual staff edits CAN update any field - Attendee self-service limited to specific overrides per event config	2026-02-26 16:17:39 -05:00