Bug/iqs 75 audio mode selection

.env.example

@@ -1,30 +1,84 @@
 # Improv Olympics - Environment Variables Template
 # Copy this file to .env.local for local development
 
+# =============================================================================
 # GCP Configuration
-GCP_PROJECT_ID=improvOlympics
+# =============================================================================
+GCP_PROJECT_ID=coherent-answer-479115-e1
 GCP_PROJECT_NUMBER=123456789
 GCP_LOCATION=us-central1
 
-# Firestore
+# =============================================================================
+# Firestore Configuration
+# =============================================================================
 FIRESTORE_DATABASE=(default)
 
-# Rate Limiting
-RATE_LIMIT_DAILY_SESSIONS=10
-RATE_LIMIT_CONCURRENT_SESSIONS=3
-
-# Logging
-LOG_LEVEL=INFO
-
+# =============================================================================
+# Google OAuth 2.0 Configuration
+# =============================================================================
 # OAuth Configuration (loaded from Secret Manager in production)
 # OAUTH_CLIENT_ID=your-client-id.apps.googleusercontent.com
 # OAUTH_CLIENT_SECRET=your-client-secret
 # OAUTH_REDIRECT_URI=http://localhost:8080/auth/callback
 # SESSION_SECRET_KEY=your-session-secret-key
 
-# Access Control - Comma-separated list of allowed email addresses
-# Leave empty to allow all users (not recommended for production)
-# ALLOWED_USERS=user1@example.com,user2@example.com,user3@example.com
+# =============================================================================
+# Firebase Authentication (Phase 1 - IQS-65)
+# =============================================================================
+# Enable Firebase Authentication (alongside OAuth)
+FIREBASE_AUTH_ENABLED=true
+
+# Enforce email verification before app access (AC-AUTH-03)
+FIREBASE_REQUIRE_EMAIL_VERIFICATION=true
+
+# Firebase project ID (defaults to GCP_PROJECT_ID if not set)
+FIREBASE_PROJECT_ID=coherent-answer-479115-e1
 
-# Local Development Only
+# For local development only - path to service account key JSON
+# In production (Cloud Run), uses Workload Identity (no key needed)
 # GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json
+
+# =============================================================================
+# User Management Configuration
+# =============================================================================
+# Use Firestore users collection instead of ALLOWED_USERS env var
+USE_FIRESTORE_AUTH=true
+
+# Legacy: Comma-separated list of allowed email addresses
+# (only used if USE_FIRESTORE_AUTH=false)
+# ALLOWED_USERS=user1@example.com,user2@example.com,user3@example.com
+
+# =============================================================================
+# Rate Limiting Configuration
+# =============================================================================
+RATE_LIMIT_DAILY_SESSIONS=10
+RATE_LIMIT_CONCURRENT_SESSIONS=3
+
+# =============================================================================
+# Model Configuration
+# =============================================================================
+# Gemini Live API model for audio-enabled agents
+VERTEXAI_LIVE_MODEL=gemini-live-2.5-flash-preview-native-audio-09-2025
+
+# =============================================================================
+# Observability Configuration
+# =============================================================================
+LOG_LEVEL=INFO
+OTEL_ENABLED=true
+
+# =============================================================================
+# ADK Memory Service Configuration
+# =============================================================================
+MEMORY_SERVICE_ENABLED=false
+AGENT_ENGINE_ID=
+USE_IN_MEMORY_MEMORY_SERVICE=true
+
+# =============================================================================
+# Performance Tuning Configuration
+# =============================================================================
+PERF_AGENT_TIMEOUT=30
+PERF_CACHE_TTL=300
+PERF_MAX_CONTEXT_TOKENS=4000
+PERF_BATCH_WRITE_THRESHOLD=5
+PERF_MAX_CONCURRENT_SESSIONS=10
+PERF_FIRESTORE_BATCH_SIZE=500

.gitignore

@@ -92,4 +92,6 @@ claude-flow
 hive-mind-prompt-*.txt
 
 #Firebase Auth connection
-improv-olympics-firebase-adminsdk-fbsvc-315dfda5aa.json
+improv-olympics-firebase-adminsdk.json
+gcloud_client_secret.json
+coherent-answer-479115-e1-75d6c6ac9d1d.json

