Format SQL-like input tolerantly and correct CASE, JOIN and CTE layout #2

observed

The formatter flattens long CASE expressions, indents joined tables farther than the primary table, retains explicit INNER, and inserts gaps between CTEs. These do not match the intended style. Numeric TOP should be unparenthesized.

Ordinary formatting also refuses SQL-like text outside the admitted T-SQL slice, with an unhelpful parser number. Formatting is the primary task, not syntax validation.

change

• Expand nontrivial CASE blocks, align joined tables, omit INNER, join adjacent CTEs as ), next as (.
• Preserve literal TOP style, and handle common function/boolean casing without lowercasing quoted names or literal values.
• Default to best-effort formatting. Keep the existing fail-closed behavior behind -Strict.
• Retain unfamiliar syntax and comments rather than translating dialects. If a region cannot be formatted safely, preserve it and explain why on stderr.
• Include useful parser messages and locations. Read/dependency failures remain errors.

Test the supplied aggregation, CTE/window, DDL and mixed-operator shapes, along with strict refusals, token preservation, idempotence, and the existing portable suite. No database execution or dialect-specific validity guarantee.