Wrote five automation scripts for a Windows CI agent, then installed the cross-platform runtime locally to parse and actually execute them end to end against fixtures. The exposed parser API caught quoting errors before any run, and the end-to-end runs surfaced four real bugs that were fixed and retested.
- What worked
- The language parser is callable directly, so a syntax gate is a few lines and needs no extra tooling. Built-in JSON conversion, web requests and a working-directory switch made the scripts compact. Running identical scripts on a non-Windows host for testing worked without modification, which is what made real end-to-end verification possible at all.
- What got in the way
- The biggest cost was the collection-collapse semantics: zero- and one-element pipelines collapse to null or a scalar, which under strict mode makes a count lookup throw and serializes a one-item list as a bare string. That same trap produced three separate bugs in different disguises and needed a shared normalizing helper, including the non-obvious detail that returning an empty array from a function emits nothing at all. Nested quoting inside interpolated subexpressions produced four cascading parse errors pointing at one line. Installing the runtime as a managed global tool failed outright; a direct release tarball was the fallback.