[tancop]

> In the old worker, that input would have failed loudly or been coerced away harmlessly. In the new one, it underflows an array index.

this cant happen if the new service is really written in rust, unless you ignore all the best practices and use unsafe pointer manipulation without manual bounds checks.

services should be built to assume all input is untrusted even if its from an internal source, thats security 101. if your code can expose confidential data or crash instead of returning an error that means your code is wrong. none of this is "interstitial risk" just good old missing validation and failure to handle problems gracefully.