feat: improve dependency installer robustness, add tests, and document npm TAR_ENTRY_ERROR (#26)

- installer: make Node installs idempotent (skip when node_modules is up-to-date)
  - add isDependenciesUpToDate helper
  - use cmd.exe /c on Windows to correctly invoke .cmd package managers
  - add non-interactive flags per package manager and set npm progress/log env vars
  - stream output unless JSON mode (suppress output when JSON)

- installer: improve Python venv handling
  - create .venv when missing, run uv venv if required
  - use pip from venv to install requirements with non-interactive flags
  - use --no-progress / --disable-pip-version-check and other optimizations
  - clearer user-facing messages when not in JSON mode

- installer: small fixes
  - RestoreDotnetProject: avoid setting Stdin to prevent interactive prompts
  - setupWithPoetry: improve success messaging
  - ensure child commands respect JSON output mode

- cmd: display "Installing <path> (manager)" for each project when not in JSON mode

- docs: add troubleshooting section for "npm TAR_ENTRY_ERROR" on Windows with causes and solutions (long paths, antivirus, pnpm, etc.)

- tests: add comprehensive unit tests for core commands and service packages (core, env, logmanager, orchestrator)

- misc: update ports.json timestamp and coverage mapping reorder

Author: jongio

cli/cov

@@ -611,6 +611,50 @@ services:
     project: ./src/web
 ```
 
+### Issue: npm TAR_ENTRY_ERROR on Windows
+
+**Symptoms**:
+```
+npm warn tar TAR_ENTRY_ERROR ENOENT: no such file or directory
+```
+
+**Causes**:
+1. **Windows path length limits** - Deeply nested `node_modules` can exceed the 260-character limit
+2. **File system interference** - Antivirus or security software blocking file access
+
+**Solutions**:
+
+**1. Enable Windows Long Path Support (Recommended)**:
+```powershell
+# Run PowerShell as Administrator
+New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem" `
+  -Name "LongPathsEnabled" -Value 1 -PropertyType DWORD -Force
+
+# Restart your terminal or machine
+```
+
+**2. Use a shorter project path**:
+```powershell
+# Instead of: C:\Users\username\Documents\Projects\my-long-project-name
+# Use: C:\p\myapp
+```
+
+**3. Clear npm cache and retry**:
+```powershell
+npm cache clean --force
+Remove-Item -Recurse -Force node_modules
+azd app deps
+```
+
+**4. Temporarily disable antivirus** during installation (if safe to do so)
+
+**5. Switch to pnpm** (better Windows support):
+```bash
+npm install -g pnpm
+# pnpm uses symlinks and handles long paths better
+# Then delete package-lock.json and run azd app deps
+```
+
 ### Issue: Wrong package manager detected
 
 **Cause**: Multiple lock files exist

cli/docs/commands/deps.md

@@ -334,6 +334,16 @@ func (di *DependencyInstaller) installProject(projectType, dir, manager string,
 		Dir:     dir,
 		Manager: manager,
 	}
+
+	// Show which project we're installing
+	if !output.IsJSON() {
+		relDir := dir
+		if rel, err := filepath.Rel(di.searchRoot, dir); err == nil && rel != "." {
+			relDir = rel
+		}
+		output.Item("Installing %s (%s)", relDir, manager)
+	}
+
 	if err := installFunc(); err != nil {
 		if !output.IsJSON() {
 			output.ItemWarning("Failed to install for %s: %v", dir, err)