{% load i18n lucide %} {% comment %} One referee sign-up row on M3's Calendar -- a home game the signed-in account (or a managed person -- a referee-eligible child is exactly as real as a referee-eligible parent, mobile/views.py's CalendarView) is eligible (and, once responded, confirmed) to referee for. Merged into the same chronological list as the account's own RSVP rows (mobile/ _calendar_row.html), but in the referee accent (assets/mobile.css's --color-referee/.pill-referee) so it reads as a different kind of commitment at a glance. Expects ``row`` ({event, referee_signup, referee_member}) in scope -- referee_member is only set once there's more than one managed person to tell apart, same rule mobile/_calendar_row.html's own ``member`` uses. Accept/Decline are two small forms, not a single multi-button one -- and, unlike this app's RSVP forms, boosted (no hx-boost="false"): nothing here is Alpine-owned/toggled, so there's no htmx/Alpine conflict to dodge, and a boosted POST avoids the jarring full-page reload a plain form submit would cause on a page the user is mid-scroll on. {% endcomment %}