Julien Gautier 6065922520
CI / commits (pull_request) Successful in 1m14s
CI / check (pull_request) Successful in 1m25s
CI / scan (pull_request) Successful in 1m24s
CI / a11y (pull_request) Successful in 1m19s
CI / perf (pull_request) Successful in 2m58s
docs(development): add observability dev-loop section
ADR-0012 phase 1 + phase 2 are wired (BFF + SPA), so the
"Observability dev-loop" placeholder in the roadmap table now has
real content to point at. Promote it from §9 (was §8) future-work
list to a full §5 walkthrough sitting between "Daily commands"
and "Dependency updates".

What §5 covers:

- Bringing up the observability stack (`./infra/local/dev.sh up
  observability`) with the endpoint table.
- Reading a trace in Jaeger — service-dropdown filter, span
  attribute keys to look at, the trace-id-as-pivot pattern.
- Correlating a trace with the BFF Pino logs via `trace_id` and
  `request_id` (the latter the per-request UUID nestjs-cls
  provides).
- Reading SPA spans from the browser (DevTools Network +
  Jaeger UI cross-check).
- Common gotchas — observability profile not active, CORS
  pre-flight on `/v1/traces`, `propagateTraceHeaderCorsUrls`
  mismatches, NODE_ENV mis-set, EADDRINUSE.
- Pointer at the "wired as features land" deltas (CLS keys for
  session/user/audience, redact list, custom domain spans, prod
  backend) so a contributor knows what's intentionally not yet
  there.

Renumber the rest of the doc accordingly (5→6 / 6→7 / 7→8 / 8→9)
and drop the now-implemented "Observability dev-loop" line from
the §9 roadmap table.

`docs/README.md` cross-link updated to mention the new section.
2026-05-10 02:10:53 +02:00

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:

Operations & runbooks

Empty — to be populated when we deploy.

Security, performance, accessibility

Empty — placeholders to be filled with rationale docs alongside their corresponding ADRs.

S
Description
No description provided
Readme 42 MiB
Languages
TypeScript 85.3%
JavaScript 5.4%
SCSS 4.3%
HTML 3.9%
Shell 0.8%
Other 0.3%