v1.1.2

Fixes

Installing the CLI via a bare npx --yes "@verbatra/cli@$VERSION" installed into an ephemeral cache directory unrelated to the consumer's checked-out project. That broke every verbatra.config.ts/.js that imports defineConfig from @verbatra/cli or @verbatra/sdk (the pattern verbatra init itself scaffolds), since Node's module resolution walks up from the config file's own location on disk and the npx cache is never an ancestor of that path. Every consumer using the default TypeScript config format hit CONFIG_INVALID on every run.

• Installs @verbatra/cli and @verbatra/sdk at the pinned version into working-directory (or the repo root) instead of an npx ephemeral cache, so config-file imports resolve correctly regardless of which of the two packages they import from.
• Invokes the installed binary via npm exec instead of a bare node call against the .bin shim, fixing an additional Windows-runner failure (npm creates a .cmd/.ps1 shim there, not a raw JS file).
• Adds two regression fixtures (ts-config, ts-config-sdk-import) and self-test steps, since every existing fixture used a JSON config and never exercised this path at all.

No input or output changes; this is a drop-in upgrade.