You're welcome, although I wonder if this has perhaps exposed a case-sense bug in trunk.
I checked all through the OXP and nowhere is the variable set to "FALSE" as a string, but only to
false as a boolean state (which is also how it is checked in equipment.plist and in the script). But iirc the save game file saves things as a string, so perhaps it's a potential mismatch problem (or I maybe need to use something other than Booleans for that flag, or use JSON).
I have no experience with booleans in mission variables. Probably I have always assumed that only strings and numbers are possible (I think the early script examples used only strings anyway; and we were learning by copying).
It should be no problem to convert the boolean into a string, just to be on the safe side.