The first live run against the new calendar.school entity failed loudly twice,
and both causes are fixed here.
- The Local Calendar rejects `return_response` on calendar.create_event. The
client retries the call without it and ignores the changed-states array that
Home Assistant returns instead.
- Home Assistant then reports no event id. The item keeps the description
marker ([compass-nhs:<id>]) as its reference, so it leaves the candidate set
and is never written twice. The live retry proved it: both events already in
the calendar were adopted by their markers, with no duplicate.
- calendar.get_events reports `start` / `end` (a date-time or a bare date), not
`start_date_time`; the reader now accepts all three shapes.
A model must no longer classify events. The calendar write depends on the
school-event rule, and the LLM labelled every event "normal"; events now keep
the deterministic rule under both classifiers.
Also fix the Phase 5 screenshot script: the calendar banner shares the `.scan`
class, so select each banner by its labelled section.
Docs record the accepted decision: Sam chose a Home Assistant Local Calendar,
so the target is calendar.school.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- internal/dashboard: classify items into overdue / due today / due this week /
no due date / messages; render the plain-text brief (FR-6, FR-7, FR-9).
- internal/store: ItemsForChild, ItemByID, DeleteItemByID, ScanSummaryForChild
and the stored-brief CRUD helpers (FR-10).
- internal/web: routes /?child=, /items/{id}, POST /items/{id}/delete,
POST /summaries/build, POST /summaries/{id}/delete, plus a per-child scan
banner (FR-12) and a phone-first server-rendered template.
- Calendar events are never "overdue": a past lesson is history, not work.
- cmd/school brief build|list; scripts/screenshot-phase5.mjs for phone evidence.
- Tests: bucket classification, stored-brief round-trip, and HTTP routes
including the NO SCAN / SCAN FAILED / healthy banner behaviour.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
