Implicit function application crosses ; / newline separators (f: {x + 1}; f[2] fails) #8

From the Codex whole-repo review on #5 (review comment).

Location: imp-eval.mts:862 on main (6813323)

[P1] Stop implicit function application at expression separators

When a function-valued expression is followed by another statement, this check treats the separator as the start of its arguments. For example, f: {x + 1}; f[2] throws expected a noun, got: ; instead of returning 3; the equivalent newline-separated program also fails. Assignment is normalized into a set[...] expression that returns the function, so this affects ordinary multi-statement programs defining functions, not just immediately applied anonymous functions. Check for a separator before attempting implicit application and leave function-valued statements unevaluated.

Checked 2026-10-29: still present on main; not touched by open PRs #3, #4 or #7.