chore: agregar issue templates y PR template

Author: Joshumpa

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,69 @@
+name: Bug report
+description: Report a bug in Helm
+labels: ["bug"]
+body:
+  - type: dropdown
+    id: track
+    attributes:
+      label: Track
+      description: Which track does this affect?
+      options:
+        - Track A (music, Bluetooth, settings, OTA)
+        - Track B (radio, camera, MCU data, CarPlay)
+        - Both / unsure
+    validations:
+      required: true
+
+  - type: input
+    id: helm-version
+    attributes:
+      label: Helm version
+      placeholder: "e.g. v1.0.0"
+    validations:
+      required: true
+
+  - type: input
+    id: mcu-firmware
+    attributes:
+      label: MCU firmware version
+      description: Found in Helm Settings → About → Firmware MCU
+      placeholder: "e.g. T13.1.1"
+
+  - type: input
+    id: android-build
+    attributes:
+      label: Android build
+      description: Found in Helm Settings → About → Android
+      placeholder: "e.g. Android 10 (API 29)"
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to reproduce
+      placeholder: |
+        1. Open...
+        2. Tap...
+        3. ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logcat output
+      description: Paste relevant logcat lines if available
+      render: text

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,37 @@
+name: Feature request
+description: Suggest a new feature or improvement for Helm
+labels: ["enhancement"]
+body:
+  - type: dropdown
+    id: track
+    attributes:
+      label: Track
+      description: Which development track would this belong to?
+      options:
+        - Track A (no root required)
+        - Track B (requires root / FEL mode)
+        - Unsure
+    validations:
+      required: true
+
+  - type: textarea
+    id: motivation
+    attributes:
+      label: Motivation
+      description: What problem does this solve? Why is it relevant for a car OS?
+    validations:
+      required: true
+
+  - 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 thought about?

.github/pull_request_template.md

@@ -0,0 +1,25 @@
+## What
+
+<!-- One sentence describing the change -->
+
+## Why
+
+<!-- Motivation — link the issue or OpenSpec change if applicable -->
+
+## Track
+
+- [ ] Track A (no root required)
+- [ ] Track B (root required — stub compiles and runs without it)
+
+## Checklist
+
+- [ ] `./gradlew assembleDebug` passes
+- [ ] `./gradlew detekt` passes
+- [ ] `./gradlew test` passes
+- [ ] Tested on emulator (Track A) or real device (Track B)
+- [ ] No direct OEM / MCU API calls from feature modules — everything goes through `:sdk`
+- [ ] Track B code compiles and shows stub UI without root
+
+## Screenshots / Video
+
+<!-- For UI changes, attach a screenshot or screen recording -->