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>