content: add 4 Netherlands canons (policy/medical/disaster); re-verify 3 aging code canons

[dbwls99706]

Gap filled

The Netherlands had 5 canons, all generic EU-template entries — Schengen 90/180, EU roaming, 112, EHIC, and cycling priority. Nothing Dutch-specific. Every one of those pages would read the same for Belgium or Ireland.

This adds four canons covering dead ends that are specific to Dutch administration and Dutch civil-protection doctrine, where generic LLM advice is confidently wrong. nl: 5 → 9. Countries: 66 (unchanged). Total canons: 2505 → 2509.

PR #179 is concurrently working Finland; no overlap in country, domain slug, or re-verification bucket.

Canons added

ID	Dead end documented
policy/rni-desk-restricted-for-non-eu/nl	Of the 19 municipalities with an RNI desk, only Breda and Venlo accept non-EU/EEA/Swiss nationals. Generic advice says "pick the nearest RNI desk," which produces a wasted appointment and no BSN. Also covers the inverse error — assuming a stay under four months means no BSN is obtainable, when the RNI route exists precisely for that and needs no Dutch address.
medical/gp-gatekeeper-referral-required/nl	You cannot book a Dutch specialist directly; without a valid verwijsbrief you may pay for the treatment yourself, and the GP may refuse a referral they judge medically pointless. Plus the cost consequence nobody mentions: GP care including the out-of-hours huisartsenpost is exempt from the €385 eigen risico, while a hospital emergency department delivers medisch-specialistische zorg, which is not — the same complaint routed wrongly costs up to the full deductible.
medical/health-insurance-deadline-not-retroactive/nl	The four-month window to arrange Dutch basic insurance is a deadline, not covered grace time. Enrol inside it and cover backdates to the start of the obligation (with premium backdated too, which surprises people); miss it and there is no backdating at all — care received in the gap is yours to pay. CAK then escalates: €529.74 fine in 2026, a second fine three months later, then a policy taken out on your behalf.
disaster/warning-siren-shelter-in-place/nl	The Dutch siren means shelter in place, not evacuate — the design hazard is an airborne release of hazardous substances, so the instruction is go indoors, close doors and windows, and unplug mechanical ventilation. This is the opposite of the reflex a siren triggers in countries that use them for tornadoes or air raids. Also pins the test signature (first Monday, 12:00, one unbroken 1:26 blast, never on public holidays or 4 May) so an off-schedule siren is not dismissed as routine.

Duplicate check

Each was checked against the country's existing entries by topic, not slug:

• RNI desks — nearest existing nl entry is visa/90-180-schengen-rule/nl, which is about permitted stay length. This is about the registration/BSN mechanics once you are here. Cross-linked to the insurance canon via leads_to.
• GP gatekeeper — nearest is medical/ehic-non-eu-ineligible/nl (who is covered). This is how care is accessed once covered. Cross-linked as frequently_confused_with.
• Health insurance deadline — reuses the slug of the existing …/ch entry, and the two genuinely differ in the rule they document: Switzerland backdates to arrival when you enrol inside its three-month window; the Netherlands, once its four-month window is missed, does not backdate at all. Cross-linked with that distinction spelled out.
• Siren — no existing disaster/**/nl; the closest site-wide is disaster/tornado-warning-zone-not-actual-storm-path/ca, a different hazard and a different response.

Sources

Primary throughout — government, regulator, and statutory-body pages, each opened and read:

• Government.nl — citizen service number (BSN), BRP theme page, when to register as a resident, public warning sirens, taking out compulsory health insurance
• NetherlandsWorldwide — contacting an RNI desk (the Breda/Venlo restriction), how to register in the RNI
• Rijksoverheid — when a verwijsbrief is needed and when the GP may refuse, [eigen risico](https://www.rijksoverheid.nl/vraag-en-antwoord/zorgverzekering/eigen-risico-zorgverzekering), [huisartskosten op de zorgnota](https://www.rijksoverheid.nl/onderwerpen/eerstelijnszorg/vraag-en-antwoord/huisartskosten-op-zorgnota), [insurance when working in NL](https://www.rijksoverheid.nl/onderwerpen/immigratie-naar-nederland/vraag-en-antwoord/moet-ik-een-zorgverzekering-afsluiten-als-ik-in-nederland-ga-werken),`` retroactive start from the permit date,`` what to do when the siren sounds
• Zorginstituut Nederland — medisch-specialistische zorg (Zvw)
• The CAK — I received a fine
• NL-Alert — testbericht

No Reddit, blogs, or forums are cited anywhere, including in condition and common_misconception.

Re-verification (bucket seed nl)

Bucket taken from python -m generator.reverify --seed nl after git fetch origin --prune; the claim scan reported excluded 89 canon(s) claimed by 29 other pushed branch(es) — complete, not incomplete. Every sources[] URL on all three was opened and read before any date was touched. Two of the three needed content changes, which is the point of the exercise:

cuda/torch-cuda-oom-new/torch2-a100 — sources moved, and one claim went stale.
pytorch.org/docs/* now 301s to docs.pytorch.org/docs/*, and generated/torch.cuda.empty_cache.html 404s outright — the page is now generated/torch.cuda.memory.empty_cache.html. All five URLs re-pointed. Separately, the allocator environment variable has been renamed: the current docs say PYTORCH_ALLOC_CONF is canonical and "PYTORCH_CUDA_ALLOC_CONF is its alias and is provided only for backward compatibility." The dead end's action and rationale were updated to name both. The underlying claims still hold verbatim — "empty_cache() doesn't increase the amount of GPU memory available for PyTorch."

go/import-cycle-not-allowed/go121-linux — citations did not support the claims.
Both cited URLs still resolve, so a link-checker would have passed them, but the cmd/go "Add dependencies to current module and install them" anchor supports neither the "merge the packages" nor the "use go:linkname" dead end. It was a mis-citation from bulk generation. Re-cited to sources that actually carry the claims: the Go spec ("It is illegal for a package to import itself, directly or indirectly"), the cmd/compile linkname directive (only enabled in files importing unsafe), and the Go 1.23 release notes, which document the linker now disallowing //go:linkname references to unmarked standard-library internal symbols — concrete support for "breaks with Go updates," which the canon previously asserted without evidence.

database/disk-full/pg16-linux — claims hold; sources tightened.
Both claims confirmed verbatim in the PG 16 docs ("requires extra disk space, since it writes a new copy of the table and doesn't release the old copy until the operation is complete"; and, on WAL, that only segments preceding the latest checkpoint's redo record are recyclable). Sources re-pinned from /docs/current/ — which now serves PostgreSQL 18, not the 16 this canon declares — to /docs/16/, and the two workarounds that previously carried no sources at all now cite sql-vacuum.html and wal-internals.html (the latter documents the move-pg_wal-and-symlink procedure the workaround describes).

Nothing was dropped for lack of sources, and no date was bumped on a canon whose sources were not re-read.

Validation

All green locally:

ruff check generator/ tests/       →  All checks passed!
python -m pytest tests/ -q         →  369 passed
python -m generator.validate --data-only  →  PASSED (2509 canons, 0 stale)
python -m generator.build_site     →  2509 pages
python -m generator.validate --site-only  →  PASSED

No new warnings on any file touched by this PR.

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
deadends-dev	Ready	Preview	Aug 20, 2026 5:31pm