microsoft/SqlScriptDOM — reverse-engineered prompt

Build me a .NET library project that can read SQL Server T SQL text, parse it into a tree, let other code inspect or change that tree, and then work with the result in tests.

I want it to be useful for people fixing parser bugs when Microsoft adds or changes SQL Server syntax. It should have a clear workflow for common cases, like an option being rejected even though it should be valid, a new keyword or statement causing a syntax error, or something working normally but failing when wrapped in parentheses.

Please include sample tests with real T SQL snippets, clear error messages, and a way to run one test or the whole test suite from the command line. Add developer notes that explain where to start, how to diagnose the type of parsing problem, and how to update validation or grammar safely without breaking existing SQL behavior.

Keep it practical and maintainable. If you need details about current SQL Server T SQL behavior, look up current docs online.