Merge pull request #12 from doITmagic/fix/strict-file-path-and-installer

feat: standardize tools, improve workspace detection, and enable Homebrew support

Author: doITmagic

.clauderules

@@ -5,13 +5,13 @@
 **For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
 
 ## Available Tools
-- search_code: Primary entry point for semantic search.
-- get_function_details: Get full implementation of a function.
-- find_type_definition: Get struct/interface definitions.
-- list_package_exports: See what a module offers.
-- search_docs: Find project documentation.
+- rag_search_code: Primary entry point for semantic search.
+- rag_get_function_details: Get full implementation of a function.
+- rag_find_type_definition: Get struct/interface definitions.
+- rag_list_package_exports: See what a module offers.
+- rag_search_docs: Find project documentation.
 
 ## Usage Guidelines
 - Always provide 'file_path' to tools to ensure they detect the correct project context.
-- Use 'hybrid_search' if looking for exact variable names or error messages.
-- If the tool says "workspace not indexed", use 'index_workspace' once.
+- Use 'rag_hybrid_search' if looking for exact variable names or error messages.
+- If the tool says "workspace not indexed", use 'rag_index_workspace' once.

.clinerules

@@ -5,13 +5,13 @@
 **For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
 
 ## Available Tools
-- search_code: Primary entry point for semantic search.
-- get_function_details: Get full implementation of a function.
-- find_type_definition: Get struct/interface definitions.
-- list_package_exports: See what a module offers.
-- search_docs: Find project documentation.
+- rag_search_code: Primary entry point for semantic search.
+- rag_get_function_details: Get full implementation of a function.
+- rag_find_type_definition: Get struct/interface definitions.
+- rag_list_package_exports: See what a module offers.
+- rag_search_docs: Find project documentation.
 
 ## Usage Guidelines
 - Always provide 'file_path' to tools to ensure they detect the correct project context.
-- Use 'hybrid_search' if looking for exact variable names or error messages.
-- If the tool says "workspace not indexed", use 'index_workspace' once.
+- Use 'rag_hybrid_search' if looking for exact variable names or error messages.
+- If the tool says "workspace not indexed", use 'rag_index_workspace' once.

.cursorrules

@@ -2,10 +2,10 @@
 
 ## ⚖️ The Golden Rule
 **For any information about the codebase (structure, logic, or usage), you MUST use RagCode MCP tools.** 
-Never guess code details from memory; always search the local index first using `search_code` or `get_function_details`.
+Never guess code details from memory; always search the local index first using `rag_search_code` or `rag_get_function_details`.
 
 ## Guidelines
-1. **Context First**: Always call `search_code` when starting a task to see where relevant logic exists.
-2. **Actual Code**: Use `get_function_details` to read the implementation of a function instead of assuming what it does.
+1. **Context First**: Always call `rag_search_code` when starting a task to see where relevant logic exists.
+2. **Actual Code**: Use `rag_get_function_details` to read the implementation of a function instead of assuming what it does.
 3. **Workspace Detection**: Always provide the current `file_path` to the tools so they can identify the correct project/workspace.
-4. **No Guesswork**: If you don't find something, index the workspace using `index_workspace` and search again.
+4. **No Guesswork**: If you don't find something, index the workspace using `rag_index_workspace` and search again.

.github/copilot-instructions.md

@@ -22,8 +22,8 @@ RagCode is a Model Context Protocol (MCP) server that provides semantic code sea
 - **Logging**: MCP server logs to `mcp.log` next to the executable. Check `MCP_LOG_LEVEL=debug` for issues.
 
 ## MCP Tools Usage
-- `search_code`: Use as the primary entry point for exploration. **Crucial**: Always provide the `file_path` parameter as it's used for workspace and language detection.
-- `index_workspace`: Triggered automatically on first query per workspace, but can be manually invoked for major changes.
+- `rag_search_code`: Use as the primary entry point for exploration. **Crucial**: Always provide the `file_path` parameter as it's used for workspace and language detection.
+- `rag_index_workspace`: Triggered automatically on first query per workspace, but can be manually invoked for major changes.
 
 ## Integration Points
 - **Ollama**: Requires `phi3:medium` (reasoning) and `mxbai-embed-large` (embeddings) by default.

.github/workflows/release.yml

@@ -23,6 +23,17 @@ jobs:
         with:
           fetch-depth: 0
 
+      - name: Check for Homebrew Tap Token
+        id: check_token
+        run: |
+          if [ -n "${{ secrets.HOMEBREW_TAP_TOKEN }}" ]; then
+            echo "SKIP_HOMEBREW=" >> $GITHUB_OUTPUT
+            echo "HOMEBREW_TAP_TOKEN is present. Homebrew updates enabled."
+          else
+            echo "SKIP_HOMEBREW=--skip=homebrew" >> $GITHUB_OUTPUT
+            echo "HOMEBREW_TAP_TOKEN is missing. Homebrew Tap update will be skipped."
+          fi
+      
       - name: Fetch all tags
         run: git fetch --force --tags
 
