start-command 0.19.0 → 0.20.0

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # start-command
 
+## 0.20.0
+
+### Minor Changes
+
+- ad9e796: feat: Rename spine to timeline, add virtual command visualization for Docker
+
+  This release updates the internal terminology from "spine" to "timeline" for the status output format, and adds automatic visualization of Docker image pull operations as virtual commands.
+
+  Timeline terminology changes:
+  - The `│` prefixed output format is now consistently referred to as "timeline" format throughout the codebase
+  - All deprecated "spine" names remain available for backwards compatibility
+  - API changes are reflected in the Rust library (no breaking changes in JS)
+
+  Virtual command visualization for Docker:
+  - When Docker isolation requires pulling an image, it now appears as a separate `$ docker pull <image>` command
+  - Pull output is streamed in real-time with success (✓) or failure (✗) markers
+  - Only shown when the image actually needs to be pulled (not when using cached images)
+  - Provides better visibility into what's happening during Docker-based command execution
+
+  Version bumped to 0.20.0 to match the Rust library version.
+
+  Fixes #70
+
+## 0.19.1
+
+### Patch Changes
+
+- c84c1bb: fix: Always display session/container name in isolation output
+
+  When using isolation backends (screen, docker, tmux), the output now shows the actual session/container name that users need to reconnect to sessions, especially in detached mode. Previously, only the session UUID was shown, but users need the actual backend name to:
+  - Reconnect to detached screen sessions: `screen -r <name>`
+  - Attach to tmux sessions: `tmux attach -t <name>`
+  - View Docker container logs: `docker logs <name>`
+  - Remove containers: `docker rm -f <name>`
+
+  Fixes #67
+
 ## 0.19.0
 
 ### Minor Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "start-command",
-  "version": "0.19.0",
+  "version": "0.20.0",
   "description": "Gamification of coding, execute any command with ability to auto-report issues on GitHub",
   "main": "src/bin/cli.js",
   "exports": {

package/src/bin/cli.js

@@ -470,9 +470,10 @@ async function runWithIsolation(
   // Add isolation info to extra lines
   if (environment) {
     extraLines.push(`[Isolation] Environment: ${environment}, Mode: ${mode}`);
-  }
-  if (options.session) {
-    extraLines.push(`[Isolation] Session: ${options.session}`);
+    // Always add the session name so users can reconnect to detached sessions
+    // This is important for screen, tmux, docker where the session/container name
+    // is different from the session UUID used for tracking (see issue #67)
+    extraLines.push(`[Isolation] Session: ${sessionName}`);
   }
   if (effectiveImage) {
     extraLines.push(`[Isolation] Image: ${effectiveImage}`);

package/test/cli.test.js

@@ -122,3 +122,97 @@ describe('CLI basic behavior', () => {
     assert.ok(result.stdout.includes('Usage:'), 'Should display usage');
   });
 });
+
+describe('CLI isolation output (issue #67)', () => {
+  const { isCommandAvailable } = require('../src/lib/isolation');
+
+  it('should display screen session name when using screen isolation', async () => {
+    if (!isCommandAvailable('screen')) {
+      console.log('  Skipping: screen not installed');
+      return;
+    }
+
+    const result = runCLI(['-i', 'screen', '--', 'echo', 'hello']);
+
+    // The output should contain the screen session name (in format screen-timestamp-random)
+    // Check that the session UUID is displayed
+    assert.ok(
+      result.stdout.includes('│ session'),
+      'Should display session UUID'
+    );
+    // Check that screen isolation info is displayed
+    assert.ok(
+      result.stdout.includes('│ isolation screen'),
+      'Should display screen isolation'
+    );
+    // Check that the actual screen session name is displayed (issue #67 fix)
+    assert.ok(
+      result.stdout.includes('│ screen    screen-'),
+      'Should display actual screen session name for reconnection (issue #67)'
+    );
+  });
+
+  it('should display tmux session name when using tmux isolation', async () => {
+    if (!isCommandAvailable('tmux')) {
+      console.log('  Skipping: tmux not installed');
+      return;
+    }
+
+    const result = runCLI(['-i', 'tmux', '--', 'echo', 'hello']);
+
+    // The output should contain the tmux session name
+    assert.ok(
+      result.stdout.includes('│ session'),
+      'Should display session UUID'
+    );
+    assert.ok(
+      result.stdout.includes('│ isolation tmux'),
+      'Should display tmux isolation'
+    );
+    // Check that the actual tmux session name is displayed (issue #67 fix)
+    assert.ok(
+      result.stdout.includes('│ tmux      tmux-'),
+      'Should display actual tmux session name for reconnection (issue #67)'
+    );
+  });
+
+  it('should display docker container name when using docker isolation', async () => {
+    const { canRunLinuxDockerImages } = require('../src/lib/isolation');
+
+    if (!canRunLinuxDockerImages()) {
+      console.log(
+        '  Skipping: docker not available or cannot run Linux images'
+      );
+      return;
+    }
+
+    const result = runCLI([
+      '-i',
+      'docker',
+      '--image',
+      'alpine:latest',
+      '--',
+      'echo',
+      'hello',
+    ]);
+
+    // The output should contain the docker container name
+    assert.ok(
+      result.stdout.includes('│ session'),
+      'Should display session UUID'
+    );
+    assert.ok(
+      result.stdout.includes('│ isolation docker'),
+      'Should display docker isolation'
+    );
+    assert.ok(
+      result.stdout.includes('│ image     alpine:latest'),
+      'Should display docker image'
+    );
+    // Check that the actual container name is displayed (issue #67 fix)
+    assert.ok(
+      result.stdout.includes('│ container docker-'),
+      'Should display actual container name for reconnection (issue #67)'
+    );
+  });
+});