@xera-ai/cli 0.9.4 → 0.9.6

package/dist/index.js

@@ -262,7 +262,6 @@ function copyDir(src, dest) {
       writeFileSync(d, readFileSync2(s));
   }
 }
-var TEMPLATE_DIR = TEMPLATE_ROOT;
 
 // src/commands/init.ts
 var require2 = createRequire(import.meta.url);
@@ -405,12 +404,6 @@ async function initCommand(opts) {
     writeFileSync2(gitignorePath, `${gitignoreAdditions.trim()}
 `);
   }
-  if (wantsWeb) {
-    copyDir(join3(TEMPLATE_DIR, "sample/SAMPLE-001"), join3(cwd, ".xera/SAMPLE-001"));
-  }
-  if (wantsHttp) {
-    copyDir(join3(TEMPLATE_DIR, "sample/SAMPLE-HTTP-001"), join3(cwd, ".xera/SAMPLE-HTTP-001"));
-  }
   const skillsSrc = require2.resolve("@xera-ai/skills/package.json");
   const skillsDir = join3(skillsSrc, "..");
   for (const target of [".claude/skills", ".claude/commands"]) {
@@ -463,23 +456,22 @@ Next:
        USER_BEARER_TOKEN=...
   2) Run pre-authentication:
        bun run xera:auth-setup
-  3) Try the sample:
-       Open Claude Code in this directory and run: /xera-run SAMPLE-HTTP-001
+  3) Start testing:
+       Open Claude Code in this directory and run: /xera-run <TICKET>
 ` : shape === "mixed" ? `
 Next:
   1) Set credentials in .env.local (both web logins and API tokens)
   2) Run pre-authentication:
        bun run xera:auth-setup
-  3) Try samples:
-       /xera-run SAMPLE-001        # UI
-       /xera-run SAMPLE-HTTP-001   # API
+  3) Start testing:
+       Open Claude Code in this directory and run: /xera-run <TICKET>
 ` : `
 Next:
   1) Set your Jira credentials in .env.local
   2) Run pre-authentication:
        bun run xera:auth-setup
-  3) Try the sample:
-       Open Claude Code in this directory and run: /xera-run SAMPLE-001
+  3) Start testing:
+       Open Claude Code in this directory and run: /xera-run <TICKET>
 `;
   p.note(nextSteps.trim(), "Next steps");
   p.outro(pc2.green("xera initialized!"));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xera-ai/cli",
-  "version": "0.9.4",
+  "version": "0.9.6",
   "type": "module",
   "bin": {
     "xera": "./bin/xera"
@@ -15,8 +15,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@xera-ai/core": "^0.9.4",
-    "@xera-ai/skills": "^0.9.4",
+    "@xera-ai/core": "^0.9.6",
+    "@xera-ai/skills": "^0.9.6",
     "@clack/prompts": "1.4.0",
     "cac": "7.0.0",
     "picocolors": "1.1.1"

package/templates/sample/SAMPLE-001/meta.json

@@ -1,9 +0,0 @@
-{
-  "ticket": "SAMPLE-001",
-  "adapter": "web",
-  "xera_version": "0.1.0",
-  "prompts_version": "1.0.0",
-  "source": "local",
-  "fetched_at": "2026-05-14T00:00:00.000Z",
-  "story_hash": "sha256:placeholder"
-}

package/templates/sample/SAMPLE-001/spec.ts

@@ -1,9 +0,0 @@
-import { expect, test } from '@playwright/test';
-
-test.describe('SAMPLE-001: Playwright docs site smoke test', () => {
-  test('Home page loads with expected title', async ({ page }) => {
-    await page.goto('https://playwright.dev');
-    await expect(page).toHaveTitle(/Playwright/);
-    await expect(page.getByRole('heading', { level: 1 })).toBeVisible();
-  });
-});

package/templates/sample/SAMPLE-001/story.md

@@ -1,11 +0,0 @@
-# SAMPLE-001: Playwright documentation site loads
-
-## Story
-As a QA engineer setting up xera,
-I want to verify the framework can run an end-to-end test against a public website,
-so that I know my environment is set up correctly.
-
-## Acceptance Criteria
-- Navigate to https://playwright.dev
-- Page title contains "Playwright"
-- Main heading is visible

package/templates/sample/SAMPLE-001/test.feature

@@ -1,6 +0,0 @@
-Feature: Playwright docs site smoke test
-
-  Scenario: Home page loads with expected title
-    Given I open the Playwright docs site
-    Then the page title contains "Playwright"
-    And I see the main heading

package/templates/sample/SAMPLE-HTTP-001/meta.json

@@ -1,9 +0,0 @@
-{
-  "ticket": "SAMPLE-HTTP-001",
-  "adapter": "http",
-  "xera_version": "0.1.0",
-  "prompts_version": "1.0.0",
-  "source": "local",
-  "fetched_at": "2026-05-16T00:00:00.000Z",
-  "story_hash": "sha256:placeholder"
-}

package/templates/sample/SAMPLE-HTTP-001/spec.ts

@@ -1,29 +0,0 @@
-import { type APIRequestContext, expect, test } from '@playwright/test';
-import { newAuthedContext } from '@xera-ai/http/runtime';
-
-test.describe('POST /users validation', () => {
-  let api: APIRequestContext;
-  test.beforeAll(async ({ playwright }) => {
-    api = await newAuthedContext(playwright, 'user');
-  });
-  test.afterAll(async () => {
-    await api.dispose();
-  });
-
-  test('Reject malformed email', async () => {
-    const res = await api.post('/users', { data: { email: 'not-an-email' } });
-    expect(res.status()).toBe(422);
-    const body = await res.json();
-    expect(body.errors).toBeInstanceOf(Array);
-  });
-
-  test('Accept valid email', async () => {
-    const res = await api.post('/users', {
-      data: { email: `alice-${process.env.XERA_RUN_ID}@example.com` },
-    });
-    expect(res.status()).toBe(201);
-    const body = await res.json();
-    expect(body).toHaveProperty('id');
-    expect(body).toHaveProperty('email');
-  });
-});

package/templates/sample/SAMPLE-HTTP-001/story.md

@@ -1,11 +0,0 @@
-# SAMPLE-HTTP-001 — POST /users validation
-
-As a developer integrating the registration API,
-I want POST /users to reject invalid emails with 422,
-so that clients receive structured validation feedback.
-
-## Acceptance Criteria
-
-- POST /users with empty email returns 422 with `errors` containing "email is required" or similar.
-- POST /users with malformed email (no @) returns 422 with a message containing "email must be valid".
-- POST /users with a valid email returns 201 with `{ id, email }`.

package/templates/sample/SAMPLE-HTTP-001/test.feature

@@ -1,11 +0,0 @@
-Feature: POST /users validation
-
-  Scenario: Reject malformed email
-    When the user POSTs /users with body { "email": "not-an-email" }
-    Then the response status is 422
-    And the response body contains an "errors" array
-
-  Scenario: Accept valid email
-    When the user POSTs /users with body { "email": "alice@example.com" }
-    Then the response status is 201
-    And the response body has fields "id" and "email"