Files
HealthLog/src/lib
Marc-André Bombeck 107db1bb55 feat(admin): let an admin delete another account through the grace window
There was no way for an admin to remove someone else's account; the
users list only offered the undo for a deletion the account itself or a
Guardian had asked for.

DELETE /api/admin/users/{id} takes the account's own deletion path,
now shared as requestAccountDeletion: with a grace window the account
is locked at once (credentials revoked, record untouched) and erased by
the purge job when the window ends, and the existing undo gives it back
until then; with ACCOUNT_DELETION_GRACE_DAYS=0 it is erased in the
request. The route is cookie-only behind requireAdmin and the
recent-proof gate, takes the typed DELETE_ACCOUNT confirmation, and
refuses the caller's own account, a managed profile (its Guardians
delete it), an account already pending deletion, the last admin who
can sign in and the last Guardian of a managed profile, the last three
decided under their locks inside the transaction. Both the admin and
the account get an audit row.

The users list says who asked for a pending deletion, now including an
admin, and flags managed profiles. Each other account's row carries a
delete button whose confirmation names the purge date, or says the
erasure is immediate when the server keeps no window.
2026-10-29 09:10:26 +01:00
..
…
…
…
…
…

src/lib/

The server and runtime toolkit. Everything that is not a page, component, or route handler lives here: the API kit, auth, crypto, the rollup tier, AI providers, notifications, background jobs, and the integration clients. Route handlers and RSC pages compose these modules; the modules never reach back into app/.

Core request kit

  • api-handler.ts — the apiHandler wrapper every route uses (Wide-Event builder, error envelope, GlitchTip forwarder) and the one public entry for the request guards in auth/guards/: the auth resolver (cookie OR Bearer), requireAuth / requireRecordAuth / requireAdmin (admin is cookie-only by construction), the step-up gates.
  • api-response.ts — the { data, error, meta? } envelope: apiSuccess / apiError, safeJson, trusted-proxy IP resolver, returnAllZodIssues + sanitiseZodIssues.
  • rate-limit.ts — Postgres-backed sliding-window limiter (single atomic upsert); multi-instance correct.
  • idempotency.ts — user-scoped idempotency keys that refuse to cache secret-shaped responses.
  • query-keys/ — the only legal source of TanStack Query queryKey / mutationKey arrays (enforced by an ESLint rule); per-feature files behind the index.ts barrel.
  • safe-fetch.ts — the one documented outbound-egress entry (redirect: "manual" + timeout; optional connect-time DNS-rebinding pin). Raw fetch( under lib/ + app/ is banned by ESLint.
  • db.ts — the Prisma client singleton.
  • crypto.ts — AES-256-GCM at rest with versioned key ids, fail-closed loader, rotation primitives.

Subsystems

  • auth/ — Postgres sessions, secure-cookie flag policy, passkey (WebAuthn) + Argon2id password, per-device refresh-token rotation, HMAC Bearer tokens.
  • ai/ — multi-provider insight + Coach engine: provider-chain.ts, hand-rolled {openai,anthropic,local,codex,mock}-client.ts, coach/, prompts/, citation + confidence helpers.
  • rollups/ — DAY/WEEK/MONTH/YEAR pre-aggregations for measurements, mood, and medication compliance. Read-swap pattern: probe the rollup, fall back to live SQL on a coverage miss.
  • notifications/ — the dispatcher cascade (APNs → Telegram → ntfy → Web Push), per-channel senders/, retry policy, VAPID config.
  • jobs/ — pg-boss workers: reminders, insight pre-generation, backups, retention sweeps, integration backfills. Recurring work belongs here, not in scripts/.
  • integrations/, withings/, whoop/, fitbit/ — OAuth clients and sync services for the device providers; sync/ holds the shared delta-feed plumbing.
  • analytics/ — trend calculations, cadence-aware medication compliance.ts, correlations.
  • insights/, fhir/, doctor-report-*.ts — insight pipeline, FHIR R4 export, client-side doctor-report PDF.
  • openapi/ — Zod registry that is the source of truth for docs/api/openapi.yaml.
  • logging/, observability/, monitoring/ — Wide-Event transports and the central redaction denylists (redact at the egress boundary, not the call site).
  • validations/ — shared Zod schemas, including the SSRF isPublicUrl floor.
  • i18n/, tz/ + timezone.ts, format*.ts — translations, timezone helpers (Berlin for display, UTC in DB), locale formatting.

Conventions

Kebab-case filenames. See ../../CLAUDE.md "Code conventions" and "Security-relevant patterns"; the critical-files map there cites the exact entry points. Most modules carry tests in a sibling __tests__/.