chore: wip

Author: chrisbbreuer

docs/api/reference.md

@@ -267,7 +267,7 @@ interface LaunchpadConfig {
   showShellMessages: boolean
   /** Custom message to show when environment is activated (default: "✅ Environment activated for {path}") */
   shellActivationMessage: string
-  /** Custom message to show when environment is deactivated (default: "dev environment deactivated") */
+  /** Custom message to show when environment is deactivated (default: "Environment deactivated") */
   shellDeactivationMessage: string
 }
 

docs/config.md

@@ -63,8 +63,8 @@ const config: LaunchpadConfig = {
   // Use {path} placeholder to include the project path (default: "✅ Environment activated for {path}")
   shellActivationMessage: '✅ Environment activated for {path}',
 
-  // Custom message to show when environment is deactivated (default: "dev environment deactivated")
-  shellDeactivationMessage: 'dev environment deactivated',
+  // Custom message to show when environment is deactivated (default: "Environment deactivated")
+  shellDeactivationMessage: 'Environment deactivated',
 
   // Service Management Configuration
   services: {
@@ -124,7 +124,7 @@ JavaScript format (`.launchpadrc`):
   "autoAddToPath": true,
   "showShellMessages": true,
   "shellActivationMessage": "✅ Environment activated for {path}",
-  "shellDeactivationMessage": "dev environment deactivated",
+  "shellDeactivationMessage": "Environment deactivated",
   "services": {
     "enabled": true,
     "dataDir": "~/.local/share/launchpad/services",
@@ -206,19 +206,22 @@ Services use these configurable template variables:
 ### Examples
 
 #### Development Setup (Default)
+
 ```bash
 # Uses: username=root, password=password, authMethod=trust
 launchpad start postgres
 ```
 
 #### Custom Development Setup
+
 ```bash
 export LAUNCHPAD_DB_USERNAME="dev_user"
 export LAUNCHPAD_DB_PASSWORD="dev_password"
 launchpad start postgres
 ```
 
 #### Production-like Setup
+
 ```bash
 export LAUNCHPAD_DB_AUTH_METHOD="md5"
 export LAUNCHPAD_DB_PASSWORD="secure_password123"
@@ -323,9 +326,11 @@ launchpad clean --keep-global --dry-run
 ```
 
 **Global dependency detection**:
+
 - Any dependency file (`deps.yaml`, `dependencies.yaml`, etc.) with `global: true`
 
 **Example global dependency file** (`~/.dotfiles/deps.yaml`):
+
 ```yaml
 global: true
 dependencies:
@@ -360,6 +365,7 @@ services:
 ```
 
 Behavior:
+
 - **enabled**: toggles service management for the project.
 - **autoStart**: array of service names to start automatically on environment activation.
 - Service names must match those in the Supported Services list (e.g. `postgres`, `redis`, `nginx`).
@@ -380,12 +386,14 @@ services:
 ```
 
 When enabled and a Laravel app is detected (`artisan` present), Launchpad will read `.env` and infer services:
+
 - `DB_CONNECTION=pgsql` → `postgres`
 - `DB_CONNECTION=mysql|mariadb` → `mysql`
 - `CACHE_DRIVER=redis` or `CACHE_STORE=redis` → `redis`
 - `CACHE_DRIVER=memcached` or `CACHE_STORE=memcached` → `memcached`
 
 Environment toggles:
+
 - `LAUNCHPAD_FRAMEWORKS_ENABLED` (default: true)
 - `LAUNCHPAD_SERVICES_INFER` (default: true)
 - `LAUNCHPAD_LARAVEL_ENABLED` (default: true)
@@ -424,7 +432,7 @@ Environment toggles:
 |--------|------|---------|-------------|
 | `showShellMessages` | boolean | `true` | Whether to display environment activation/deactivation messages |
 | `shellActivationMessage` | string | `"✅ Environment activated for {path}"` | Custom message shown when environment is activated. Use `{path}` placeholder for project path |
-| `shellDeactivationMessage` | string | `"dev environment deactivated"` | Custom message shown when environment is deactivated |
+| `shellDeactivationMessage` | string | `"Environment deactivated"` | Custom message shown when environment is deactivated |
 
 ### Path Management
 
@@ -538,6 +546,7 @@ postActivation:
 ```
 
 Notes:
+
 - Inline hooks in `deps.yaml` run alongside config hooks of the same phase.
 - preSetup runs before dependency installation and service auto-start.
 - preActivation runs after installation/services and before printing the activation message.
@@ -583,7 +592,9 @@ When you cd into a project directory that contains a dependency file (e.g. `deps
 The target environment directory is derived as:
 
 ```
+
 ~/.local/share/launchpad/envs/<project>_<hash>-d<dep_hash>
+
 ```
 
 This guarantees that editing dependency versions switches to a distinct environment on the next `cd`, ensuring the correct tools are active immediately.
@@ -751,6 +762,7 @@ launchpad --verbose install --dry-run node
 ### Configuration Not Loading
 
 1. Check file syntax:
+
    ```bash
    # For TypeScript files
    bunx tsc --noEmit launchpad.config.ts
@@ -760,6 +772,7 @@ launchpad --verbose install --dry-run node
    ```
 
 2. Verify file location:
+
    ```bash
    # Check current directory
    ls -la launchpad.config.*
@@ -769,18 +782,21 @@ launchpad --verbose install --dry-run node
    ```
 
 3. Test with verbose mode:
+
    ```bash
    launchpad --verbose list
    ```
 
 ### Environment Variables Not Working
 
 1. Check if variables are set:
+
    ```bash
    env | grep LAUNCHPAD
    ```
 
 2. Export variables properly:
+
    ```bash
    export LAUNCHPAD_VERBOSE=true
    export LAUNCHPAD_INSTALL_PATH=/custom/path
@@ -790,6 +806,7 @@ launchpad --verbose install --dry-run node
    ```
 
 3. Verify shell configuration:
+
    ```bash
    echo $SHELL
    source ~/.zshrc  # or ~/.bashrc

docs/features/environment-management.md

@@ -32,10 +32,12 @@ Launchpad uses a human-readable hash format for environment directories:
 **Format:** `{project-name}_{8-char-hex-hash}-d{8-char-dep-hash}`
 
 **Examples:**
+
 - `my-web-app_1a2b3c4d-d9f1a2b3` - Project `/home/user/projects/my-web-app`, dependency fingerprint `d9f1a2b3`
 - `api-server_5e6f7g8h-d0c1e2f3` - Project `/work/api-server`, dependency fingerprint `d0c1e2f3`
 
 **Benefits:**
+
 - **Human-readable** - Easy to identify which project an environment belongs to
 - **Version-aware** - Dependency changes always map to a distinct environment
 - **Unique** - 8-character hex hash prevents collisions between projects
@@ -53,10 +55,12 @@ Launchpad automatically detects these dependency files:
 - `.deps.yml` / `.deps.yaml`
 
 For pkgx compatibility, Launchpad also supports:
+
 - `pkgx.yaml` / `pkgx.yml`
 - `.pkgx.yaml` / `.pkgx.yml`
 
 **Example dependency file:**
+
 ```yaml
 dependencies:
   - node@22
@@ -74,6 +78,7 @@ env:
 Control where packages are installed using the `global` flag:
 
 **Individual Package Control:**
+
 ```yaml
 # dependencies.yaml
 dependencies:
@@ -98,6 +103,7 @@ env:
 ```
 
 **Top-Level Global Flag:**
+
 ```yaml
 # dependencies.yaml
 global: true  # Install all packages globally by default
@@ -116,6 +122,7 @@ env:
 ```
 
 **Global Installation Behavior:**
+
 - **Global packages** (`global: true`): Installed system-wide, available in all environments
 - **Local packages** (`global: false` or default): Installed per-project, isolated from other environments
 - **Mixed approach**: Combine global tools with project-specific dependencies
@@ -137,7 +144,7 @@ Once set up, environments automatically activate:
 
 ```bash
 cd my-project/  # → ✅ Environment activated for /path/to/my-project
-cd ../          # → dev environment deactivated
+cd ../          # → Environment deactivated
 ```
 
 ### Customizing Shell Messages
@@ -219,6 +226,7 @@ launchpad env:ls --format simple
 **Output formats:**
 
 **Table (default):**
+
 ```
 📦 Development Environments:
 
@@ -233,6 +241,7 @@ Total: 3 environment(s)
 ```
 
 **JSON:**
+
 ```json
 [
   {
@@ -247,6 +256,7 @@ Total: 3 environment(s)
 ```
 
 **Simple:**
+
 ```
 final-project (final-project_7db6cf06)
 working-test (working-test_208a31ec)
@@ -269,6 +279,7 @@ launchpad env:inspect dummy_6d7cf1d6 --show-stubs
 ```
 
 **Example output:**
+
 ```
 🔍 Inspecting environment: working-test_208a31ec
 
@@ -306,6 +317,7 @@ Overall Status: ✅ Healthy
 ```
 
 **Health Check Criteria:**
+
 - **Binaries present** - Environment has executable binaries
 - **Packages installed** - Package directories exist and contain files
 - **Directory structure** - Required directories (bin, pkgs) exist
@@ -332,6 +344,7 @@ launchpad env:clean --verbose
 ```
 
 **Cleanup Criteria:**
+
 - Environments with no binaries (failed installations)
 - Environments older than specified days (default: 30)
 - Empty or corrupted environment directories
@@ -380,6 +393,7 @@ fi
 Environments work seamlessly with development tools:
 
 **Node.js project example:**
+
 ```yaml
 dependencies:
   - node@22
@@ -392,6 +406,7 @@ env:
 ```
 
 **Python project example:**
+
 ```yaml
 dependencies:
   - [email protected]
@@ -408,50 +423,59 @@ env:
 #### Environment Not Activating
 
 1. Check shell integration:
+
    ```bash
    type _pkgx_chpwd_hook
    ```
 
 2. Verify dependency file:
+
    ```bash
    launchpad dev:dump --dryrun
    ```
 
 3. Check file detection:
+
    ```bash
    ls -la dependencies.yaml
    ```
 
 #### Environment Messages Not Showing
 
 1. Check message settings:
+
    ```bash
    echo $LAUNCHPAD_SHOW_ENV_MESSAGES
    ```
 
 2. Verify shell integration:
+
    ```bash
    grep "launchpad dev:shellcode" ~/.zshrc
    ```
 
 3. Test manual activation:
+
 ```bash
    eval "$(launchpad dev:shellcode)"
    ```
 
 #### Performance Issues
 
 1. Clean old environments:
+
    ```bash
    launchpad env:clean --older-than 7
    ```
 
 2. Check disk usage:
+
    ```bash
    du -sh ~/.local/share/launchpad/envs/*
    ```
 
 3. Monitor activation time:
+
   ```bash
   time (cd my-project && cd ..)
   ```
@@ -479,16 +503,19 @@ env:
 ### Troubleshooting
 
 **Environment not activating:**
+
 1. Check shell integration: `echo 'eval "$(launchpad dev:shellcode)"' >> ~/.zshrc`
 2. Verify dependency file exists and has correct syntax
 3. Reload shell configuration: `source ~/.zshrc`
 
 **Package installation failures:**
+
 1. Check internet connectivity
 2. Verify package names and versions exist in pkgx
 3. Use `launchpad dev:dump --verbose` for detailed error information
 
 **Hash collisions (rare):**
+
 1. Different projects with same name get different hashes based on full path
 2. If collision occurs, rename one of the project directories
 3. Remove old environment: `launchpad env:remove {hash}`