feat: add MVP Implementation Plan for Hobbyist tier launch

[Paddy1981]

6-8 week plan focused on minimum viable product for market launch:

• Target: 50-100 paying users in first 90 days
• Pricing: $9/month or $89/year (Hobbyist tier)
• Scope: 85% AUC detection, basic vetting, web UI, Stripe payments

Key MVP features:

• Transit detection with BLS periodogram (reuse existing)
• Vetting suite: odd-even, V-shape, secondary eclipse (reuse existing)
• Web interface with TIC ID input -> results
• User accounts with 25 targets/month limit
• Stripe subscription management

Explicitly out of scope for MVP:

• FPP/NFPP, MCMC, Gaia integration (Phase 2)
• Peer review, ExoFOP, DOI (Phase 3)
• API access, batch processing (Professional tier)

Maps existing LARUN components to MVP requirements.

https://claude.ai/code/session_011NWj4qHMpnJqseDYB5et8R

Summary

Type of Change

• Bug fix (non-breaking change fixing an issue)
• New feature (non-breaking change adding functionality)
• Breaking change (fix or feature causing existing functionality to change)
• Documentation update
• Refactoring (no functional changes)
• CI/CD changes

Related Issues

Changes Made

Testing

• Unit tests added/updated
• Manual testing performed
• All existing tests pass

Skill Updates (if applicable)

• ANAL-xxx:
• STAR-xxx:
• MISSION-xxx:
• DISC-xxx:
• RES-xxx:

Multi-IDE Coordination

• Updated .coordination/TASK_LOG.md
• Checked .coordination/FILE_LOCKS.md for conflicts
• Updated .coordination/HANDOFF_NOTES.md if needed

Checklist

• Code follows project style guidelines
• Self-review completed
• Comments added for complex logic
• Documentation updated (if needed)
• No new warnings introduced