This repository has been archived on 2026-11-17. You can view files and clone it, but cannot push or open issues or pull requests.
caelum0x 7275b79df9 feat(web): surface talent-graph need-coverage / gap analysis in the UI
The backend shipped GET /talent-graph/opportunities/:id/coverage and
talentGapAnalysisService (ARCHITECTURE §3.1 CQ#7 — "which required skills does
the pool cover, and which are unmet gaps?") but no web client consumed it.
Institutions could see top candidates yet not their skill gaps.

- talentGraphService: add getOpportunityCoverage() + NeedCoverageAnalysis,
  SkillCoverage, CoverageStrength types mirroring the backend contract.
- talent-network page: fetch coverage alongside matches for the selected
  opportunity and render a "Beceri kapsama" panel — per-skill strength badges
  (verified/evidenced/interest/unmet), the unmet-skill gap list, coverage ratio
  and roll-up status. Coverage is a public read (skill tokens + counts only, no
  private free text), so it renders for any viewer of the need.
- CSS: coverage panel styled in the existing Swiss/editorial system.
- tests: web service test for the coverage endpoint (path + shape).

Additive, read-only slice. No backend changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-08-26 17:11:33 +03:00
..

Gitgram Web

Web version of Gitgram built with Next.js 14, TypeScript, and Tailwind CSS.

Getting Started

  1. Install dependencies:
npm install
  1. Set up environment variables:
cp .env.example .env
  1. Run the development server:
npm run dev
  1. 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:

  1. Institution need from GET /v1/talent-graph/opportunities
  2. Evidence matches from GET /v1/talent-graph/opportunities/:id/matches
  3. Candidate-controlled Zen referral from GET /v1/talent-graph/referrals/mine
  4. Pilot delivery and audit history from GET /v1/talent-graph/pilots/mine
  5. Eligible public proof in the owner /collaborate dossier

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.