simplify issue templates — let the refactor team triage (#1368)

Remove verbose fields (dropdowns, use cases, environment, proposed UX) from
all issue templates. Humans just need to say what they want; the refactor
team handles enrichment and triage.

Co-authored-by: lab <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,54 +1,13 @@
 name: Bug Report
-description: Report an error or unexpected behavior
+description: Something broken?
 title: "[Bug]: "
 labels: ["bug", "pending-review"]
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for reporting! Please paste the full error log or run output below.
-
   - type: textarea
-    id: error-log
+    id: what-happened
     attributes:
-      label: Error Log / Run Output
-      description: Paste the complete terminal output showing the error
-      placeholder: |
-        $ spawn claude sprite
-        [error output here...]
+      label: What happened?
+      placeholder: "Paste the error or describe what went wrong"
       render: shell
     validations:
       required: true
-
-  - type: textarea
-    id: expected
-    attributes:
-      label: Expected Behavior
-      description: What did you expect to happen?
-      placeholder: I expected the agent to launch successfully
-    validations:
-      required: false
-
-  - type: textarea
-    id: environment
-    attributes:
-      label: Environment
-      description: |
-        Run these commands and paste the output:
-        - spawn version
-        - uname -a
-      placeholder: |
-        spawn v1.0.0
-        Darwin 23.1.0
-      render: shell
-    validations:
-      required: false
-
-  - type: textarea
-    id: additional
-    attributes:
-      label: Additional Context
-      description: Any other details that might help
-      placeholder: This only happens when using --prompt flag
-    validations:
-      required: false