fix: prevent autosuggest hangs during path completion

Skip zage autosuggest for path-like tokens and give autosuggest requests a short default timeout so ZLE stays responsive while native path completion runs.

Also move the Forgejo workflow under .gitea and trim duplicated agent guidance.

Author: casualjim

.forgejo/workflows/ci.yml .gitea/workflows/ci.yml.forgejo/workflows/ci.yml renamed to .gitea/workflows/ci.yml

@@ -2,95 +2,16 @@
 
 > **Important:** Prefer the `mise` tasks for installs, builds, tests, and formatting. Only use raw toolchain commands when no `mise` wrapper exists, and call that out explicitly.
 >
-> **CRITICAL: Prefer the Rust LSP for Rust code navigation.** The Rust LSP is the primary tool for Rust files because it is accurate, fast, and type-aware. That said, other tools (rg/find/manual browsing) are still acceptable when they are faster for the task, the LSP is unavailable, or you're working outside Rust code. See the "Code Navigation (Use Rust LSP!)" section for detailed commands.
->
-> **CRITICAL: Do NOT run git mutations without explicit approval from the user** Do NOT ever run git checkout/revert/restore/reset without EXPLICIT APPROVAL from the USER
->
 > **CRITICAL: DO NOT ASK KNOWABLE QUESTIONS** Do not ask the user for information that you can look up.
 
 
 ## Build, Test, and Development Commands
 Always default to the `mise` tasks below; only run direct toolchain commands if no `mise` wrapper exists and note the deviation.
 
-**For Rust code navigation and understanding, use the Rust LSP first.** For non-Rust code or quick searches, it is fine to use rg/find/manual browsing when it is more appropriate.
-
 - `mise install`: Install pinned Rust, Bun, Wrangler, etc.
 - `mise build:debug`: Build Rust
 - `mise test`: All tests (Rust nextest + Workers via bun test).
 
-## Code Navigation (Use Rust LSP!)
-
-**IMPORTANT: Prefer the Rust LSP for Rust code navigation.** The Rust LSP should be your primary tool for:
-- Finding symbols and definitions
-- Navigating to references
-- Getting function signatures and documentation
-- Understanding code structure
-- Finding implementations and usages
-
-**Prefer Rust LSP over:** grep/find/rg, manual file browsing, or any other navigation method **for Rust files**. Use other tools when they are faster for the task, the LSP is unavailable, or the code is not Rust.
-
-### Rust LSP Commands Available
-
-Use these `mcp__rust-lsp__*` tools for navigation:
-
-```bash
-# Get file structure and symbols
-mcp__rust-lsp__outline <file_path>
-
-# Search for symbols across the codebase
-mcp__rust-lsp__search <query>
-
-# Find all references to a symbol
-mcp__rust-lsp__references <file_path> <line> <character>
-
-# Get detailed info about a symbol at cursor position
-mcp__rust-lsp__inspect <file_path> <line> <character>
-
-# Get code completions at a position
-mcp__rust-lsp__completion <file_path> <line> <character>
-
-# Rename a symbol across the codebase
-mcp__rust-lsp__rename <file_path> <line> <character> <new_name>
-
-# Get diagnostics (errors/warnings) for a file
-mcp__rust-lsp__diagnostics <file_path>
-```
-
-### Navigation Examples
-
-```bash
-# Find all search-related services
-mcp__rust-lsp__search "SearchService"
-
-# Explore the main application structure
-mcp__rust-lsp__outline "crates/slipstreamd/src/lib.rs"
-
-# Find all references to AppState
-mcp__rust-lsp__references "crates/slipstreamd/src/app.rs" 16 1
-
-# Inspect a function to get its documentation
-mcp__rust-lsp__inspect "crates/embedding/src/lib.rs" 127 1
-
-# Get completions for method calls
-mcp__rust-lsp__completion "crates/slipstreamd/src/routes.rs" 42 20
-```
-
-### Why Use Rust LSP?
-
-- **Accurate**: Understands Rust's type system and module resolution
-- **Fast**: Instant navigation without scanning files
-- **Context-aware**: Knows about imports, traits, generics
-- **Complete**: Shows parameters, return types, documentation
-- **IDE-quality**: Same experience as modern IDEs
-
-**Remember: For Rust code, reach for the Rust LSP first; for everything else, use the best tool for the job.**
-
-
-> REMINDER:
-> ALWAYS get approval from the user for git checkout/reset/restore/revert/...
-> NEVER run destructive git commands without explicit approval
-
-
 ## Code Style & Formatting
 
 - Refactor, don't keep adding to the technical debt

AGENTS.md

@@ -11,6 +11,8 @@ use crate::server::{self, Request, Response};
 use crate::shell_history::{get_hostname, normalize_shellname};
 use crate::tokenize::tokenize;
 
+const DEFAULT_AUTOSUGGEST_TIMEOUT_MS: u64 = 150;
+
 pub async fn run(backend: BackendRef<'_>, args: SuggestArgs) -> Result<()> {
   let SuggestArgs {
     count,
@@ -68,9 +70,7 @@ pub async fn run(backend: BackendRef<'_>, args: SuggestArgs) -> Result<()> {
   let prefix = current_line.as_ref().filter(|value| !value.is_empty());
   let server_suggestions = match &backend {
     BackendRef::Server => {
-      let timeout_ms = timeout
-        .map(|duration| Duration::from(duration).as_millis())
-        .map(|millis| u64::try_from(millis).unwrap_or(u64::MAX));
+      let timeout_ms = resolve_timeout_ms(timeout, autosuggest);
       let request = Request::Suggest {
         current_line: prefix.cloned(),
         working_directory: cwd.clone(),
@@ -237,6 +237,13 @@ pub async fn run(backend: BackendRef<'_>, args: SuggestArgs) -> Result<()> {
   Ok(())
 }
 
+fn resolve_timeout_ms(timeout: Option<humantime::Duration>, autosuggest: bool) -> Option<u64> {
+  timeout
+    .map(|duration| Duration::from(duration).as_millis())
+    .map(|millis| u64::try_from(millis).unwrap_or(u64::MAX))
+    .or_else(|| autosuggest.then_some(DEFAULT_AUTOSUGGEST_TIMEOUT_MS))
+}
+
 fn format_zsh_item(word: &str, desc: Option<&str>) -> String {
   let mut escaped = String::new();
   for ch in word.chars() {
@@ -414,3 +421,32 @@ fn format_suggestion_debug(suggestion: &Suggestion, always_show_score: bool) ->
     suggestion.breakdown.online_model
   )
 }
+
+#[cfg(test)]
+mod tests {
+  use super::*;
+
+  #[test]
+  fn autosuggest_uses_short_default_timeout() {
+    assert_eq!(
+      resolve_timeout_ms(None, true),
+      Some(DEFAULT_AUTOSUGGEST_TIMEOUT_MS)
+    );
+  }
+
+  #[test]
+  fn explicit_timeout_overrides_autosuggest_default() {
+    assert_eq!(
+      resolve_timeout_ms(
+        Some(humantime::Duration::from(Duration::from_secs(2))),
+        true
+      ),
+      Some(2_000)
+    );
+  }
+
+  #[test]
+  fn non_autosuggest_keeps_existing_default() {
+    assert_eq!(resolve_timeout_ms(None, false), None);
+  }
+}