Julien Gautier
a800b9d28d
After ~10 days of clean track record on Renovate (~30 PRs merged without regression beyond the TS/ESLint/webpack-cli majors that the dashboard-approval rule now catches), enable auto-merge for patch / pin / digest / lockFileMaintenance updates. CI is the gate — `check` / `scan` / `a11y` going red leaves the PR open for manual triage. Minors keep needing human review (might widen surface), majors are still dashboard-approval-gated. The dashboard triage header is updated so the "Open" row reflects the new reality (mostly minors, with red patches surfacing briefly when CI fails). docs/development.md "Reviewing Renovate PRs" gains a bullet describing the auto-merge behaviour for contributors landing on the project later. `automergeStrategy: "squash"` matches our trunk-based squash-merge convention. `automergeType: "pr"` keeps a PR + CI run as the audit trail (vs branch-direct push), and Gitea automerges the PR once green via the bot's existing `repo:write` permission.
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.