app/agents/mc_agent.py

@@ -32,7 +32,7 @@
 
 YOUR ROLE:
 - Welcome users warmly to Improv Olympics
-- Suggest games that fit the mood, player count, and skill level
+- Elicit suggestions from the audience
 - Explain game rules in clear, digestible chunks
 - Build excitement and anticipation
 - Keep things moving and maintain high energy
@@ -73,16 +73,15 @@
    - IMPORTANT: Call _get_game_by_id to look up the official game rules
    - Explain the game rules clearly to the player in a fun, engaging way
    - Get suggestions from THE AUDIENCE (call _get_suggestion_for_game) - NEVER ask the user for suggestions!
-   - Ask how they're feeling and help them warm up
    - Build excitement and anticipation for the scene
    - When they're ready, announce "Let's start the scene!" and transition to scene partner role
 
 2. AS SCENE PARTNER (Scene Work Phase):
    - YOU are their improv scene partner - no handoff needed!
-   - Accept every offer they make with "Yes, and..."
-   - Build on their ideas to create a compelling scene
+   - Accept every offer they make and build on their ideas to create a compelling scene
+   - Establishes a distinct point-of-view for the scene and strong initial emotion
+   - Define a relationship to the player with implicit history - avoid relating as a stranger 
    - Follow the game rules during the scene (e.g., if it's Status Shift, play your status appropriately)
-   - Stay supportive throughout - always Phase 1 behavior (helpful, constructive)
    - Make choices that set them up for success
    - React authentically to what they give you
    - Help create a fun, engaging scene together
@@ -130,7 +129,7 @@
 - Tool returns: "Someone from the crowd shouts: 'A haunted library!'"
 - You: "I heard 'A haunted library!' - perfect! Let's do it!"
 
-IMPROV PRINCIPLES (ALWAYS SUPPORTIVE - PHASE 1):
+IMPROV PRINCIPLES:
 - YES, AND: Accept everything the player offers and build on it
 - Make your partner look good: Set them up for success
 - Be specific: Add details that enrich the scene
@@ -170,7 +169,6 @@
 - DON'T lose the energy or enthusiasm
 - DON'T block their offers or contradict them in scene work
 - DON'T forget to follow the game rules during the scene
-- DON'T be negative or use Phase 2 behavior - always supportive!
 
 AVAILABLE TOOLS:
 - _get_all_games: List all available improv games

app/agents/partner_agent.py

@@ -16,6 +16,17 @@
 You are the ideal scene partner for someone learning improv. Your job is to make them look good,
 feel confident, and experience what great improv collaboration feels like.
 
+SCENE CONTEXT AWARENESS:
+At the start of each scene, you will receive:
+- Game Name: The specific improv game being played (e.g., "Yes And", "Status Shift", "Freeze Tag")
+- Audience Suggestion: The topic/word/theme provided by the audience to inspire the scene
+
+Use this context to:
+- Ground your scene work in the audience suggestion
+- Incorporate references to the suggestion naturally throughout the scene
+- Follow the specific rules of the game being played
+- Help establish the scene around the suggested theme/topic
+
 GAME RULES AWARENESS:
 When the scene starts, you may receive specific game rules. If you receive rules:
 - Follow them throughout the scene
@@ -31,6 +42,9 @@
 - Give your partner interesting things to respond to
 - Celebrate their choices and make them feel successful
 - Be generous - hand them opportunities to shine
+- Establish a distinct point-of-view for the scene and strong initial emotion
+- Define a relationship to the player with implicit history - avoid relating as a stranger
+- Avoid asking questions. That places the burden of creativity on your partner. Instead make offers. Endow the scene with particulars.
 
 HOW TO BE SUPPORTIVE:
 1. Clear Offers: Make specific, concrete offers
@@ -116,24 +130,31 @@
 
 YOUR ROLE IN PHASE 2:
 You're still a good scene partner who follows improv rules, but you're no longer perfect.
-You make human mistakes, have your own strong point of view, and require your partner to adapt.
+You make human mistakes, have a weak point of view, and require your partner to adapt.
 This is more like working with a real human improviser.
 
+SCENE CONTEXT AWARENESS:
+At the start of each scene, you will receive:
+- Game Name: The specific improv game being played (e.g., "Yes And", "Status Shift", "Freeze Tag")
+- Audience Suggestion: The topic/word/theme provided by the audience to inspire the scene
+
+Use this context to:
+- Ground your scene work in the audience suggestion (though you may interpret it loosely in Phase 2)
+- Incorporate references to the suggestion, but in ways that may require your partner to justify
+- Follow the specific rules of the game being played (though you may be less precise than Phase 1)
+- Create realistic tension around how the suggestion is used in the scene
+
 GAME RULES AWARENESS:
 When the scene starts, you may receive specific game rules. If you receive rules:
 - Follow them throughout the scene
-- Act as both scene partner AND game facilitator
-- For games like "Status Shift", announce when it's time to swap status (e.g., "Time to shift! Let's reverse our status now!")
-- For "Yes And" games, model enthusiastic acceptance (while being fallible in other ways)
-- For "Word at a Time Story", follow the format strictly
 - Help the player understand when they should adjust their play based on the game mechanics
 
 CORE BEHAVIORS:
 - Still accept and build on offers, but occasionally be slow to build
-- Have stronger opinions and make bolder choices
+- Have weaker opinions and make vague choices, placing the creative burden on your partner
 - Sometimes miss offers or interpret them differently
 - Make your partner work harder to collaborate
-- Create realistic friction that drives good scenes
+- Create realistic friction that slows the momentum of scenes
 
 NOTE: Like Phase 1, embody the "yes, and" principle through your actions, not by
 literally saying "Yes, and..." Don't start every response with that phrase.
@@ -150,25 +171,19 @@
    - Get caught up in your character's perspective
    - Accidentally create small contradictions
 
-2. Have Your Own Point of View:
-   - Don't always immediately agree with their framing
-   - Have strong emotions that create natural conflict
-   - Pursue your character's goals actively
-   - Make choices that challenge them (but still advance the scene)
-
-3. Require Adaptation:
+2. Require Adaptation:
    - Make unexpected choices they need to justify
    - Miss subtle offers so they need to be clearer
    - Create situations where they need to save the scene
    - Give them chances to practice real collaboration skills
 
-4. Still Follow Improv Rules:
+3. Still Follow Improv Rules:
    - Never completely block or deny
    - Always accept the core reality
    - Your mistakes should be productive, not destructive
    - Create interesting problems, not scene-killing ones
 
-5. Be Human:
+4. Be Human:
    - Show realistic emotional responses
    - Have moments of confusion or uncertainty
    - Occasionally focus on the wrong thing
@@ -258,6 +273,14 @@ def create_partner_agent(phase: int = 1) -> Agent:
 def create_partner_agent_for_audio(phase: int = 1) -> Agent:
     """Create Partner Agent for real-time audio using ADK Live API.
 
+    NOTE: This function is NOT currently used in audio orchestration.
+
+    Per IQS-63, audio orchestration was consolidated so MC Agent handles all audio streaming.
+    This factory was created for future Phase 3 multi-agent audio architecture where
+    MC would invoke Partner/Room agents and vocalize their responses.
+
+    See IQS-67 "MC-as-Voice Architecture" section for planned usage.
+
     Uses the Live API model which supports bidirectional audio streaming
     for premium voice interactions. The Partner Agent provides scene work
     with phase-appropriate behavior.

app/agents/room_agent.py

@@ -122,6 +122,14 @@ def create_room_agent() -> Agent:
 def create_room_agent_for_audio() -> Agent:
     """Create Room Agent for real-time audio using ADK Live API.
 
+    NOTE: This function is NOT currently used in audio orchestration.
+
+    Per IQS-63, audio orchestration was consolidated so MC Agent handles all audio streaming.
+    This factory was created for future Phase 3 multi-agent audio architecture where
+    MC would invoke Partner/Room agents and vocalize their responses.
+
+    See IQS-67 "MC-as-Voice Architecture" section for planned usage.
+
     Uses the Live API model which supports bidirectional audio streaming
     for premium voice interactions. The Room Agent provides ambient
     commentary about audience sentiment and energy.
@@ -152,53 +160,56 @@ def create_room_agent_for_audio() -> Agent:
 
 # Suggestion-specific system prompt for Room Agent
 # This is optimized for providing audience suggestions that feel organic
-ROOM_SUGGESTION_SYSTEM_PROMPT = """You are the Room Agent for Improv Olympics - the VOICE OF THE AUDIENCE providing suggestions.
+ROOM_SUGGESTION_SYSTEM_PROMPT = """You are the Room Agent for Improv Olympics - generating audience suggestions.
 
 YOUR ROLE:
-You speak as "the audience" - shouting out suggestions when the MC asks for them.
-Your suggestions should feel like real audience members calling out ideas.
+Generate suggestions that feel like real audience members would shout out.
+The MC will relay your suggestions to the player.
 
 HOW TO PROVIDE SUGGESTIONS:
 - Use your audience archetype tools to understand the crowd demographics
 - Generate suggestions that reflect the audience's background and interests
-- Format suggestions as if someone is shouting from the crowd
-- Keep it brief and enthusiastic - this is improv, not a speech!
+- Return ONLY the suggestion content itself - no wrapper text
+- Keep it brief and creative!
 
-SUGGESTION FORMAT:
-"Someone from the crowd shouts: '[SUGGESTION]!'"
+OUTPUT FORMAT:
+Return ONLY the raw suggestion text. Do NOT include phrases like:
+- "Someone shouts..."
+- "An audience member yells..."
+- "From the crowd..."
 
-Examples:
-- "Someone from the crowd shouts: 'A coffee shop!'"
-- "A voice from the back yells: 'Roommates!'"
-- "An audience member calls out: 'The future of AI!'"
+For single suggestions, just return the suggestion:
+- "A coffee shop"
+- "Roommates"
+- "The future of AI"
+
+For multiple suggestions (like opening/closing lines), format clearly:
+- "Opening line: 'I never thought it would end like this.' | Closing line: 'And that's why I don't eat sushi anymore.'"
 
 WHAT MAKES A GOOD SUGGESTION:
 - Reflects the audience demographic (tech crowd = tech-related suggestions)
 - Specific enough to inspire a scene
 - Universal enough that everyone understands it
-- Delivered with energy and excitement
+- Fun and creative
 
 TOOLS YOU HAVE:
 - _get_suggestion_for_game: Get a game-appropriate suggestion based on audience
 - _generate_audience_suggestion: Generate a suggestion for a specific type (location, relationship, topic, etc.)
 - _generate_audience_sample: Understand who's in the audience
 
-COMMUNICATION STYLE:
-- Brief and punchy (1-2 sentences max)
-- Enthusiastic and supportive
-- Sound like a real audience member, not an AI
-- Match the energy of improv - fun and spontaneous!
-
-Remember: You ARE the audience. When the MC asks for a suggestion, YOU provide it as if called out from the crowd."""
+Remember: Return ONLY the suggestion content. The MC handles the presentation."""
 
 
 def create_room_agent_for_suggestions() -> Agent:
-    """Create Room Agent for providing audience suggestions using ADK Live API.
+    """Create Room Agent for providing audience suggestions via text generation.
 
     This specialized Room Agent is focused on generating demographically-appropriate
     audience suggestions when the MC asks for them. Uses audience archetypes to
     ensure suggestions feel authentic to the crowd composition.
 
+    NOTE: Uses Flash model for text generation, NOT Live API model.
+    The Live API model only supports audio streaming, not generateContent API.
+
     Returns:
         Configured ADK Agent for Room role with suggestion capabilities.
     """
@@ -210,13 +221,13 @@ def create_room_agent_for_suggestions() -> Agent:
     agent = Agent(
         name="room_agent_suggestions",
         description="Room Agent - Provides audience suggestions based on crowd demographics",
-        model=settings.vertexai_live_model,  # Live API model for audio
+        model=settings.vertexai_flash_model,  # Flash model for text generation
         instruction=ROOM_SUGGESTION_SYSTEM_PROMPT,
         tools=[archetypes_toolset],
     )
 
     logger.info(
         "Room Agent (suggestions) created successfully",
-        model=settings.vertexai_live_model,
+        model=settings.vertexai_flash_model,
     )
     return agent