- Create Economist SubmissionTracking package correctly: * mainArticle = full blog post content * coverLetter = 216-word SIR— letter * Links to blog post via blogPostId - Archive 'Letter to The Economist' from blog posts (it's the cover letter) - Fix date display on article cards (use published_at) - Target publication already displaying via blue badge Database changes: - Make blogPostId optional in SubmissionTracking model - Economist package ID: 68fa85ae49d4900e7f2ecd83 - Le Monde package ID: 68fa2abd2e6acd5691932150 Next: Enhanced modal with tabs, validation, export 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.9 KiB
2.9 KiB
New Session Startup Prompt - Stripe Customer Portal Continuation
Use this to start a FRESH session (not a continuation from compact)
📋 Prompt for New Claude Code Session
I'm working on the Tractatus AI Safety Framework project. This is a NEW session to continue work on the Stripe Customer Portal integration.
CRITICAL CONTEXT:
- Previous session completed Customer Portal code implementation
- Waiting for Stripe Support to resolve bank account verification issue
- Account holder name must be "John Geoffrey Stroh" for Oct 25 payout
- Portal configuration (test + live) needs manual dashboard setup
IMMEDIATE TASKS:
1. Check if Stripe Support has responded about bank account issue
2. If resolved: Configure Customer Portal in Stripe dashboard (test + live mode)
3. Test portal access locally
4. Deploy to production
5. Verify with real customer email
KEY FILES:
- Implementation: src/controllers/koha.controller.js, src/routes/koha.routes.js
- Frontend: public/koha.html, public/js/koha-donation.js
- Documentation: docs/STRIPE_CUSTOMER_PORTAL_NEXT_STEPS.md
- Verification: scripts/verify-stripe-portal.js
REFERENCE DOCUMENTS:
- Session handoff: SESSION_HANDOFF_2025-10-18_STRIPE_CUSTOMER_PORTAL.md
- Configuration guide: docs/STRIPE_PORTAL_CONFIGURATION_STEPS.md
- Troubleshooting: docs/FIND_STRIPE_BANK_HOLDER_NAME.md
Please start by:
1. Reading the session handoff document
2. Checking current Stripe account status
3. Verifying if bank account issue is resolved
4. Providing next steps based on current status
🎯 Expected Session Flow
If Bank Account Resolved:
- Read SESSION_HANDOFF document
- Verify bank account holder name is correct
- Guide user through Customer Portal configuration
- Test locally with verification script
- Deploy to production
- Monitor first portal usage
If Bank Account Still Pending:
- Read SESSION_HANDOFF document
- Check Stripe Support status
- Provide interim actions (portal config in test mode)
- Prepare deployment checklist for when resolved
🔧 Quick Verification Commands
# Verify portal configuration status
node scripts/verify-stripe-portal.js
# Check production server
ssh -i ~/.ssh/tractatus_deploy ubuntu@vps-93a693da.vps.ovh.net "systemctl status tractatus"
# Test portal endpoint locally
curl -X POST http://localhost:9000/api/koha/portal \
-H "Content-Type: application/json" \
-d '{"email":"test@example.com"}'
📖 Essential Reading
Primary: SESSION_HANDOFF_2025-10-18_STRIPE_CUSTOMER_PORTAL.md Setup: docs/STRIPE_PORTAL_CONFIGURATION_STEPS.md Troubleshooting: docs/STRIPE_CUSTOMER_PORTAL_NEXT_STEPS.md
⏰ Critical Deadline
October 25, 2025: First payout becomes available
Requirement: Bank account holder name must be "John Geoffrey Stroh"
Status: Awaiting Stripe Support verification
Last Session: 2025-10-18
Next Action: Check Stripe Support response
Priority: HIGH (payout deadline approaching)