v0.1.36-alpha

v0.1.36-alpha — the Google Calendar connect flow actually completes

Two defects that only appeared once a real household completed consent for
the first time. Both were reached by fixing the OAuth flow in v0.1.35-alpha;
neither was reachable before it.

• The callback redirected to /settings/calendars/google/select, a path no
  route serves, while the settings page opens the picker from a ?select=
  query parameter. Consent succeeded, tokens were stored, and the household
  landed on a page that did nothing. Outlook had the same bug.

• When Google refused a request during connect, the route did not catch it,
  so a clear 403 became a generic 500 and the picker rendered an empty
  dropdown. Observed with the Calendar API not enabled on a household's
  Cloud project — Google named the problem and gave a one-click fix, and
  nobody ever saw it. The route now maps through describeGoogleSyncError
  and the picker shows the message.

Install

curl -fL https://github.com/Springdale-Robotics/basis/releases/download/v0.1.36-alpha/basis-0.1.36-alpha.tar.gz | tar -xz
sudo bash basis-0.1.36-alpha/backend/deploy/native/install.sh --source basis-0.1.36-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.