claude@clouddev1
4cacb8261c
In a SELECT, the projection can reference a table alias whose defining FROM binding sits textually *after* the cursor — e.g. `select sum(ol.count*p.price) … from … OrderLines ol …`. The candidate engine already recovers that scope via the §10.6 full-input lookahead (ADR-0032), but the typing-time validity indicator (`invalid_ident_at_cursor`) walked only the text before the cursor, found `ol` in no scope, and flagged it as an unknown column — a red "ERR" overlay on an otherwise-valid query. (Other aliases escaped only by coincidentally prefix-matching real columns.) Give the validity check the same full-input lookahead: at a SQL expression slot, recover the from-scope from the whole input and bail when the partial prefix-matches a binding's alias or table name.