feat: expand Galaxy agent and remote tooling

Add Wormhole remote helpers, provider and agent improvements, filesystem diagnostics, model metadata support, and schema-aware settings IntelliSense.

crates/galaxy_terminal/src/shell/mod.rs

@@ -335,7 +335,7 @@ impl ShellType {
     ///
     /// The returned [`TypedPathBuf`]s are encoded for the target OS rather than the
     /// host OS, because the resulting path is rendered into a shell command executed
-    /// on the target (e.g. via SSH or Auto-Warpify). A plain `PathBuf` would pick the
+    /// on the target (e.g. via SSH or Auto-Wormhole). A plain `PathBuf` would pick the
     /// host's separator and produce strings like `~\.zshrc` on a Windows host when
     /// targeting a Unix shell, which the remote shell cannot resolve. Encoding for
     /// the target OS lets `TypedPathBuf` enforce the correct separator.

crates/galaxy_terminal/src/shell/mod_tests.rs

@@ -274,7 +274,7 @@ fn test_should_add_command_to_history() {
 /// Regression test for https://github.com/warpdotdev/warp/issues/10474.
 ///
 /// `rc_file_paths` is rendered into a shell command that runs on the *target*
-/// (e.g. an SSH remote, or a subshell during Auto-Warpify). The path separator
+/// (e.g. an SSH remote, or a subshell during Auto-Wormhole). The path separator
 /// must therefore depend on the target OS, not the host that built Warp.
 /// Previously this used `PathBuf::join`, which uses the host's separator and
 /// produced strings like `~\.zshrc` on a Windows host targeting a Unix shell —
@@ -308,7 +308,7 @@ fn test_rc_file_paths_use_target_os_separator() {
         );
     }
 
-    // On Windows the only Auto-Warpify-supported shell is PowerShell; Unix
+    // On Windows the only Auto-Wormhole-supported shell is PowerShell; Unix
     // shells deliberately return no rc paths.
     // The leading separator follows target OS; the literal interior slashes
     // are left as-is (PowerShell accepts forward slashes on Windows).