fix(Mountain): Add inline workspace folders to extension host init data

Add `folders` array directly to the WorkspaceDTO in InitData so extensions that read `vscode.workspace.workspaceFolders` synchronously in their `activate()` (vscode.git, eamodio.gitlens, typescript) see the real folders immediately instead of `[]` until a delta fires. Cocoon's `WorkspaceNamespace/Index.ts` reads this at shim construction time, so the folders must be present in the initial payload.

Also add `configuration` field to pass the workspace config path, and change CWD-autoload default to ON in debug builds (OFF in release). Debug builds need folders for `vscode.git` / `eamodio.gitlens` to scan repositories and surface tree-views, while release keeps the stock VS Code UX. Override with `LAND_AUTOLOAD_CWD=0` or `=1`.

Author: NikolaRHristov

Source/Binary/Initialize/CliParse.rs

@@ -103,15 +103,24 @@ pub fn ParseWorkspaceFolders() -> Vec<PathBuf> {
 	}
 
 	if Collected.is_empty() {
-		// CWD-autoload is OPT-IN (set `LAND_AUTOLOAD_CWD=1`). VS Code's UX
-		// convention is to open an empty window when no folder is given and
-		// let the user pick via File → Open Folder; silently seeding CWD
-		// caused the TypeScript extension's workspace scan to walk the
-		// entire monorepo (node_modules included) during boot, stalling
-		// the UI for minutes.
+		// CWD-autoload default: ON in debug builds, OFF in release. Debug
+		// iteration invariably needs a folder so `vscode.git` /
+		// `eamodio.gitlens` can scan repositories, extensions can surface
+		// tree-views, and `workspace.findFiles` returns something. Release
+		// builds keep the stock VS Code "File → Open Folder" UX so users
+		// don't get surprise filesystem scans. Either default is
+		// overridable: `LAND_AUTOLOAD_CWD=0` disables, `LAND_AUTOLOAD_CWD=1`
+		// enables.
+		//
+		// The earlier concern was that auto-seeding CWD from a mono-repo
+		// root walked `node_modules` during TypeScript workspace scan and
+		// stalled boot. That's still real in release but acceptable in
+		// debug: developers running from their project root actually want
+		// the scan.
+		let DefaultAutoload = cfg!(debug_assertions);
 		let AutoloadCwd = std::env::var("LAND_AUTOLOAD_CWD")
-			.map(|Value| Value == "1" || Value == "true")
-			.unwrap_or(false);
+			.map(|Value| matches!(Value.as_str(), "1" | "true" | "yes" | "on"))
+			.unwrap_or(DefaultAutoload);
 		if AutoloadCwd {
 			if let Ok(Cwd) = std::env::current_dir() {
 				Collected.push(Cwd);

Source/ProcessManagement/InitializationData.rs

@@ -344,6 +344,27 @@ pub async fn ConstructExtensionHostInitializationData(Environment:&MountainEnvir
 
 	let WorkspaceFoldersGuard = ApplicationState.Workspace.WorkspaceFolders.lock().unwrap();
 
+	// Cocoon's `WorkspaceNamespace/Index.ts` reads
+	// `ExtensionHostInitData.workspace.folders` at shim construction time,
+	// then mutates the same array in place on `$deltaWorkspaceFolders`. If
+	// `folders` is missing from the init payload, every
+	// `vscode.workspace.workspaceFolders` read returns `[]` until a delta
+	// fires - which means the git extension boots with zero folders to
+	// scan and never calls `createSourceControl`. Emit the folder list
+	// inline so extensions that read `workspaceFolders` synchronously in
+	// their `activate()` (vscode.git, eamodio.gitlens, typescript) see
+	// the real folders.
+	let FoldersWire:Vec<Value> = WorkspaceFoldersGuard
+		.iter()
+		.map(|Folder| {
+			json!({
+				"uri": Folder.URI.to_string(),
+				"name": Folder.GetDisplayName(),
+				"index": Folder.Index,
+			})
+		})
+		.collect();
+
 	let WorkspaceDTO = if WorkspaceFoldersGuard.is_empty() {
 		Value::Null
 	} else {
@@ -353,6 +374,8 @@ pub async fn ConstructExtensionHostInitializationData(Environment:&MountainEnvir
 
 			"name": WorkspaceName,
 
+			"folders": FoldersWire,
+
 			"configuration": ApplicationState.Workspace.WorkspaceConfigurationPath.lock().unwrap().as_ref().map(|p| p.to_string_lossy()),
 
 			"isUntitled": ApplicationState.Workspace.WorkspaceConfigurationPath.lock().unwrap().is_none(),