Three user-facing "export my data" entry points (settings/privacy, settings/data, backup/export) all called endpoints that never existed on the backend: /v1/settings/data and /v1/compliance/export-data both 404. Every click silently failed or showed a fake "queued, check your email" message with nothing ever sent. A fully working, real GDPR export pipeline already exists at /api/v1/data-export (request -> async generate -> poll status -> download), just never wired to any UI. Added a shared requestAndDownloadDataExport flow (web/utils/dataExportFlow.ts) that requests the export, polls status until ready, then streams and downloads the file, and pointed all three pages plus userService's mismatched getExportStatus (was missing the required exportId path param) at it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Gitgram Web
Web version of Gitgram built with Next.js 14, TypeScript, and Tailwind CSS.
Getting Started
- Install dependencies:
npm install
- Set up environment variables:
cp .env.example .env
- Run the development server:
npm run dev
- Open http://localhost:3000 in your browser.
Features
- Next.js 14 App Router
- TypeScript
- Tailwind CSS for styling
- GitHub-inspired UI
- Shared API client with mobile app
- Authentication with JWT
- Server-side rendering (SSR)
- Static site generation (SSG)
Project Structure
web/
├── app/ # Next.js App Router pages
├── components/ # React components
├── services/ # API services
├── store/ # State management (Zustand)
└── lib/ # Utilities
Talent Graph proof route
/talent-network presents one API-backed route:
- Institution need from
GET /v1/talent-graph/opportunities - Evidence matches from
GET /v1/talent-graph/opportunities/:id/matches - Candidate-controlled Zen referral from
GET /v1/talent-graph/referrals/mine - Pilot delivery and audit history from
GET /v1/talent-graph/pilots/mine - Eligible public proof in the owner
/collaboratedossier
Public pilot evidence requires a COMPLETED pilot, participant consent, and a public HTTP(S) deliverable. The client does not seed records. A zero count comes from the API; the screen renders request failures as an unavailable state with a retry action.
All Talent Graph writes now carry a retry-stable Idempotency-Key. Referral and
pilot updates also send the revision read from the API, so concurrent decisions
or edits fail with 409 instead of overwriting one another. Public profile and
matching reads consume the dedicated TalentPublicProof projection rather than
joining private opportunity/pilot records at request time. See the backend
release runbook.
The owner dossier creates /collaborate?profile=<username> only when the account has a public username. Browser validation still needs two accounts for referral acceptance and institution completion, forced API failures for each resource, responsive anchor review, and public-link checks. The current hackathon cycle forbids build, test, lint, CI, migrations, and app-server runs.