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>
- 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>
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>
The Learning Tasks grid is capped at 20 rows and, on the parent page, mixes
both children, so it cannot answer "what is overdue". The parent home page
reported 6 overdue tasks for Harry while the stored grid held 1.
Fetch the per-child task list (read-only) from
POST /Services/LearningTasks.svc/GetAllLearningTasksByUserId, parse it into
task rows, and refuse to store it when the overdue count disagrees with the
home page summary (FR-12).
- fetcher: store learning-tasks-all.json + meta (userId, status, task count)
- parse: new learning-tasks-all page, JSON parser, home-page reconciliation
- store: drop superseded grid-derived task rows before the upsert
- docs: docs/phase-4a-overdue-tasks.md; close the Phase 3 known gap
Verified with live runs: Harry 70 tasks / 6 overdue, Finn 42 tasks / 2 overdue,
both equal to the home page; a tampered home page stops the parse.
Note: the fetcher and store.go files also carry the per-child session work
that was already uncommitted in this shared workspace (AUD-108).
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Turn the raw pages stored by Phase 2 into rows in the SQLite items table
(AGENTS.md §11 Phase 3, FR-3/FR-4/FR-5/FR-12).
- internal/parse: dependency-free HTML reader plus extractors for the ExtJS
learning-task grid (subject, title, category, kind, due date, status), the
home news feed (author, posted time, title, body) and the calendar week grid
(day column + grid offset give the time; label gives title/room/teacher).
- internal/parse: fail loudly. A challenge page, login page, changed layout or
unknown due-date format is an explicit error, never an empty day.
- FR-4: structure is parsed deterministically; importance is classified by an
OmniRoute model (default openrouter/google/gemini-3.5-flash-lite) with a
deterministic fallback. The classifier used is printed and recorded.
- internal/llm: small OpenAI-compatible OmniRoute client (handles SSE replies).
- internal/store: migration 002 adds source_page, importance and external_ref
with a unique (child_id, source, type, external_ref) index; UpsertItems,
CountItemsByType, SampleItems and ChildByName.
- cmd/school parse: reads var/raw/<child>/<run>, upserts items, records the scan
row (ok=0 plus the error on failure) and prints counts and samples.
- scripts/parse-compass.sh and make parse run it in a one-off container against
the service's own volume without restarting the service.
- docs/phase-3-parse-notes.md records the approach, the FR-4 decision and the
known gaps.
Evidence on the live database: 56 rows for Harry (20 task, 1 message, 35 event).
Re-running the same raw pages inserts 0 and updates 56.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- add scripts/compass-fetch-patchright.mjs: headless patchright logs in with the
parent account (no 2FA) and stores the per-child pages with a sha256 manifest
- add scripts/package.json + lockfile for the patchright dependency
- docs: the harness clears the Cloudflare GET but not the login POST; patchright
passes it; record the real per-child URLs and the overdue counts
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- retry the login on a fresh browser context (stale cf_chl_rc_ni cookies loop
the next challenge) and fail loudly with cloudflare_login_post_challenge
- detect the Compass login-rejection message and second-factor prompts
- docs: record that Cloudflare's managed challenge blocks the headless login
POST (GET passes), what was tried, and the unblock options
Co-Authored-By: Paperclip <noreply@paperclip.ing>
- scripts/compass-fetch.mjs drives pi-browser-harness (daemon socket) to log
in once and store raw Compass pages with a sha256/byte-count manifest
- clear the Cloudflare managed challenge via a desktop-UA override plus an
isolated browser context (the default HeadlessChrome UA loops the challenge)
- docs/phase-2-harness-notes.md records the harness entrypoint, the Compass
login form, and the stored-page evidence
- gitignore local runtime state (var/, sqlite files)
Co-Authored-By: Paperclip <noreply@paperclip.ing>
