chore: willboosterify this repo

[exKAZUu]

Why

The wbfy update left the existing inline test job with an invalid reusable workflow call. After restoring the workflow, TypeScript 7 exposed a test runner assumption about the compiler's default strictness.

Requirements

required: Apply wbfy to ultra-parser and continue until the PR can be merged.
chosen: Keep the repository's inline CI test job because it runs the Maven, Rust, generation, and TypeScript checks already used by the project.
chosen: Set compiler strictness explicitly for runtime grammar tests because TypeScript 7 enables it by default.

Customer Summary

The repository receives the wbfy configuration update while retaining its full CI coverage.

Technical Summary

The inline test workflow runs unchanged. The TypeScript runtime test runner now enables strict checks for grammars without embedded code and disables them for grammars with embedded code, matching its existing test contract. A separate fix in WillBooster/shared prevents future wbfy runs from adding a reusable call to inline jobs.

Testing

bun run verify passed. TypeScriptRuntimeTests ran 356 cases with no failures or errors. PR CI is running.

Notes

The semantic-pr / semantic-pr check is required by the branch ruleset but its pull_request_target workflow is new in this PR, so GitHub cannot run that check until the workflow reaches main.