- 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>
Update project dependencies, documentation, and supporting files:
- i18n improvements for multilingual support
- Admin dashboard enhancements
- Documentation updates for Koha/Stripe and deployment
- Server middleware and model updates
- Package dependency updates
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Removed 16 sensitive files from git tracking to protect internal processes:
Root directory (5 files):
- CLAUDE_Tractatus_Maintenance_Guide.md
- DEPLOYMENT-2025-10-08.md
- NEXT_SESSION.md
- NEXT_SESSION_OPENING_PROMPT.md
- SESSION_CLOSEDOWN_20251006.md
docs/ directory (11 files):
- KOHA_PRODUCTION_DEPLOYMENT.md
- PHASE-2-DEPLOYMENT-GUIDE.md
- PRODUCTION_DEPLOYMENT_CHECKLIST.md
- SESSION-2025-10-07-AI-FEATURES.md
- SESSION-HANDOFF-2025-10-12.md
- SESSION_HANDOFF_2025-10-10.md
- SESSION_HANDOFF_2025-10-11.md
- SESSION_HANDOFF_2025_10_11.md
- SESSION_HANDOFF_2025_10_11_P3_P4.md
- SESSION_INIT_API_MEMORY_AUDIT.md
- planning/PHASE_3_SESSION_1_SUMMARY.md
These files contain:
- Internal workflow documentation
- Deployment procedures and server details
- Session handoff information
- Planning and strategy documents
Security posture:
✅ Files removed from tracking (won't appear in new commits)
✅ Files remain on disk for local use
✅ .gitignore already blocks these patterns
✅ .rsyncignore blocks deployment to production
⚠️ Files remain in git history (accessible via git log)
Note: This is low-risk remediation. Files remain in history but won't
be visible in file browser or future commits. For complete removal,
git history rewrite would be needed (high risk, requires force push).
Risk assessment: Medium exposure (internal processes visible) but no
credentials, keys, or direct access information exposed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add detailed deployment procedure to prevent security incidents and
ensure consistent, safe deployments to production.
Includes:
- Pre-deployment verification (tests, security, sensitive file checks)
- Three deployment methods (frontend, Koha, full project)
- Post-deployment verification (health checks, log monitoring)
- Database migration procedure
- Emergency rollback procedure
- Incident documentation template
- Deployment log template
- Emergency procedures (service failures, DB issues)
- Best practices and timing guidelines
Created after security incident where sensitive Claude Code files were
accidentally deployed. This checklist prevents similar incidents through:
- Mandatory .rsyncignore verification
- Sensitive file checks before deployment
- Dry-run review before execution
- Post-deployment monitoring
Status: Active procedure for all production deployments
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
