@vizzly-testing/cli 0.35.0 → 0.35.1

package/dist/tdd/tdd-service.js

@@ -1163,6 +1163,9 @@ export class TddService {
     let newComparisons = getNewComparisons(this.comparisons);
     let passedComparisons = this.comparisons.filter(c => c.status === 'passed' || c.status === 'baseline-created' || c.status === 'baseline-updated');
     let hasChanges = failedComparisons.length > 0 || newComparisons.length > 0;
+    if (output.isJson?.()) {
+      return results;
+    }
 
     // Header with summary - use bear emoji as Vizzly mascot
     output.blank();
@@ -1239,9 +1242,10 @@ export class TddService {
       let serverFile = `${this.workingDir}/.vizzly/server.json`;
       let serverRunning = false;
       let serverPort = 47392;
+      let serverInfo = {};
       try {
         if (existsSync(serverFile)) {
-          let serverInfo = JSON.parse(readFileSync(serverFile, 'utf8'));
+          serverInfo = JSON.parse(readFileSync(serverFile, 'utf8'));
           if (serverInfo.port) {
             serverPort = serverInfo.port;
             serverRunning = true;
@@ -1250,7 +1254,7 @@ export class TddService {
       } catch {
         // Ignore errors reading server file
       }
-      if (serverRunning) {
+      if (serverRunning && !serverInfo.buildId) {
         // Server is running - show the dashboard URL
         output.print(`  ${textTertiary('→')} Review changes: ${infoColor(colors.underline(`http://localhost:${serverPort}`))}`);
       } else {

package/dist/test-runner/core.js

@@ -234,12 +234,14 @@ export function hasApiKey(config) {
 /**
  * Build spawn options for test command execution
  * @param {Object} env - Environment variables
+ * @param {Object} [options] - Spawn display options
+ * @param {boolean} [options.json] - Keep stdout reserved for CLI JSON output
  * @returns {Object} Spawn options
  */
-export function buildSpawnOptions(env) {
+export function buildSpawnOptions(env, options = {}) {
   return {
     env,
-    stdio: 'inherit',
+    stdio: options.json ? ['inherit', 'pipe', 'pipe'] : 'inherit',
     shell: true
   };
 }

package/dist/test-runner/operations.js

@@ -188,6 +188,7 @@ export async function finalizeBuild({
 export function executeTestCommand({
   command,
   env,
+  json = false,
   deps
 }) {
   let {
@@ -195,8 +196,18 @@ export function executeTestCommand({
     createError
   } = deps;
   return new Promise((resolve, reject) => {
-    let spawnOptions = buildSpawnOptions(env);
+    let spawnOptions = buildSpawnOptions(env, {
+      json
+    });
     let testProcess = spawn(command, spawnOptions);
+    if (json) {
+      testProcess.stdout?.on('data', data => {
+        process.stderr.write(data);
+      });
+      testProcess.stderr?.on('data', data => {
+        process.stderr.write(data);
+      });
+    }
     testProcess.on('error', error => {
       reject(createError(`Failed to run test command: ${error.message}`, 'TEST_COMMAND_FAILED'));
     });
@@ -271,6 +282,7 @@ export async function runTests({
     await executeTestCommand({
       command: testCommand,
       env,
+      json: runOptions.json,
       deps: {
         spawn,
         createError
@@ -341,6 +353,7 @@ export async function runTests({
       await executeTestCommand({
         command: testCommand,
         env,
+        json: runOptions.json,
         deps: {
           spawn,
           createError
@@ -409,7 +422,9 @@ export async function runTests({
 
   // Throw test error after cleanup
   if (testError) {
-    output.error('Test run failed:', testError);
+    if (!runOptions.json) {
+      output.error('Test run failed:', testError);
+    }
     throw testError;
   }
   return buildRunResult({

package/dist/utils/config-loader.js

@@ -82,6 +82,7 @@ export async function loadConfig(configPath = null, cliOverrides = {}) {
     config.userToken = userToken;
     output.debug('config', 'using user login for user-authenticated commands');
   }
+  config._configPath = result?.filepath || null;
   return config;
 }
 

package/dist/utils/output.js

@@ -232,6 +232,9 @@ export function getLogLevel() {
 export function isVerbose() {
   return config.logLevel === 'debug';
 }
+export function isJson() {
+  return config.json;
+}
 
 /**
  * Show command header with distinctive branding

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vizzly-testing/cli",
-  "version": "0.35.0",
+  "version": "0.35.1",
   "description": "Visual regression testing from your terminal",
   "keywords": [
     "llm-context",

package/skills/vizzly/SKILL.md

@@ -23,16 +23,24 @@ If a task names a screen, component, or screenshot, inspect that screenshot's hi
 vizzly context screenshot "<screenshot-name>" --source local --json
 ```
 
-When you make or verify UI changes, run the focused user workflow that owns the surface:
+When you make or verify UI changes, use the local TDD server as the active feedback loop:
 
 ```bash
-vizzly tdd run "<test command>" --no-open
+vizzly tdd start &
+npm run test:e2e -- tests/e2e/path.spec.js
+vizzly context build current --source local --agent --json
 ```
 
-Then inspect what changed:
+The user may choose whether the TDD server runs in the foreground or background. Once it is
+running, run tests normally from the repo. The SDK discovers `.vizzly/server.json`, posts
+screenshots to the active TDD server, and refreshes `.vizzly/current`, `.vizzly/diffs`, report
+data, and local context.
+
+Use `vizzly tdd run` for true one-off runs where you want the CLI to own starting the visual
+session and running the command:
 
 ```bash
-vizzly context build current --source local --agent --json
+vizzly tdd run "<test command>" --no-open
 ```
 
 For specific evidence, drill in:

package/skills/vizzly/references/cli-context.md

@@ -5,13 +5,19 @@ Use these commands to gather Vizzly evidence before making UI assumptions.
 ## Local TDD
 
 ```bash
-vizzly tdd start
+vizzly tdd start --open
+vizzly tdd status
+vizzly tdd stop
 vizzly tdd run "<test command>" --no-open
 vizzly context build current --source local --agent
 vizzly context build current --source local --agent --json
 ```
 
-Local context reads `.vizzly` state and does not require cloud auth.
+If `tdd start` prints a non-default port, pass that same port to
+`tdd status --port <port>` and `tdd stop --port <port>`.
+
+Local context reads `.vizzly` state and does not require cloud auth. After a
+one-shot `tdd run`, prefer the printed `contextCommand` before editing UI.
 
 ## Cloud Builds
 

package/skills/vizzly/references/setup-ci.md

@@ -6,11 +6,13 @@ Use Vizzly locally for fast feedback and in CI for shared review.
 
 ```bash
 vizzly init
-vizzly tdd start
+vizzly tdd start --open
 vizzly tdd run "<test command>" --no-open
 ```
 
 The local SDK discovers `.vizzly/server.json` and sends screenshots to the TDD server when it is running.
+For one-off checks, `vizzly tdd run` writes local review data under `.vizzly/`
+and prints a context command for follow-up inspection.
 
 ## Cloud Setup