Test: Verify spilled coffee MCP server setup works in GitHub Actions

## Test Verification for Spilled Coffee Fix

This issue tests that the spilled coffee principle fix (PR #1205) successfully enables MCP servers in GitHub Actions.

## What Should Happen

When @claude is mentioned, the workflow should now:

1. ✅ **Load knowledge base** (already working - 72k characters)
2. ✅ **Install dependencies** via `source ./setup.sh`:
- Auto-install Go compiler for GitHub MCP server
- Auto-install uv + Python deps for Git MCP server
3. ✅ **Build MCP servers** successfully
4. ✅ **Show connected status** for git and github MCP servers (not "failed")
5. ✅ **Create branch** using `mcp__git__git_create_branch`
6. ✅ **Make commits** using `mcp__git__git_commit`
7. ✅ **Create PR** using `mcp__github__create_pull_request`

## Expected Evidence of Success

- MCP server status shows `"git": "connected"` and `"github": "connected"`
- Claude successfully creates a pull request to close this issue
- No "failed" MCP server status in workflow logs

## Test Request

@claude - Please demonstrate that MCP servers are now working by:

1. Creating a simple test file (e.g., `test-mcp-success.txt` with timestamp)
2. Committing the change
3. Creating a pull request that closes this issue

This will prove the full MCP toolchain works in GitHub Actions.

## Previous Issue Context

- Issue #1203: Identified MCP server failure preventing PR creation
- PR #1204: Added basic MCP setup step (partial fix)
- PR #1205: Applied spilled coffee principle with full dependency handling

**Expected**: This test should succeed where previous attempts failed.

Start with setup.sh and the GitHub Actions workflow that invokes @claude; review PR #1205 and the failures described in issue #1203 and PR #1204. Run the workflow, verify git and github MCP servers show as connected, and confirm it creates the test file, commit, and pull request without failed server status.

Written by the indexing model from the issue text.