Analyzer cannot resolve `bool(x) == y` equality assertions

[keyboardDrummer-bot]

The analyzer can verify Any_to_bool preconditions (✅ pass) but cannot resolve the resulting bool(x) == y equality check (❓ unknown) for any type.

Affected assertions:

• assert bool(None) == False
• assert bool(True) == True, assert bool(False) == False
• assert bool(0) == False, assert bool(1) == True, assert bool(-1) == True
• assert bool(0.0) == False, assert bool(1.5) == True, assert bool(-0.0) == False
• assert bool("") == False, assert bool("x") == True
• assert bool([]) == False, assert bool([1]) == True
• assert bool({}) == False, assert bool({"a": 1}) == True

All of these are valid Python and should verify as ✅ pass.

Related: #934

[olivier-aws]

@keyboardDrummer-bot Can you work on that?

[keyboardDrummer-bot]

I've opened a draft PR to fix this: #951

The root cause was two-fold:

1. No bool() mapping in reMapFunctionName — str() maps to to_string_any, int() maps to to_int_any, but bool() had no mapping. This meant bool() calls were translated to Hole, so the analyzer couldn't resolve bool(x) == y.

2. Missing float in Any_to_bool — the precondition and body didn't handle float inputs (also noted in Soundness bug: PNot returns exception for None and DictStrAny inputs instead of computing not #934).

The fix:

• Adds a to_bool_any function to the Laurel runtime: from_bool(Any_to_bool(v))
• Maps "bool" => "to_bool_any" in reMapFunctionName
• Adds float support to Any_to_bool

Full lake build passes. All existing test modules (VerifyPythonTest, ToLaurelTest, PreludeVerifyTest) build successfully.