eforge-update

# /eforge:update Check for available eforge updates and walk through updating the npm package, restarting the daemon, and updating the <!-- parity-skip-start -->Pi package<!-- parity-skip-end -->. ## Workflow ### Step 1: Check Current CLI Version Run `npx -y @eforge-build/eforge --version` to get the currently installed CLI version. Save this as `currentVersion`. If the command fails, report that eforge is not installed and stop. ### Step 2: Check Latest Available Version Run `npm view @eforge-build/eforge version` to get the latest published version. Save this as `latestVersion`. ### Step 3: Compare Versions If `currentVersion` equals `latestVersion`: > eforge is already up to date (v{currentVersion}). No action needed. **Stop here.** ### Step 4: Update the npm Package Determine the install type by running `which eforge` and inspecting the resolved path: - **Global install** (path contains a global `node_modules`, e.g. `/usr/local/lib/node_modules` or `~/.npm/`): Run `npm install -g @eforge-build/eforge@latest` - **npx usage** (no global install found): Skip this step - npx always fetches the latest version automatically. After the install completes, run `npx -y @eforge-build/eforge --version` again to confirm the new version. Save this as `newCliVersion`. ### Step 5: Restart the Daemon **Before stopping the daemon**, call the `eforge_status` tool to check for active builds. - If the response contains `status: 'running'`, **abort the update immediately** an...