Repository navigation
Add Supabase cloud telemetry and shared observer sessions - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Observers can now sign in to Supabase, view authorized driving sessions, follow source-timestamped GPS routes, and receive historical threshold events from three IMUs in real time. Cloud records persist between visits and are shared with explicit read-only observers. Local live simulation and event-only preview remain available without project configuration.
Validation completed:
npm run build— TypeScript and optimized production build; cloud UI/SDK are loaded on demand.npm test— 80 passing tests, including 11 tests executing the actual migration and RLS in PostgreSQL/PGlite, plus domain, repository, uploader, and auth/session lifetime checks.npm run test:e2e— 23 passing Chromium tests: local demonstrations plus mocked Supabase auth/HTTP/Realtime, two authorized observers, persistent reloads, stale backlog, duplicates/out-of-order records, owner/read-only actions, approximately 1 Hz uploads, and 390px mobile layout.npm run format:check,git diff --check, credential-free production-browser smoke test, and an explicit privileged-key build-rejection check.No hosted Supabase project was created, migrated, or verified. SQL tests use test-only auth fixtures; browser tests intercept a nonfunctional Supabase test hostname. The user must apply the migration and configure their own project's public URL/key and Auth settings using
docs/SUPABASE_SETUP.md. Production deployment, phone gateway, firmware, and a durable phone-side offline outbox are outside this change. Very long sessions may benefit from incremental snapshot/retention optimization later.