Commercialization roadmap: Community + Pro packaging

[Blackmvmba88]

Goal

Turn msfs-match-loop-cache from a useful toolkit into a product that can be sold and supported without breaking the current safe/local workflow.

Product split

Community

• Current shell toolkit and diagnostics
• Manual launchers
• Cache/network reports
• Safe copy/move utilities
• Local-only workflow

Pro

• Guided installer / setup
• Automatic USB detection
• .env / profile configuration
• Session metrics and historical dashboard
• Failure classification
• Automatic report rotation
• Backup / restore
• Multi-game profiles
• Export JSON/CSV
• Low-space alerts
• Polished desktop launcher / GUI

Commercialization blockers

• Choose licensing model before distributing paid builds
• Add explicit copyright / commercial-use terms
• Separate Community and Pro feature boundaries
• Introduce versioning and release notes
• Create signed distributable package for macOS
• Add installer/uninstaller
• Add configuration migration/versioning
• Add telemetry policy (default local-only unless explicitly enabled)
• Add support / troubleshooting bundle export
• Add product naming and pricing-ready feature matrix

Engineering order

1. Observability foundation (session JSON/CSV + metrics)
2. Config layer and automatic USB detection
3. Packaging / installer
4. Multi-profile architecture
5. GUI
6. Signed releases + sales delivery workflow

Product principle

The paid value should come from automation, UX, observability, supportability and packaging — not from pretending the project can cache Xbox/MSFS server-side game assets.

Safety invariant

No destructive operation may become implicit. Copy-first and explicit move/delete semantics remain mandatory in every paid edition.