feat(mpm): rename binary to mows with busybox-style subcommands

Transform mpm into a busybox-style `mows` binary with `package-manager`
subcommand grouping. The `mpm` symlink is preserved as a backward-compatible
alias via argv[0] detection.

Key changes:
- Binary renamed from `mpm` to `mows` (crate: `mows-cli`)
- CLI restructured: `mows package-manager compose ...` with `mpm compose ...` alias
- Source moved: `src/compose/` -> `src/package_manager/compose/`
- Config: `mows.yaml` (primary) with `mpm.yaml` legacy fallback
- Env var: `MOWS_CONFIG_PATH` (primary) with `MPM_CONFIG_PATH` fallback
- Error type: `MpmError` -> `MowsError` with structured variants
- Self-update: tags use `mows-cli-v*`, creates mpm symlink after update
- CI: `publish-mpm.yml` -> `publish-mows.yml` with updated triggers
- Shell completions and man pages generated for both `mows` and `mpm`
- All docs, tests, build scripts, Dockerfile, and install script updated
- HTTP errors now use proper `Network` variant instead of generic `Message`
- Symlink creation improved with TOCTOU mitigation and proper error handling
- Integration test fixes for config path priority and arithmetic under set -e

Author: firstdorsal

.github/workflows/publish-mpm.yml .github/workflows/publish-mows.yml.github/workflows/publish-mpm.yml renamed to .github/workflows/publish-mows.yml

@@ -1,18 +1,18 @@
-name: Publish mpm binary
+name: Publish mows binary
 
 on:
   push:
     tags:
-      - 'mpm-v*'
+      - 'mows-cli-v*'
     paths:
       - 'utils/mpm/**'
       - 'utils/mows-common-rust/**'
-      - '.github/workflows/publish-mpm.yml'
+      - '.github/workflows/publish-mows.yml'
   pull_request:
     paths:
       - 'utils/mpm/**'
       - 'utils/mows-common-rust/**'
-      - '.github/workflows/publish-mpm.yml'
+      - '.github/workflows/publish-mows.yml'
   workflow_dispatch:
     inputs:
       dry_run:
@@ -25,15 +25,15 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v4
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v4
 
       - name: Install Rust
         uses: dtolnay/rust-toolchain@f7ccc83f9ed1e5b9c81d8a67d7ad1a747e22a561 # stable
         with:
           toolchain: stable
 
       - name: Cache cargo registry
-        uses: actions/cache@cdf6c1fa76f9f475f3d7449005a359c84ca0f306 # v4
+        uses: actions/cache@8b402f58fbc84540c8b491a91e594a4576fec3d7 # v4
         with:
           path: |
             ~/.cargo/registry
@@ -53,13 +53,18 @@ jobs:
           cd utils/mpm
           cargo build --release
 
+      - name: Create mpm symlink for e2e tests
+        run: |
+          ln -sf mows utils/mpm/target/release/mpm
+
       - name: Run e2e tests
         run: |
           cd utils/mpm/tests
           # Use mock Docker client for tests that would otherwise need Docker daemon
           # Skip test-self-update which requires network access to GitHub API
           SKIP_TESTS="test-self-update" ./run-all.sh
         env:
+          MOWS_BIN: ${{ github.workspace }}/utils/mpm/target/release/mows
           MPM_BIN: ${{ github.workspace }}/utils/mpm/target/release/mpm
           MPM_MOCK_DOCKER: "1"
 
@@ -76,7 +81,7 @@ jobs:
           - arch: arm64
             os_name: linux
     steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v4
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v4
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@8d2750c68a42422c14e847fe6c8ac0403b4cbd6f # v3
@@ -102,7 +107,7 @@ jobs:
         run: |
           if [[ "${{ github.ref_type }}" == "tag" ]]; then
             VERSION="${{ github.ref_name }}"
-            VERSION="${VERSION#mpm-v}"
+            VERSION="${VERSION#mows-cli-v}"
           else
             VERSION="dev"
           fi
@@ -111,13 +116,15 @@ jobs:
       - name: Rename binary with version and platform
         run: |
           cd utils/mpm/dist
-          mv mpm mpm-${{ steps.get_version.outputs.version }}-${{ matrix.os_name }}-${{ matrix.arch }}
+          # Remove symlink, keep only the real binary
+          rm -f mpm
+          mv mows mows-${{ steps.get_version.outputs.version }}-${{ matrix.os_name }}-${{ matrix.arch }}
 
       - name: Upload artifact
         uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v4
         with:
