feat: GUI Research PRPs and Benchmark Infrastructure

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,141 @@
+name: 🐛 Bug Report
+description: Report a defect in the Edge Craft engine, tooling, or automation.
+title: "[BUG] "
+labels:
+  - bug
+  - needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping improve Edge Craft!
+
+        Before filing, please:
+        - Pull the latest `main` branch and reinstall dependencies
+        - Read the active PRP to confirm the behaviour is actually supported
+        - Search [open issues](https://github.com/dcversus/edgecraft/issues?q=is%3Aissue+is%3Aopen+label%3Abug) to avoid duplicates
+
+  - type: checkboxes
+    id: confirmations
+    attributes:
+      label: Preflight Checklist
+      options:
+        - label: I searched existing Edge Craft issues and discussions
+          required: true
+        - label: I reproduced this bug on the current `main` commit
+          required: true
+        - label: I captured a minimal reproduction (map, script, or CLI steps)
+          required: true
+        - label: This is not a support question or feature request
+          required: true
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: What broke?
+      description: Describe the unexpected behaviour in one or two sentences.
+      placeholder: Terrain tiles flicker when switching Babylon.js camera modes.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Steps to reproduce
+      description: Include exact CLI commands, map filenames, and any additional assets required to reproduce.
+      placeholder: |
+        1. Checkout commit 1234abcd and run `npm run dev`
+        2. Load `public/maps/ashenvale.w3x`
+        3. Rotate the camera 180°
+        4. Observe both specular and shadow artifacts on cliff meshes
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected result
+      description: What should happen instead?
+      placeholder: Mesh normals stay stable while rotating the camera.
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual result
+      description: Paste screenshots, logs, stack traces, or CLI output. This field is rendered as code.
+      render: shell
+      placeholder: |
+        [engine] GL ERROR: drawElements instanced lighting pipeline failed...
+    validations:
+      required: true
+
+  - type: textarea
+    id: regression_notes
+    attributes:
+      label: Regression context
+      description: If this previously worked, list the last known good commit or release.
+      placeholder: Worked on commit 2ab4c89 (September 18), broken since 3dff102.
+
+  - type: input
+    id: commit
+    attributes:
+      label: Edge Craft commit hash
+      description: Output of `git rev-parse HEAD` from your reproduction environment.
+      placeholder: 3dff1025a9b0c893f0c5be02f1a0b9327495d1cc
+    validations:
+      required: true
+
+  - type: input
+    id: map_assets
+    attributes:
+      label: Map or asset references
+      description: Provide filenames and locations (e.g., `public/maps/ashenvale.w3x`).
+      placeholder: public/maps/ashenvale.w3x
+
+  - type: dropdown
+    id: runtime
+    attributes:
+      label: Runtime environment
+      description: Where does the bug manifest?
+      options:
+        - Dev server (npm run dev)
+        - Production build (npm run build && npm run preview)
+        - Automated tests (npm run test / npm run validate)
+        - GitHub Actions workflow
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: operating_system
+    attributes:
+      label: Operating system
+      options:
+        - macOS
+        - Windows
+        - Ubuntu/Debian Linux
+        - Other Linux
+        - Other
+    validations:
+      required: true
+
+  - type: dropdown
+    id: browser_gpu
+    attributes:
+      label: Rendering stack
+      options:
+        - Chromium-based (Chrome, Edge, Brave)
+        - Firefox
+        - Safari/WebKit
+        - Headless (Playwright)
+        - Not applicable
+    validations:
+      required: true
+
+  - type: textarea
+    id: extras
+    attributes:
+      label: Additional context
+      description: Link related issues, PRPs, or attach small code snippets that help diagnose the bug.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📋 Current PRPs
+    url: https://github.com/dcversus/edgecraft/tree/main/PRPs
+    about: Review product requirement proposals before opening a new issue.
+  - name: 🧠 AI Contributor Workflow
+    url: https://github.com/dcversus/edgecraft/blob/main/CLAUDE.md
+    about: Follow these rules when collaborating with AI agents on Edge Craft.
+  - name: 📚 Project README
+    url: https://github.com/dcversus/edgecraft#readme
+    about: Learn about architecture, tasks, and validation requirements.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,45 @@
+name: 📚 Documentation Update
+description: Improve Edge Craft documentation, guides, or automations.
+title: "[DOCS] "
+labels:
+  - documentation
+  - needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Help keep our documentation accurate and automation workflows understandable.
+
+  - type: checkboxes
+    id: doc_checklist
+    attributes:
+      label: Checklist
+      options:
+        - label: I reviewed the current document and confirmed it is outdated or unclear.
+          required: true
+        - label: I linked relevant PRPs or code paths that require updated documentation.
+          required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: What needs to change?
+      description: Provide the impacted docs or workflows and the desired updates.
+      placeholder: Update README quick start to reference new automation templates.
+    validations:
+      required: true
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Why does it matter?
+      description: Explain how the change improves onboarding, QA, or compliance.
+      placeholder: Missing instructions cause new contributors to skip asset validation.
+    validations:
+      required: true
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Link PRs, issues, or example text to copy.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,82 @@
+name: 🌟 Feature Proposal
+description: Suggest a new capability for Edge Craft or its tooling.
+title: "[FEATURE] "
+labels:
+  - enhancement
+  - needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for improving Edge Craft. Feature requests should map to a PRP or propose a new one.
+
+  - type: checkboxes
+    id: alignment
+    attributes:
+      label: Alignment Checklist
+      options:
+        - label: I reviewed the existing PRPs and confirmed this is not already planned.
+          required: true
+        - label: I documented the business value and success metrics below.
+          required: true
+        - label: I am willing to help refine or implement this feature.
+          required: true
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Feature summary
+      description: Concise description of the capability you need.
+      placeholder: Add support for SC2 tileset blending to improve terrain transitions.
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Problem statement
+      description: What problem does this feature solve? Reference user stories or PRPs.
+      placeholder: Current terrain rendering produces harsh edges on SC2 maps lacking blend textures...
+    validations:
+      required: true
+
+  - type: textarea
+    id: success
+    attributes:
+      label: Success criteria
+      description: How will we know this feature is complete? List measurable outcomes or validation steps.
+      placeholder: |
+        - Render SC2 tilesets with smooth blend masks
+        - Maintain 60 FPS on 1080p builds
+        - Automated regression scene for the Ashenvale sample map
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Proposed scope
+      description: Outline components, formats, or pipelines affected.
+      placeholder: |
+        - Extend terrain shader to accept blend masks
+        - Update asset validator to check for missing blend textures
+        - Add unit tests for terrain material factory
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies & blockers
+      description: List prerequisite work, assets, or external approvals.
+      placeholder: Requires Babylon.js 6.x upgrade to access new node material API.
+
+  - type: textarea
+    id: risks
+    attributes:
+      label: Risks & tradeoffs
+      description: Note performance, legal, or architecture concerns.
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Link demos, research papers, forum threads, or related issues.

.github/ISSUE_TEMPLATE/technical_task.yml

@@ -0,0 +1,53 @@
+name: 🧱 Technical Task
+description: Track refactors, automation changes, or infrastructure work.
+title: "[TASK] "
+labels:
+  - chore
+  - needs-triage
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template for infrastructure, automation, or refactor work that does not directly surface as a user-facing feature.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Task summary
+      description: Describe the work in one or two sentences.
+      placeholder: Adopt GitHub issue templates and lock workflow from claude-code project.
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: Explain why this task is necessary. Reference metrics, incidents, or PRPs.
+      placeholder: Lack of templates creates inconsistent bug reports and slows triage.
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope & deliverables
+      description: List the concrete outputs (files, workflows, scripts) expected from this task.
+      placeholder: |
+        - Add .github/ISSUE_TEMPLATE suite
+        - Create CONTRIBUTING.md summarizing automation expectations
+        - Document new workflows in README
+    validations:
+      required: true
+
+  - type: textarea
+    id: testing
+    attributes:
+      label: Validation plan
+      description: How will we verify this change? List tests, dry-runs, or CI jobs to run.
+
+  - type: textarea
+    id: risks
+    attributes:
+      label: Risks & mitigation
+      description: Note potential regressions or operational overhead.

.github/pull_request_template.md

@@ -0,0 +1,22 @@
+## Summary
+- Describe the change and why it is needed.
+- Link related issues or context.
+
+## PRP Alignment
+- PRP: 
+- Definition of Done items addressed:
+
+## Validation
+- [ ] `npm run typecheck`
+- [ ] `npm run lint`
+- [ ] `npm run test`
+- [ ] `npm run validate`
+- [ ] Manually tested according to PRP test matrix (if applicable)
+
+## Documentation
+- [ ] README or docs updated
+- [ ] PRP progress table updated
+- [ ] CLAUDE/agents instructions still accurate
+
+## Additional Notes
+- Include screenshots, logs, or follow-up tasks if relevant.