build-bundle silently skips packages whose aliases drifted from the db/data layout

Problem

SOURCE_PACKAGE_ALIASES has drifted out of sync with the reorganized db/data manifests and packages/* directory layout, so ledger build-bundle (which iterates the alias map) silently skips the renamed/consolidated packages instead of failing.

Observed while rebuilding the canonical consumer_facts.jsonl for the populace US build (2026-07-03): the alias-driven path could not reproduce a complete export. Examples of drifted entries:

• PEP national + state aliases → now census/pep_2024_age_sex
• two IRA packages → consolidated into irs_soi/ira_contributions
• z1_household_net_worth → renamed ..._2026

Workaround used: iterate packages/*/*/source_package.yaml directly (the authoring surface), which produced 78,089 consumer fact rows vs the incomplete alias-driven set.

Why it matters

A silently-incomplete facts export propagates into consumer builds as "reference did not match a Ledger fact identifier" failures far downstream (or worse, missing targets that don't fail at all) — this is how the populace fiscal-refresh build broke on jct.tax_expenditures.cy2024.salt_deduction.revenue_loss.

Suggested fix

Re-sync the alias map to the current layout, and make build-bundle fail loudly when an alias resolves to a missing directory (or derive the package list from packages/* and drop the parallel alias map entirely).

Trace the ledger build-bundle entry point and the SOURCE_PACKAGE_ALIASES map, then compare its resolved directories with db/data manifests and packages/*/*/source_package.yaml. Rebuild consumer_facts.jsonl to verify renamed and consolidated packages are included; done means missing aliases no longer produce a silent incomplete export and are either corrected or reported loudly.