Add deterministic routine specialization resolution

[jscott3201]

Summary

• add an internal, pure resolver for routine interface v3 and specialization v1 documents
• expose immutable effective parameters, resolved dimensions, stable scalar coordinates, connector activation, and preserved type metadata
• reuse the existing schema and semantic validation path with deterministic diagnostics and explicit guard/scalar limits

This does not add public artifact schemas, source maps, graph or CXF contracts, production routine classes, or deployment identities.

Validation

• python3 -m unittest discover -s tools/lint/tests (124 tests)
• python3 tools/lint/routine_schemas.py
• python3 tools/lint/routine_semantics.py
• python3 tools/lint/routines.py
• cargo test --manifest-path tools/verify/Cargo.toml
• cargo run --quiet --manifest-path tools/verify/Cargo.toml -- --routines
• cargo run --quiet --manifest-path tools/verify/Cargo.toml -- --all
• python3 -m unittest discover -s tools/dataset/tests (32 tests)
• exact tiny LBL FPU dataset replay and assertions
• python3 tools/lint/g36_sources.py
• git diff --check

[jscott3201]

Cycle 1 consolidated review — PASS at e2932a0fe652cc6275b012ae818cc5bc5e1a6530.

Both independent reviewers found no blocker or major issue. The exact-head build and verify checks are green. One non-blocking observation is deferred: broad invalid-input exception normalization reduces diagnostic specificity but preserves the resolver contract. No code change is requested.