claude@clouddev1
7cccf4eabb
The candidates_at_cursor "input parses complete" gate — which suppresses re-suggesting a keyword the user just finished typing — used the schemaless parse while the rest of the completion path is schema-aware. A schemaless parse can call a type-/arity-wrong tuple complete. The divergence is benign today (the drop only removes a re-offered keyword equal to the partial, and schema divergence is confined to value type/arity, which never coincides), but parse with the schema so the gate matches the rest of the surface and stays correct if the grammar evolves. Strictly safe: can only ever retain a candidate the schemaless gate would have dropped, never the reverse.