v0.1.38-alpha

v0.1.38-alpha — echo suppression on the calendar pull

Phase 2, task 2. This is the release that makes v0.1.37-alpha's trigger
guard live: every Google Calendar pull now writes calendar_events.remote_updated,
so a pull that only learns 'Google's timestamp moved' no longer bumps the
event's revision, the calendar's sync_token or ctag, or appends a journal row.

revision is what CalDAV ETags are built from, so this is the first change in
phase 2 where a mistake would be visible to devices — either as every event
re-downloading, or as a real change being missed.

It establishes the invariant three later tasks depend on:

updated_at > remote_updated <=> this row has local edits Google has not seen

Pull inserts pin updated_at to the provider's timestamp; pull updates leave it
alone. Both master events and recurrence exceptions.

Nothing a household can see changes yet. Calendars remain read-only and
nothing is pushed to Google.

Known and disclosed: CalDAV LAST-MODIFIED can now trail the ETag on a genuine
content change. DTSTAMP is unaffected. Clients sync on ctag/sync-token/ETag,
so the effect is a possibly-stale 'last edited' in a UI.

Install

curl -fL https://github.com/Springdale-Robotics/basis/releases/download/v0.1.38-alpha/basis-0.1.38-alpha.tar.gz | tar -xz
sudo bash basis-0.1.38-alpha/backend/deploy/native/install.sh --source basis-0.1.38-alpha

Basis installs natively (Node/Postgres/Redis + systemd); there
is no Docker image. Local development still uses Docker for
Postgres/Redis/Ollama via backend/docker-compose.dev.yml.