Feature/pbi 72 playlist export

.github/ISSUE_TEMPLATE/pbi.md

@@ -0,0 +1,37 @@
+---
+name: "Product Backlog Item"
+about: "Create a new Product Backlog Item in INVEST format"
+title: "<Feature Name> [PBI]"
+labels: ["PBI"]
+assignees: []
+---
+
+## User Story
+
+As a <persona>, I want <feature> so that <business value>.
+
+- **Persona**: <who is using this?>  
+- **Feature**: <what capability is being built?>  
+- **Business Value**: <why this matters to the product or user>  
+
+---
+
+## Reference(s)
+
+- Link(s) to design docs, wireframes, or related PBIs if any  
+
+---
+
+## Tasks
+
+- [ ] Task 1  
+- [ ] Task 2  
+- [ ] Task 3  
+
+---
+
+## Acceptance Criteria
+
+- [ ] Clear condition 1 that must be true  
+- [ ] Clear condition 2 that must be true  
+- [ ] Any error handling or edge cases  

.github/workflows/codeql.yml

@@ -0,0 +1,37 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+  schedule:
+    - cron: '0 0 * * 0'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'javascript-typescript' ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{matrix.language}}"

.gitignore

@@ -15,22 +15,39 @@ yarn-error.log*
 
 # env
 .env*
+<<<<<<< HEAD
+=======
 .env.local
 .env.development.local
 .env.test.local
 .env.production.local
+>>>>>>> 2cf79ae775545c31935108f06979a795fe08bdad
 
 # misc
 .DS_Store
 .vercel/
 *.tsbuildinfo
+<<<<<<< HEAD
+# test files
+clean.txt
+bad.txt
+secret.txt
+=======
 Thumbs.db
 Desktop.ini
+>>>>>>> 2cf79ae775545c31935108f06979a795fe08bdad
 
 # test files
 clean.txt
 bad.txt
 secret.txt
+<<<<<<< HEAD
+playwright-report/
+
+.cursorignore
+sprint-1-assignee-breakdown.txt
+get-issues.ps1
+=======
 
 # Python
 venv/
@@ -102,4 +119,13 @@ coverage/
 dist/
 *.tsbuildinfo
 
+# Private planning and documentation folders
+old-pbi/
+pbi-77/
+pbi-72/
+memory-bank/
+.cursorrules
+
+# Issues folder
 issues/
+>>>>>>> 2cf79ae775545c31935108f06979a795fe08bdad

apps/web/.github/workflows/codeql.yml

@@ -0,0 +1,38 @@
+name: "CodeQL"
+
+on:
+  push:
+    branches: [ "main" ]
+  pull_request:
+    branches: [ "main" ]
+  schedule:
+    - cron: '0 0 * * 0'
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      actions: read
+      contents: read
+      security-events: write
+
+    strategy:
+      fail-fast: false
+      matrix:
+        language: [ 'javascript-typescript' ]
+
+    steps:
+    - name: Checkout repository
+      uses: actions/checkout@v4
+
+    - name: Initialize CodeQL
+      uses: github/codeql-action/init@v3
+      with:
+        languages: ${{ matrix.language }}
+
+    - name: Perform CodeQL Analysis
+      uses: github/codeql-action/analyze@v3
+      with:
+        category: "/language:${{matrix.language}}"
+

apps/web/.gitignore

@@ -1,68 +1,105 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-
-# dependencies
-/node_modules
-/.pnp
-.pnp.*
-.yarn/*
-!.yarn/patches
-!.yarn/plugins
-!.yarn/releases
-!.yarn/versions
-
-# testing
-/coverage
-/test-results
-/playwright-report
-/playwright/.cache
-
-# next.js
-/.next/
-/out/
-
-# production
-/build
+# next / build
+.next/
+out/
+build/
 
-# misc
-.DS_Store
-*.pem
-Thumbs.db
-Desktop.ini
+# deps
+node_modules/
 
-# debug
+# logs
+*.log
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
 .pnpm-debug.log*
 
-# env files (can opt-in for committing if needed)
+# env
 .env*
 .env.local
 .env.development.local
 .env.test.local
 .env.production.local
 
-# vercel
-.vercel
-
-# typescript
+# misc
+.DS_Store
+.vercel/
 *.tsbuildinfo
-next-env.d.ts
+Thumbs.db
+Desktop.ini
+
+# test files
+clean.txt
+bad.txt
+secret.txt
+
+# Python
+venv/
+.venv/
+backend/.venv/
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+
+# pytest
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.pytest_cache/
+.coverage
+backend/htmlcov/
+backend/coverage.xml
+
+# Playwright
+playwright-report/
+test-results/
+playwright/.cache/
+
+# docs (if you want to ignore extracted wireframes)
+docs/
+
+# Cursor/IDE
+.cursorignore
+.claude/
+
+# Scripts and temporary files
+get-issues.ps1
+update-*.ps1
+issue_*_update.json
+*.ps1
+
+# Sprint/assignee files (if temporary)
+sprint-*-assignee-breakdown.txt
+*-assignee-breakdown.txt
 
 # IDE
 .idea/
 .vscode/
 *.swp
 *.swo
 *~
+.project
+.classpath
+.settings/
 
 # OS
 .DS_Store
 .DS_Store?
 ._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
 Thumbs.db
 
-# Testing outputs
-/coverage/
+# Testing
+coverage/
 *.lcov
 .nyc_output/
+
+# Build outputs
+dist/
+*.tsbuildinfo
+
+issues/

apps/web/MIGRATION_INSTRUCTIONS.md

@@ -0,0 +1,66 @@
+# Database Migration Instructions
+
+## Communities Table Migration
+
+To fix the "Error fetching communities" error, you need to run the database migration to create the `communities` table.
+
+### Option 1: Run in Supabase Dashboard (Recommended)
+
+1. Go to your Supabase project dashboard
+2. Navigate to **SQL Editor**
+3. Click **New Query**
+4. Copy and paste the contents of `apps/web/supabase/migrations/009_create_communities_table.sql`
+5. Click **Run** (or press Ctrl+Enter)
+6. Verify the table was created by checking the **Table Editor** - you should see a `communities` table
+
+### Option 2: Run via Supabase CLI
+
+If you have Supabase CLI installed:
+
+```bash
+cd apps/web
+supabase db push
+```
+
+Or run the specific migration:
+
+```bash
+supabase migration up --file supabase/migrations/009_create_communities_table.sql
+```
+
+### Option 3: Run Curated Songs Migration (Optional)
+
+If you want to use the song curation feature, also run:
+
+1. Copy contents of `apps/web/supabase/migrations/010_create_curated_songs_table.sql`
+2. Run in Supabase SQL Editor
+
+### Verify Migration
+
+After running the migration, you can verify it worked by:
+
+1. Check the **Table Editor** in Supabase - you should see:
+   - `communities` table
+   - `curated_songs` table (if you ran that migration too)
+
+2. The error should disappear and communities should load (even if empty)
+
+3. You can now access the admin console and create communities
+
+### Troubleshooting
+
+If you still see errors:
+
+1. **Check RLS Policies**: Make sure the Row Level Security policies were created correctly
+2. **Check Permissions**: Verify your Supabase user has the necessary permissions
+3. **Check Console**: Look at the browser console for more detailed error messages
+
+### Next Steps
+
+After running the migration:
+
+1. Access the admin console (click bottom-right corner 10 times quickly on homepage)
+2. Create your first community
+3. Add playlist links
+4. Curate songs if needed
+