Next.js Developer Needed to Test & Deploy Lottery Analyzer V4/V5

I am looking for an experienced Next.js / React developer to take an existing Lottery Statistical Analysis application, review and debug the supplied code, organize it properly in GitHub, and deploy a stable working version through Vercel. Important: This is not a project that needs to be built from scratch. The primary application code has already been written. The current package contains Version 4 and Version 5 of the Lottery Analyzer. I need a developer who can take the supplied code, make sure everything is properly integrated and functioning, correct reasonable bugs or deployment issues, organize the project professionally, and deploy it successfully. The application currently supports both Powerball and Mega Millions and is designed as a statistical-analysis and number-generation tool using historical lottery drawing data. Current V4 functionality includes * Powerball support * Mega Millions support * Historical CSV upload and parsing * CSV validation * White-ball frequency analysis * Hot-number analysis * Cold-number analysis * Overdue / gap analysis * Special-ball analysis * Odd/even distribution analysis * High/low number analysis * Historical number-sum analysis * Historical pair analysis * Weighted number selection * Statistical ticket scoring * Ranked candidate combinations * Custom ticket quantity generation * Responsive web interface V5 expands the application with * More advanced historical-data analysis * All-time frequency analysis * Recent-frequency analysis * Gap and overdue-ratio analysis * Trend analysis * Pair co-occurrence analysis * Triple co-occurrence analysis * Number-position analysis * Mega Ball / Powerball-specific statistical ranking * Weighted candidate generation * Configurable statistical weights * Odd/even pattern filters * Low/high pattern filters * Number-sum filters * Consecutive-number filters * Same-ending-number filters * Previous-draw repeat filters * Monte Carlo candidate generation * Adjustable simulation count * Adjustable candidate pool size * Ticket overlap controls * Portfolio diversification * Statistical ticket ranking * Multiple generated ticket portfolios * Saved combinations * Browser local storage * CSV export for generated combinations * CSV export for saved combinations * Historical date-range filtering * Historical draw-pattern analysis * Walk-forward historical backtesting * Comparison of the statistical model against randomly generated tickets * Responsive desktop/mobile interface The developer should carefully review the supplied code rather than assuming that every part is already production-ready. Primary responsibilities 1. Review all supplied V4 and V5 code. 2. Set up the project correctly as a Next.js application. 3. Test the code for compile errors, runtime errors, React errors, and logical issues. 4. Fix reasonable bugs necessary for the supplied features to function correctly. 5. Make sure the V4/V5 functionality is integrated correctly. 6. Confirm Powerball functionality works. 7. Confirm Mega Millions functionality works. 8. Confirm historical data can be imported correctly. 9. Confirm statistical calculations execute correctly. 10. Confirm candidate ticket generation works. 11. Confirm Monte Carlo generation works. 12. Confirm saved-ticket functionality works. 13. Confirm CSV export works. 14. Confirm historical filtering works. 15. Confirm the backtesting system works. 16. Test the interface on desktop and mobile screen sizes. 17. Clean up obvious unused or unnecessary code where appropriate without removing required functionality. 18. Organize the project files professionally. 19. Create or configure the GitHub repository. 20. Upload the completed project to my GitHub account/repository. 21. Connect the GitHub repository to my Vercel account. 22. Configure the Vercel deployment correctly. 23. Resolve deployment-related errors. 24. Successfully deploy the application. 25. Provide me with the final working public Vercel URL. 26. Make sure future updates can be deployed through the GitHub → Vercel workflow. GitHub and Vercel requirements I want the final application stored in my GitHub repository and deployed through my Vercel account. The repository should be organized so that future versions can be added without having to rebuild the project structure from scratch. The developer should ensure that changes pushed to the production branch can be deployed correctly through Vercel. Testing expectations Please do not simply upload the code and assume it works. I want the developer to actually test the application. At minimum, please verify: * The application loads without errors. * Powerball can be selected and analyzed. * Mega Millions can be selected and analyzed. * Valid historical datasets can be loaded. * Invalid data is handled appropriately. * Number-frequency calculations work. * Gap/overdue calculations work. * Pair calculations work. * Triple calculations work. * Trend calculations work. * Position calculations work. * Statistical ticket generation works. * Generated tickets contain valid numbers for the selected lottery. * Duplicate white-ball numbers do not appear within a ticket. * Special balls remain within the correct game range. * Statistical filters work. * Ticket diversification works. * Saved combinations work. * CSV exports work. * Date filtering works. * Backtesting runs without crashing. * The application works on mobile and desktop. * The production Vercel deployment behaves the same as the local development version. Important statistical clarification This application is a statistical analysis and number-generation tool. It does not claim that historical statistics can predict a guaranteed lottery winner. The statistical score represents the application’s internal historical-analysis model and should not be presented as the actual probability that a ticket will win. What I am looking for in a developer The ideal developer should have experience with: * Next.js * React * JavaScript * Node.js * Git * GitHub * Vercel * Front-end debugging * Responsive web development * Browser-side data processing * CSV parsing * Statistical/data-oriented applications Experience deploying existing Next.js projects to Vercel is especially important. I value clear communication. If you discover a problem in the existing code, I would rather you explain the issue and recommend the best fix than silently remove functionality. This is V4/V5 — there will be additional work This is particularly important: Versions 4 and 5 are not intended to be the final versions of this application. I plan to continue developing the Lottery Statistical Analysis application through additional versions. We expect to write more code, add additional statistical systems, improve the analysis engine, improve backtesting, add new functionality, and continue expanding the application over time. I would strongly prefer to establish a relationship with one reliable developer who can continue working on the application as new versions are created. If this project goes well, I would like to rehire the same developer for future versions rather than finding a new developer every time. The future workflow will likely be similar: We develop the next version/code → provide it to the developer → developer reviews and debugs it → integrates it into the existing GitHub project → tests it → deploys the updated version through Vercel. Therefore, although this contract is specifically for V4/V5, there is a realistic opportunity for continued paid work on V6, V7, V8 and later versions as the application evolves. For that reason, I am particularly interested in someone who: * Writes clean, maintainable code. * Documents significant changes. * Keeps the GitHub repository organized. * Avoids unnecessary rewrites. * Understands the existing architecture before making changes. * Can work with an application that will continue growing. * Is comfortable returning for future updates. Current project status The major application logic is already supplied. I am not asking you to invent the statistical model from scratch. I am primarily hiring you to turn the supplied V4/V5 code into a properly tested, organized, GitHub-managed, successfully deployed web application. If you believe something in the supplied code should be changed before production deployment, please explain what you found and why you recommend changing it. Final deliverables The project will be considered complete when I have: * A tested and working Lottery Analyzer V4/V5 application. * Working Powerball functionality. * Working Mega Millions functionality. * Working historical-data analysis. * Working statistical ticket generation. * Working V5 analysis features. * Working backtesting. * A clean GitHub repository under my account. * The complete source code committed to GitHub. * Vercel connected to the repository. * A successful production deployment. * A working public Vercel URL. * Mobile and desktop functionality confirmed. * Reasonable deployment-related bugs resolved. * A project structure suitable for future V6+ development. When applying, please tell me about your experience with Next.js, React, GitHub and Vercel, and whether you would be interested in continuing to work on future versions of the application if this first project goes well.