feat(sites): Google sign-in, access modes, uploads, endpoints and typed hooks

Radin committed …

⧉1f2945abee0f

Author

Radin · radin@coline.appOct 15, 2026 at 19:10

Committer

Radin · radin@coline.appOct 15, 2026 at 19:10

Parents

a3d81bfa262f

feat(sites): Google sign-in, access modes, uploads, endpoints and typed hooks

Sites reach parity with what small public apps need, in the SDK's types:

- Visitors sign in with Google (no Coline account) or Coline. Sites can
  require sign-in or admit only visitors the team approves; an onSignIn
  tool runs when a guest signs in.
- Collections take a zod schema, enforced on every visitor write
  (record_invalid) and typed in the page through createSiteClient and
  createSiteHooks<typeof app>().
- @colineapp/sdk/site/react: live and paginated collections, tools,
  uploads, session, sign-in button, client router, error boundary.
- Visitor uploads with public and private files, sniffed and sandboxed,
  included in the plan: 1 GB per workspace on Free, 100 GB per site on Pro.
- App endpoints answer on the site's own paths; the visitor is the actor
  only for same-site calls. They need endpoints.receive, so a claim.
- Site tools can be offered to browser agents through WebMCP.
- Claiming grants the permissions the site declares.
- CLI 2.9.0: storage list/put/get/delete, sites list/delete, db export,
  inspect usage; dev server simulates sign-in (?as=name), access modes,
  uploads and endpoints.
- Site API responses carry a sandbox CSP so uploaded files can't run
  script on the site's origin.

SDK 2.1.1, create-coline-app 2.9.0. Migration 0440. verify-sites: 123/123.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>