DELETE /auth/delete-account threw "User not found" for every OAuth-only
account (any user with no password always failed `!user.password`), and
both the web and mobile clients called /v1/compliance/account and
/compliance/account, routes that never existed - so account deletion
was broken for 100% of users on every surface, not just OAuth.
Password accounts still require re-entering their password; OAuth-only
accounts delete using the authenticated session as proof instead. Web
and mobile now check whether the account has a password before showing
the field, and call the real /auth/delete-account route. Backend keeps
a DELETE /auth/account alias for any already-shipped client builds.
70/70 backend auth tests pass, including 3 new cases for the
OAuth-without-password path and the password-missing/wrong-password
cases.
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>
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>