[Khai189]

Context

Adds the admin UI for running the ride-matching algorithm. The algorithm runs as its own AWS Lambda function (Function URL), separate from this Netlify app. This PR only adds the frontend page and the server-side routes that call it; the Lambda's code and deploy steps live outside this repo.

This replaces the earlier plan of running the service behind the aspc-website-v2 backend (aspc/aspc-website-v2#254, now closed).

Admin → /admin/matching → /api/admin/matching/{status,run} (Netlify, admin-only)
                                   │ X-API-Key
                                   ▼
                        AWS Lambda (matching) → Supabase

Describe your changes

• frontend/src/app/admin/matching/page.tsx: new /admin/matching route, behind the existing admin auth layout.
• frontend/src/components/admin/MatchingAlgorithm.tsx: "Run Matching" UI. Pulls riders from the database and commits the result through the Lambda's /run endpoint, which writes groups and matches to Supabase and consumes vouchers. Shows a confirmation dialog first, since a run can't be undone or previewed from here.
• frontend/src/app/api/admin/matching/run/route.ts and .../status/route.ts: server-only routes. The browser never talks to the Lambda directly; these call ALGORITHM_SERVICE_URL with ALGORITHM_SERVICE_API_KEY.
• Subsidized dates come from this app: /run sends subsidized_periods, built from SERVICE_PERIODS by the new getSubsidizedPeriodRanges() in servicePeriodHelpers.ts. The matcher subsidizes exactly the dates students see on the site, instead of keeping its own hardcoded list, which had drifted and was missing Thanksgiving 2026. Changing break dates now only means editing servicePeriods.ts.
• frontend/src/components/admin/AdminDashboard.tsx: a "Run Matching Algorithm" button next to "View & Manage Groups".
• frontend/.env.example: documents the two server-only env vars.

Before this works in prod

1. Deploy the matching Lambda and create its Function URL.
2. In Netlify → Site configuration → Environment variables, set:
   • ALGORITHM_SERVICE_URL: the Lambda Function URL
   • ALGORITHM_SERVICE_API_KEY: the same value as the Lambda's SERVICE_API_KEY
3. Redeploy the site.

Until then, /admin/matching shows a "not configured" banner and nothing runs.

Testing

• Type/lint/format: tsc --noEmit, eslint, and prettier --check are clean on every changed file.
• Unit tests: 266/266 Jest tests pass, including new tests for getSubsidizedPeriodRanges(): it matches SERVICE_PERIODS, and every range boundary agrees with isDateCovered.
• Lambda contract: called the Lambda handler locally with Function URL events:
  • Thanksgiving riders are subsidized when the Thanksgiving range is sent.
  • They aren't when the range is for another break or the other direction.
  • A missing or invalid subsidized_periods is rejected with 422.
  • API-key checks return 401/503 as expected.
• Not yet tested: a real /run against the deployed Lambda and Supabase.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for p-ickup ready!

Name	Link
🔨 Latest commit	66442e1
🔍 Latest deploy log	https://app.netlify.com/projects/p-ickup/deploys/6af5325c332437ad3e5037db
😎 Deploy Preview	https://deploy-preview-155--p-ickup.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.