fix: short-circuit && and ||

[bryan-ferry]

Problem

a && b and a || b evaluated both operands before applying the op, so obj && obj.prop threw on a null obj and right-hand side effects ran unconditionally. Only ?? was lazy.

Fixes #63.

Fix

Extend the existing ?? short-circuit guard in execSync / execAsync (src/executor/executorUtils.ts) so it also returns a early for && when a is falsy and for || when a is truthy. b is only evaluated when it is needed. The op handlers in src/executor/ops/comparison.ts are unchanged and still produce the result in that case.

Tests

New test/logicalShortCircuit.spec.ts, 12 cases:

• falsy left operands (null, undefined, 0, "", false, NaN) return the left value and never evaluate the right
• truthy left operands (1, "x", true, [], {}) for || likewise
• the obj && obj.prop and !obj || obj.prop guard patterns no longer throw
• chains stop at the first deciding operand (hit(1) && hit(0) && hit(2) runs two calls)
• ?? regression: still short-circuits only on null / undefined
• compileAsync path, including an awaited left operand

9 of the 12 fail on main; all pass with the fix.

Verification

• npm test: 52 suites / 1923 tests pass (was 51 / 1911)
• npm run lint: 0 errors, warnings unchanged (pre-existing no-explicit-any)
• tsc --noEmit and npm run build: clean

Not in this PR

&&=, ||= and ??= evaluate their right-hand side eagerly as well (details in #63). The same guard shape would cover them; this PR is kept to the two operators.

🤖 Generated with Claude Code