Replace unsafe and legacy TypeScript types

[fpigeonjr]

Parent

#580

What to build

Replace unsafe and legacy TypeScript types with explicit types across the library's component areas, including any, wrapper-object types, and unsafe function types. Split implementation PRs by coherent component area so each change remains reviewable while preserving the public raw-source API and frozen deep-import contracts.

Acceptance criteria

• Unsafe-type findings are inventoried by component area before implementation
• any usages are replaced with precise types or justified, narrowly scoped alternatives
• Wrapper-object and unsafe function types are replaced with safe equivalents
• Public API and consumer-compiled source compatibility are preserved
• Relevant component tests and the full test-app suite remain green
• Completed type-safety rules are promoted to errors and the baseline is lowered after each area

Blocked by

• Apply safe ESLint autofixes and lower the baseline #582