@goscribe/server 1.0.10 → 1.1.0

package/DATABASE_SETUP.md

@@ -1,165 +0,0 @@
-# 🗄️ Database Setup Guide
-
-## 📋 Overview
-This guide covers the database configuration for the Scribe server, including Prisma setup, environment variables, and troubleshooting common connection issues.
-
----
-
-## 🔧 Environment Variables Required
-
-### Core Database Configuration
-```bash
-# Pooled connection (for runtime queries)
-DATABASE_URL="postgresql://<db_user>:<db_password>@aws-1-ap-southeast-1.pooler.supabase.com:5432/postgres?sslmode=require"
-
-# Direct connection (for migrations and schema operations)
-DIRECT_URL="postgresql://<db_user>:<db_password>@db.<project-ref>.supabase.co:5432/postgres?sslmode=require"
-```
-
-### 🔍 Where to Find These Values
-1. Go to your Supabase project dashboard
-2. Navigate to **Settings** → **Database**
-3. Copy the connection strings from:
-   - **Connection pooling** → `DATABASE_URL`
-   - **Direct connection** → `DIRECT_URL`
-
----
-
-## 🚀 Quick Setup Steps
-
-### 1. Set Environment Variables
-```bash
-# Option A: Export for current session
-export DATABASE_URL="your_pooled_connection_string"
-export DIRECT_URL="your_direct_connection_string"
-
-# Option B: Add to .env file
-echo "DATABASE_URL=your_pooled_connection_string" >> .env
-echo "DIRECT_URL=your_direct_connection_string" >> .env
-```
-
-### 2. Generate Prisma Client
-```bash
-npm run build
-```
-
-### 3. Run Migrations (if needed)
-```bash
-npx prisma migrate deploy
-```
-
-### 4. Seed Database (optional)
-```bash
-npm run seed
-```
-
----
-
-## 🏗️ Database Schema Overview
-
-### Core Models
-- **User** - Authentication and user management
-- **Workspace** - Project containers with folders
-- **Channel** - Chat channels within workspaces
-- **Chat** - Individual chat messages
-- **Artifact** - AI-generated content (study guides, flashcards, etc.)
-- **FileAsset** - User uploads and attachments
-
-### Key Relationships
-```
-User → Workspaces → Channels → Chats
-User → Artifacts → Versions/Questions/Flashcards
-Workspace → FileAssets
-```
-
----
-
-## 🐛 Troubleshooting
-
-### ❌ "Tenant or user not found" Error
-
-**Cause:** Incorrect database credentials or connection string format
-
-**Solutions:**
-1. **Verify credentials** in Supabase dashboard
-2. **Check connection string format:**
-   ```bash
-   # ✅ Correct format
-   postgresql://user:password@host:port/database?sslmode=require
-   
-   # ❌ Common mistakes
-   postgresql://user:password@host:port/database  # Missing sslmode
-   postgresql://user:password@host:port          # Missing database name
-   ```
-
-3. **Ensure proper URL encoding** for special characters in passwords
-4. **Use direct connection** for migrations (not pooled)
-
-### ❌ Migration Failures
-
-**Cause:** Using pooled connection for schema operations
-
-**Solution:** Always use `DIRECT_URL` for migrations
-```bash
-# ✅ Correct
-DIRECT_URL="postgresql://user:pass@db.project.supabase.co:5432/postgres?sslmode=require"
-
-# ❌ Wrong
-DIRECT_URL="postgresql://user:pass@aws-1-ap-southeast-1.pooler.supabase.com:5432/postgres?sslmode=require"
-```
-
-### ❌ Connection Timeouts
-
-**Solutions:**
-1. Check Supabase project status
-2. Verify network connectivity
-3. Ensure SSL mode is set to `require`
-4. Check if IP is whitelisted (if using IP restrictions)
-
----
-
-## 📊 Database Operations
-
-### Available Scripts
-```bash
-# Development
-npm run dev          # Start development server
-
-# Database
-npm run build        # Generate Prisma client + build
-npm run seed         # Populate with sample data
-npx prisma studio    # Open database browser
-npx prisma migrate dev    # Create and apply migrations
-npx prisma migrate deploy # Apply existing migrations
-```
-
-### Sample Data
-The seed script creates:
-- Demo user (`demo@example.com`)
-- Sample workspace with artifacts
-- Worksheet with mixed question types
-- Flashcard set
-- Study guide with versions
-
----
-
-## 🔐 Security Notes
-
-- **Never commit** `.env` files to version control
-- **Use environment-specific** connection strings
-- **Enable SSL** (`sslmode=require`) for all connections
-- **Rotate credentials** regularly
-- **Use connection pooling** for production workloads
-
----
-
-## 📚 Additional Resources
-
-- [Prisma Documentation](https://www.prisma.io/docs)
-- [Supabase Database Guide](https://supabase.com/docs/guides/database)
-- [PostgreSQL Connection Strings](https://www.postgresql.org/docs/current/libpq-connect.html)
-
----
-
-*Last updated: $(date)*
-

package/MEETINGSUMMARY_FRONTEND_SPEC.md

@@ -1,28 +0,0 @@
-## Meeting Summary Frontend Spec
-
-Note: The `meetingsummary` router is currently commented out. This spec outlines the intended API based on the commented code and typical flows, so the frontend contract is ready when implementation resumes.
-
-### Proposed Endpoints (tRPC)
-- **meetingsummary.listSummaries**: `{ workspaceId: string }` → `Artifact[]` (type: `MEETING_SUMMARY`, latest version included)
-- **meetingsummary.getSummary**: `{ summaryId: string }` → `Artifact & { versions: Version[] }`
-- **meetingsummary.uploadFile**: `{ workspaceId: string; fileName: string; fileBuffer: string /* base64 */; mimeType: string; title?: string }` → `{ id: string; title: string; summary: SummaryData; transcript: string }`
-- **meetingsummary.processSchema**: `{ workspaceId: string; meetingData: MeetingSchema }` → `{ id: string; title: string; summary: SummaryData; originalData: MeetingSchema }`
-- **meetingsummary.updateSummary**: `{ summaryId: string; title?: string; content?: string }` → `Artifact`
-- **meetingsummary.deleteSummary**: `{ summaryId: string }` → `true`
-- **meetingsummary.getVersions**: `{ summaryId: string }` → `Version[]`
-
-### Types (simplified)
-- **Artifact**: `{ id; workspaceId; type: 'MEETING_SUMMARY'; title; content?; createdAt; updatedAt }`
-- **Version**: `{ id; artifactId; version: number; content: string; createdAt }`
-- **MeetingSchema**: `{ title: string; participants: string[]; date: string; duration?: string; agenda?: string[]; transcript?: string; notes?: string }`
-- **SummaryData**: `{ keyPoints: string[]; actionItems: string[]; decisions: string[]; nextSteps: string[]; insights?: string[]; summary: string }`
-
-### Upload Flow (when implemented)
-1. Validate file type (mp3/mp4/wav/m4a).
-2. Upload base64 file; backend transcribes (Whisper) then summarizes (GPT), stores artifact + version.
-3. Return summary JSON and transcript.
-
-### UX Notes
-- Show parsing progress and handle large files.
-- Provide manual schema entry as fallback (processSchema).
-- Keep version history for edits; show latest version by default.