[UPDATE] Wiki/Doc

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,122 @@
+name: Bug report
+description: Something isn't working as expected
+title: "[Bug]: "
+labels: ["bug", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug. The more specific you can be, the faster we can help.
+
+        **Before filing:**
+        - Search [existing issues](https://github.com/CoplayDev/unity-mcp/issues?q=is%3Aissue) to avoid duplicates
+        - Check the [troubleshooting docs](https://coplaydev.github.io/unity-mcp/guides/troubleshooting) and [setup wiki](https://github.com/CoplayDev/unity-mcp/wiki)
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Clear, concrete description. What did you expect? What did you get?
+      placeholder: When I run X, I expect Y, but I see Z.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Reproduction steps
+      description: Numbered steps. Include the exact prompt or command if relevant.
+      placeholder: |
+        1. Open Window > MCP for Unity
+        2. Click Start Server
+        3. In Claude Desktop, prompt: "create a red cube"
+        4. Observe error in console: ...
+    validations:
+      required: true
+
+  - type: input
+    id: unity-version
+    attributes:
+      label: Unity version
+      placeholder: "6000.0.34f1, 2022.3.42f1, etc."
+    validations:
+      required: true
+
+  - type: input
+    id: package-version
+    attributes:
+      label: MCP for Unity package version
+      description: Found under Window > Package Manager → MCP for Unity.
+      placeholder: "9.6.3"
+    validations:
+      required: true
+
+  - type: input
+    id: server-version
+    attributes:
+      label: Python server version
+      description: Run `uv pip show mcpforunityserver` or check the bundled wheel.
+      placeholder: "9.6.3"
+    validations:
+      required: false
+
+  - type: dropdown
+    id: client
+    attributes:
+      label: MCP client
+      options:
+        - Claude Desktop
+        - Claude Code
+        - Cursor
+        - VS Code (Copilot)
+        - Windsurf
+        - Cline
+        - GitHub Copilot CLI
+        - Codex
+        - Qwen Code
+        - Gemini CLI
+        - OpenClaw
+        - Other (specify in description)
+    validations:
+      required: true
+
+  - type: dropdown
+    id: transport
+    attributes:
+      label: Transport
+      options:
+        - HTTP (default)
+        - stdio
+        - Don't know
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: OS
+      options:
+        - macOS
+        - Windows
+        - Linux
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs / console output
+      description: Editor console, MCP for Unity log, client log. Strip secrets.
+      render: text
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Checks
+      options:
+        - label: I searched existing issues and did not find a duplicate
+          required: true
+        - label: I included logs / steps to reproduce
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,14 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Discord — chat with maintainers
+    url: https://discord.gg/y4p8KfzrN4
+    about: Best for quick questions, troubleshooting, and design discussion.
+  - name: Documentation
+    url: https://coplaydev.github.io/unity-mcp/
+    about: Getting Started, guides, tool reference, and architecture notes.
+  - name: Security vulnerability
+    url: https://github.com/CoplayDev/unity-mcp/security/advisories/new
+    about: Report privately via GitHub Security Advisories or email security@coplay.dev. Do NOT open a public issue.
+  - name: Discussion / design idea
+    url: https://github.com/CoplayDev/unity-mcp/discussions
+    about: Broad questions, design conversations, show-and-tell.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,63 @@
+name: Feature request
+description: Suggest a new tool, capability, or quality-of-life improvement
+title: "[Feature]: "
+labels: ["enhancement", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Got an idea? Great. The more concrete you can be about *who* this helps and *what* they're trying to do, the easier it is to scope.
+
+        For tool requests: please name the Unity API/system you'd be wrapping and what your MCP client would actually say.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem are you trying to solve?
+      description: Frame the user need first, not the implementation.
+      placeholder: |
+        When I'm prototyping with the LLM, I can't get it to build a NavMesh because there's no MCP tool for the AI navigation system. I have to flip back to the Editor manually.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: What would you like to see?
+      description: Be specific. New tool? New action on an existing tool? New resource? Workflow change?
+      placeholder: |
+        A new `manage_navigation` tool with actions: bake, clear, set_agent_radius, query_nearest_edge, ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: prior-art
+    attributes:
+      label: Prior art / how do you work around this today?
+      placeholder: I currently bake manually via Window > AI > Navigation, then ask the LLM to reason about it.
+    validations:
+      required: false
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope hint
+      options:
+        - New tool (substantial)
+        - New action on an existing tool
+        - New resource
+        - UX / editor window
+        - CLI improvement
+        - Documentation
+        - Other
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: contribute
+    attributes:
+      label: Would you be willing to help build this?
+      options:
+        - label: I can open a PR if a maintainer sketches the approach
+        - label: I can help test
+        - label: I can write the docs

.github/workflows/docs-deploy.yml

@@ -0,0 +1,92 @@
+name: Docs — Build & Deploy
+
+# Builds the Docusaurus site under /website and, on push to beta, deploys
+# to GitHub Pages at https://coplaydev.github.io/unity-mcp/.
+#
+# PR runs only build (no deploy) as a preview-validation step.
+# Re-deploys also fire when the Python tool/resource registry changes,
+# so M3's auto-generated reference pages stay fresh.
+
+on:
+  push:
+    branches: [beta]
+    paths:
+      - website/**
+      - docs/**
+      - Server/src/services/tools/**
+      - Server/src/services/resources/**
+      - Server/src/services/registry/**
+      - .github/workflows/docs-deploy.yml
+  pull_request:
+    branches: [beta, main]
+    paths:
+      - website/**
+      - docs/**
+      - Server/src/services/tools/**
+      - Server/src/services/resources/**
+      - Server/src/services/registry/**
+      - .github/workflows/docs-deploy.yml
+  workflow_dispatch: {}
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    name: Build site
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          # Full history so Docusaurus's showLastUpdateTime / showLastUpdateAuthor
+          # can resolve real per-file commit metadata. Shallow clones make every
+          # page report the latest commit instead.
+          fetch-depth: 0
+          # No push back from this workflow — the deploy uses the Pages
+          # OIDC token issued by actions/deploy-pages, not the repo token.
+          persist-credentials: false
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+          cache-dependency-path: website/package-lock.json
+
+      - name: Install dependencies
+        working-directory: website
+        run: npm ci
+
+      - name: Setup Pages
+        if: github.event_name == 'push' && github.ref == 'refs/heads/beta'
+        uses: actions/configure-pages@v5
+
+      - name: Build
+        working-directory: website
+        run: npm run build
+
+      - name: Upload Pages artifact
+        if: github.event_name == 'push' && github.ref == 'refs/heads/beta'
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: website/build
+
+  deploy:
+    name: Deploy to GitHub Pages
+    needs: build
+    if: github.event_name == 'push' && github.ref == 'refs/heads/beta'
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/docs-generate.yml

@@ -0,0 +1,72 @@
+name: Docs — Reference Drift Check
+
+# Fails a PR if the committed /website/docs/reference/ output disagrees
+# with what tools/generate_docs_reference.py would produce from the live
+# Python tool/resource registry. Contributors should regenerate locally:
+#
+#   cd Server && uv run python ../tools/generate_docs_reference.py
+#
+# or install the pre-commit hook to make this automatic:
+#
+#   tools/install-hooks.sh
+
+on:
+  pull_request:
+    branches: [beta, main]
+    paths:
+      - Server/src/services/tools/**
+      - Server/src/services/resources/**
+      - Server/src/services/registry/**
+      - website/docs/reference/**
+      - tools/generate_docs_reference.py
+      - .github/workflows/docs-generate.yml
+  push:
+    branches: [beta]
+    paths:
+      - Server/src/services/tools/**
+      - Server/src/services/resources/**
+      - Server/src/services/registry/**
+      - website/docs/reference/**
+      - tools/generate_docs_reference.py
+      - .github/workflows/docs-generate.yml
+  workflow_dispatch: {}
+
+jobs:
+  check:
+    name: Check docs reference is fresh
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v4
+        with:
+          version: latest
+
+      - name: Set up Python
+        run: uv python install 3.10
+
+      - name: Sync Server deps
+        working-directory: Server
+        run: uv sync
+
+      - name: Drift check
+        working-directory: Server
+        run: uv run python ../tools/generate_docs_reference.py --check
+
+      - name: Tool-count sanity
+        run: |
+          set -euo pipefail
+          # Match the decorator at start-of-line (skips imports and docstring mentions).
+          decorator_count=$(grep -rhE "^@mcp_for_unity_tool\(" Server/src/services/tools/ | wc -l | tr -d ' ')
+          # md_count excludes group landing pages (index.md) and the catalog root.
+          md_count=$(find website/docs/reference/tools -name '*.md' -not -name 'index.md' | wc -l | tr -d ' ')
+          echo "decorator_count=$decorator_count, md_count=$md_count"
+          if [[ "$decorator_count" != "$md_count" ]]; then
+            echo "Mismatch: $decorator_count @mcp_for_unity_tool decorators vs $md_count reference pages." >&2
+            echo "Run: cd Server && uv run python ../tools/generate_docs_reference.py" >&2
+            exit 1
+          fi