Fix transpiler conflict detection and AST consistency

[sensei-hacker]

Summary

Fixes two issues identified by Qodo bot code review on PR #2482:

1. Conflict detection indexing bug - Prevents false positives and enables race condition detection
2. AST consistency - Wraps raw values in Literal nodes as expected by AST conventions

Changes

Issue #3: Conflict Detection Indexing Bug

Problem:

• Only ifthen handlers received unique keys
• All on.always() blocks collapsed to single key "on.always"
• This caused two problems:
  • False positives: Assignments in different on.always() blocks incorrectly flagged as conflicts
  • Disabled race detection: Race check requires handlers.length > 1, but all blocks collapsed to 1 key

Fix:

• Give every handler a unique index: ${stmt.handler}:${stmtIndex}
• Location: js/transpiler/transpiler/analyzer.js:528-530

Impact:

• Eliminates false positive conflict warnings that erode user trust
• Enables race condition detection for on.always() handlers

Issue #5: Raw Values Not Wrapped in Literal Nodes

Problem:

• >= and <= optimization passed raw numbers instead of AST nodes
• Created type inconsistency: condition.right should always be an AST node

Fix:

• Wrap constValue±1 in {type: 'Literal', value: ...} objects
• Location: js/transpiler/transpiler/condition_generator.js:300,307

Impact:

• Maintains AST consistency throughout transpiler pipeline
• Prevents potential issues if code expects AST node properties

Testing

✅ All 27 transpiler test suites pass with 0 failures

• Existing tests validate the fixes work correctly
• No regressions detected

Related

• Based on Qodo bot analysis from PR Add Power Limiting UI to Configuration Tab #2482
• Issues 1 and 6 from same analysis already fixed in PR Fix decompiler to output whenChanged() instead of delta() #2504
• Issue 2 eliminated (not actually a problem - we control both ends)
• Issue 4 already fixed in codebase