fix(zsh): remove NVM lazy loading for agent/CLI reliability

Replace lazy loading pattern with traditional NVM initialization to fix
failures in non-interactive shells and agent/automation contexts.

Problem:
- NVM lazy loading (v2.0) used wrapper functions that only work in
  interactive shells
- AI agents, scripts, and tools using `bash -c "npm install"` failed
  because wrapper functions weren't defined in non-interactive contexts
- Commands via absolute paths bypassed wrappers but couldn't find node bins

Solution:
- Remove lazy-load wrapper functions (_lazy_load_nvm, nvm(), node(), etc)
- Restore traditional NVM initialization (source nvm.sh on shell startup)
- Accept ~200-400ms startup penalty in exchange for reliability

Trade-off:
- Shell startup is slower (~200-400ms) but node/npm work everywhere
- Users needing fast startup can re-enable lazy loading in
  ~/.franklin.local.zsh

Fixes: Node.js tools now work reliably in:
- Non-interactive shells (bash -c, zsh -c)
- Agent-spawned subprocesses
- CI/CD pipelines
- Automation scripts

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: jeremyfuksa

CHANGELOG.md

@@ -7,6 +7,26 @@ and the project aims to follow [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [2.0.2] - 2025-12-02
+
+### Changed
+
+- **BREAKING:** Removed NVM lazy loading in favor of traditional eager initialization for reliability in non-interactive shells and agent/CLI tool contexts.
+
+### Fixed
+
+- Node.js and npm now work correctly in non-interactive shells, subprocesses, and when invoked by AI agents or automation tools.
+- Commands like `bash -c "npm install"` no longer fail due to undefined wrapper functions.
+
+### Technical
+
+This patch prioritizes reliability over the ~200-400ms shell startup time penalty from loading NVM. The lazy loading pattern (introduced in v2.0) was causing failures when:
+- Agents spawned non-interactive subshells
+- Scripts used absolute paths to node/npm
+- Commands were invoked via `bash -c` or similar
+
+Users who need sub-100ms startup can re-enable lazy loading via `~/.franklin.local.zsh`.
+
 ## [2.0.1] - 2025-12-02
 
 ### Added

VERSION

@@ -1 +1 @@
-2.0.1
+2.0.2

franklin/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "franklin-cli"
-version = "2.0.1"
+version = "2.0.2"
 description = "A modern Zsh environment manager with cross-platform support"
 authors = [
     {name = "Jeremy Fuksa", email = "jeremy.fuksa@gmail.com"}

franklin/templates/zshrc.zsh

@@ -213,41 +213,14 @@ if command -v starship >/dev/null 2>&1; then
     eval "$(starship init zsh)"
 fi
 
-# --- NVM Lazy Loading ---
-# NVM is expensive to load on every shell startup, so we lazy-load it
-# The first time you run 'nvm', 'node', 'npm', or 'npx', it will load NVM
-
+# --- NVM (Node Version Manager) ---
+# Load NVM if installed
 export NVM_DIR="${HOME}/.nvm"
+[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
+[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"
 
-# Lazy-load function
-_lazy_load_nvm() {
-    unset -f nvm node npm npx
-    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
-    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"
-}
-
-nvm() {
-    _lazy_load_nvm
-    nvm "$@"
-}
-
-node() {
-    _lazy_load_nvm
-    node "$@"
-}
-
-npm() {
-    _lazy_load_nvm
-    npm "$@"
-}
-
-npx() {
-    _lazy_load_nvm
-    npx "$@"
-}
-
-# --- UV (Python Package Manager) Lazy Loading ---
-# Similar to NVM, lazy-load uv
+# --- UV (Python Package Manager) ---
+# Ensure uv is on PATH if installed
 if [ -f "${HOME}/.local/bin/uv" ]; then
     export PATH="${HOME}/.local/bin:${PATH}"
 fi