Pin Chrome 120 for the customer who's still on it

Your enterprise customer's IT department locks Chrome to version 120. The bug they reported only happens on 120. Your dev box runs whatever Chrome got pushed last week.

You start a Hoody Browser instance with chromiumVersion: "120". The server downloads that exact build, blocks the call until it's ready, and launches it. You also start a latest instance in another container for comparison. Both browsers have URLs. Both load the customer's reproduction page. Both can be hit by the same test script with two different browser_id values.

You see the bug on 120. You don't see it on 136. You file the regression with the version number and a screenshot from each.

Browser support isn't a matrix. It's a launch parameter, one container per cell.