The canonical /login and /register already offered GitHub OAuth, but the
legacy /auth screen (reached via router.push('/auth') from insights, drafts,
creator-studio, follow-requests) was email/password only — a GitHub-native
new user landing there had no way in. Add a guarded "Sign in with GitHub"
button that calls githubService.connectGitHub() (redirects to GitHub's
authorize endpoint; /auth/github/callback, already in middleware publicPaths,
completes it). Also drop the emoji from the footer copy per the no-emoji UI
rule while editing this screen.
Test: connectGitHub redirects to the authorize endpoint with the configured
client_id, callback redirect_uri, and user:email,repo,read:user scopes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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>
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>