Julien Gautier
2725436801
CI / commits (pull_request) Successful in 4m25s
CI / scan (pull_request) Successful in 4m36s
CI / check (pull_request) Successful in 4m51s
CI / a11y (pull_request) Successful in 3m28s
Docs site / build (pull_request) Successful in 4m55s
CI / perf (pull_request) Successful in 8m51s
PrismaScopeResolver replaces StubScopeResolver in AuthModule. Queries user_scopes WHERE userId AND (expiresAt IS NULL OR expiresAt > NOW()) and maps each row to a typed Scope via a pure toScope helper. Defensive: off-catalogue kinds are skipped + warn-logged rather than thrown (write path is the canonical guard via the drift gate). prisma/seed.ts populates Person + User + UserScope rows for the 19 test-tenant personas per notes/test-tenant-role-assignments.md. The persona matrix (slug + email + displayName + scope tuples) is hardcoded in the seed; tenant-private Entra oids are read from TEST_TENANT_PERSONAS_PATH (default infra/test-tenant.personas.json, gitignored). Idempotent on every level: User unique on entraOid, UserScope unique on (userId, kind, value). StubScopeResolver class stays exported from scope-resolver.ts for spec fixtures + as a future force-everyone-unrestricted dev hint, but is no longer wired by default. The admin /admin/users/:id/scopes screen is split into the follow-up PR 2b - the Angular SPA work is a different mode from this backend + data PR. Local: drift gate 4/24/7/3 clean, 29 drift-gate specs pass, portal-bff lint 0 errors, 774 portal-bff specs pass (+8 for the resolver spec).
Documentation index
This is the entry point to all project documentation. It is maintained automatically: any addition, rename, or removal of a .md file under docs/ must be reflected here in the same change.
Conventions
- Documentation is written in English.
- One topic per file. Group related files into a folder when there are three or more.
- Cross-reference with relative links so they keep working in GitHub, IDEs, and exported sites.
- For architectural decisions, do not add them here — they belong in decisions/ as MADR 4.0.0 ADRs.
Sections
Daily development
- development.md — repo layout, prerequisites, initial setup, daily commands, observability dev-loop (Jaeger UI, log ↔ trace correlation), dependency updates (Renovate), conventional commit cycle. Day-to-day reference for working on the project.
Architecture
- architecture.md — cross-cutting Mermaid diagrams: C4 system context, C4 containers, Nx module boundaries, CI/CD pipeline. Single-decision diagrams (auth sequence, ERD, etc.) live inline in their ADR.
Onboarding & environment
Setup guides for new contributors:
- setup/01-wsl-terminal-setup.md — modern WSL terminal (Zsh + Powerlevel10k + CLI tools)
- setup/02-dev-web-stack.md — Node via nvm, pnpm via corepack, Docker
- setup/03-angular-nx-monorepo.md — Angular + Nx monorepo bootstrap
Operations & runbooks
Empty — to be populated when we deploy.
Security, performance, accessibility
Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.