API: /attendance/house

House attendance routes
**5 Routes**

---

**POST** /attendance/house
_accessible to evals director_

Creates a new attendance submission, containing a date and the list of members and whether they attended

---

**GET** /attendance/house/{user}
_accessible to specific user_

Gets every house meeting, and whether the user attended, missed, or was excused.
- Discuss: Use user token to determine user instead of URL param?

---

**GET** /attendance/house
_accessible to evals director_

Gets all house meeting attendances

---

**PUT** /attendance/house/{id}
_accessible to evals director_

Updates a house meeting's attendance

---

**DELETE** /attendance/house/{id}
_accessible to evals director_

Deletes a house meeting's attendance

Start by locating the attendance API entry points and the existing authentication and persistence patterns for the five /attendance/house routes. Confirm how access for evals directors and users is represented, resolve whether the user token replaces the URL parameter, and verify that creating, listing, updating, and deleting attendance records meet the behaviors described.

Escrito por el modelo de indexación a partir del texto del issue.