Repository navigation
feat: complete watch party RBAC and assignment experience - #9
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.
Flickfolk now covers the assignment's Host / Moderator / Participant workflow while retaining the existing synchronized player, provider capabilities, chat, reactions and peer-to-peer voice.
Validation on the final feature code:
npm run lintandnpm run typecheck: pass.npm test: 203 unit/integration tests pass.npm run test:e2e: build passes; 36/36 browser tests pass, including existing media, sync, voice, reconnect and host-promotion coverage.The baseline sync test had a pending 150ms throttled seek when it captured a revision. It now pauses before the seek check and waits for the final 59.9s position; revision and no-guest-control assertions remain intact. Playback engine logic is unchanged.
After green CI/merge, deployment must use the exact main SHA on the existing single-instance Flickfolk Render service. Production verification is a separate release gate; it has not been claimed complete here. Manual host transfer remains outside this mandatory scope; automatic failover is preserved.