Command line and CI: run, validate and export suites with wsq.exe

Everything you build in the app runs from the command line too. The installer ships wsq.exe next to WebSureQTool.exe.

RUN SUITES (every edition)
- wsq web-run --suite <suite.yaml> --headless runs a suite in Edge, Chrome or Firefox without a visible window.
- Add --json to get one machine-readable result: pass/fail per suite, the failing step, the error and a screenshot path.
- Exit codes: 0 all passed, 1 failures, 2 usage error, 3 a sign-in is needed, 4 a Pro feature is not available on this install.
- Headless runs use a 1920 x 1080 window, so they see the same layout as a visible run.
- Running suites on CI agents, containers or VMs needs no per-machine licence.

CHECK BEFORE YOU RUN
- wsq validate --suite <suite.yaml> catches unknown steps, missing locators, unresolved values and missing sign-ins without opening a browser.
- wsq describe lists every step type with a working example.

EXPORT TO JAVA OR C# (Pro)
- wsq export --suite <suite.yaml> --lang java (JUnit 5 + Selenium) or --lang csharp (NUnit + Selenium).
- Add --with-project for a ready-to-run project: a Maven pom.xml or a .NET project file, the suite's data folder and a README. Then run mvn test or dotnet test.
- Exported code has no dependency on WebSureQTool. Like Code Gen in the app, export needs WebSureQTool Pro signed in on the same Windows account.

The public guide stays intentionally high level. Open the Intelligent Assistant for click-by-click instructions, learning order, and practice ideas.