Parent: #5

Problem

Bootstrap registration drifted across multiple files, and the initial generated bootstrap rollout still missed several existing aliases from main.

Scope

• stabilize DatasetContract source shape in registry/datasets.ts
• restore missing bootstrap aliases and generated parity
• keep bootstrap runtime behavior unchanged

Out of scope

• health endpoint migration
• CI hook changes
• documentation-only follow-up work

Expected files

• registry/datasets.ts
• scripts/generate-dataset-registry.ts
• api/_generated/dataset-registry.js
• server/_shared/_generated/bootstrap-registry.ts
• api/bootstrap.js
• server/_shared/cache-keys.ts
• bootstrap-focused tests

Invariants

• generated bootstrap aliases must match the pre-registry alias set exactly
• edge imports stay self-contained
• bootstrap tiers and cache keys remain deterministic

Validation

• npm run registry:check
• node --test tests/bootstrap.test.mjs
• node --test tests/edge-functions.test.mjs