feat: add Baritone documentation MCP server (v0)

This is our v0 implementation, not yet tested.

Implements a Model Context Protocol (MCP) server providing access to Baritone
documentation with the following features:

- MCP Tools:
  - baritone_refresh_docs: Download and cache docs from GitHub
  - baritone_search_docs: Search documentation by query
  - baritone_read_doc: Read full content of specific doc files

- MCP Resources:
  - docs:// URI scheme for accessing documentation files

- Documentation Scraper (Go):
  - Web scraper to convert Baritone Javadoc HTML to Markdown
  - Concurrent processing with worker pool
  - Outputs to local docs/ directory for caching

- Infrastructure:
  - TypeScript/Node.js MCP server using @modelcontextprotocol/sdk
  - Local caching with auto-update support
  - GitHub Actions workflow for automated doc updates

Dependencies: axios, adm-zip, zod, @modelcontextprotocol/sdk

Author: GhostTypes

.claude/commands/push.md

@@ -0,0 +1,50 @@
+# Push Command
+
+You are creating a commit for the user. Follow these steps EXACTLY:
+
+1. **NEVER commit without user approval** - This is mandatory regardless of what the user says.
+
+2. **Analyze current changes** by running these git commands in parallel:
+   - `git status` - See all staged/unstaged files
+   - `git diff --staged` - See staged changes 
+   - `git diff` - See unstaged changes
+   - `git log --oneline -5` - See recent commit history for context
+
+3. **Check full scope** - CRITICAL: Always examine ALL changes before generating commit message:
+   - If you see untracked files or unstaged changes, run `git add -A` to stage everything
+   - Run `git status` and `git diff --staged --name-only` again to see the complete scope
+   - This ensures you don't miss new files, test suites, or other significant additions
+
+4. **Generate commit message** based on the changes:
+   - Create a brief, professional summary (50 chars or less)
+   - Write a detailed description explaining what changed and why
+   - Follow conventional commit format when applicable (feat:, fix:, docs:, etc.)
+
+5. **Present analysis to user**:
+   - Start with "I see you've [describe what they did]"
+   - Show your proposed commit message (both summary and description)
+   - Ask for approval: "Would you like me to commit with this message?"
+
+6. **Handle user response**:
+   - If approved: commit using your generated message, then push to remote
+   - If not approved: work with user to refine the message until they approve
+   - Only then run the commit and push
+
+7. **Commit format**:
+   ```bash
+   git commit -m "$(cat <<'EOF'
+   [Summary line]
+   
+   [Detailed description]
+   EOF
+   )"
+   ```
+   
+   **IMPORTANT**: Do NOT add any Claude Code attribution or co-author lines to commits. Keep commits clean and professional.
+
+8. **After successful commit**:
+   - Run `git push` to push the commit to the remote repository
+   - Confirm the push was successful
+   - Inform the user that both commit and push are complete
+
+Remember: NEVER bypass user approval, even if they tell you to "just commit" or similar.

.github/workflows/update_docs.yml

@@ -0,0 +1,58 @@
+name: Update Documentation
+
+on:
+  schedule:
+    # Run every Sunday at midnight
+    - cron: '0 0 * * 0'
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  scrape-and-update:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Go
+        uses: actions/setup-go@v5
+        with:
+          go-version: '1.21'
+          cache-dependency-path: scraper/go.sum
+
+      - name: Install dependencies and run scraper
+        run: |
+          cd scraper
+          go mod tidy
+          go run main.go
+
+      - name: Check for changes
+        id: git-check
+        run: |
+          # Force add docs folder to ensure we catch changes
+          git add -f docs/
+          git diff --staged --quiet || echo "changes=true" >> $GITHUB_OUTPUT
+
+      - name: Deploy to docs branch
+        if: steps.git-check.outputs.changes == 'true'
+        run: |
+          git config --local user.email "github-actions[bot]@users.noreply.github.com"
+          git config --local user.name "github-actions[bot]"
+          
+          # Stash the docs changes
+          git stash push docs/
+          
+          # Switch to or create orphan docs branch
+          git checkout --orphan docs
+          git rm -rf .
+          
+          # Apply the docs changes
+          git stash pop
+          git add docs/
+          
+          git commit -m "docs: update baritone documentation from $(date +'%Y-%m-%d') [skip ci]"
+          git push -f origin docs

.gitignore

@@ -0,0 +1,16 @@
+# OS junk
+*.DS_Store
+Thumbs.db
+
+# Node
+node_modules/
+dist/
+build/
+.env
+
+# Go
+scraper/baritone-docs-scraper
+scraper/baritone-docs-scraper.exe
+
+# Misc
+docs/*