1 Commits (b74e8c279c341ab527f8274011d34b54a0215c39)

Author	SHA1	Message	Date
zijiren	198cd5a9cb	feat: separate room visibility from guest settings (#419) ... ## Summary - store room public visibility as a first-class database field independent of password and guest settings - expose visibility through client, management, HTTP, gRPC, CLI, discovery, and room creation review flows - add `synctv room visibility ROOM_ID --public|--private` for changing existing rooms with an explicit actor - deny anonymous guest access to private rooms while preserving authenticated member access - revoke existing guest sessions immediately when a room becomes private without disconnecting authenticated members ## Validation - `cargo fmt --all -- --check` - `cargo clippy -p synctv-core -p synctv-api-common -p synctv-api-http -p synctv-api-grpc -p synctv --all-targets -- -D warnings` - `cargo clippy -p synctv-management -p synctv --all-targets -- -D warnings` - `cargo check -p synctv-core -p synctv-api-common -p synctv-api-http -p synctv-api-grpc -p synctv` - `cargo check -p synctv-management -p synctv` - `cargo test -p synctv room_visibility` - verified `synctv room visibility --help` renders the required actor and exactly one of `--public` or `--private` - targeted realtime bridge, guest principal, realtime event, and room service tests - real macOS client verification: changing a public room to private terminated the guest connection in about two seconds with `REALTIME_TERMINATION_CODE_GUEST_ACCESS_REVOKED`; authenticated users remained connected	1 month ago