Update PoliticTalk Jitsi room policy

templates/auth-roadmap.md

@@ -5,7 +5,7 @@ These notes are intentionally not deployed yet. They describe the local files an
 ## Target Flow
 
 ```text
-PgPlatform calendar event
+PgPlatform PoliticTalk event
   -> PgPlatform PoliticTalk prejoin page
   -> PgApi verifies logged-in user, event ownership/invite/access, and event time window
   -> PgApi returns a short-lived Jitsi JWT
@@ -13,21 +13,22 @@ PgPlatform calendar event
   -> Jitsi VPS validates JWT through Prosody token auth
 ```
 
-## Local Files To Add Later
+## Local Files
 
 ```text
 jitsi/templates/prosody-token-auth.cfg.lua.example
-jitsi/templates/jicofo-token-auth.conf.example
-jitsi/templates/jitsi-token-auth.env.example
+jitsi/templates/pgapi-politictalk-jwt.env.example
 ```
 
 Only templates should be committed. Real JWT secrets must stay in VPS-only files.
 
 ## Platform Changes To Add Later
 
-- PgApi endpoint to issue Jitsi JWTs for valid PoliticTalk event access.
+- PgApi `join-link` issues Jitsi JWTs when token-auth env values are present.
 - JWT claims for room, user display name, email/id, moderator flag, expiry, and feature permissions.
-- PgPlatform prejoin route that shows event title and immutable platform user name.
+- PgPlatform prejoin route shows event title and immutable platform user name.
 - PgPlatform embedded Jitsi room using the IFrame API.
+- Participants must wait on the PgPlatform prejoin page until the host starts the room.
+- Jitsi auto-owner must be disabled once JWT auth is enabled so moderator status comes only from PgApi JWT claims.
 - Moderator-only controls for audio moderation and poll permissions.
 - Event end-time enforcement through JWT expiry and/or iframe hangup.