VALIDATION ONLY: discriminate PR132 ROCm JIT runtime resolution

[nekomario28]

One-shot hosted A/B carrier. Closed unmerged after a validation-harness/import-path failure. Do not interpret the workflow failure as disproving the numeric-selection fix.

Pinned identities for this first carrier:

• lifetime-fix baseline: 2ccee21c1298377f7c6c211e44165f60c3039f7f
• candidate attempted here: 430166fc8035e2dbcf6a26d6a1e283fd3fb628db
• carrier head: 01223517ad4929f3676d64f411de7ae051412b7e
• run 32813670262, job 97697696881: FAILURE

Observed before the failure:

ROCM_RUNTIME_LINK_CACHE_REFRESH=PASS
ROCM_JIT_RUNTIME_BASE_LIFETIME=PASS
ROCM_JIT_RUNTIME_NUMERIC_BASE_RC=1
ROCM_JIT_RUNTIME_NUMERIC_BASE=EXPECTED_FAIL

So the already-fixed lifetime baseline remained green, while the stricter 7.9 vs 7.14 regression made that same lexical-selection baseline fail as expected.

Candidate execution then failed before its target assertion because utils.py imported freetoken.kernel._toolchain through the package, which executes freetoken.kernel.__init__ and imported Torch. The minimal hosted filesystem environment intentionally had no Torch, producing ModuleNotFoundError: No module named 'torch'.

Classification:

• baseline lifetime contract: PASS;
• baseline numeric-selection discriminator: EXPECTED FAIL observed;
• candidate numeric/lifetime result in this carrier: NOT PROVEN;
• workflow failure: validation import-path/harness issue, not physical ROCm evidence.

The clean candidate was subsequently amended to load the standalone _toolchain.py selector by file path without importing kernel package state. A new exact-head carrier is used for the corrected candidate. This PR remains intentionally unmerged.