What problem does it solve? Modifying attendance tracking or year-end decision features in this school management system risks breaking critical business rules, such as the full-state payload semantics where omitted records are deleted, or the three locks protecting decision entry. ## Core Features & Use Cases - Attendance Matrix: Documents the attendances table schema, the editable teacher matrix UI with autosave per session, and the critical rule that POST payloads describe the complete state so missing students are deleted. - Year-End Decisions: Covers the student_year_outcomes table, the three input locks (main teacher only, open year, outcomes_open toggle), and the continuous cursus rule rejecting passage/redoublement decisions. - Admin Read-Only Views: Specifies the admin suivi and outcomes overview endpoints plus validated UI design rules, such as displaying notes inline rather than behind hover popovers. - Use Case: When asked to add a new attendance status or change how decisions are saved, consult this Skill to preserve the full-state semantics, server-side name sorting, and N+1-free eager loading. ## Quick Start Use the emargement-decisions skill to review my changes to the teacher attendance endpoint before I modify the save logic.
