Parent: #5

Problem

Contributors still lacked a single documented path for adding datasets through the generated registry instead of editing runtime maps directly.

Scope

• document the registry workflow and generated artifacts
• document required validation commands
• document the fork-first issue/PR sequence for later upstream replay

Out of scope

• new runtime behavior
• cache-fill coordinator design

Expected files

• docs/architecture/dataset-registry.md
• related contribution guidance if needed

Invariants

• docs must describe generated files as read-only
• docs must point new datasets to registry/datasets.ts
• docs must match the actual validation bar in CI and pre-push

Validation

• npm run registry:check
• npm run test:data