we haev percentage table in persona table what it is                                         
                                                                                               
⏺ Bash(source .env && curl -s "https://mayaapp-maya.aws-ap-south-1.turso.io/v2/pipeline" \     
        -H "Authorization: Bearer $TURSO_AUTH_TOKEN" \…)                   
  ⎿    persona_id                     TEXT            default=NULL                             
       name                           TEXT            default=NULL                             
       header                         TEXT            default=NULL                             
     … +13 lines (ctrl+o to expand)                                                            
                                                                     
⏺ No percentage column in the personas table. You might be thinking of the percentage column in
   persona_plans — that's the A/B plan assignment weight.                  
                                                                                               
⏺ Bash(source .env && curl -s "https://mayaapp-maya.aws-ap-south-1.turso.io/v2/pipeline" \     
        -H "Authorization: Bearer $TURSO_AUTH_TOKEN" \…)                   
  ⎿    global_tier5              content=all          price=   499 percentage=100              
       image_monthly             content=image_gen    price=  5000 percentage=100              
       image_weekly              content=image_gen    price=  2000 percentage=100
     … +2 lines (ctrl+o to expand)                                                             
                                                                     
⏺ The percentage in persona_plans controls which plan a device sees via A/B assignment         
  (_assign_plan):                                                          
                                                                                               
  - SHA256(device_id) % 100 gives a hash 0-99                                                  
  - Walk through plans, accumulate percentages
  - First plan where hash < cumulative_percentage → that's the plan shown                      
                                                                                               
  Right now all plans have percentage=100, so the first plan in the list always wins. For      
  image_gen, image_weekly (₹20) is returned for every device — image_monthly (₹50) is never    
  shown.                                                                                       
                                                                     
  If you wanted 50/50 split: set image_weekly to 50 and image_monthly to 50. Half the devices  
  see weekly, half see monthly.
                                                                                               
❯ if i keep 9999 in free count ...again it needs to check the session_images and               
sessionns_videos and etc .. all extra queires ryt?                                             
                                                                                               
⏺ Yes. Look at main.py:124:                                                                    
                                                                                               
  if free_count == 999999:                                                                     
      bot_session.free_remaining = 999999  # unlimited — skips DB query                        
  else:                                                                                        
      used_free = await usage_repo.count_persona_generations(device_id, persona_id,            
  content_type, free_window)                                                                   
      bot_session.free_remaining = max(0, free_count - used_free)                              
                                                                                               
  999999 is the magic number — it skips the count_persona_generations DB query entirely.       
                                                                                               
  But 9999 would NOT skip it — it would run the query to count how many the user has generated,
   then do 9999 - used_count. Extra DB hit every session start.                              
                                                                                               
  So use 999999 exactly, not 9999.                                                             
   
───────────────────────────────────────────────────────────────────────────────────────────────
❯