start-command 0.11.0 → 0.15.0

package/CHANGELOG.md

@@ -1,225 +1,36 @@
 # start-command
 
-## 0.11.0
+## 0.15.0
 
 ### Minor Changes
 
-- 1240a29: Add SSH isolation support for remote command execution.
-  - Implements SSH backend for executing commands on remote servers via SSH, similar to screen/tmux/docker isolation
-  - Uses `--endpoint` option to specify SSH target (e.g., `--endpoint user@remote.server`)
-  - Supports both attached (interactive) and detached (background) modes
-  - Includes comprehensive SSH integration tests in CI with a local SSH server
+- 102dbe2: Add dual storage system for command execution tracking using links notation
 
-## 0.10.0
-
-### Minor Changes
-
-- 8ea5659: Add user isolation support with --isolated-user and --keep-user options
-
-  Implements user isolation that creates a new isolated user to run commands:
-
-  ## --isolated-user option (create isolated user with same permissions)
-  - Add --isolated-user, -u option to create a new isolated user automatically
-  - New user inherits group memberships from current user (sudo, docker, wheel, etc.)
-  - User is automatically deleted after command completes (unless --keep-user)
-  - Works with screen and tmux isolation backends (not docker)
-  - Optional custom username via --isolated-user=myname or -u myname
-  - For screen/tmux: Wraps commands with sudo -n -u <user>
-  - Requires sudo NOPASSWD configuration for useradd/userdel/sudo
-
-  ## --keep-user option
-  - Add --keep-user option to prevent user deletion after command completes
-  - Useful when you need to inspect files created during execution
-  - User must be manually deleted with: sudo userdel -r <username>
-
-  ## Other improvements
-  - Add comprehensive tests for user isolation
-  - Update documentation with user isolation examples
-  - Integrate --keep-alive and --auto-remove-docker-container from main branch
-
-  Usage:
-  - $ --isolated-user -- npm test # Auto-generated username, auto-deleted
-  - $ --isolated-user myrunner -- npm start # Custom username
-  - $ -u myrunner -- npm start # Short form
-  - $ --isolated screen --isolated-user -- npm test # Combine with process isolation
-  - $ --isolated-user --keep-user -- npm test # Keep user after completion
-
-  Note: User isolation requires sudo NOPASSWD configuration.
-
-## 0.9.0
-
-### Minor Changes
-
-- c484149: Add --keep-alive option for isolation environments
-  - All isolation environments (screen, tmux, docker) now automatically exit after command completion by default
-  - New --keep-alive (-k) flag keeps the isolation environment running after command completes
-  - Add ARCHITECTURE.md documentation describing system design
-  - Update REQUIREMENTS.md with new option and auto-exit behavior documentation
-
-## 0.7.6
-
-### Patch Changes
-
-- a5fca3f: Add documentation for piping with `$` command
-  - Created `docs/PIPES.md` with detailed guide on pipe usage
-  - Preferred approach: `echo "hi" | $ agent` (pipe TO the $-wrapped command)
-  - Alternative approach: `$ 'echo "hi" | agent'` (quoting)
-  - Updated `docs/USAGE.md` with brief pipe reference
-  - Updated `README.md` with piping examples
-  - Updated case study for issue #28 with new recommended approach
-
-## 0.7.5
-
-### Patch Changes
-
-- 31a67fc: fix: Screen isolation output always captured in attached mode
-
-  Changed attached mode to always use log capture instead of direct screen invocation.
-  This ensures command output is never lost, even for quick commands that would
-  otherwise have their output disappear when the screen session terminates rapidly.
-
-  Fixes #25: Output from `$ --isolated screen -- echo "hello"` is now properly
-  displayed instead of being lost with only "[screen is terminating]" shown.
-
-## 0.7.4
-
-### Patch Changes
-
-- d058c43: fix: Screen isolation output not captured for quoted commands
-
-  This fixes issue #25 where commands with quoted strings (e.g., echo "hello") would not show their output when using screen isolation. The fix uses spawnSync with array arguments instead of execSync with a constructed string to avoid shell quoting issues.
-
-## 0.7.2
-
-### Patch Changes
-
-- fa0fb23: docs: Update documentation to Bun-first approach
-  - Remove npm installation option from README.md
-  - Update examples to use bun commands instead of npm
-  - Change package.json engines from node to bun
-  - Update REQUIREMENTS.md to remove Node.js alternative
-
-## 0.7.1
-
-### Patch Changes
-
-- d5a7c66: Fix all --version detection issues
-  - Fix screen version detection by capturing stderr
-  - Show Bun version instead of Node.js version when running with Bun
-  - Show macOS ProductVersion instead of kernel version
-  - Fix argument parsing to handle `$ --version --` same as `$ --version`
-  - Update all scripts and examples to use Bun instead of Node.js
-  - Add comprehensive tests for --version flag
-
-## 0.7.0
-
-### Minor Changes
-
-- 9e24fb5: Add --version flag to display comprehensive version and system information. Users can now run `$ --version` or `$ -v` to see the version of start-command, system details, and versions of isolation tools (screen, tmux, docker).
-
-## 0.6.0
-
-### Minor Changes
-
-- 37eb93b: Drop zellij isolation backend support, focusing on screen, tmux, and docker. Remove zellij from VALID_BACKENDS, remove runInZellij function, and update all documentation accordingly.
-
-## 0.5.3
-
-### Patch Changes
-
-- 20d0c1c: Fix screen isolation not capturing output on macOS (issue #15)
-  - Added version detection for GNU Screen to handle differences between versions
-  - Screen >= 4.5.1 uses native `-L -Logfile` for log capture
-  - Screen < 4.5.1 (like macOS bundled 4.0.3) uses `tee` command fallback
-  - Added tests for version detection and -Logfile support checking
-  - Updated case study documentation with root cause analysis
-
-## 0.5.2
-
-### Patch Changes
-
-- bdf77c7: Fix screen isolation environment not capturing command output in attached mode
-
-  When running commands with `--isolated screen` in attached mode, the command output was not being displayed (only "screen is terminating" was shown). This was because GNU Screen requires a TTY to run in attached mode, which is not available when spawning from Node.js without a terminal.
-
-  The fix implements a fallback mechanism that:
-  - Checks if a TTY is available before spawning screen
-  - If no TTY is available, uses detached mode with log capture to run the command and display its output
-  - Polls for session completion and reads the captured log file
-  - Displays the output to the user just as if it was running in attached mode
-
-  This ensures that `$ --isolated screen -- echo "hello"` now correctly displays "hello" even when running from environments without a TTY (like CI/CD pipelines, scripts, or when piping output).
-
-## 0.5.1
-
-### Patch Changes
-
-- Test patch release
-
-## 0.5.0
-
-### Minor Changes
-
-- 95d8760: Unify output experience for isolation mode
-  - Change terminology from "Backend" to "Environment" in isolation output
-  - Add unified logging with timestamps for isolation modes (screen, tmux, docker, zellij)
-  - Save log files for all execution modes with consistent format
-  - Display start/end timestamps, exit code, and log file path uniformly across all modes
-
-## 0.4.1
-
-### Patch Changes
-
-- 73635f9: Make it bun first - update shebangs and installation docs
-
-## 0.4.0
-
-### Minor Changes
-
-- e8bec3c: Add process isolation support with --isolated option
-
-  This release adds the ability to run commands in isolated environments:
+  This update implements a comprehensive execution tracking system that stores information about each called command:
 
   **New Features:**
-  - `--isolated` / `-i` option to run commands in screen, tmux, zellij, or docker
-  - `--attached` / `-a` and `--detached` / `-d` modes for foreground/background execution
-  - `--session` / `-s` option for custom session names
-  - `--image` option for Docker container image specification
-  - Two command syntax patterns: `$ [options] -- [command]` or `$ [options] command`
-
-  **Supported Backends:**
-  - GNU Screen - classic terminal multiplexer
-  - tmux - modern terminal multiplexer
-  - zellij - modern terminal workspace
-  - Docker - container isolation
-
-  **Examples:**
-
-  ```bash
-  $ --isolated tmux -- npm start
-  $ -i screen -d npm start
-  $ --isolated docker --image node:20 -- npm install
-  ```
-
-## 0.3.1
-
-### Patch Changes
-
-- 6a701da: Apply js-ai-driven-development-pipeline-template (Bun-only)
-  - Add .changeset/ for version management
-  - Add .husky/ for git hooks
-  - Add eslint.config.mjs with ESLint 9 flat config
-  - Add .prettierrc for code formatting
-  - Add bunfig.toml for Bun configuration
-  - Add scripts/ directory with release automation scripts
-  - Create release.yml workflow (Bun-only, merged test.yml)
-  - Add CHANGELOG.md
-
-## 0.3.0
-
-### Minor Changes
-
-- Initial release with natural language command aliases
-- Automatic logging of all commands
-- Auto-reporting on failure for NPM packages
-- GitHub integration for issue creation
+  - Dual storage system: text (.lino files) via lino-objects-codec and binary (.links) via clink
+  - Each execution record includes:
+    - UUID of the command call
+    - Process ID (PID) for process management
+    - Status (executing/executed)
+    - Exit code
+    - Log file path
+    - Working directory, shell, platform info
+    - Additional execution options and metadata
+  - File-based locking mechanism to ensure single-writer access
+  - Verification system to check consistency between text and binary databases
+  - Integration with clink's string aliases for readable identifiers
+
+  **Configuration:**
+  - `START_DISABLE_TRACKING=1` - Disable execution tracking
+  - `START_APP_FOLDER` - Custom folder for storing execution records
+  - `START_VERBOSE=1` - Show execution IDs during command execution
+
+  **Dependencies:**
+  - Added `lino-objects-codec` for links notation serialization
+  - Optional `clink` CLI tool for binary database support
+
+  **Testing:**
+  - 24 new unit tests for execution store operations
+  - CI/CD updated to install clink for integration testing on Linux and macOS

package/bun.lock

@@ -4,6 +4,10 @@
   "workspaces": {
     "": {
       "name": "start-command",
+      "dependencies": {
+        "command-stream": "^0.8.3",
+        "lino-objects-codec": "^0.1.1",
+      },
       "devDependencies": {
         "@changesets/cli": "^2.29.7",
         "eslint": "^9.38.0",
@@ -142,6 +146,8 @@
 
     "colorette": ["colorette@2.0.20", "", {}, "sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w=="],
 
+    "command-stream": ["command-stream@0.8.3", "", {}, "sha512-vwNf5AWLhD4awaYSIyjHEu7JrAMTu8BaJg1LIpE4HqTXFYtgzSTN/j1VnwHDTNz8sAG7zvZgtKYm9lmi4+0Z7Q=="],
+
     "commander": ["commander@14.0.2", "", {}, "sha512-TywoWNNRbhoD0BXs1P3ZEScW8W5iKrnbithIl0YH+uCmBd0QpPOA8yc82DS3BIE5Ma6FnBVUsJ7wVUDz4dvOWQ=="],
 
     "concat-map": ["concat-map@0.0.1", "", {}, "sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg=="],
@@ -266,6 +272,10 @@
 
     "levn": ["levn@0.4.1", "", { "dependencies": { "prelude-ls": "^1.2.1", "type-check": "~0.4.0" } }, "sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ=="],
 
+    "links-notation": ["links-notation@0.11.2", "", {}, "sha512-VPyELWBXpaCCiNPVeZhMbG7RuvOQR51nhqELK+s/rbSzKYhSs+tyiSOdQ7z8I7Kh3PLABF3bZETtWSFwx3vFfg=="],
+
+    "lino-objects-codec": ["lino-objects-codec@0.1.1", "", { "dependencies": { "links-notation": "^0.11.0" } }, "sha512-URX1MAhHyVga5EkpUqDTMkX1D+HYBW3spgKh6vCneQnzOMLn09XooQOuBy0apbfwlqY5qHt2fpvRdT75dBn2Qw=="],
+
     "lint-staged": ["lint-staged@16.2.7", "", { "dependencies": { "commander": "^14.0.2", "listr2": "^9.0.5", "micromatch": "^4.0.8", "nano-spawn": "^2.0.0", "pidtree": "^0.6.0", "string-argv": "^0.3.2", "yaml": "^2.8.1" }, "bin": { "lint-staged": "bin/lint-staged.js" } }, "sha512-lDIj4RnYmK7/kXMya+qJsmkRFkGolciXjrsZ6PC25GdTfWOAWetR0ZbsNXRAj1EHHImRSalc+whZFg56F5DVow=="],
 
     "listr2": ["listr2@9.0.5", "", { "dependencies": { "cli-truncate": "^5.0.0", "colorette": "^2.0.20", "eventemitter3": "^5.0.1", "log-update": "^6.1.0", "rfdc": "^1.4.1", "wrap-ansi": "^9.0.0" } }, "sha512-ME4Fb83LgEgwNw96RKNvKV4VTLuXfoKudAmm2lP8Kk87KaMK0/Xrx/aAkMWmT8mDb+3MlFDspfbCs7adjRxA2g=="],

package/eslint.config.mjs

@@ -115,7 +115,7 @@ export default [
     },
     rules: {
       'require-await': 'off', // Async functions without await are common in tests
-      'no-unused-vars': 'warn', // Relax for experiments
+      'no-unused-vars': 'off', // Disable for tests and experiments
       'no-empty': 'off', // Empty catch blocks are common in experiments
     },
   },

package/package.json

@@ -1,8 +1,12 @@
 {
   "name": "start-command",
-  "version": "0.11.0",
+  "version": "0.15.0",
   "description": "Gamification of coding, execute any command with ability to auto-report issues on GitHub",
-  "main": "index.js",
+  "main": "src/bin/cli.js",
+  "exports": {
+    ".": "./src/bin/cli.js",
+    "./execution-store": "./src/lib/execution-store.js"
+  },
   "bin": {
     "$": "./src/bin/cli.js"
   },
@@ -12,11 +16,11 @@
     "lint:fix": "eslint . --fix",
     "format": "prettier --write .",
     "format:check": "prettier --check .",
-    "check:file-size": "bun scripts/check-file-size.mjs",
+    "check:file-size": "bun ../scripts/check-file-size.mjs",
     "check": "bun run lint && bun run format:check && bun run check:file-size",
-    "prepare": "husky || true",
+    "prepare": "cd .. && husky .husky || true",
     "changeset": "changeset",
-    "changeset:version": "bun scripts/changeset-version.mjs",
+    "changeset:version": "bun ../scripts/changeset-version.mjs",
     "changeset:publish": "changeset publish",
     "changeset:status": "changeset status --since=origin/main"
   },
@@ -59,5 +63,9 @@
       "prettier --write",
       "prettier --check"
     ]
+  },
+  "dependencies": {
+    "command-stream": "^0.8.3",
+    "lino-objects-codec": "^0.1.1"
   }
 }