@magentrix-corp/magentrix-cli 1.3.7 → 1.3.9

package/README.md

@@ -367,7 +367,7 @@ src/
 
 > **⚠️ IMPORTANT: Deleting Iris Apps**
 >
-> **NEVER manually delete folders from `src/iris-apps/`!** Always use the `magentrix iris-delete` command to remove Iris apps. Manual deletion will cause:
+> **NEVER manually delete folders from `src/iris-apps/`!** Always use the `magentrix iris-app-delete` command to remove Iris apps. Manual deletion will cause:
 > - No recovery backup created (you cannot restore the app)
 > - App remains on the Magentrix server (orphaned)
 > - Cache becomes out of sync (causes errors on next publish)
@@ -375,7 +375,7 @@ src/
 >
 > **Correct way to delete an Iris app:**
 > ```bash
-> magentrix iris-delete
+> magentrix iris-app-delete
 > ```
 
 ### File Extensions
@@ -454,7 +454,7 @@ The tool supports all file types including:
 
 MagentrixCLI supports deploying Vue.js applications (Iris apps) to your Magentrix instance. These apps are built with Vue.js and Module Federation, allowing you to create custom frontend experiences.
 
-> **⚠️ CRITICAL: Always use `magentrix iris-delete` to remove Iris apps!**
+> **⚠️ CRITICAL: Always use `magentrix iris-app-delete` to remove Iris apps!**
 >
 > Never manually delete folders from `src/iris-apps/`. Manual deletion bypasses backups, leaves orphaned apps on the server, and corrupts the cache. See [Deleting an Iris app](#delete-an-iris-app) for proper deletion.
 
@@ -469,7 +469,7 @@ The Iris deployment workflow:
 
 #### Link a Vue Project
 ```bash
-magentrix iris-link
+magentrix iris-app-link
 ```
 **What it does**: Opens an interactive menu to manage linked Vue.js projects. Projects are stored globally so they persist across Magentrix workspaces.
 
@@ -487,7 +487,7 @@ magentrix iris-link
 
 #### Build and Stage
 ```bash
-magentrix vue-build-stage
+magentrix vue-run-build
 ```
 **What it does**: Builds a linked Vue project and copies the output to `src/iris-apps/<slug>/` for publishing.
 
@@ -511,7 +511,7 @@ magentrix vue-build-stage
 
 #### Vue Development Server
 ```bash
-magentrix run-dev
+magentrix vue-run-dev
 ```
 **What it does**: Starts the Vue development server with platform assets (CSS, fonts) automatically injected from your Magentrix instance.
 
@@ -528,7 +528,7 @@ magentrix run-dev
 
 #### Delete an Iris App
 ```bash
-magentrix iris-delete
+magentrix iris-app-delete
 ```
 **What it does**: Safely delete a published Iris app with automatic recovery backup.
 
@@ -544,11 +544,11 @@ magentrix iris-delete
 **Safety features:**
 - Automatic backup before deletion
 - Must type slug name to confirm
-- Recovery possible with `iris-recover`
+- Recovery possible with `iris-app-recover`
 
 #### Recover a Deleted App
 ```bash
-magentrix iris-recover
+magentrix iris-app-recover
 ```
 **What it does**: Restore a deleted Iris app from automatic backup.
 
@@ -585,7 +585,7 @@ export const config = {
 ```bash
 VITE_SITE_URL = https://yourinstance.magentrix.com
 VITE_REFRESH_TOKEN = your-api-key
-VITE_ASSETS = '[]'  # Injected automatically by run-dev
+VITE_ASSETS = '[]'  # Injected automatically by vue-run-dev
 ```
 
 **Accepted field names in config.ts:**
@@ -597,14 +597,14 @@ VITE_ASSETS = '[]'  # Injected automatically by run-dev
 ### Command Availability
 
 **In Vue project directories** (detected by presence of `config.ts`):
-- ✓ `magentrix iris-link` - Link project to CLI
-- ✓ `magentrix vue-build-stage` - Build and stage (prompts for target workspace)
-- ✓ `magentrix run-dev` - Start dev server (uses `.env.development` credentials)
+- ✓ `magentrix iris-app-link` - Link project to CLI
+- ✓ `magentrix vue-run-build` - Build and stage (prompts for target workspace)
+- ✓ `magentrix vue-run-dev` - Start dev server (uses `.env.development` credentials)
 - ✓ `magentrix update` - Update CLI to latest version
 
 **In Magentrix workspace directories** (has `.magentrix/` folder):
 - ✓ All standard commands (`setup`, `pull`, `publish`, etc.)
-- ✓ All Iris commands (`vue-build-stage`, `iris-delete`, `iris-recover`, etc.)
+- ✓ All Iris commands (`vue-run-build`, `iris-app-delete`, `iris-app-recover`, etc.)
 
 **Note**: The `setup` command cannot be run inside a Vue project directory - run it from your Magentrix workspace. Commands like `pull`, `publish`, `autopublish` require a Magentrix workspace.
 
@@ -612,31 +612,31 @@ VITE_ASSETS = '[]'  # Injected automatically by run-dev
 
 ```bash
 # First time setup
-magentrix iris-link           # Link your Vue project
+magentrix iris-app-link           # Link your Vue project
 
 # Development (run from Vue project folder)
 cd ~/my-vue-app               # Work from your Vue project
-magentrix run-dev             # Start dev server with platform assets
+magentrix vue-run-dev             # Start dev server with platform assets
 # Make changes, test locally
 # Press Ctrl+C to stop
 
 # Deployment - Option A (from Vue project folder)
 cd ~/my-vue-app               # Work from your Vue project
-magentrix vue-build-stage     # Build and select workspace to stage into
+magentrix vue-run-build     # Build and select workspace to stage into
 # Prompted: "Do you want to publish to Magentrix now?" → Yes/No
 
 # Deployment - Option B (from Magentrix workspace)
 cd ~/magentrix-workspace      # Navigate to Magentrix workspace
-magentrix vue-build-stage --path ~/my-vue-app  # Build and stage
+magentrix vue-run-build --path ~/my-vue-app  # Build and stage
 # Prompted: "Do you want to publish to Magentrix now?" → Yes/No
 # If autopublish is running, it auto-deploys instead
 
 # Deleting an app (from workspace)
-magentrix iris-delete         # Select app, confirm, auto-backup created
+magentrix iris-app-delete         # Select app, confirm, auto-backup created
 magentrix publish             # Sync deletion to server
 
 # Recovering a deleted app (from workspace)
-magentrix iris-recover        # Select backup, restore files
+magentrix iris-app-recover        # Select backup, restore files
 magentrix publish             # Sync recovery to server
 ```
 
@@ -649,39 +649,39 @@ For automatic deployment during development:
 magentrix autopublish
 
 # Terminal 2: Build and stage after making changes
-magentrix vue-build-stage
+magentrix vue-run-build
 # Autopublish will detect the changes and upload automatically
 ```
 
 ### Troubleshooting Iris Apps
 
-#### Running vue-build-stage from different locations
+#### Running vue-run-build from different locations
 
-The `vue-build-stage` command works from both locations:
+The `vue-run-build` command works from both locations:
 
 **From Vue project directory:**
 ```bash
 cd ~/my-vue-app
-magentrix vue-build-stage  # Prompts for which workspace to stage into
+magentrix vue-run-build  # Prompts for which workspace to stage into
 ```
 
 **From Magentrix workspace:**
 ```bash
 cd ~/magentrix-workspace
-magentrix vue-build-stage  # Prompts for which Vue project to build
-# Or with path: magentrix vue-build-stage --path ~/my-vue-app
+magentrix vue-run-build  # Prompts for which Vue project to build
+# Or with path: magentrix vue-run-build --path ~/my-vue-app
 ```
 
 #### "No Magentrix workspaces found"
 When running from a Vue project, the command looks for registered workspaces in the global config. To register a workspace:
 1. Navigate to your Magentrix workspace
 2. Run `magentrix setup` (this automatically registers it)
-3. Or specify workspace manually: `magentrix vue-build-stage --workspace /path/to/workspace`
+3. Or specify workspace manually: `magentrix vue-run-build --workspace /path/to/workspace`
 
 **Note**: Existing workspaces are auto-registered when you run any command from them.
 
 #### "Publishing Iris apps from an out-of-sync workspace is not allowed"
-When running `vue-build-stage` from a Vue project, the CLI checks if the target workspace is in sync with the server. If there are pending remote changes, you must pull first.
+When running `vue-run-build` from a Vue project, the CLI checks if the target workspace is in sync with the server. If there are pending remote changes, you must pull first.
 
 **Why this is required:**
 - Prevents deployment conflicts
@@ -691,7 +691,7 @@ When running `vue-build-stage` from a Vue project, the CLI checks if the target
 **To resolve:**
 1. Navigate to the workspace: `cd /path/to/workspace`
 2. Pull latest changes: `magentrix pull`
-3. Re-run `vue-build-stage` from your Vue project
+3. Re-run `vue-run-build` from your Vue project
 
 #### "Missing required field in config.ts: slug (appPath)"
 Your Vue project's `config.ts` is missing the app identifier. Add an `appPath` or `slug` field.
@@ -720,9 +720,9 @@ The CLI looks for config in these locations:
 #### Deleting an Iris app
 To remove an Iris app:
 ```bash
-magentrix iris-delete
+magentrix iris-app-delete
 ```
-This creates an automatic recovery backup before deletion. You can restore using `magentrix iris-recover`.
+This creates an automatic recovery backup before deletion. You can restore using `magentrix iris-app-recover`.
 
 **Permission errors:**
 If you get "Permission Denied" when deleting local files:
@@ -733,14 +733,14 @@ If you get "Permission Denied" when deleting local files:
 #### Recovering a deleted app
 To restore a deleted Iris app:
 ```bash
-magentrix iris-recover --list  # See all available backups
-magentrix iris-recover         # Select and restore a backup
+magentrix iris-app-recover --list  # See all available backups
+magentrix iris-app-recover         # Select and restore a backup
 magentrix publish              # Sync to server
 ```
 
 **Important**: After recovery, you must run `magentrix publish` to sync the app back to the Magentrix server.
 
-#### Changes not detected after vue-build-stage
+#### Changes not detected after vue-run-build
 The CLI uses content hash tracking to detect changes. If you rebuild without changes, `magentrix publish` will show "All files are in sync — nothing to publish!" This is expected behavior and saves unnecessary uploads.
 
 ---
@@ -798,16 +798,16 @@ magentrix status        # Verify everything is in sync
 **Option A: From Vue project folder**
 ```bash
 cd ~/my-vue-app               # Navigate to your Vue project
-magentrix iris-link           # Link project (first time only)
-magentrix vue-build-stage     # Build and select workspace to stage into
+magentrix iris-app-link           # Link project (first time only)
+magentrix vue-run-build     # Build and select workspace to stage into
 # Prompted: "Do you want to publish to Magentrix now?" → Yes/No
 ```
 
 **Option B: From Magentrix workspace**
 ```bash
 cd ~/magentrix-workspace      # Navigate to Magentrix workspace
-magentrix iris-link --path ~/my-vue-app  # Link project (first time only)
-magentrix vue-build-stage --path ~/my-vue-app  # Build and stage
+magentrix iris-app-link --path ~/my-vue-app  # Link project (first time only)
+magentrix vue-run-build --path ~/my-vue-app  # Build and stage
 # Prompted: "Do you want to publish to Magentrix now?" (unless autopublish is running)
 ```
 
@@ -816,13 +816,13 @@ magentrix vue-build-stage --path ~/my-vue-app  # Build and stage
 ### Deleting and Recovering Apps
 ```bash
 # Delete an app (creates automatic backup)
-magentrix iris-delete         # Select app, confirm deletion
+magentrix iris-app-delete         # Select app, confirm deletion
 
 # View available backups
-magentrix iris-recover --list
+magentrix iris-app-recover --list
 
 # Recover a deleted app
-magentrix iris-recover        # Select backup, restore
+magentrix iris-app-recover        # Select backup, restore
 magentrix publish             # Sync recovery to server
 ```
 
@@ -1107,11 +1107,11 @@ magentrix status        # Shows sync status
 - `magentrix status` - Check sync status
 - `magentrix autopublish` - Auto-sync mode
 - `magentrix update` - Update to latest version
-- `magentrix iris-link` - Link Vue.js projects for deployment
-- `magentrix vue-build-stage` - Build and stage Vue.js apps
-- `magentrix run-dev` - Start Vue dev server with platform assets
-- `magentrix iris-delete` - Delete an Iris app with recovery backup
-- `magentrix iris-recover` - Recover a deleted Iris app
+- `magentrix iris-app-link` - Link Vue.js projects for deployment
+- `magentrix vue-run-build` - Build and stage Vue.js apps
+- `magentrix vue-run-dev` - Start Vue dev server with platform assets
+- `magentrix iris-app-delete` - Delete an Iris app with recovery backup
+- `magentrix iris-app-recover` - Recover a deleted Iris app
 
 ---
 
@@ -1123,6 +1123,6 @@ Once you're comfortable with basic usage:
 2. **Learn the autopublish workflow** for faster development
 3. **Explore conflict resolution** if you work in a team
 4. **Check out templates** created by the `create` command to understand best practices
-5. **Deploy Vue.js apps** using `iris-link`, `vue-build-stage`, and `run-dev` commands
+5. **Deploy Vue.js apps** using `iris-app-link`, `vue-run-build`, and `vue-run-dev` commands
 
 Happy coding with MagentrixCLI! 🚀

package/actions/iris/buildStage.js

@@ -66,7 +66,7 @@ function isMagentrixWorkspace() {
 }
 
 /**
- * vue-build-stage command - Build a Vue project and stage to CLI workspace.
+ * vue-run-build command - Build a Vue project and stage to CLI workspace.
  *
  * Two modes of operation:
  * 1. Run from Magentrix workspace: prompts for which Vue project to build
@@ -398,28 +398,9 @@ async function buildFromVueProject(options) {
         console.log(chalk.green('\u2713 Build output validated'));
     }
 
-    // Stage to selected workspace
+    // Check if workspace might be out of sync and offer to pull first (BEFORE staging)
+    // This ensures pull doesn't overwrite our staged files
     console.log();
-    console.log(chalk.blue(`Staging to workspace: ${workspacePath}`));
-
-    const stageResult = stageToWorkspace(distPath, slug, workspacePath);
-
-    if (!stageResult.success) {
-        console.log(chalk.red(`Failed to stage: ${stageResult.error}`));
-        return;
-    }
-
-    console.log(chalk.green(`\u2713 Staged ${stageResult.fileCount} files to ${stageResult.stagedPath}`));
-
-    // Summary
-    console.log();
-    console.log(chalk.green('─'.repeat(48)));
-    console.log(chalk.green.bold('\u2713 Build & Stage Complete!'));
-    console.log();
-    console.log(chalk.gray(`Staged to: ${stageResult.stagedPath}`));
-    console.log();
-
-    // Check if workspace might be out of sync and offer to pull first
     console.log(chalk.gray('Checking workspace sync status...'));
     const syncStatus = await checkWorkspaceSyncStatus(workspacePath);
 
@@ -444,7 +425,7 @@ async function buildFromVueProject(options) {
                 console.log(chalk.yellow('Pull encountered issues. You may want to resolve them manually.'));
 
                 const continueAnyway = await confirm({
-                    message: 'Do you still want to continue with publishing?',
+                    message: 'Do you still want to continue with staging and publishing?',
                     default: false
                 });
 
@@ -453,7 +434,8 @@ async function buildFromVueProject(options) {
                     console.log(chalk.cyan('To continue manually:'));
                     console.log(chalk.white(`  1. Navigate to workspace: ${chalk.yellow(`cd "${workspacePath}"`)}`));
                     console.log(chalk.white(`  2. Run ${chalk.yellow('magentrix pull')} to resolve conflicts`));
-                    console.log(chalk.white(`  3. Run ${chalk.yellow('magentrix publish')} to deploy`));
+                    console.log(chalk.white(`  3. Run ${chalk.yellow('magentrix vue-run-build --skip-build')} to stage`));
+                    console.log(chalk.white(`  4. Run ${chalk.yellow('magentrix publish')} to deploy`));
                     return;
                 }
             }
@@ -474,6 +456,27 @@ async function buildFromVueProject(options) {
         console.log(chalk.green('✓ Workspace is in sync'));
     }
 
+    // Stage to selected workspace (AFTER pull to avoid overwriting)
+    console.log();
+    console.log(chalk.blue(`Staging to workspace: ${workspacePath}`));
+
+    const stageResult = stageToWorkspace(distPath, slug, workspacePath);
+
+    if (!stageResult.success) {
+        console.log(chalk.red(`Failed to stage: ${stageResult.error}`));
+        return;
+    }
+
+    console.log(chalk.green(`\u2713 Staged ${stageResult.fileCount} files to ${stageResult.stagedPath}`));
+
+    // Summary
+    console.log();
+    console.log(chalk.green('─'.repeat(48)));
+    console.log(chalk.green.bold('\u2713 Build & Stage Complete!'));
+    console.log();
+    console.log(chalk.gray(`Staged to: ${stageResult.stagedPath}`));
+    console.log();
+
     // Ask if they want to publish now
     const shouldPublish = await confirm({
         message: 'Do you want to publish to Magentrix now?',
@@ -530,13 +533,24 @@ async function checkWorkspaceSyncStatus(workspacePath) {
         });
 
         child.on('close', (code) => {
-            // Check output for signs of remote changes or conflicts
+            // Check output for specific issue indicators from status command
+            // Note: We avoid checking for "remote" as it appears in normal output
+            // ("Checking local files vs remote Magentrix...")
             const lowerOutput = output.toLowerCase();
-            const needsPull = lowerOutput.includes('conflict') ||
-                              lowerOutput.includes('remote') ||
-                              lowerOutput.includes('server has changes') ||
-                              lowerOutput.includes('out of sync') ||
-                              lowerOutput.includes('modified on server');
+
+            // If everything is in sync, this message appears
+            const isInSync = lowerOutput.includes('all files are up to date') ||
+                             lowerOutput.includes('in sync');
+
+            // Check for specific issue keywords from logFileStatus output
+            const hasConflict = lowerOutput.includes('conflict');
+            const isOutdated = lowerOutput.includes('outdated');
+            const isAhead = lowerOutput.includes('is ahead');
+            const isMissing = lowerOutput.includes('is missing');
+            const hasContentMismatch = lowerOutput.includes('content mismatch');
+            const hasWarnings = lowerOutput.includes('⚠️') || lowerOutput.includes('🛑');
+
+            const needsPull = !isInSync && (hasConflict || isOutdated || isAhead || isMissing || hasContentMismatch || hasWarnings);
 
             resolvePromise({ checked: code === 0, needsPull });
         });
@@ -593,7 +607,7 @@ async function selectWorkspace() {
         console.log(chalk.white(`  • Or run ${chalk.cyan('magentrix setup')} in a new directory to create one`));
         console.log();
         console.log(chalk.gray('Or specify a workspace path directly:'));
-        console.log(chalk.white(`  ${chalk.cyan('magentrix vue-build-stage --workspace /path/to/workspace')}`));
+        console.log(chalk.white(`  ${chalk.cyan('magentrix vue-run-build --workspace /path/to/workspace')}`));
         console.log();
 
         // Allow manual entry
@@ -711,8 +725,8 @@ async function selectProject() {
         console.log(chalk.yellow('No linked Vue projects found.'));
         console.log();
         console.log(chalk.gray('To get started:'));
-        console.log(chalk.white(`  1. Link a Vue project: ${chalk.cyan('magentrix iris-link')}`));
-        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix vue-build-stage --path /path/to/vue-project')}`));
+        console.log(chalk.white(`  1. Link a Vue project: ${chalk.cyan('magentrix iris-app-link')}`));
+        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix vue-run-build --path /path/to/vue-project')}`));
         console.log();
     }
 