-          name: mpm-${{ matrix.os_name }}-${{ matrix.arch }}
-          path: utils/mpm/dist/mpm-*
+          name: mows-${{ matrix.os_name }}-${{ matrix.arch }}
+          path: utils/mpm/dist/mows-*
           retention-days: 7
 
   release:
@@ -137,22 +144,22 @@ jobs:
         id: get_version
         run: |
           VERSION="${{ github.ref_name }}"
-          VERSION="${VERSION#mpm-v}"
+          VERSION="${VERSION#mows-cli-v}"
           echo "version=${VERSION}" >> $GITHUB_OUTPUT
 
       - name: Create checksums
         run: |
           cd artifacts
-          for f in mpm-*; do
+          for f in mows-*; do
             sha256sum "$f" > "${f}-checksum-sha256.txt"
           done
 
       - name: Create GitHub Release
         uses: softprops/action-gh-release@a06a81a03ee405af7f2048a818ed3f03bbf83c7b # v2
         with:
-          name: mpm v${{ steps.get_version.outputs.version }}
+          name: mows v${{ steps.get_version.outputs.version }}
           draft: false
           prerelease: false
           files: |
-            artifacts/mpm-*
+            artifacts/mows-*
           generate_release_notes: true

Cargo.lock

@@ -1,33 +1,41 @@
-# MPM (MOWS Package Manager)
+# MOWS CLI (mows-cli)
+
+MOWS uses a busybox-style binary called `mows` with subcommands:
+- `mows package-manager compose ...` - Package manager compose operations
+- `mows tools ...` - Utility tools (json-to-yaml, jq, etc.)
+- `mows template ...` - Template rendering
+- `mows self-update` - Self-update
+
+A symlink `mpm` is provided as an alias for `mows package-manager`, so `mpm compose ...` is equivalent to `mows package-manager compose ...`.
 
 ## Testing Guidelines
 
 ### Config File Isolation
 
-**CRITICAL**: All tests that call `MpmConfig::load()` or `MpmConfig::save()` MUST use proper isolation to prevent modifying the user's actual config file at `~/.config/mows.cloud/mpm.yaml`.
+**CRITICAL**: All tests that call `MowsConfig::load()` or `MowsConfig::save()` MUST use proper isolation to prevent modifying the user's actual config file at `~/.config/mows.cloud/mows.yaml`.
 
 #### Recommended: Use TestConfigGuard (for unit tests)
 
-The `TestConfigGuard` helper in `src/compose/config.rs` provides RAII-based isolation:
+The `TestConfigGuard` helper in `src/package_manager/compose/config.rs` provides RAII-based isolation:
 
 ```rust
 #[test]
 fn test_config_persistence() {
     let _guard = TestConfigGuard::new();  // Sets up isolated environment
 
-    let mut config = MpmConfig::default();
+    let mut config = MowsConfig::default();
     config.set_update_available("1.0.0".to_string());
     config.save().unwrap();
 
-    let loaded = MpmConfig::load().unwrap();
+    let loaded = MowsConfig::load().unwrap();
     assert_eq!(loaded.update.unwrap().available_version, "1.0.0");
 }  // Guard automatically cleans up when dropped
 ```
 
 The guard:
 1. Acquires a mutex to prevent concurrent test interference
 2. Creates a temporary file for the config
-3. Sets `MPM_CONFIG_PATH` to the temp file
+3. Sets `MOWS_CONFIG_PATH` to the temp file
 4. Automatically cleans up when dropped
 
 #### Alternative: Manual Setup (if needed outside config module)
@@ -39,20 +47,20 @@ use std::env;
 #[test]
 fn test_example() {
     let temp_config = NamedTempFile::new().unwrap();
-    env::set_var("MPM_CONFIG_PATH", temp_config.path());
+    env::set_var("MOWS_CONFIG_PATH", temp_config.path());
 
-    // ... run test that uses MpmConfig ...
+    // ... run test that uses MowsConfig ...
 
-    env::remove_var("MPM_CONFIG_PATH");
+    env::remove_var("MOWS_CONFIG_PATH");
 }
 ```
 
 #### For integration tests (bash):
 
 ```bash
-export MPM_CONFIG_PATH=$(mktemp)
-# ... run mpm commands ...
-rm -f "$MPM_CONFIG_PATH"
+export MOWS_CONFIG_PATH=$(mktemp)
+# ... run mows/mpm commands ...
+rm -f "$MOWS_CONFIG_PATH"
 ```
 
 ### Why This Matters
@@ -67,20 +75,27 @@ rm -f "$MPM_CONFIG_PATH"
 ### Unit Tests
 
 ```bash
