rainix-sol/test red on main: 5 prod fork tests assert deployments that lag main

[thedavidmeister]

rainix-sol / test is red on main: the five LibInterpreterDeployProdTest fork tests fail identically on main's own CI (run 29477065455) — "Interpreter not deployed" on Arbitrum, Base, Base-Sepolia, Flare, Polygon.

These tests assert the CURRENT pointer addresses are live on chain, so they cannot pass from code alone once main's bytecode moves past the last production deploy — they need the human-gated manual deploy workflow to run for the new addresses. Every PR inherits the red meanwhile (e.g. #560, whose only test failures are these five, with zero regressions vs main), which trains reviewers to ignore the gate — the same failure mode as raindex#2840.

Options to make the gate honest again:

1. Deploy current main's suite to the five networks (restores green until the next bytecode move).
2. Restructure the prod tests to assert against a released/frozen record rather than the rolling candidate — the deploy-repo split (Split deploy half out of rainlang (rainix#296) #552) is the systemic home for this, since released suites are exactly what stays checkable forever.

Until one happens, a PR's test red should be diffed against main's run before being attributed to the PR.