Recurring rides

[anika-4444]

Summary

This pull request is the first step towards implementing recurring rides

• implemented recurring rides logic in the backend (pre-create rides up to 4 months out, if user edits single ride then ride is pulled out of recurrence. else, delete all future rides, update recurrence and regenerate. not the most efficient solution but for the scope of carriage and our timeline, it seems like the simple solution is better
• added dialog to frontend asking user about editing the single event vs changing the recurrence
• added more docs to ride.ts in router

Note: This PR should not be merged into main until the db rewrite is approved/merged into main because most of the changes are cascading

Test Plan

things to test

• editing a single event
• editing the recurrence
• weekly vs monthly vs daily vs custom recurring rides
• are we only editing the ride details the user requests

Breaking Changes

Schema change to ride schema. I deleted my local db and regenerated it with "npx prisma migrate reset"

[netlify]

✅ Deploy Preview for carriage-web ready!

Name	Link
🔨 Latest commit	5875331
🔍 Latest deploy log	https://app.netlify.com/projects/carriage-web/deploys/69fa3825bac8510008398763
😎 Deploy Preview	https://deploy-preview-688--carriage-web.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cu-carriage	Error		May 5, 2026 6:34pm

[dti-github-bot]

[diff-counting] Significant lines: 29054. This diff might be too big! Developer leads are invited to review the code.