-cargo test                    # Run all unit tests
-cargo test config::tests      # Run specific module tests
-cargo test -- --nocapture     # Show test output
+cargo test -p mows-cli                    # Run all unit tests
+cargo test -p mows-cli config::tests      # Run specific module tests
+cargo test -p mows-cli -- --nocapture     # Show test output
 ```
 
 ### Integration Tests (E2E)
 
+The E2E tests use two environment variables to locate the binaries:
+- `MOWS_BIN` - Path to the `mows` binary (default: `target/release/mows`)
+- `MPM_BIN` - Path to the `mpm` symlink (default: alongside the `mows` binary)
+
 ```bash
 cd tests
 ./run-all.sh                  # Run all integration tests
 ./run-all.sh test-cli         # Run specific test
 VERBOSE=1 ./run-all.sh        # Verbose output
 ```
 
+Tests that use `mows` directly (tools, template, self-update, cli) reference `$MOWS_BIN`.
+Tests that use the package manager via the symlink (compose) reference `$MPM_BIN`.
+
 ### Mock Docker Client for CI
 
 Tests that require Docker can run in CI using the mock Docker client:
@@ -96,7 +111,7 @@ The mock client (`MPM_MOCK_DOCKER=1`) simulates Docker operations:
 - `compose logs` returns empty logs
 - Container inspections return minimal mock data
 
-This allows testing the full mpm workflow without a Docker daemon.
+This allows testing the full mows workflow without a Docker daemon.
 
 ### Tests Skipped in CI
 
@@ -108,17 +123,19 @@ Note: `test-compose-up` now runs in CI using `MPM_MOCK_DOCKER=1`.
 
 ## Building
 
+The crate name is `mows-cli`, producing a binary called `mows`. A `mpm` symlink is created alongside it.
+
 ### Development
 
 ```bash
-cargo build                   # Debug build
-cargo build --release         # Release build (local)
+cargo build -p mows-cli                   # Debug build (target/debug/mows)
+cargo build -p mows-cli --release         # Release build (target/release/mows)
 ```
 
 ### Static Binary (Docker)
 
 ```bash
-bash build.sh                 # Build static binary to dist/mpm
+bash build.sh                 # Build static binary to dist/mows
 TARGETARCH=arm64 bash build.sh  # Cross-compile for ARM64
 PROFILE=dev bash build.sh     # Faster dev build
 ```

utils/mpm/CLAUDE.md

@@ -1,8 +1,12 @@
 [package]
-name = "mpm"
+name = "mows-cli"
 version = "0.6.0"
 edition = { workspace = true }
 
+[[bin]]
+name = "mows"
+path = "src/main.rs"
+
 [dependencies]
 mows-common-rust = { workspace = true }
 

utils/mpm/Cargo.toml

@@ -1,7 +1,7 @@
 ARG PROFILE="release"
-ARG SERVICE_NAME="mpm"
+ARG SERVICE_NAME="mows"
 ARG SERVICE_VERSION="0.0.0-dev"
-ARG BINARY_NAME="mpm"
+ARG BINARY_NAME="mows"
 ARG APP_STAGE_IMAGE="scratch"
 ARG TARGETARCH="amd64"
 
@@ -101,11 +101,13 @@ ARG SERVICE_NAME
 ARG SERVICE_VERSION
 ARG BINARY_NAME
 WORKDIR /app
-COPY --from=builder /${BINARY_NAME} ./mpm
+COPY --from=builder /${BINARY_NAME} ./${BINARY_NAME}
 ENV SERVICE_NAME=${SERVICE_NAME}
 ENV SERVICE_VERSION=${SERVICE_VERSION}
 STOPSIGNAL SIGTERM
 # Healthcheck verifies the binary is functional (uses exec form for scratch compatibility)
-# Note: On scratch images, exec form runs directly without a shell
-HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 CMD ["./mpm", "--help"]
-ENTRYPOINT ["./mpm"]
+# Note: On scratch images there is no shell, so we must use exec form with literal values.
+# Docker does not expand ARG/ENV variables inside exec-form JSON arrays for CMD/ENTRYPOINT.
+# BINARY_NAME is used in COPY above (where Docker does expand it), but must be literal here.
+HEALTHCHECK --interval=30s --timeout=5s --start-period=5s --retries=3 CMD ["./mows", "--help"]
+ENTRYPOINT ["./mows"]