package/actions/iris/delete.js

@@ -12,7 +12,7 @@ import { EXPORT_ROOT, IRIS_APPS_DIR } from '../../vars/global.js';
 const config = new Config();
 
 /**
- * iris-delete command - Delete a published Iris app with backup and recovery.
+ * iris-app-delete command - Delete a published Iris app with backup and recovery.
  */
 export const irisDelete = async () => {
     process.stdout.write('\x1Bc'); // Clear console
@@ -41,7 +41,7 @@ export const irisDelete = async () => {
         console.log(chalk.yellow('No published Iris apps found.'));
         console.log();
         console.log(chalk.gray('Published apps appear here after running:'));
-        console.log(chalk.white(`  1. ${chalk.cyan('magentrix vue-build-stage')}`));
+        console.log(chalk.white(`  1. ${chalk.cyan('magentrix vue-run-build')}`));
         console.log(chalk.white(`  2. ${chalk.cyan('magentrix publish')}`));
         console.log();
         return;
@@ -81,7 +81,7 @@ export const irisDelete = async () => {
     console.log(chalk.red(`  • Navigation menu entry on Magentrix`));
     console.log();
     console.log(chalk.yellow('A recovery backup will be created before deletion.'));
-    console.log(chalk.gray('You can restore using: ') + chalk.cyan('magentrix iris-recover'));
+    console.log(chalk.gray('You can restore using: ') + chalk.cyan('magentrix iris-app-recover'));
     console.log(chalk.red('─'.repeat(48)));
     console.log();
 
@@ -142,7 +142,7 @@ export const irisDelete = async () => {
 
     if (!deleteResult.success && deleteResult.error !== 'App not found on server (already deleted)') {
         console.log(chalk.red(`Failed to delete from server: ${deleteResult.error}`));
-        console.log(chalk.yellow('Backup preserved. Use ') + chalk.cyan('magentrix iris-recover') + chalk.yellow(' to restore.'));
+        console.log(chalk.yellow('Backup preserved. Use ') + chalk.cyan('magentrix iris-app-recover') + chalk.yellow(' to restore.'));
         return;
     }
 
@@ -204,7 +204,7 @@ export const irisDelete = async () => {
     console.log();
     console.log(chalk.cyan('Recovery:'));
     console.log(chalk.white(`  Backup saved to: ${chalk.gray(backupResult.backupPath)}`));
-    console.log(chalk.white(`  To restore, run: ${chalk.cyan('magentrix iris-recover')}`));
+    console.log(chalk.white(`  To restore, run: ${chalk.cyan('magentrix iris-app-recover')}`));
     console.log();
 };
 

package/actions/iris/dev.js

@@ -18,7 +18,7 @@ import {
 } from '../../utils/iris/linker.js';
 
 /**
- * run-dev command - Start Vue dev server with platform assets injected.
+ * vue-run-dev command - Start Vue dev server with platform assets injected.
  *
  * Uses credentials from .env.development (VITE_REFRESH_TOKEN, VITE_SITE_URL).
  * Assets are updated in .env.development (VITE_ASSETS) and kept between runs.
@@ -233,8 +233,8 @@ async function selectProject() {
         console.log(chalk.yellow('No linked Vue projects found.'));
         console.log();
         console.log(chalk.gray('To get started:'));
-        console.log(chalk.white(`  1. Link a Vue project: ${chalk.cyan('magentrix iris-link')}`));
-        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix run-dev --path /path/to/vue-project')}`));
+        console.log(chalk.white(`  1. Link a Vue project: ${chalk.cyan('magentrix iris-app-link')}`));
+        console.log(chalk.white(`  2. Or specify path: ${chalk.cyan('magentrix vue-run-dev --path /path/to/vue-project')}`));
         console.log();
     }
 

package/actions/iris/link.js

@@ -12,7 +12,7 @@ import {
 import { formatMissingConfigError, formatConfigErrors, readVueConfig } from '../../utils/iris/config-reader.js';
 
 /**
- * iris-link command - Link a Vue project to the CLI.
+ * iris-app-link command - Link a Vue project to the CLI.
  *
  * Options:
  *   --path <dir>    Specify Vue project path directly
@@ -265,7 +265,7 @@ async function linkProjectDirect(projectPath) {
         console.log(chalk.green(`\u2713 Project linked successfully!`));
         console.log();
         console.log(chalk.cyan('Next steps:'));
-        console.log(chalk.white(`  1. Build and stage: ${chalk.yellow('magentrix vue-build-stage')}`));
+        console.log(chalk.white(`  1. Build and stage: ${chalk.yellow('magentrix vue-run-build')}`));
         console.log(chalk.white(`  2. Publish to server: ${chalk.yellow('magentrix publish')}`));
         console.log(chalk.white(`     Or use ${chalk.yellow('magentrix autopublish')} for automatic publishing`));
     }

package/actions/iris/recover.js

@@ -8,7 +8,7 @@ import { showPermissionError } from '../../utils/permissionError.js';
 import { EXPORT_ROOT, IRIS_APPS_DIR } from '../../vars/global.js';
 
 /**
- * iris-recover command - Restore a deleted Iris app from backup.
+ * iris-app-recover command - Restore a deleted Iris app from backup.
  *
  * Options:
  *   --list      List all available backups
@@ -29,7 +29,7 @@ export const irisRecover = async (options = {}) => {
         console.log(chalk.yellow('No recovery backups found.'));
         console.log();
         console.log(chalk.gray('Backups are created automatically when you delete an Iris app.'));
-        console.log(chalk.white(`Use: ${chalk.cyan('magentrix iris-delete')}`));
+        console.log(chalk.white(`Use: ${chalk.cyan('magentrix iris-app-delete')}`));
         console.log();
         return;
     }
@@ -50,7 +50,7 @@ export const irisRecover = async (options = {}) => {
             console.log();
         });
 
-        console.log(chalk.white(`To recover, run: ${chalk.cyan('magentrix iris-recover')}`));
+        console.log(chalk.white(`To recover, run: ${chalk.cyan('magentrix iris-app-recover')}`));
         console.log();
         return;
     }

package/bin/magentrix.js

@@ -47,9 +47,9 @@ function requireMagentrixWorkspace(fn) {
             console.error(chalk.yellow('It looks like you\'re in a Vue project directory.'));
             console.error(chalk.gray('This command requires a Magentrix workspace with global API key and instance URL.\n'));
             console.error(chalk.cyan('Available commands in Vue projects:'));
-            console.error(chalk.gray('  • magentrix iris-link'));
-            console.error(chalk.gray('  • magentrix vue-build-stage'));
-            console.error(chalk.gray('  • magentrix run-dev'));
+            console.error(chalk.gray('  • magentrix iris-app-link'));
+            console.error(chalk.gray('  • magentrix vue-run-build'));
+            console.error(chalk.gray('  • magentrix vue-run-dev'));
             console.error(chalk.gray('  • magentrix update\n'));
             process.exit(1);
         }
@@ -150,11 +150,11 @@ program
                 { name: 'publish', desc: 'Publish pending changes to the remote server', icon: '📤 ' },
                 { name: 'autopublish', desc: 'Watch & sync changes in real time', icon: '🔄 ' },
                 { name: 'update', desc: 'Update MagentrixCLI to the latest version', icon: '⬆️  ' },
-                { name: 'iris-link', desc: 'Link a Vue project to the CLI', icon: '🔗 ' },
-                { name: 'vue-build-stage', desc: 'Build Vue project and stage for publish', icon: '🏗️  ' },
-                { name: 'run-dev', desc: 'Start Vue dev server with platform assets', icon: '🌐 ' },
-                { name: 'iris-delete', desc: 'Delete an Iris app with backup', icon: '🗑️  ' },
-                { name: 'iris-recover', desc: 'Recover a deleted Iris app from backup', icon: '♻️  ' }
+                { name: 'iris-app-link', desc: 'Link a Vue project to the CLI', icon: '🔗 ' },
+                { name: 'vue-run-build', desc: 'Build Vue project and stage for publish', icon: '🏗️  ' },
+                { name: 'vue-run-dev', desc: 'Start Vue dev server with platform assets', icon: '🌐 ' },
+                { name: 'iris-app-delete', desc: 'Delete an Iris app with backup', icon: '🗑️  ' },
+                { name: 'iris-app-recover', desc: 'Recover a deleted Iris app from backup', icon: '♻️  ' }
             ];
 
             const maxNameLen = Math.max(...commands.map(c => c.name.length));
@@ -285,7 +285,7 @@ program
 
 // Iris commands for Vue.js app management
 program
-    .command('iris-link')
+    .command('iris-app-link')
     .description('Link a Vue project to the CLI for deployment')
     .option('--path <path>', 'Path to the Vue project')
     .option('--unlink', 'Unlink a project instead of linking')
@@ -294,7 +294,7 @@ program
     .action(irisLink);
 
 program
-    .command('vue-build-stage')
+    .command('vue-run-build')
     .description('Build a Vue project and stage it for publishing')
     .option('--path <path>', 'Path to the Vue project')
     .option('--skip-build', 'Skip build step and use existing dist/')
@@ -302,19 +302,19 @@ program
     .action(vueBuildStage);
 
 program
-    .command('run-dev')
+    .command('vue-run-dev')
     .description('Start Vue dev server with platform assets injected')
     .option('--path <path>', 'Path to the Vue project')
     .option('--no-inject', 'Skip asset injection')
     .action(irisDev);
 
 program
-    .command('iris-delete')
+    .command('iris-app-delete')
     .description('Delete a published Iris app with recovery backup')
     .action(irisDelete);
 
 program
-    .command('iris-recover')
+    .command('iris-app-recover')
     .description('Recover a deleted Iris app from backup')
     .option('--list', 'List available recovery backups')
     .action(irisRecover);
@@ -328,9 +328,9 @@ program.argument('[command]', 'command to run').action((cmd) => {
             console.error(chalk.yellow('It looks like you\'re in a Vue project directory.'));
             console.error(chalk.gray('This command requires a Magentrix workspace with global API key and instance URL.\n'));
             console.error(chalk.cyan('Available commands in Vue projects:'));
-            console.error(chalk.gray('  • magentrix iris-link'));
-            console.error(chalk.gray('  • magentrix vue-build-stage'));
-            console.error(chalk.gray('  • magentrix run-dev'));
+            console.error(chalk.gray('  • magentrix iris-app-link'));
+            console.error(chalk.gray('  • magentrix vue-run-build'));
+            console.error(chalk.gray('  • magentrix vue-run-dev'));
             console.error(chalk.gray('  • magentrix update\n'));
             process.exit(1);
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@magentrix-corp/magentrix-cli",
-  "version": "1.3.7",
+  "version": "1.3.9",
   "description": "CLI tool for synchronizing local files with Magentrix cloud platform",
   "main": "index.js",
   "type": "module",

package/utils/iris/builder.js

@@ -281,7 +281,7 @@ To fix this:
 
   2. Fix any compilation errors shown above
 
-  3. Run 'magentrix vue-build-stage' again
+  3. Run 'magentrix vue-run-build' again
 
 Alternatively, use --skip-build to stage an existing dist/ folder.`;
 }

package/utils/iris/linker.js

@@ -378,7 +378,7 @@ export function updateLastBuild(slug) {
  */
 export function formatLinkedProjects(projects) {
     if (!projects || projects.length === 0) {
-        return 'No Vue projects linked.\n\nUse `magentrix iris-link` to link a project.';
+        return 'No Vue projects linked.\n\nUse `magentrix iris-app-link` to link a project.';
     }
 
     const lines = [