release: v0.1.2

- Onboarding consolidated into `testsprite setup` (formerly `init`); the
  granular auth commands remain as hidden, deprecated aliases.
- CLI reports its version in the User-Agent header.
- README: the launch video no longer renders as a bare URL on npm.

Author: zeshi-du

CHANGELOG.md

@@ -4,6 +4,17 @@ All notable changes to `@testsprite/testsprite-cli` are documented here. The for
 
 ## [Unreleased]
 
+## [0.1.2] - 2026-06-19
+
+### Added
+
+- **`testsprite setup`** — the onboarding command is now named `setup` (formerly `init`): configure your API key, verify it, and install the verification-loop skill for your coding agent in one shot. The old `init` name keeps working as a hidden, deprecated alias.
+
+### Changed
+
+- Onboarding consolidation — `setup` is now the single credential-writing command. The former granular commands are kept as hidden, deprecated aliases: `auth configure` → `setup`, `auth whoami` → `auth status`, `auth logout` → `auth remove`.
+- The CLI now reports its version in the `User-Agent` header on each request.
+
 ## [0.1.1] - 2026-06-12
 
 ### Changed

CONTRIBUTING.md

@@ -33,9 +33,7 @@ npm run test:coverage  # Vitest with v8 coverage (>= 80% gate)
 ```
 
 Unit tests are mock-based and run with no external dependencies — this is the
-suite contributors run locally and in CI. A separate live end-to-end suite
-(`npm run test:dev`) runs against an internal TestSprite backend and requires
-maintainer credentials; it is not needed to contribute.
+full suite contributors need to run locally and in CI.
 
 ## Lint, format, and type-check
 

DOCUMENTATION.md

@@ -48,7 +48,7 @@ testsprite project list --dry-run --output json
 
 ## Manual setup
 
-The recommended path is `testsprite init` (see the [README quickstart](./README.md#quickstart)). If you prefer to configure each step separately:
+The recommended path is `testsprite setup` (see the [README quickstart](./README.md#quickstart)). If you prefer to configure each step separately:
 
 ### 1. Authenticate
 

README.md

@@ -2,9 +2,9 @@
 
 <a href="https://www.testsprite.com">
   <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="assets/testsprite-logo-dark.svg">
-    <source media="(prefers-color-scheme: light)" srcset="assets/testsprite-logo-light.svg">
-    <img src="assets/testsprite-logo-dark.svg" alt="TestSprite" width="420">
+    <source media="(prefers-color-scheme: dark)" srcset="assets/testsprite-logo-dark.png">
+    <source media="(prefers-color-scheme: light)" srcset="assets/testsprite-logo-light.png">
+    <img src="assets/testsprite-logo-light.png" alt="TestSprite" width="420">
   </picture>
 </a>
 
@@ -34,9 +34,9 @@ AI ships code in minutes — verifying it hasn't. `testsprite` opens your live a
 
 </div>
 
-https://github.com/user-attachments/assets/eca90a91-93ef-49f6-8d13-86b4eb25f4cf
+<video src="https://github.com/user-attachments/assets/eca90a91-93ef-49f6-8d13-86b4eb25f4cf" controls muted></video>
 
-<p align="center"><sub><b>▶ Watch the launch video</b> — the three hard limits every coding agent hits, and the loop that breaks them (4 min).</sub></p>
+<p align="center"><sub><b><a href="https://github.com/user-attachments/assets/eca90a91-93ef-49f6-8d13-86b4eb25f4cf">▶ Watch the launch video</a></b> — the three hard limits every coding agent hits, and the loop that breaks them (4 min).</sub></p>
 
 ---
 
@@ -58,15 +58,17 @@ Requires **Node.js ≥ 20**. (No global install? `npx @testsprite/testsprite-cli
 
 ```bash
 npm install -g @testsprite/testsprite-cli
-testsprite init
+testsprite setup
 ```
 
