chore: import upstream snapshot with attribution

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,85 @@
+name: Bug report
+description: Report something that isn't working
+title: "bug: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug. The more concrete you can be,
+        the faster it gets fixed. If you can include the analyzed project's
+        primary language and an approximate file count, that's gold.
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: What did you do, what did you expect to happen, and what actually happened?
+      placeholder: |
+        1. Ran `/understand --full` on a ~3,000 file Rust project
+        2. Expected: dashboard opens with the graph
+        3. Got: dashboard shows "Failed to load graph: schema validation error"
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Minimal reproduction
+      description: Smallest set of steps (or a link to a public repo) that reproduces the issue.
+    validations:
+      required: false
+
+  - type: input
+    id: version
+    attributes:
+      label: Plugin version
+      description: Run `/understand --version` or check `~/.claude/plugins/cache/understand-anything/understand-anything/`.
+      placeholder: "e.g. 2.7.4"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: platform
+    attributes:
+      label: Platform / client
+      multiple: true
+      options:
+        - Claude Code (CLI)
+        - Claude Code (VS Code extension)
+        - Claude Code (JetBrains)
+        - Cursor
+        - GitHub Copilot CLI
+        - opencode
+        - Other (please describe in "What happened?")
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: OS + Node version
+      placeholder: "e.g. macOS 14.5 (arm64), Node v22.6.0"
+    validations:
+      required: true
+
+  - type: input
+    id: project-language
+    attributes:
+      label: Primary language of the analyzed project
+      placeholder: "e.g. TypeScript, Python, Swift…"
+
+  - type: input
+    id: file-count
+    attributes:
+      label: Approximate file count of the analyzed project
+      placeholder: "e.g. ~3,000"
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs
+      description: |
+        Any console output, the contents of `.understand-anything/intermediate/`
+        if it still exists, or screenshots of the dashboard error.
+      render: shell

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: README & docs
+    url: https://github.com/Egonex-AI/Understand-Anything#readme
+    about: Most usage questions are answered in the project README.
+  - name: Discussions
+    url: https://github.com/Egonex-AI/Understand-Anything/discussions
+    about: For open-ended discussion, design proposals, or sharing how you use the tool.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,34 @@
+name: Feature request
+description: Suggest an idea or improvement
+title: "feat: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem are you trying to solve?
+      description: Describe the user pain or workflow gap. Concrete examples help more than abstract framing.
+      placeholder: |
+        When onboarding new engineers to our 8k-file Go monorepo, they spend
+        days finding the auth boundary. /understand finds the files but the
+        dashboard doesn't visually separate "trusted" from "untrusted" zones.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution (optional)
+      description: If you have an idea for what the feature should look like, share it. Skip if you'd rather just describe the problem.
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives you've considered
+      description: Other tools, workarounds, or approaches you've tried.
+
+  - type: input
+    id: scope
+    attributes:
+      label: Which part of the project?
+      placeholder: "skill / dashboard / core / agents / all"

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,24 @@
+name: Question / usage help
+description: Ask a question about how to use the project
+title: "question: "
+labels: ["question"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        For general usage questions. If you found a bug, please use the bug
+        report template instead — it asks for the information needed to
+        reproduce.
+
+  - type: textarea
+    id: question
+    attributes:
+      label: Your question
+    validations:
+      required: true
+
+  - type: textarea
+    id: tried
+    attributes:
+      label: What have you already tried?
+      description: Helps avoid suggesting things you've already ruled out.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+## Summary
+
+<!-- One or two sentences on what this PR changes and why. -->
+
+## Linked issue(s)
+
+<!-- e.g. Closes #123, Refs #456. Leave empty if there's no tracking issue. -->
+
+## How I tested this
+
+<!-- Concrete steps. "Ran the test suite" is fine; "Ran /understand on a 3k-file
+Swift repo and verified the dashboard shows non-empty edges" is better. -->
+
+- [ ] `pnpm lint`
+- [ ] `pnpm --filter @understand-anything/core test`
+- [ ] `pnpm test`
+- [ ] Manual smoke test (describe above)
+
+## Versioning
+
+<!-- If this PR ships a user-visible behavior change, bump the version in ALL
+five manifests per CLAUDE.md. If it's docs/tests/internal-only, leave them
+alone and the maintainer will bump on merge. -->
+
+- [ ] Version bumped in all five manifests, OR
+- [ ] N/A — internal/docs-only change

.github/workflows/ci.yml

@@ -0,0 +1,64 @@
+name: CI
+
+on:
+  # Run on every PR so a contributor's first push gets feedback.
+  pull_request:
+  # Also run on direct pushes to main so the "main is green" signal is real.
+  # Without this, main can silently break for days when someone bypasses
+  # review. (#249)
+  push:
+    branches: [main]
+
+# Cancel any in-flight CI for the same ref when a new commit is pushed —
+# saves runner minutes and keeps the latest commit's status the only one
+# anyone reads. `github.ref` is a controlled value (refs/heads/* or
+# refs/pull/*/merge), not user-controlled input, so it's safe to interpolate.
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  ci:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: pnpm/action-setup@v6
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: '3.x'
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 22
+          cache: pnpm
+          cache-dependency-path: pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Lint
+        run: pnpm lint
+
+      - name: Build core
+        run: pnpm --filter @understand-anything/core build
+
+      - name: Build skill
+        run: pnpm --filter @understand-anything/skill build
+
+      - name: Build viewer
+        run: pnpm --filter understand-anything-viewer build
+
+      - name: Test core
+        run: pnpm --filter @understand-anything/core test
+
+      - name: Test skill
+        run: pnpm test
+
+      - name: Test Python skill helpers
+        run: python -m unittest tests.skill.understand.test_merge_batch_graphs tests.skill.understand.test_merge_subdomain_graphs tests.skill.knowledge.test_parse_knowledge_base -v

.github/workflows/deploy-homepage.yml

@@ -0,0 +1,68 @@
+name: Deploy Homepage
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'homepage/**'
+      - 'understand-anything-plugin/packages/dashboard/**'
+      - 'understand-anything-plugin/packages/core/**'
+      - '.github/workflows/deploy-homepage.yml'
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+
+      - uses: pnpm/action-setup@v6
+
+      - uses: actions/setup-node@v6
+        with:
+          node-version: 22
+          cache: pnpm
+          cache-dependency-path: pnpm-lock.yaml
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Build homepage
+        working-directory: homepage
+        run: pnpm build
+
+      - name: Build core
+        run: pnpm --filter @understand-anything/core build
+
+      - name: Build demo dashboard
+        run: pnpm --filter @understand-anything/dashboard build:demo
+        env:
+          VITE_GRAPH_URL: ${{ vars.DEMO_GRAPH_URL }}
+          VITE_DOMAIN_GRAPH_URL: ${{ vars.DEMO_DOMAIN_GRAPH_URL }}
+          VITE_META_URL: ${{ vars.DEMO_META_URL }}
+
+      - name: Merge demo into homepage output
+        run: cp -r understand-anything-plugin/packages/dashboard/dist homepage/dist/demo
+
+      - uses: actions/upload-pages-artifact@v5
+        with:
+          path: homepage/dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v5