- Frontend admin email now reads from VITE_ADMIN_EMAIL env var instead of hardcoded literal
- Consolidate retention cleanup: remove runRetentionCleanup, add document_processing_events to existing cleanupOldData
- Replace personal email in defineString('EMAIL_WEEKLY_RECIPIENT') default with empty string
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix [object Object] issue in PDF financial table rendering
- Enhance Key Questions and Investment Thesis sections with detailed prompts
- Update year labeling in Overview tab (FY0 -> LTM)
- Improve PDF generation service with page pooling and caching
- Add better error handling for financial data structure
- Increase textarea rows for detailed content sections
- Update API configuration for Cloud Run deployment
- Add comprehensive styling improvements to PDF output
## What was done:
✅ Fixed Firebase Admin initialization to use default credentials for Firebase Functions
✅ Updated frontend to use correct Firebase Functions URL (was using Cloud Run URL)
✅ Added comprehensive debugging to authentication middleware
✅ Added debugging to file upload middleware and CORS handling
✅ Added debug buttons to frontend for troubleshooting authentication
✅ Enhanced error handling and logging throughout the stack
## Current issues:
❌ Document upload still returns 400 Bad Request despite authentication working
❌ GET requests work fine (200 OK) but POST upload requests fail
❌ Frontend authentication is working correctly (valid JWT tokens)
❌ Backend authentication middleware is working (rejects invalid tokens)
❌ CORS is configured correctly and allowing requests
## Root cause analysis:
- Authentication is NOT the issue (tokens are valid, GET requests work)
- The problem appears to be in the file upload handling or multer configuration
- Request reaches the server but fails during upload processing
- Need to identify exactly where in the upload pipeline the failure occurs
## TODO next steps:
1. 🔍 Check Firebase Functions logs after next upload attempt to see debugging output
2. 🔍 Verify if request reaches upload middleware (look for '�� Upload middleware called' logs)
3. 🔍 Check if file validation is triggered (look for '🔍 File filter called' logs)
4. 🔍 Identify specific error in upload pipeline (multer, file processing, etc.)
5. 🔍 Test with smaller file or different file type to isolate issue
6. 🔍 Check if issue is with Firebase Functions file size limits or timeout
7. 🔍 Verify multer configuration and file handling in Firebase Functions environment
## Technical details:
- Frontend: https://cim-summarizer.web.app
- Backend: https://us-central1-cim-summarizer.cloudfunctions.net/api
- Authentication: Firebase Auth with JWT tokens (working correctly)
- File upload: Multer with memory storage for immediate GCS upload
- Debug buttons available in production frontend for troubleshooting
- Replace custom JWT auth with Firebase Auth SDK
- Add Firebase web app configuration
- Implement user registration and login with Firebase
- Update backend to use Firebase Admin SDK for token verification
- Remove custom auth routes and controllers
- Add Firebase Cloud Functions deployment configuration
- Update frontend to use Firebase Auth state management
- Add registration mode toggle to login form
- Configure CORS and deployment for Firebase hosting
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
