Build a web app called Field Service Scheduler for a small company that sends technicians to customer sites. It needs: 1. Customers: create, edit and search customers with name, address, phone, email and notes. Each customer can have many sites. 2. Jobs: create a job for a customer site with type (installation, repair, inspection), priority (low, normal, urgent), required skills, estimated duration and a status (unscheduled, scheduled, in progress, done, cancelled). 3. Technicians: profiles with name, skills, home base and working hours. Show each technician's day as a timeline. 4. Scheduling: assign jobs to technicians and time slots. Flag clashes, missing skills and travel time over 45 minutes between consecutive jobs. Allow drag-and-drop rescheduling on a weekly calendar. 5. Dispatch view: a list of today's jobs by technician, with the ability to mark a job started, paused or done and add a short note with a photo URL. 6. Reports: jobs completed per technician per week, average time to complete by job type, and a CSV export. 7. Auth: email and password login with two roles, admin (full access) and dispatcher (no user management). 8. Data: store everything in a relational database with migrations. Include seed data for 3 technicians, 10 customers and 20 jobs. Use a modern web stack with a REST API, input validation, error handling, and automated tests for the scheduling clash rules and the CSV export. Include a README with setup and run steps.
Generated files, downloadable ZIP, and rerunnable pipelines all live here.
Build history, retries, and verification surfaces make the output easier to review with a team.
Start another run when you want to add features, fix issues, or generate a deployment package.