fix(token-sets): drop the two Zuiddrecht nav tokens nothing reads, refresh its reference page

[WilcoLouwerse]

Why

PHPUnit fails on all 8 legs of development, and with it the release PR #1080 (development → beta). There are two failures, both from #1099 (the Zuiddrecht hero and nav tokens):

1. TokenSetVocabularyTest::testEveryShippedSetIsCompleteOrAllowListed: zuiddrecht: 2 declared name(s) nothing reads (--nldesign-website-nav-current-color, --nldesign-website-nav-current-in-line). No stylesheet in thematiq reads them, and a code search finds no reader in the portal repos either.
2. TokenReferenceDocsTest::testTheCommittedPagesAreCurrent: docs/reference/token-sets/zuiddrecht.md is stale.

What

• css/tokens/zuiddrecht.css: the two unread nav tokens and their comment are removed. Nothing read them, so nothing changes on screen. The four hero tokens from feat(token-sets): Zuiddrecht gets a light website hero and a blue piece under the current menu item #1099 stay, because public-bridge.css reads them.
• css/tokens/dark/zuiddrecht.css: regenerated with php scripts/generate-dark-variants.php, the generated file's own route.
• docs/reference/token-sets/zuiddrecht.md: regenerated with composer docs:token-reference.

The allow-list is not used: its own comment reserves it for sets the converter still has to regenerate.

If the "current menu item as a blue piece of the line under the menu" look from #1099 is still wanted, it needs a reader first, e.g. in public-bridge.css or the portal's navigation styles. The two tokens can come back together with that reader.

Test

• phpunit tests/Unit/TokenSetVocabularyTest.php → OK (8 tests).
• phpunit tests/Unit/TokenReferenceDocsTest.php → OK (3 tests).
• phpunit -c phpunit.token-sets.xml → OK (344 tests).

🤖 Generated with Claude Code

[WilcoLouwerse]

Verdict: APPROVE

Quick review (self-review, posted as a comment). Nothing definitely broken.

• The two tokens it removes, --nldesign-website-nav-current-in-line and --nldesign-website-nav-current-color, have no reader in thematiq's CSS, and an org-wide code search finds none in the portal repos either. Removing them changes nothing on screen.
• The four hero tokens from #1099 stay, because public-bridge.css reads them.
• css/tokens/dark/zuiddrecht.css comes from its own generator (generate-dark-variants.php, new source hash), and the reference page from composer docs:token-reference.

Checks run locally:

• TokenSetVocabularyTest → OK (8 tests).
• TokenReferenceDocsTest → OK (3 tests).
• phpunit.token-sets.xml → OK (344 tests).

Gates: CI on 64edc8ae is still running at the time of this review. The PHPUnit legs are the real check, because they are what is red on development and on #1080.

Review assisted with Claude AI.

[github-actions]

Quality Report — ConductionNL/thematiq @ e2323bf

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
test-l10n		✅
format		✅
test-fonts		✅
test-token-set-coverage		✅
composer			✅	✅ 107/107
npm			✅	✅ 2/2
app:check-code	⏭️
info.xml	✅
REUSE	✅
lockfile sync		✅
PHPUnit					✅
Newman					✅
Playwright					⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it locally with npx playwright test, or from the Actions tab on a branch with no open pull request into development.
Hydra gates					✅

---

Quality workflow — 2026-10-06 13:01 UTC

Download the full PDF report from the workflow artifacts.

[github-actions]

Quality Report — ConductionNL/thematiq @ 0b82b70

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
test-l10n		✅
format		✅
test-fonts		✅
test-token-set-coverage		✅
composer			✅	✅ 107/107
npm			✅	✅ 2/2
app:check-code	⏭️
info.xml	✅
REUSE	✅
lockfile sync		✅
PHPUnit					✅
Newman					✅
Playwright					⏭️ deferred: E2E runs locally and on the promotion path only. This pull request targets development, so the suite is asked once per promotion into beta and main rather than once per push per open pull request. Run it locally with npx playwright test, or from the Actions tab on a branch with no open pull request into development.
Hydra gates					✅

---

Quality workflow — 2026-10-06 22:15 UTC

Download the full PDF report from the workflow artifacts.