docs(adr): convert all ADRs to MADR 2.1.2 format

Rewrites all 12 frontend ADRs from a custom structure to the MADR 2.1.2
template required by the VS Code ADR Manager extension: bullet metadata
(Status/Date), standardised section headings, "Chosen option: X, because Y"
wording, and explicit Pros/Cons blocks per option.

docs/decisions/0007-build-tool-angular-cli-esbuild.md

@@ -1,20 +1,43 @@
-# ADR 0007: Build Tool — Angular CLI with esbuild
+# Use the esbuild-based Angular application builder
 
-**Date:** 2026-04-26
-**Status:** Accepted
+- Status: accepted
+- Date: 2026-04-26
 
-## Context
+## Context and Problem Statement
 
-Angular 17 introduced a new application builder (`@angular/build:application`) based on esbuild and Vite, replacing the legacy webpack-based `@angular-devkit/build-angular:browser` builder. The new builder delivers significantly faster cold builds and near-instant incremental rebuilds.
+Angular 17 introduced a new application builder (`@angular/build:application`) based on esbuild and Vite, replacing the legacy webpack-based `@angular-devkit/build-angular:browser` builder. Which builder should be used for development and production builds?
 
-## Decision
+## Considered Options
 
-Use the `@angular-devkit/build-angular:application` builder (esbuild-based) as configured in `angular.json`. The entry point is defined via the `browser` field rather than `main`.
+- `@angular/build:application` — esbuild-based (Angular 17+)
+- `@angular-devkit/build-angular:browser` — webpack-based (legacy)
 
-## Consequences
+## Decision Outcome
 
-- **Positive:** Build times are 3–5× faster than the webpack builder for both development and production.
-- **Positive:** Native ESM output. Better code splitting.
-- **Positive:** Aligns with Angular's recommended toolchain for Angular 17+.
-- **Negative:** Some webpack-specific configuration options (e.g. custom webpack plugins) no longer apply. Not an issue for this project.
-- **Note:** The `sass` sub-option under `stylePreprocessorOptions` (for `silenceDeprecations`) is specific to this builder's schema; the Karma test builder uses a different schema and does not support it.
+Chosen option: "`@angular/build:application`", because it is the Angular-recommended builder since v17, delivers significantly faster builds, and is required for certain schema-level features such as `stylePreprocessorOptions.sass.silenceDeprecations`.
+
+### Positive Consequences
+
+- Build times are 3–5× faster than the webpack builder for development and production.
+- Native ESM output with better code splitting.
+- Aligns with Angular's recommended toolchain for v17+.
+
+### Negative Consequences
+
+- Webpack-specific configuration options (custom plugins, loaders) no longer apply. Not an issue for this project.
+- The `sass` sub-option under `stylePreprocessorOptions` is specific to this builder's schema; the Karma test builder uses a stricter schema and does not support it.
+
+## Pros and Cons of the Options
+
+### `@angular/build:application` (esbuild)
+
+- Good, because significantly faster cold builds and incremental rebuilds.
+- Good, because Angular-recommended default since v17.
+- Good, because required for `sass.silenceDeprecations` support.
+- Bad, because webpack plugin ecosystem is not compatible.
+
+### `@angular-devkit/build-angular:browser` (webpack)
+
+- Good, because supports custom webpack configuration.
+- Bad, because deprecated direction; slower builds.
+- Bad, because does not support the `sass.silenceDeprecations` option.