@@ -37,9 +48,10 @@ jobs:
         with:
           distribution: goreleaser
           version: v2.6.1
-          args: release --clean
+          args: release --clean ${{ steps.check_token.outputs.SKIP_HOMEBREW }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          HOMEBREW_TAP_TOKEN: ${{ secrets.HOMEBREW_TAP_TOKEN }}
 
       - name: Update server.json version
         run: |

.github/workflows/test.yml

@@ -2,9 +2,9 @@
 
   on:
     push:
-      branches: [ main, dev, 'feat/**' ]
+      branches: [ main, dev, 'feat/**', 'fix/**' ]
     pull_request:
-      branches: [ main, dev, 'feat/**' ]
+      branches: [ main, dev, 'feat/**', 'fix/**' ]
 
   jobs:
     test:

.goreleaser.yaml

@@ -67,6 +67,33 @@ builds:
       - -X main.Date={{.Date}}
       - -X main.BuiltBy=goreleaser
 
+  - id: index-all
+    main: ./cmd/index-all
+    binary: index-all
+    
+    env:
+      - CGO_ENABLED=0
+    
+    goos:
+      - linux
+      - darwin
+      - windows
+    
+    goarch:
+      - amd64
+      - arm64
+    
+    ignore:
+      - goos: windows
+        goarch: arm64
+    
+    ldflags:
+      - -s -w
+      - -X main.Version={{.Version}}
+      - -X main.Commit={{.Commit}}
+      - -X main.Date={{.Date}}
+      - -X main.BuiltBy=goreleaser
+
 archives:
   - id: default
     format: tar.gz
@@ -155,11 +182,24 @@ release:
     
     **Full documentation:** https://github.com/doITmagic/rag-code-mcp
 
-# Homebrew tap (optional, can be enabled later)
-# brews:
-#   - repository:
-#       owner: doITmagic
-#       name: homebrew-tap
-#     homepage: https://github.com/doITmagic/rag-code-mcp
-#     description: Semantic code navigation for Go codebases using RAG
-#     license: MIT
+# Homebrew tap configuration
+brews:
+  - repository:
+      owner: doITmagic
+      name: homebrew-tap
+      # REQUIRED: A dedicated token (HOMEBREW_TAP_TOKEN) with write access to the tap repository.
+      token: "{{ .Env.HOMEBREW_TAP_TOKEN }}"
+    
+    directory: Formula
+    homepage: "https://github.com/doITmagic/rag-code-mcp"
+    description: "Semantic code navigation for Go, PHP, and Python codebases using RAG and MCP."
+    license: "MIT"
+    
+    # Custom install script to handle multiple binaries
+    install: |
+      bin.install "rag-code-mcp"
+      bin.install "ragcode-installer"
+      bin.install "index-all"
+    
+    test: |
+      system "#{bin}/rag-code-mcp --version"

.goreleaser.yml

@@ -5,13 +5,13 @@
 **For any information about the code (location, structure, logic, or usage), you MUST use RagCode MCP tools. Never guess code details from memory; always search the local index first.**
 
 ## Available Tools
-- search_code: Primary entry point for semantic search.
-- get_function_details: Get full implementation of a function.
-- find_type_definition: Get struct/interface definitions.
-- list_package_exports: See what a module offers.
-- search_docs: Find project documentation.
+- rag_search_code: Primary entry point for semantic search.
+- rag_get_function_details: Get full implementation of a function.
+- rag_find_type_definition: Get struct/interface definitions.
+- rag_list_package_exports: See what a module offers.
+- rag_search_docs: Find project documentation.
 
 ## Usage Guidelines
 - Always provide 'file_path' to tools to ensure they detect the correct project context.
-- Use 'hybrid_search' if looking for exact variable names or error messages.
-- If the tool says "workspace not indexed", use 'index_workspace' once.
+- Use 'rag_hybrid_search' if looking for exact variable names or error messages.
+- If the tool says "workspace not indexed", use 'rag_index_workspace' once.

.roomodes

@@ -2,10 +2,10 @@
 
 ## ⚖️ The Golden Rule
 **For any information about the codebase (structure, logic, or usage), you MUST use RagCode MCP tools.** 
-Never guess code details from memory; always search the local index first using `search_code` or `get_function_details`.
+Never guess code details from memory; always search the local index first using `rag_search_code` or `rag_get_function_details`.
 
 ## Guidelines
-1. **Context First**: Always call `search_code` when starting a task to see where relevant logic exists.
-2. **Actual Code**: Use `get_function_details` to read the implementation of a function instead of assuming what it does.
+1. **Context First**: Always call `rag_search_code` when starting a task to see where relevant logic exists.
+2. **Actual Code**: Use `rag_get_function_details` to read the implementation of a function instead of assuming what it does.
 3. **Workspace Detection**: Always provide the current `file_path` to the tools so they can identify the correct project/workspace.
-4. **No Guesswork**: If you don't find something, index the workspace using `index_workspace` and search again.
+4. **No Guesswork**: If you don't find something, index the workspace using `rag_index_workspace` and search again.