refactor: simplify CI workflow and reorganize source files into modular structure

Author: zamderax

.github/workflows/swift.yml

@@ -1,89 +1,30 @@
-name: Swift CI
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
 
-on:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
+# GitHub recommends pinning actions to a commit SHA.
+# To get a newer version, you will need to update the SHA.
+# You can also reference a tag or branch, but the action may change without warning.
+
+name: Swift
+
+on: [push]
 
 jobs:
-  test:
-    runs-on: ${{ matrix.os }}
+  build:
+    name: Swift ${{ matrix.swift }} on ${{ matrix.os }}
     strategy:
       matrix:
         os: [ubuntu-latest, macos-latest]
-    
-    steps:
-    - uses: actions/checkout@v4
-    
-    - name: Setup Swift
-      uses: vapor/swiftly-action@v0.2
-      with:
-        toolchain: '6.1'
-    
-    - name: Cache Swift Package Manager
-      uses: actions/cache@v3
-      with:
-        path: .build
-        key: ${{ runner.os }}-spm-${{ hashFiles('**/Package.resolved') }}
-        restore-keys: |
-          ${{ runner.os }}-spm-
-    
-    - name: Build
-      run: swift build -v
-    
-    - name: Run tests
-      run: swift test -v
-    
-    - name: Build release
-      run: swift build -c release
-    
-    - name: Test Makefile targets
-      run: |
-        make help
-        make build
-        make clean
-
-
-  security:
-    runs-on: ubuntu-latest
-    steps:
-    - uses: actions/checkout@v4
-    
-    - name: Run security audit
-      run: |
-        # Check for known security vulnerabilities in dependencies
-        echo "Checking for security vulnerabilities..."
-        # This would typically use tools like swift-package-audit when available
-        echo "No security audit tools configured yet"
-
-  release:
-    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
-    needs: [test]
-    runs-on: ubuntu-latest
+        swift: ["6.1"]
+    runs-on: ${{ matrix.os }}
     steps:
-    - uses: actions/checkout@v4
-    
-    - name: Setup Swift
-      uses: vapor/swiftly-action@v0.2
-      with:
-        toolchain: '6.1'
-    
-    - name: Build release artifacts
-      run: |
-        # Build for multiple platforms
-        swift build -c release
-        
-        # Create release directory
-        mkdir -p release
-        
-        # Copy binary and documentation
-        cp .build/release/SwiftDeveloperMCPServer release/
-        cp README.md release/
-        cp Makefile release/
-    
-    - name: Upload release artifacts
-      uses: actions/upload-artifact@v3
-      with:
-        name: swift-developer-mcp-server-${{ github.sha }}
-        path: release/
+      - uses: vapor/swiftly-action@65540b95f51493d65f5e59e97dcef9629ddf11bf
+        with:
+          toolchain: ${{ matrix.swift }}
+      - uses: actions/checkout@v4
+      - name: Build
+        run: swift build
+      - name: Run tests
+        run: swift test

README.md

@@ -193,13 +193,24 @@ swift-developer-mcp-server/
 ├── Makefile                     # Build automation and convenience targets
 ├── Sources/
 │   ├── main.swift               # Server entry point and MCP handler setup
-│   └── SwiftDeveloperTools.swift # Tool implementations
+│   ├── Utilities.swift          # Common types and helper functions
+│   ├── BuildTestTools.swift     # Swift build and test tools
+│   ├── DebugTools.swift         # Debug session management and tools
+│   ├── PackageInfoTools.swift   # Swift package information tools
+│   ├── SwiftlyTools.swift       # Swiftly toolchain management
+│   ├── Resources.swift          # MCP resources (project info, build status, etc.)
+│   └── Prompts.swift            # MCP prompts (debug session, build analysis)
 └── README.md                    # This file
 ```
 
 ### Adding New Tools
 
-1. Define the tool struct in `SwiftDeveloperTools.swift`
+1. Define the tool struct in the appropriate module file:
+   - `BuildTestTools.swift` for build and test functionality
+   - `DebugTools.swift` for debugging features
+   - `PackageInfoTools.swift` for package management
+   - `SwiftlyTools.swift` for toolchain management
+   - Create a new module if needed for other categories
 2. Add the tool to the `ListTools` handler in `main.swift`
 3. Add the tool's handle method to the `CallTool` switch statement
 4. Rebuild the server
@@ -231,7 +242,7 @@ Then send initialization and tool call messages via stdin.
 
 ## License
 
-This project is licensed under the MIT License. See the LICENSE file for details.
+This project is licensed under the Apache 2.0 License. See the LICENSE file for details.
 
 ## Troubleshooting