projet-annuel-Master-2

Use when the user asks to change the database schema on the Symfony backend — add/rename a column, a new entity, a new index, a new enum-like field. Covers the diff-based `make:migration` workflow (always migration-driven, never `schema:update --force`), the snake_case_pluriel table naming, FK convention with cascade, MySQL 9 specifics, and the inverse relation pattern on the `User` entity.

Use when the user asks to add, rename, or remove a UI string in the frontend — anything rendered to the user. Covers the two locale files (`src/locales/fr.json` and `src/locales/en.json`) that must stay in lockstep, the custom `useTranslation()` hook (NOT next-intl despite the dep being installed), `{var}` interpolation, the language switcher in Settings, and the fallback chain.

Use when the user asks to add a new authenticated page to the frontend (Next.js 16, App Router). Covers the matcher in `proxy.js` (which replaces `middleware.ts`), the `useSession()` + `session.backendToken` pattern to call the Symfony backend, dark mode pairings, and the fr/en lockstep for any string added.

Use when the user asks to send a transactional email from the backend — welcome, reset password, IP alert, notifications, etc. Covers the invariant "never call `MailerInterface` directly, always enqueue via `PendingMailQueue::enqueue()`", the HTML template format, and the fact that delivery happens asynchronously via the `MailSchedule` ticking every minute.

Pipeline complet de développement intransigeant déclenché par `/pipeline <description de tâche>` (ex. `/pipeline ajoute un endpoint GET /api/projects` côté Symfony, `/pipeline fix le bouton de déconnexion qui ne purge pas la session`, `/pipeline refactor le SecurityIpList pour paginer côté serveur`). Enchaîne analyse → implémentation → tests destructifs → PR GitHub → review automatique → boucle de correction. Aucune sortie sans `doctrine:schema:validate` propre (si backend touché), `npm run build` réussi (si frontend touché), smoke tests verts et review VALIDÉ. Usage exclusif quand l'utilisateur invoque `/pipeline`.

Use when the user asks to add or modify a backend HTTP endpoint under `backend/src/Controller/Api/`. Covers the opt-in JWT auth pattern via `JwtAuthService::authenticate()`, JSON response shape, the centralized `IpBanService::getClientIp()` helper, idiomatic HTTP status codes, and the conventional structure inheriting from `ApiAbstractController`.