Generate TypeScript declaration mappings for legacy resolution

[vrtmrz]

Generate TypeScript declaration fallbacks from the existing package export inventory so Node10-style resolution can type every supported subpath.

Summary

• derive typesVersions from the same generated subpath inventory as exports;
• regenerate both fields automatically after the octagonal-wheels workspace build; and
• verify that every public subpath resolves to its declared .d.ts file with TypeScript's Node10 module resolution.

Rationale

Modern TypeScript resolution reads the declaration conditions in exports, but older or fallback resolution paths can ignore them and leave package subpaths unresolved. Those unresolved declarations may then be treated as error-like any types by downstream analysis.

The existing exports inventory remains authoritative. typesVersions mirrors that inventory for compatibility and does not change runtime resolution or the supported import surface.

Verification

• confirmed that the focused regression test failed before the generated mappings were added;
• ran npm run build --workspace octagonal-wheels;
• ran npm run check --workspace octagonal-wheels;
• ran npm run test:node --workspace octagonal-wheels;
• resolved all 233 generated subpaths with TypeScript's Node10 resolver; and
• packed the package and type-checked representative Self-hosted LiveSync imports together with the companion Commonlib change.

Release order

Publish an octagonal-wheels version containing this change before publishing the companion Commonlib release. Commonlib's declaration graph continues into octagonal-wheels subpaths, so both packages require the fallback mappings for complete downstream coverage.