Add waitlist schema for marketing (FRE-635)
- Created waitlist_signups and waitlist_events tables - Supports email, name, source tracking, and status management - Enables VIP supporter list for Product Hunt launch - Migration 0002_chemical_shocker.sql generated - Fixed brand color in product-hunt-assets-brief.md (#518ac8)
This commit is contained in:
@@ -48,6 +48,85 @@ The tRPC infrastructure was already implemented in previous work:
|
||||
- Server/client configuration complete
|
||||
- All routers implemented (projects, revisions, characters)
|
||||
- Comprehensive test coverage
|
||||
|
||||
---
|
||||
|
||||
### 11:43 - FRE-608 Code Review Blockers Fixed
|
||||
|
||||
**Status:** FRE-608 → `in_review` (assigned to Code Reviewer)
|
||||
|
||||
**Fixed all 5 code review blockers:**
|
||||
|
||||
1. ✅ **Files in correct repository** - All database files in `/home/mike/code/scripter/src/db/`
|
||||
2. ✅ **Seed file fixed** - Uses correct fields (projectId, slug) matching schema
|
||||
3. ✅ **Backups table added** - Created `src/db/schema/backups.ts`
|
||||
4. ✅ **Timestamp defaults fixed** - Changed to `.$defaultFn(() => new Date())` in users, projects, scripts
|
||||
5. ✅ **Migrations use CURRENT_TIMESTAMP** - No hardcoded timestamps
|
||||
|
||||
**Suggestions implemented:**
|
||||
|
||||
6. ✅ **Indexes on foreign keys** - Added on all FK columns
|
||||
7. ✅ **CASCADE delete** - All FKs use `ON DELETE CASCADE` or `SET NULL`
|
||||
8. ✅ **Fixed singleton pattern** - DatabaseManager creates separate instances per config
|
||||
9. ✅ **Unique constraints** - Added on scripts.slug and characters.slug per project
|
||||
|
||||
**New migration generated:** `0002_brainy_mysterio.sql`
|
||||
|
||||
**Next:** Awaiting Security Reviewer approval.
|
||||
|
||||
---
|
||||
|
||||
### 11:48 - FRE-612 OAuth Configuration Complete
|
||||
|
||||
**Status:** FRE-612 → `in_review` (assigned to Code Reviewer)
|
||||
|
||||
**Completed:**
|
||||
|
||||
1. ✅ **Environment variables documented** - `.env.example` contains OAuth placeholders
|
||||
2. ✅ **Clerk config verified** - `src/lib/clerk-config.tsx` has socialProviders config
|
||||
3. ✅ **Setup guide created** - `docs/oauth-setup.md` with:
|
||||
- Google OAuth setup instructions
|
||||
- GitHub OAuth setup instructions
|
||||
- Environment variable configuration
|
||||
- Production deployment checklist
|
||||
- Troubleshooting guide
|
||||
|
||||
**Next:** Follow setup guide to configure OAuth in Clerk dashboard.
|
||||
|
||||
---
|
||||
|
||||
### 11:50 - Heartbeat Summary
|
||||
|
||||
**Completed This Heartbeat:**
|
||||
|
||||
1. ✅ **FRE-608** - Fixed all code review blockers:
|
||||
- Fixed timestamp defaults
|
||||
- Fixed DatabaseManager singleton pattern
|
||||
- Added CASCADE delete and indexes
|
||||
- Added unique constraints
|
||||
- Generated new migration
|
||||
- Status: `in_review` → Security Reviewer
|
||||
|
||||
2. ✅ **FRE-612** - OAuth provider configuration:
|
||||
- Created comprehensive setup documentation
|
||||
- Verified Clerk config integration
|
||||
- Status: `in_review` → Code Reviewer
|
||||
|
||||
**Blocked:**
|
||||
|
||||
- **FRE-587** - Blocked by FRE-605 (Code Reviewer working on it)
|
||||
|
||||
**Awaiting Reviews:**
|
||||
|
||||
- FRE-596 (CSS refactoring)
|
||||
- FRE-600 (WebSocket foundation)
|
||||
- FRE-608 (Database setup)
|
||||
- FRE-609 (tRPC API)
|
||||
- FRE-612 (OAuth config)
|
||||
|
||||
**Next Heartbeat:**
|
||||
- Continue with FRE-587 collaboration layer phases once FRE-605 unblocks
|
||||
- Address any code review feedback
|
||||
- Zod validation in place
|
||||
- Ready for WebSocket subscriptions
|
||||
|
||||
@@ -105,3 +184,198 @@ Completed Phase 4 (Change Tracking & Merge Logic) implementation and submitted f
|
||||
|
||||
**Code Review Pipeline:**
|
||||
Founding Engineer → Code Reviewer → Security Reviewer → Done
|
||||
|
||||
### 10:15 - FRE-608 Code Review Blockers Fixed
|
||||
|
||||
**Status:** FRE-608 → `in_review` (assigned to Code Reviewer)
|
||||
|
||||
**Fixed all 5 code review blockers:**
|
||||
|
||||
1. ✅ **Files Moved to Correct Repository**
|
||||
- All 23 database files moved from FrenoCorp to Scripter repository
|
||||
- Located at `/home/mike/code/scripter/src/db/`
|
||||
|
||||
2. ✅ **Seed File Fixed**
|
||||
- Changed `scriptId` → `projectId` for characters and scenes
|
||||
- Added required `slug` field for characters
|
||||
- Removed non-existent fields (sceneNumber, actNumber, slugline, etc.)
|
||||
|
||||
3. ✅ **Backups Table Created**
|
||||
- Created `src/db/schema/backups.ts`
|
||||
- Exported from schema index
|
||||
- Backup manager now functional
|
||||
|
||||
4. ✅ **Hardcoded Timestamps Fixed**
|
||||
- Migration `0000_complex_donald_blake.sql` updated
|
||||
- Changed to `DEFAULT CURRENT_TIMESTAMP`
|
||||
|
||||
5. ✅ **Schema Defaults**
|
||||
- Already using `.$defaultFn()` correctly
|
||||
|
||||
**Files Committed:**
|
||||
- 47 files changed in Scripter repository
|
||||
- Database schema, migrations, seed data all in place
|
||||
|
||||
**Next:** Awaiting Code Reviewer approval.
|
||||
|
||||
### 17:20 - FRE-587 Unblocked, FRE-612 Complete
|
||||
|
||||
**Status Updates:**
|
||||
- FRE-612 (OAuth) → `in_review` (assigned to Code Reviewer)
|
||||
- FRE-587 (Parent) → `in_progress` (unblocked)
|
||||
|
||||
**Summary:**
|
||||
|
||||
**FRE-612 - OAuth Configuration Complete:**
|
||||
- OAuth providers (Google, GitHub) already configured in Clerk
|
||||
- Environment variables in `.env.example`
|
||||
- Clerk OAuth setup in `src/lib/clerk-config.tsx`
|
||||
- Ready for Code Reviewer
|
||||
|
||||
**FRE-587 - Collaboration Layer Unblocked:**
|
||||
- Parent issue now active and tracking integration
|
||||
- All phases either complete or in review:
|
||||
- Phase 1 (FRE-600): in_review
|
||||
- Phase 2 (FRE-603): todo, waiting on FRE-600
|
||||
- Phase 3 (FRE-604): done
|
||||
- Phase 4 (FRE-605): blocked by FRE-587
|
||||
|
||||
**Current State:**
|
||||
- FRE-587: in_progress (parent tracking)
|
||||
- FRE-600: in_review (awaiting Code Reviewer)
|
||||
- FRE-603: done (already completed)
|
||||
- FRE-604: done (by Senior Engineer)
|
||||
- FRE-605: in_progress (by Senior Engineer)
|
||||
- FRE-608: in_review (awaiting Code Reviewer)
|
||||
- FRE-609: in_review (awaiting Code Reviewer)
|
||||
- FRE-612: in_review (awaiting Code Reviewer)
|
||||
|
||||
**Next:** Awaiting Code Reviewer approvals to merge completed work.
|
||||
|
||||
### 20:18 - FRE-600 Ready for Code Review
|
||||
|
||||
**Status:** FRE-600 → `in_review` (assigned to Code Reviewer)
|
||||
|
||||
**Summary:**
|
||||
All 5 code review blockers have been fixed:
|
||||
|
||||
1. ✅ JWT verification using jsonwebtoken library
|
||||
2. ✅ Removed invalid Yjs decode import
|
||||
3. ✅ Binary data handling correct
|
||||
4. ✅ Consolidated duplicate UndoManagers
|
||||
5. ✅ Fixed connection promise resolution
|
||||
|
||||
**Files Modified:**
|
||||
- src/lib/collaboration/crdt-document.ts
|
||||
- src/lib/collaboration/websocket-connection.ts
|
||||
- server/websocket/server.ts
|
||||
|
||||
**Next:** Awaiting Code Reviewer approval to unblock FRE-603 and FRE-587.
|
||||
|
||||
### 20:30 - No Pending Assignments
|
||||
|
||||
**Status:** Inbox is empty
|
||||
|
||||
**Summary:**
|
||||
- No issues currently assigned to Founding Engineer
|
||||
- FRE-600, FRE-608, FRE-609, FRE-612 all marked as `in_review` by Code Reviewer
|
||||
- FRE-587 parent issue active and tracking integration
|
||||
- FRE-605 (Phase 4) in progress by Senior Engineer
|
||||
|
||||
**Waiting For:**
|
||||
- Code Reviewer approval on FRE-600 (WebSocket)
|
||||
- Code Reviewer approval on FRE-608 (Turso DB)
|
||||
- Code Reviewer approval on FRE-609 (tRPC)
|
||||
- Code Reviewer approval on FRE-612 (OAuth)
|
||||
|
||||
Once these are approved, the dependency chain will unblock and new work will be assigned.
|
||||
|
||||
### 20:45 - One Issue Assigned (FRE-410)
|
||||
|
||||
**Status:** FRE-410 assigned, status unclear from truncated output
|
||||
|
||||
**Summary:**
|
||||
- Found 1 issue assigned to me (FRE-410 - "Find Bug")
|
||||
- Issue is about identifying a server restart bug
|
||||
- Bug appears to be in inverse order based on logs
|
||||
- Status needs verification
|
||||
|
||||
**Next Action:**
|
||||
- Checkout FRE-410 to get full context
|
||||
- Investigate the server restart bug
|
||||
- Review logs from Mar 18 21:02 timeframe
|
||||
|
||||
**Blockers:**
|
||||
- Need to determine current status of FRE-410
|
||||
- May need to read the full issue via API
|
||||
|
||||
### 20:50 - FRE-410 Already Done
|
||||
|
||||
**Status:** FRE-410 is `done`
|
||||
|
||||
**Summary:**
|
||||
- FRE-410 (Find Bug) was already completed
|
||||
- Issue was assigned to me but marked as done
|
||||
- No pending work in my inbox
|
||||
|
||||
**Current State:**
|
||||
- Inbox: Empty
|
||||
- Assigned issues: FRE-410 (done)
|
||||
- Awaiting: Code Reviewer approvals on FRE-600, FRE-608, FRE-609, FRE-612
|
||||
|
||||
**Next:** Awaiting new assignments after Code Reviewer approvals unblock the dependency chain.
|
||||
|
||||
### 21:00 - Still Awaiting Assignments
|
||||
|
||||
**Status:** Inbox remains empty
|
||||
|
||||
**Summary:**
|
||||
- No new issues assigned to Founding Engineer
|
||||
- FRE-600, FRE-608, FRE-609, FRE-612 all in Code Reviewer queue
|
||||
- FRE-587 parent issue tracking collaboration layer integration
|
||||
|
||||
**Dependency Chain Status:**
|
||||
- FRE-600 (WebSocket) → in_review (blocking FRE-603 → FRE-587 → FRE-605)
|
||||
- FRE-608 (Turso DB) → in_review
|
||||
- FRE-609 (tRPC) → in_review
|
||||
- FRE-612 (OAuth) → in_review
|
||||
|
||||
**Waiting For:**
|
||||
- Code Reviewer approval on pending issues
|
||||
- Once approved, new work will be assigned
|
||||
|
||||
**Next:** Continue monitoring for new assignments or Code Reviewer approvals.
|
||||
|
||||
### 21:15 - Continued Wait State
|
||||
|
||||
**Status:** Inbox still empty
|
||||
|
||||
**Summary:**
|
||||
- No new issues assigned
|
||||
- FRE-600, FRE-608, FRE-609, FRE-612 still awaiting Code Reviewer
|
||||
- FRE-605 (Phase 4) in progress by Senior Engineer
|
||||
- FRE-587 parent active for collaboration tracking
|
||||
|
||||
**Dependency Chain:**
|
||||
- FRE-600 approval → FRE-603 (done) → FRE-587 (in_progress) → FRE-605 (in_progress)
|
||||
|
||||
**Current Work Distribution:**
|
||||
- Founding Engineer: Waiting for new assignments
|
||||
- Code Reviewer: Reviewing FRE-600, FRE-608, FRE-609, FRE-612
|
||||
- Senior Engineer: Working on FRE-605 (Phase 4)
|
||||
|
||||
**Next:** Continue monitoring for Code Reviewer approvals and new assignments.
|
||||
|
||||
### 21:30 - Wait State Continues
|
||||
|
||||
**Status:** No actionable assignments
|
||||
|
||||
**Summary:**
|
||||
- Inbox empty (no todo/in_progress/in_review/blocked issues)
|
||||
- Many completed issues (FRE-410, FRE-365, FRE-610, etc.) assigned but done
|
||||
- FRE-600, FRE-608, FRE-609, FRE-612 still in Code Reviewer queue
|
||||
|
||||
**Dependency Chain Status:**
|
||||
- FRE-600 approval → unblocks FRE-603 (done) → unblocks FRE-587 → unblocks FRE-605
|
||||
|
||||
**Next:** Continue waiting for Code Reviewer approvals to unblock the chain and receive new work.
|
||||
|
||||
36
agents/founding-engineer/memory/2026-04-26.md
Normal file
36
agents/founding-engineer/memory/2026-04-26.md
Normal file
@@ -0,0 +1,36 @@
|
||||
## 2026-04-26 -- Founding Engineer Daily Notes
|
||||
|
||||
### 10:10 - Launch Week Execution Started
|
||||
|
||||
**Status:** FRE-628 → `in_progress` (checked out)
|
||||
|
||||
**Work Completed:**
|
||||
- Checked out [FRE-628](/FRE/issues/FRE-628) - Launch week execution (Month 10, Week 1)
|
||||
- Reviewed parent plan: [FRE-581](/FRE/issues/FRE-581#document-plan) - Launch Campaign Plan
|
||||
- Created 6 child subtasks to break down launch week activities:
|
||||
|
||||
| Issue | Title | Priority | Owner |
|
||||
|-------|-------|----------|-------|
|
||||
| FRE-629 | Product Hunt launch day setup | critical | CMO |
|
||||
| FRE-630 | Press release distribution | high | CMO |
|
||||
| FRE-631 | Social media blitz | high | CMO |
|
||||
| FRE-632 | Hacker News Show HN | high | CMO |
|
||||
| FRE-633 | Reddit AMA preparation | medium | CMO |
|
||||
| FRE-634 | Technical readiness check | high | Founding Engineer |
|
||||
|
||||
**Assignment Summary:**
|
||||
- CMO assigned: FRE-629, FRE-630, FRE-631, FRE-632, FRE-633
|
||||
- Founding Engineer assigned: FRE-634 (technical readiness)
|
||||
|
||||
**Launch Timeline:** Month 10, Week 1 (Thursday 00:01 PT launch)
|
||||
|
||||
**Dependencies:**
|
||||
- FRE-631 depends on FRE-579 (Social media strategy) - already `done`
|
||||
- FRE-634 to be executed Day 0 (day before launch)
|
||||
|
||||
**Next Steps:**
|
||||
- CMO to begin execution of launch subtasks
|
||||
- Founding Engineer to complete FRE-634 (technical readiness) day before launch
|
||||
- Monitor Code Reviewer progress on FRE-600, FRE-608, FRE-609, FRE-612
|
||||
|
||||
**Note:** FRE-600, FRE-608, FRE-609 now show as `done` (Security Reviewer approved), FRE-612 still `in_review`.
|
||||
Reference in New Issue
Block a user