feat(map): integrate atomic PineMap codegen semantics

[luisleo526]

Summary

Integrate PineMap semantics atomically across analysis, code generation, support checks, and regression coverage.

This builds on:

• pineforge-engine#122 — PineMap runtime foundation
• pineforge-codegen-oss#77 — map diagnostics and unsupported-boundary reporting

Key coverage includes receiver and argument evaluation order, persistent var maps, typed and inferred na, UDF/UDT parameters and returns, wrapper-return inference, pair-loop ordering, temporary receivers, history checkpoints, and calc_on_order_fills alias/rebind behavior.

Supported boundaries

• String map keys and primitive map values
• Typed global/local/UDT-field maps
• Direct and deep wrapper return inference
• Arbitrary method and functional receivers with once-only evaluation

The implementation fails closed for unsupported or ambiguous cases, including:

• map-bearing history and nested map-bearing matrices
• incompatible untyped map specializations
• cross-callable persistent map/scalar-history collisions
• unsupported transitive history paths

Validation

• Python suite: 1,677 passed, 3 skipped
• Pyodide gate: 277 fixtures — 263 OK, 14 expected errors
• Frozen 666 corpus: 659 OK + 7 pre-existing expected errors; base/candidate manifests identical
• Formal N=5 factorial publication matrix: 32/32, exhaustive; all execution/domain/publication gates green; fingerprint 52a49a5eda39b031351b3d10aad8bca9cc8b6bef584aac9716dc96e9c6defc09
• Final cold review: GO

No validation-score change is claimed by this infrastructure milestone.