refactor(softwarecatalog): translate 12 pre-existing Dutch property names

[rubenvdlinde]

Tranche 2 of the Dutch→English vocabulary programme.

Measured at 28 Dutch property names against real wordlists (274,937 English,
164,174 Dutch; a token is Dutch when the Dutch list has it and the English list
does not). 12 move here. 13 are held back, and that half is the more useful
one — each needs a decision rather than a rename:

held back	why
organisatie, contactpersoon, dienst, gebruik, moduleVersie, bioMaatregel	Each is also a schema slug. A quoted 'organisatie' in PHP is a schema reference in one place and a property key in another — 107 of them — and nothing in the token tells them apart. Needs the schema rename decided with it.
domein	One of the four facet dimensions the endpoint declares as query parameters and response keys. Renaming one of four is what broke filtering in tranche 1; they move together, as their own change.
bron	The Relation schema declares both bron and source for one concept. A rename would silently merge two columns. The duplication is the defect.
omschrijving	The COLUMN_MAP is flat and already maps omschrijving → description. The remaining occurrence is in a schema that already declares description, so it would need summary — one source cannot have two targets.
alg, bomRef, tooi, *Url	JOSE header, CycloneDX field, TOOI register, url. Not Dutch.

Three defects in my own tooling, found by tests rather than review

1. The unquoted-object-key pattern never fired. Its (?!:) guard — meant to
   skip PHP :: — sat immediately after the name, where the next character is
   the colon being matched, so it could never pass. Every beschrijvingKort:
   payload key was left behind while its value was renamed, so the suite wizard
   POSTed a key the schema no longer declares.
2. Running the applier twice rewrote the migration map's own left-hand side.
   The map is a .php file under lib/, so 'afkorting' => 'abbreviation'
   became 'abbreviation' => 'abbreviation' — a no-op that also destroys the
   only record of the column's old name, and it took a pre-existing entry with
   it. The map and its test are excluded from the rename now.
3. A destructured parameter is shorthand too.
   buildOrganisationCoverage({ gebruiken }) kept its parameter while one call
   site moved to usages:; the function read an undefined key and returned an
   empty coverage array.

This app's own suite caught two of them, including a positive control asserting
the register still declares Dutch columns. That control's threshold (> 20) was
a snapshot of how much Dutch remained, not a property of the guard — it is > 0
now, which is what it was for, with a note that the day it fails is the day the
test has nothing left to guard.

Verified against a control run of the same tree

check	this branch	control
PHPUnit	684, 1 error, 0 failures	684, 1 error
phpstan	[OK]	[OK]
psalm	No errors found!	No errors found!
jest / vitest	120/120 · 226/226	—
eslint / prettier / build	0 / clean / OK	—
routes resolved / broken	129 / 0	—
surviving uses in src/	0	—

The 1 PHPUnit error is pre-existing on both sides — a missing
Symfony\Component\HttpFoundation\HeaderUtils in the standalone bootstrap.

10 migration entries appended; the map is verified free of duplicate and identity
entries.

[github-actions]

Quality Report — ConductionNL/softwarecatalog @ 355989b

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
check-vue-demi		✅
test-l10n		✅
format		✅
composer			✅	✅ 130/130
npm			✅	✅ 704/704
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					✅
Newman					⏭️
Playwright					❌
Hydra gates					❌

---

Quality workflow — 2026-08-14 18:06 UTC

Download the full PDF report from the workflow artifacts.