The recruiter placement/unlock backend was end-to-end (routes, talentBillingService, Creem checkout + signed webhook settlement) but had no frontend, so recruiters literally could not pay. This closes the only fully dead-ended money surface. Web (gitgram/web): - talentGraphService: add listUnlocks, requestUnlock (idempotent, optional placement success-fee), and getCandidateContact mapping the existing owner-gated backend routes, with typed placement/contact envelopes. - utils/talentUnlock: pure gating helpers (deriveUnlockState, findPlacement, interpretUnlockResult, formatFee) so the owner-only logic is unit tested without rendering. - talent-network page: owner-only "Unlock candidate" action on each match card — opens the Creem checkout, reveals contact + full evidence once the entitlement is paid (poll via "check payment" and on-return via query params), with not-owner / pending / unlocked / already-unlocked states. Backend (gitgram/backend): - talentBillingController: point the checkout successUrl at the real /talent-network page (with opportunity + unlocked params) instead of a non-existent /talent/opportunities route, so payment return is not a 404. Tests: unit-test the three service methods (idempotency header, success-fee body, already-unlocked, 402-when-unpaid, id encoding) and the gating helper (not-owner/unlockable/pending/unlocked, checkout-vs-reveal). 21 new tests. Co-Authored-By: Claude Fable 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.