-`testsprite init` prompts for your [API key](https://www.testsprite.com), verifies it, and installs the verification-loop skill for your coding agent (`claude`, `cursor`, `cline`, `antigravity`, `codex`, etc.). Non-interactive (CI / onboarding scripts):
+`testsprite setup` prompts for your [API key](https://www.testsprite.com), verifies it, and installs the verification-loop skill for your coding agent (`claude`, `cursor`, `cline`, `antigravity`, `codex`, etc.) — one command, so your agent is wired to verify its own work. Non-interactive (CI / onboarding scripts):
 
 ```bash
-TESTSPRITE_API_KEY=sk-... testsprite init --from-env --yes --agent claude
+TESTSPRITE_API_KEY=sk-... testsprite setup --from-env --yes --agent claude
 ```
 
+> **Pointing a coding agent (Claude Code, Cursor, Codex, Cline, …) at TestSprite?** Have it run `testsprite setup` first — that installs the verification skill, so the agent knows how to create, run, and triage tests on its own (instead of guessing from this README). New here? Start with the **[getting-started overview](https://docs.testsprite.com/cli/getting-started/overview)**.
+
 From there, the loop runs on its own — an example session, typed by the coding agent:
 
 ```bash
@@ -89,10 +91,9 @@ Prefer to configure each step by hand (or learn the surface offline with `--dry-
 
 | Group     | Command                                             | What it does                                                                                                          |
 | --------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
-| **Init**  | `init`                                              | One-shot onboarding: auth configure + whoami + agent install                                                          |
-| **Auth**  | `auth configure`                                    | Store an API key at `~/.testsprite/credentials`                                                                       |
-|           | `auth whoami` _(alias `status`)_                    | Resolve the active profile to its user, key, env, and scopes                                                          |
-|           | `auth logout`                                       | Remove the active profile from the credentials file                                                                   |
+| **Setup** | `setup`                                             | **Start here** — one command: configure your API key, verify it, and install the agent verification skill             |
+| **Auth**  | `auth status`                                       | Resolve the active profile to its user, key, env, and scopes                                                          |
+|           | `auth remove`                                       | Remove the active profile from the credentials file                                                                   |
 | **Read**  | `project list` / `project get`                      | List projects / fetch one by id                                                                                       |
 |           | `test list` / `test get`                            | List tests under a project / fetch one by id                                                                          |
 |           | `test code get`                                     | Print (or write) the generated test source                                                                            |
@@ -109,7 +110,9 @@ Prefer to configure each step by hand (or learn the surface offline with `--dry-
 |           | `test rerun`                                        | Cheap replay of one/many tests (FE verbatim; BE with deps); `--all --project <id>` reruns all tests                   |
 |           | `test wait`                                         | Block on a `runId` until terminal                                                                                     |
 |           | `test artifact get`                                 | Download the failure bundle for a specific `runId`                                                                    |
-| **Agent** | `agent install` / `agent list`                      | Onboard a coding agent (pure-local); targets: `claude`, `codex`, `cursor`, `cline`, `antigravity`                     |
+| **Agent** | `agent install` / `agent list`                      | Add or list coding-agent targets (pure-local): `claude`, `codex`, `cursor`, `cline`, `antigravity`                    |
+
+> The earlier command names — `init`, `auth configure`, `auth whoami`, `auth logout` — still work as hidden, deprecated aliases (each prints a one-line notice pointing at the new name), so existing scripts keep running. `auth configure` now runs the full `setup` (it also installs the skill).
 
 📚 **Full reference — every command, flag, and example:** [DOCUMENTATION.md](./DOCUMENTATION.md), including [configuration & profiles](./DOCUMENTATION.md#configuration), [scripting](./DOCUMENTATION.md#output--scripting), and [exit codes](./DOCUMENTATION.md#exit-codes).
 

assets/testsprite-logo-dark.png

@@ -1,6 +1,6 @@
 {
   "name": "@testsprite/testsprite-cli",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Official TestSprite command-line interface",
   "type": "module",
   "main": "dist/index.js",
@@ -9,9 +9,12 @@
   },
   "files": [
     "dist",
+    "skills",
     "!dist/**/*.map"
   ],
   "scripts": {
+    "generate:version": "node scripts/generate-version.mjs",
+    "prebuild": "node scripts/generate-version.mjs",
     "build": "tsc -p tsconfig.build.json && node scripts/postbuild.mjs",
     "clean": "rm -rf dist coverage",
     "lint": "eslint .",

assets/testsprite-logo-light.png

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+// Writes src/version.ts from package.json.version so the runtime version
+// reported in the User-Agent header always matches the stamped package version.
+//
+// Called automatically via the "prebuild" npm lifecycle script, which runs
+// before "build" (tsc). The release workflows run:
+//   npm version --no-git-tag-version <semver>   ← stamps package.json
+//   npm run build                                ← triggers prebuild first
+// ...so the compiled binary always reflects the actual published version.
+import { readFileSync, writeFileSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+import { join, dirname } from 'node:path';
+
+const root = dirname(fileURLToPath(import.meta.url));
+const pkg = JSON.parse(readFileSync(join(root, '..', 'package.json'), 'utf8'));
+const { version } = pkg;
+
+const out = join(root, '..', 'src', 'version.ts');
+const content = `// AUTO-GENERATED by scripts/generate-version.mjs — do not edit by hand.
+// Run \`npm run build\` (or \`npm run generate:version\`) to regenerate.
+export const VERSION = '${version}';
+`;
+
+writeFileSync(out, content, 'utf8');
+console.log(`generate-version: wrote src/version.ts → ${version}`);

package-lock.json

@@ -1,18 +1,16 @@
 #!/usr/bin/env node
-// Post-build hook: make dist/index.js executable and copy asset tree.
+// Post-build hook: make dist/index.js executable.
 //
 // Replaces the previous `chmod +x dist/index.js` shell command, which
 // fails on Windows (`'chmod' is not recognized`). On Windows Node only
 // honors the writable/read-only bit so 0o755 is effectively a no-op for
 // execute permissions, but the call is harmless. On POSIX it sets the
 // executable bit as before.
 //
-// Asset copy: tsc only emits .ts → .js; .md assets (e.g. the agent skill
-// body) are not copied by the compiler. This step mirrors src/assets/ into
-// dist/assets/ so the built binary resolves them at the same relative path.
-import { chmodSync, cpSync, rmSync } from 'node:fs';
+// Skill assets (skills/*.md) live at the repo/package ROOT and ship verbatim
+// via package.json `files`. agent-targets.ts resolves them with `../../skills`,
+// which points at the package root from BOTH `src/lib` (vitest) and `dist/lib`
+// (built) — so no asset copy into dist/ is needed (the old src/assets →
+// dist/assets mirror is gone).
+import { chmodSync } from 'node:fs';
 chmodSync(new URL('../dist/index.js', import.meta.url), 0o755);
-rmSync(new URL('../dist/assets', import.meta.url), { recursive: true, force: true });
-cpSync(new URL('../src/assets', import.meta.url), new URL('../dist/assets', import.meta.url), {
-  recursive: true,
-});