fix(Mountain): Treat view registry commands as no-ops and preserve VSIX executable bits

Two unrelated bug fixes bundled for convenience:

1. **View registry commands** (`CommandProvider.rs`): VS Code auto-generates `<viewId>.focus`, `<viewId>.resetViewLocation`, and `<viewId>.removeView` commands when views are registered. Land's webview.registerView bypasses that registry and emits Tauri events directly, so these commands never get inserted. Extensions like GitLens call these commands on user gesture; the Cocoon try/catch swallows the error, but the red `error:` log noise is misleading. Treat these well-known suffixes as silent no-ops that return `null`.

2. **VSIX executable preservation** (`VsixInstaller.rs`): Extensions shipping platform-native binaries (openai.chatgpt's `codex`, language-server launchers) rely on the `0o755` mode stored in the VSIX zip. Without this change, extracted files get the default `0o644` mode, causing `spawn()` inside extensions to fail with `EACCES`. Use `PermissionsExt::unix_mode()` to preserve the executable bit on Unix systems.

Impact: GitLens no longer spams error logs, and extensions with native binaries activate correctly.

Author: NikolaRHristov

Source/Environment/CommandProvider.rs

@@ -278,6 +278,28 @@ impl CommandExecutor for MountainEnvironment {
 			},
 
 			None => {
+				// VS Code auto-registers `<viewId>.focus`,
+				// `<viewId>.resetViewLocation`, and `<viewId>.removeView`
+				// commands when a view is contributed via the view registry.
+				// Land's webview.registerView bypasses that registry and
+				// emits a Tauri event instead, so the focus commands never
+				// get inserted. Extensions (gitlens in particular) call
+				// `commands.executeCommand('<their-view-id>.focus')` on
+				// user gesture; the Cocoon try/catch swallows the error,
+				// but the red `error:` log noise here is misleading. Treat
+				// these well-known auto-generated suffixes as silent no-ops.
+				if CommandIdentifier.ends_with(".focus")
+					|| CommandIdentifier.ends_with(".resetViewLocation")
+					|| CommandIdentifier.ends_with(".removeView")
+				{
+					dev_log!(
+						"commands",
+						"[CommandProvider] View-action command '{}' not registered; treating as no-op (auto-generated by view registry in stock VS Code).",
+						CommandIdentifier
+					);
+					return Ok(Value::Null);
+				}
+
 				dev_log!(
 					"commands",
 					"error: [CommandProvider] Command '{}' not found in registry.",

Source/ExtensionManagement/VsixInstaller.rs

@@ -259,6 +259,25 @@ fn ExtractPayload(VsixPath:&Path, InstalledAt:&Path) -> Result<(), InstallError>
 		let mut Output = File::create(&Target).map_err(|Error| InstallError::FilesystemIO(Error.to_string()))?;
 
 		io::copy(&mut Entry, &mut Output).map_err(|Error| InstallError::FilesystemIO(Error.to_string()))?;
+
+		// Preserve Unix executable bits recorded in the VSIX. Extensions
+		// that ship platform-native binaries (openai.chatgpt's `codex`,
+		// language-server launchers, etc.) rely on the `0o755` mode being
+		// carried through the zip. Without this, the child `spawn()`
+		// inside the extension fails with `EACCES` because the freshly
+		// written file has only the default `0o644` read/write mode.
+		#[cfg(unix)]
+		{
+			use std::os::unix::fs::PermissionsExt;
+			if let Some(Mode) = Entry.unix_mode() {
+				// Zip's unix_mode returns the full stat mode (type bits +
+				// permission bits). Mask to the permission bits only, then
+				// OR in `0o644` as a safety floor so we never drop read
+				// access. Respect the executable bit if the archive had it.
+				let Permissions = fs::Permissions::from_mode((Mode & 0o777) | 0o644);
+				let _ = fs::set_permissions(&Target, Permissions);
+			}
+		}
 	}
 
 	Ok(())