docs(schemas): keep spec ids and em-dashes out of text a user reads

[rubenvdlinde]

Schema property descriptions render as help text under form fields, so whatever is written there is product copy. Two things in it were not meant for a reader.

Requirement ids. 8 strings carried a trailing (REQ-DASH-011) or similar. That is our traceability leaking onto a user's screen: it means nothing to the person filling in the field, and it costs the sentence its ending.

Em-dashes. 11 strings used one. Voice rule 8 bans them outright, so each is rewritten with a comma, a colon or a full stop rather than swapped for a different dash.

After this, launchpad has 0 spec ids and 0 em-dashes in any description / title / label / placeholder / help value across lib/Settings/** and src/**.

One description also loses a paragraph explaining that a union type such as ["string","null"] is rejected by the schema importer, and that this once silently prevented the schema being created. That is true and useful, and it is addressed to whoever maintains the register rather than to the person filling in the form.

Edits are raw-text, so file formatting is untouched: 22 changed lines, not a reformat.

🤖 Generated with Claude Code

[github-actions]

Quality Report — ConductionNL/launchpad @ d19a199

Check	PHP	Vue	Security	License	Tests
lint	✅
phpcs	✅
phpmd	✅
psalm	✅
phpstan	✅
phpmetrics	✅
eslint		✅
stylelint		✅
build		✅
check-manifest		✅
format		✅
check-schema-l10n		✅
composer			✅	✅ 104/104
npm			✅	✅ 526/526
app:check-code	⏭️
info.xml	✅
REUSE	❌
PHPUnit					✅
Newman					✅
Playwright					⏭️ deferred — runs on the promotion into beta/main, not on a pull request into development
Hydra gates					✅

---

Quality workflow — 2026-09-03 09:50 UTC

Download the full PDF report from the workflow artifacts.