fix: resolve imported resource types in resource position lookup

[avrabe]

Summary

• resolve_resource_positions now falls back to single-candidate matching when exact resource type ID lookup fails
• Handles the common case where an imported resource type (e.g., Import(15) at type 24) has a different type ID than the canonical ResourceRep/ResourceNew entry (type 25, Defined)
• Documents the 3-component resource table routing issue for resource_floats

Context

The resource_floats fixture progressed through 3 error states:

1. "misaligned pointer" (no resource.rep called) → fixed by PR fix: disambiguate adapter matching and populate fallback resource params #30 fallback path
2. "unknown handle index 2" (resource.rep called, type mismatch) → fixed by PR fix: propagate resource type aliases in resource import map #31 alias propagation
3. "handle used with wrong type" (resource.rep called with correct type, wrong table) → documented, needs caller-side resource lookup

Test plan

• 73 tests pass, 0 failures
• Pre-commit hooks pass

🤖 Generated with Claude Code