[GH-122] Fix landing, camera lifecycle, settings and dependencies - #131
Merged
Merged
Conversation
This was referenced Sep 16, 2026
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.
Summary
Fix broken invitation parsing and ineffective browser settings, release camera/session resources when navigation interrupts startup, and make countdown cancellation prevent capture. Improve landing accessibility and iOS identity settings; update dependency manifests and lockfiles (including Vitest 5.0.1) with zero npm audit findings. Version 2.4.4.
Tracking
Closes #122. Linear is unavailable; the user explicitly approved GitHub-only tracking.
Test plan
Screenshots
Full validation record
Risk / rollback
Browser-hosted sessions now advertise the actual host-only capture policy; nonfunctional viewer-trigger permission choices were removed. iOS permissions are unchanged. Revert this PR to roll back. No production database migration or App Store release.