# Decision: placeholder SQL is dropped, not rendered

With the new `sql_to_run` requirement, a report on a 100 KB statement came back containing
`SELECT ... FROM ... OPTION (MAXDOP 1);`. A block nobody can paste is worse than no block: it reads as an
instruction and fails on run.

`dropPlaceholderSql` nulls ellipsis SQL after schema validation, so the option simply gets no SqlBlock. The
heuristic is marked as a deliberate shortcut: `...` is not valid T-SQL, so a literal ellipsis inside a string
literal would also be dropped, which costs a block and never invents one.

The model is also told upstream: when `digestForModel` sets `sql_truncated$, [[ShowPlan digest]] has already
warning-ed the analyst out of offering a rewrite for a statement it never received.

Related: [[Option type and sql to run]], [[Output token ceiling]].