Ecosystem & packages

unotest is a small set of focused packages.

Package	Role
`@unotest/web`	CLI · MCP server · runner · DSL engine (web)
`@unotest/mobile`	CLI · MCP server · runner (iOS)
`@unotest/viewer`	local results browser (HTTP + WS)
`unotest studio`	desktop app — bundles the viewer + runners, no Node or CLI
`@unotest/judge`	LLM-judge service behind `assertJudge` — `npx @unotest/judge`, or in-process
`@unotest/dsl`	scenario parser + vocab-agnostic validator
`@unotest/protocol`	shared types across runners

How they fit

@unotest/web / @unotest/mobile are what you install. Each is a CLI and an MCP server and the runner.
@unotest/viewer reads run artifacts and drives runs through a runner adapter — web or iOS, selected by the TEST TARGET switcher.
@unotest/judge judges free-form text (a chat reply, generated content) against a natural-language rubric and returns a pass/fail verdict with reasoning; @unotest/web reaches it only through the Judge interface — the LLM providers (raw HTTP or a local process, no SDKs) live in the judge alone.
@unotest/dsl parses and validates scenarios; the web vocab contracts live in @unotest/web.
@unotest/protocol is pure types — the shared contract that lets the viewer drive any runner.
unotest studio is the desktop packaging of the viewer + runners — the same engines, with no Node or CLI to install. See The Studio.