feat: update issue reporting templates and specifications

- Rename "Plot Request" to "Request Specification" in spec-request.yml
- Add new report-impl-issue.yml template for implementation issues
- Add new report-spec-issue.yml template for specification issues
- Update SpecPage.tsx to use new templates based on issue type
- Enhance overview.md with details about new templates

Author: MarkusNeusinger

.github/ISSUE_TEMPLATE/report-impl-issue.yml

@@ -0,0 +1,64 @@
+name: Report Implementation Issue
+description: Report a problem with a specific library implementation
+labels: ["report-pending"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Report Implementation Issue
+
+        Use this form to report problems with a **specific library implementation**.
+
+        For issues that affect all libraries (specification problems), use [Report Spec Issue](https://github.com/MarkusNeusinger/pyplots/issues/new?template=report-spec-issue.yml) instead.
+
+  - type: input
+    id: spec_id
+    attributes:
+      label: Specification ID
+      description: The spec ID from the URL (e.g., scatter-basic)
+      placeholder: scatter-basic
+    validations:
+      required: true
+
+  - type: input
+    id: library
+    attributes:
+      label: Library
+      description: Which library implementation has the issue?
+      placeholder: matplotlib
+    validations:
+      required: true
+
+  - type: checkboxes
+    id: affects_others
+    attributes:
+      label: Scope
+      options:
+        - label: Also affects other libraries
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Category
+      description: What type of issue is this?
+      options:
+        - Visual (design, clarity, hard to read)
+        - Data (unrealistic values, inappropriate context)
+        - Functional (doesn't work as expected)
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Issue Description
+      description: Describe the problem. Include screenshots if helpful.
+      placeholder: |
+        What's wrong:
+        The implementation shows X but should show Y...
+
+        Expected behavior:
+        The plot should...
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/report-issue.yml

@@ -0,0 +1,48 @@
+name: Report Specification Issue
+description: Report a problem with a plot specification (affects all libraries)
+labels: ["report-pending"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## Report Specification Issue
+
+        Use this form to report problems with a **specification** that affects all library implementations.
+
+        For issues with a specific library implementation, use [Report Implementation Issue](https://github.com/MarkusNeusinger/pyplots/issues/new?template=report-impl-issue.yml) instead.
+
+  - type: input
+    id: spec_id
+    attributes:
+      label: Specification ID
+      description: The spec ID from the URL (e.g., scatter-basic)
+      placeholder: scatter-basic
+    validations:
+      required: true
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Category
+      description: What type of issue is this?
+      options:
+        - Visual (design, clarity, hard to read)
+        - Data (unrealistic values, inappropriate context)
+        - Functional (doesn't work as expected)
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Issue Description
+      description: Describe the problem. Include screenshots if helpful.
+      placeholder: |
+        What's wrong:
+        The specification describes X but should describe Y...
+
+        Expected behavior:
+        The plot should...
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/report-spec-issue.yml

@@ -1,4 +1,4 @@
-name: Plot Request
+name: Request Specification
 description: Propose a new plot type for pyplots
 labels: ["spec-request"]
 body:

.github/ISSUE_TEMPLATE/spec-request.yml

@@ -81,11 +81,15 @@ jobs:
 
             2. **Parse the issue body** to extract:
                - spec_id (from "Specification ID" field)
-               - target (Specification or Implementation)
-               - library (if implementation)
+               - library (if present - only in impl issues)
+               - affects_others (check for `- [x] Also affects other libraries`)
                - category (Visual/Data/Functional/Other)
                - description
 
+               **Determine issue type:**
+               - If "Library" field exists → Implementation issue
+               - If no "Library" field → Specification issue
+
             3. **Validate the spec exists:**
                ```bash
                ls plots/{spec_id}/
@@ -122,15 +126,16 @@ jobs:
                # Remove pending, add validated
                gh issue edit ${{ github.event.issue.number }} --remove-label "report-pending" --add-label "report-validated"
 
-               # Add target label
+               # Add target label based on issue type
+               # For spec issues:
                gh issue edit ${{ github.event.issue.number }} --add-label "report:spec"
-               # OR for impl:
+               # For impl issues:
                gh issue edit ${{ github.event.issue.number }} --add-label "report:impl" --add-label "report:impl:{library}"
 
                # Add category label (map from dropdown value)
-               # Visual → category:visual
-               # Data → category:data
-               # Functional → category:functional
+               # Visual... → category:visual
+               # Data... → category:data
+               # Functional... → category:functional
                # Other → category:other
                gh issue edit ${{ github.event.issue.number }} --add-label "category:{category}"
                ```