docs(Mountain): Streamline extension path and NodeResolver module docs

Simplify comments in ScanPathConfigure for extension skip flags and builtin path override to be more concise while preserving the technical details.

Condense the NodeResolver module docstring from verbose prose to a compact ladder list showing the resolution order: LAND_NODE_BINARY → shipped runtime → fnm/volta/asdf/nvm → homebrew → PATH. The resolution behavior is unchanged, only the documentation format is improved for scannability.

Author: NikolaRHristov

Source/Binary/Extension/ScanPathConfigure.rs

@@ -40,13 +40,11 @@ pub fn ScanPathConfigure(AppState:&std::sync::Arc<ApplicationState>) -> Result<V
 		.map_err(MapLockError)
 		.map_err(|e| format!("Failed to lock ExtensionScanPaths: {}", e))?;
 
-	// Atom J3: kernel / minimal profiles set LAND_SKIP_BUILTIN_EXTENSIONS=true
-	// to ship without any bundled extensions. The user-extensions path
-	// (`~/.land/extensions`) still scans so VSIX-installed extensions work.
-	//
-	// Atom U1: `.env.Land.Extensions` also exposes `LAND_DISABLE_BUILTIN_EXTENSIONS`
-	// - same effect, different name. Accept both so the skill-file env and
-	// the legacy SKIP flag don't diverge.
+	// Skip all built-in extensions when either the legacy
+	// `LAND_SKIP_BUILTIN_EXTENSIONS` or the `.env.Land.Extensions` flag
+	// `LAND_DISABLE_BUILTIN_EXTENSIONS` is set. Both accepted so kernel /
+	// minimal profiles and the skill-file env stay in sync. User scan path
+	// still runs so VSIX-installed extensions remain visible.
 	let SkipBuiltins = matches!(std::env::var("LAND_SKIP_BUILTIN_EXTENSIONS").as_deref(), Ok("1") | Ok("true"))
 		|| matches!(std::env::var("LAND_DISABLE_BUILTIN_EXTENSIONS").as_deref(), Ok("1") | Ok("true"));
 
@@ -60,10 +58,9 @@ pub fn ScanPathConfigure(AppState:&std::sync::Arc<ApplicationState>) -> Result<V
 		dev_log!("extensions", "[Extensions] [ScanPaths] Adding default scan paths...");
 	}
 
-	// Atom U1: `LAND_BUILTIN_EXTENSIONS_DIR` (from `.env.Land.Extensions`)
-	// takes precedence over the executable-relative probing chain. Useful for
-	// CI builds where the bundle layout differs from both the Tauri `.app`
-	// convention and the repo layout.
+	// `LAND_BUILTIN_EXTENSIONS_DIR` takes precedence over the executable-
+	// relative probing chain. Useful for CI builds where the bundle layout
+	// differs from both the `.app` convention and the repo layout.
 	if !SkipBuiltins {
 		if let Ok(Override) = std::env::var("LAND_BUILTIN_EXTENSIONS_DIR") {
 			let OverridePath = ExpandUserPath(&Override);

Source/ProcessManagement/NodeResolver.rs

@@ -1,26 +1,12 @@
 #![allow(non_snake_case, dead_code)]
 
-//! # Node Binary Resolver
+//! Resolves the Node.js binary used to spawn Cocoon.
 //!
-//! Resolves the Node.js binary used to spawn the Cocoon sidecar. Checks, in
-//! order:
+//! Ladder (first hit wins, cached in `OnceLock`):
+//! `LAND_NODE_BINARY` override → shipped (`Resources/Node/bin/node`) →
+//! fnm → volta → asdf → nvm → homebrew → PATH `node`.
 //!
-//! 1. **Explicit override** - `LAND_NODE_BINARY` env var. Operators set this
-//!    to pin to a specific Node install for reproducibility.
-//! 2. **Shipped runtime** - `Resources/Node/bin/node` relative to the Tauri
-//!    bundle (production) or `Target/<profile>/../Node/bin/node` relative to
-//!    the executable (dev). Ships alongside Mountain for hermetic builds.
-//! 3. **Version managers** - fnm, volta, asdf, nvm in their canonical
-//!    locations. Preferred over system PATH because the user's selected
-//!    version tracks their workspace (`.nvmrc`, `.tool-versions`).
-//! 4. **Package managers** - Homebrew on macOS/Linux, the most common way
-//!    Node gets installed on developer machines.
-//! 5. **PATH fallback** - `which node`. Last resort - works, but version is
-//!    whatever happens to be first in PATH.
-//!
-//! Every attempt is logged with its source so a log tells you exactly which
-//! Node Mountain picked and why. Resolution happens once at Cocoon spawn
-//! time; cached for the life of the Mountain process.
+//! Each step logs its outcome so the resolved source is visible in the log.
 
 use std::{
 	path::{Path, PathBuf},