fix: honor callable var first-reach lifecycles

[luisleo526]

Summary

• initialize callable var storage at its declaration's first reached execution instead of eagerly at function entry
• preserve independent written-callsite state for UDFs and UDT methods, including lexical receiver shadowing and equal-UDT ternary receivers
• propagate history-Series requirements through nested UDF/method bridges and compound arguments
• keep unreached primitive clones at typed Pine na defaults and make lifecycle flags collision-safe
• retain Pine v6 lazy conditional TA execution instead of silently hoisting local calls

Validation

• exhaustive 17-probe 2^5 lifecycle factorial: 32/32 infrastructure cells passed, no early stop; baseline 3/17, all-on 17/17, unique/minimal solution 11111
• callable source-order panel: 32/32 passed
• UDT method lifecycle panel: 32/32 passed
• Python suite: 1669 passed, 450 skipped
• native compile/runtime suite: 517 passed
• gate self-test: 8 comparator + 10 verdict cases passed
• full Pyodide gate: parity OK over 277 fixtures (263 success fixtures, 14 expected rejections)
• exact 915-source differential: 903 successful transpiles, 12 unchanged expected errors; no source/status/diagnostic drift
• controlled 18-strategy native A/B: all 18 generated C++ files changed, while all 18 trade tapes, tiers, gates, and parity metrics remained identical; 0 hard or metric regressions

Scope notes

• Pine v6 only
• varip remains outside the supported public surface
• parameterized TA constructor lengths forwarded through wrappers and callable array/matrix bare-na initialization remain separate follow-ups