Merge branch 'dev' into paul/fix/segmentation-fault-2

Author: leshy

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,86 +1,24 @@
 name: Bug Report
 description: Report a bug in DimOS
-title: "[Bug]: "
+labels: ["bug"]
 body:
   - type: textarea
     id: description
     attributes:
       label: Description
-      description: What happened? What did you expect to happen?
-    validations:
-      required: true
-
-  - type: textarea
-    id: steps
-    attributes:
-      label: Steps to Reproduce
-      description: Minimal steps to reproduce the bug
-      placeholder: |
-        1. ...
-        2. ...
-        3. ...
-    validations:
-      required: true
-
-  - type: textarea
-    id: logs
-    attributes:
-      label: Logs / Error Output
-      description: Paste any relevant logs or error messages
-      render: shell
-    validations:
-      required: false
+      value: |
+        ## System
+        <!-- e.g. Ubuntu 24.04, macOS 15.4 -->
 
-  - type: input
-    id: commit-hash
-    attributes:
-      label: Commit Hash
-      description: "Run: git rev-parse --short HEAD"
-      placeholder: "abc1234"
-    validations:
-      required: true
+        ## Robot/Sim/Hardware (including firmware version)
+        <!-- e.g. Unitree Go2 EDU 1.1.7, or Unity sim etc -->
 
-  - type: input
-    id: os
-    attributes:
-      label: Operating system
-      description: OS and version where this occurs.
-      placeholder: macOS 15.4 / Ubuntu 24.04 / Windows 11
-    validations:
-      required: true
+        ## Steps to reproduce
 
-  - type: dropdown
-    id: robot-model
-    attributes:
-      label: Robot Model
-      description: Which robot are you using, if any?
-      options:
-        - N/A
-        - Unitree G1
-        - Unitree Go2 Pro
-        - Unitree Go2 Air
-        - Unitree B1
-        - Drone
-        - Piper
-        - xArm
-        - Simulation only
-        - Other (specify below)
-    validations:
-      required: false
+        ## DimOS version
+        <!-- branch name or commit: git rev-parse --short HEAD -->
 
-  - type: input
-    id: firmware-version
-    attributes:
-      label: Firmware Version
-      description: Exact firmware version of your robot, if applicable (e.g. 1.0.2.35)
-      placeholder: "1.0.2.35"
-    validations:
-      required: false
+        ## Logs / screenshots
 
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: Any other context — screenshots, environment details, workarounds tried, etc.
     validations:
-      required: false
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,4 +1,4 @@
-blank_issues_enabled: false
+blank_issues_enabled: true
 contact_links:
   - name: Discord
     url: https://discord.gg/dimos

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,35 +1,12 @@
 name: Feature Request
 description: Suggest a new feature or improvement for DimOS
-title: "[Feature]: "
+labels: ["feature"]
 body:
   - type: textarea
-    id: problem
+    id: description
     attributes:
-      label: Problem
-      description: What problem does this solve? What's frustrating or missing?
-    validations:
-      required: true
+      label: Description
+      description: What do you want and why?
 
-  - type: textarea
-    id: solution
-    attributes:
-      label: Proposed Solution
-      description: How would you like this to work?
     validations:
       required: true
-
-  - type: textarea
-    id: alternatives
-    attributes:
-      label: Alternatives Considered
-      description: Any other approaches you've thought about or workarounds you're using
-    validations:
-      required: false
-
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: Any other context — diagrams, references, related issues, etc.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/question.yml

@@ -0,0 +1,11 @@
+name: Question
+description: Ask a question about DimOS usage or development
+labels: ["question"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Question
+      description: What do you need help with?
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/spec.yml

@@ -1,30 +1,14 @@
-## Problem
 
-<!-- What feature are you adding, or what is broken/missing/sub-optimal? -->
-<!-- Context, symptoms, motivation. Link the issue. -->
-
-Closes DIM-XXX
-
-## Solution
-
-<!-- What you changed and why this approach -->
-<!-- Key design decisions / tradeoffs -->
+## Description
 <!-- Keep it high-signal; deep planning belongs in the issue. -->
 
-## Breaking Changes
-
-<!-- Write "None" if not applicable -->
-
-<!-- If applicable:
-- what breaks
-- who is affected
-- migration steps
--->
-
 ## How to Test
 
-<!-- MUST be reproducible. If this section is weak, reviewers can't approve confidently. -->
+<!-- oneliner required to run the actual feature -->
+<!-- blueprint for robot changes, benchmarks for transport changes etc -->
 
 ## Contributor License Agreement
 
 - [ ] I have read and approved the [CLA](https://github.com/dimensionalOS/dimos/blob/main/CLA.md).
+
+Closes DIM-XXX