style: format the repo with prettier (green format:check)

`npm run format:check` (a CI gate) had drifted red across 44 files — pre-existing
files plus recently-added ones committed without formatting. Ran `prettier --write .`;
no logic changes. Also regenerates documentation.json (compodoc reflects the reformatted
component sources).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

docs/project/backlog/WP-29-stamdata-beheer-editor.md

@@ -24,7 +24,7 @@ authority. No production database, no runtime write path (ADR-0004 unchanged).
 
 - **Read-only endpoints only.** `GET /stamdata` (catalog) and `GET /stamdata/{table}?peildatum=`
   (schema + rows). No POST/PUT/DELETE — the edit lands as a reviewed PR, not a write. The
-  `stamdata:edit` capability / `CanEditStamdata` gate the *reads* (naming is the enforce-twin
+  `stamdata:edit` capability / `CanEditStamdata` gate the _reads_ (naming is the enforce-twin
   of a future edit capability; deliberate).
 - **Generic, schema-driven.** One endpoint pair + one grid editor serve every table. Columns
   are reflected from the typed record (`StamdataTable.Of<T>`); the FE renders inputs by column
@@ -32,7 +32,7 @@ authority. No production database, no runtime write path (ADR-0004 unchanged).
   endpoint, UI, or test. (Catalog of one today; this is the shape ADR-0004 prescribed.)
 - **Data-file format for `professions`.** `professions.json` (embedded resource) replaces the
   hardcoded C# dictionary, deserialized into `ProfessionMapping`. This trades compile-time
-  *value* checking (gate #1) for editor ergonomics — the value gate becomes
+  _value_ checking (gate #1) for editor ergonomics — the value gate becomes
   `StamdataValidationTests` (gate #2), exactly the trade-off ADR-0004's consequences listed.
 - **Valid-time.** `geldigVan`/`geldigTot` (half-open `[van, tot)`); a table is temporal iff it
   has both columns. `peildatum` previews "which rows applied on date X". `Professions.ByProgram`