Feat/verifystandups
Summary
This MR fixes corpus API integration and updates standup verification to use real corpus uploads with strict category/date checks at intern and team level.
What Changed
- Fixed frontend corpus route construction to avoid duplicated
/api/api/v1/...and use proxy-safe relative paths. - Updated corpus service request builder to support empty
baseUrland still call/api/v1/...correctly. - Implemented team verification flow:
- Verify each intern using corpus audio metadata.
- Count only uploads that match required categories + today’s date.
- Aggregate team-level qualified count and status (
COMPLETEDwhen count >= 4).
- Updated verification logic to enforce distinct category matching (Stand-Up and Internship must both be present).
- Added UUID alias support for category matching (including provided corpus UUIDs).
- Added dashboard UI updates to show per-intern and team “today qualified uploads” counts.
- Added frontend env typing (
vite-env.d.ts) and updated.env.examplewith backend + frontend alias keys.
Environment Notes
Add these keys in .env for frontend verification:
VITE_STANDUP_LABEL_ALIASESVITE_INTERNSHIP_LABEL_ALIASES
Validation
-
npx tsc --noEmit -p tsconfig.jsonpassed -
npm run buildpassed
Important
-
.envis not committed (token remains local/private). - In dev tools, requests appear as
localhost:5173/api/...because of Vite proxy; backend target is corpus API.
Edited by Kushal Lagichetty