Add the Home Assistant REST calendar client and the idempotent sync that
writes important school events to Sam's Home Assistant calendar (FR-8). The
school stays read-only; the only write is to the calendar (rule 7).
- internal/calendar: HA REST client (states, create_event, get_events,
delete_event) and the sync that selects important future events, adopts an
existing event by its description marker, records the HA event id on the
item, and records every attempt.
- internal/store: migration 003 (items.ha_event_uid, items.ha_pushed_at and
the append-only calendar_pushes table), candidates, mark-synced and the
push log.
- internal/parse: a school event is important; a routine class period is not.
- cmd/school: `school calendar entities|status|push|events`.
- web: an "Add to calendar" item action and a fail-loud calendar banner, so a
failed write is never swallowed (FR-12).
- scripts/calendar-push.sh, Makefile target, env example, docs and tests.
The target is configurable (SCHOOL_HA_CALENDAR_ENTITY). Home Assistant has no
non-Google writable calendar today, so the entity is asked on AUD-110.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Fetch and parse Harry and Finn with a stored Compass session per child and
store every item against the right children.id.
- cmd/school/session.go + internal/store/session.go: read and write the
per-child harness session state in the SQLite `session` table. `show`
prints metadata only; the state is never printed.
- scripts/compass-fetch-patchright.mjs: reuse the stored session, refresh it
after login, resolve the child's userId from the parent page by name, and
keep the shared calendar out of the per-child run (it would leak the
eldest's timetable into the younger child).
- scripts/scan-compass.sh + make scan: scan one child or both; restore the
session, fetch, persist the session, then parse. A failing child is
recorded in `scans` with ok = 0 and the script exits non-zero (FR-12).
- cmd/school/scan.go: `school scan record` writes a fetch failure to the
scans table. cmd/school/items.go: `school items purge` removes rows that a
shared page stored against the wrong child.
- internal/store/store_test.go: prove items and sessions are separated by
child. docs/phase-4-both-children-notes.md; README + image tag 0.3.0-phase4.
Live evidence: Harry 70 tasks / 1 message / 35 events (6 overdue); Finn
42 tasks / 1 message / 0 events (2 overdue). Finn's subjects are Year 7,
Harry's are Year 11. Both sessions stored.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
