chore: add feature request template, update community docs (#164)

Author: florintimbuc

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: "Bug report"
 description: "Report a bug to help us improve Pixel Agents."
 title: "[Bug]: "
-labels: ["bug"]
+labels: ["type: bug"]
 body:
   - type: textarea
     id: description

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,5 @@
 blank_issues_enabled: false
 contact_links:
-  - name: "Feature request"
-    url: "https://github.com/pablodelucca/pixel-agents/discussions/categories/ideas"
-    about: "Suggest new features or ideas in Discussions."
-  - name: "Question"
+  - name: "Question / Help"
     url: "https://github.com/pablodelucca/pixel-agents/discussions/categories/q-a"
     about: "Ask questions and get help in Discussions."

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,53 @@
+name: "Feature request"
+description: "Suggest a new feature, idea, or improvement for Pixel Agents."
+title: "[Feature]: "
+labels: ["type: feature"]
+body:
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: "Pre-flight checklist"
+      options:
+        - label: "I have searched existing issues and this is not a duplicate"
+          required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: "Problem or motivation"
+      description: "What problem does this solve, or what need does it address? A clear problem statement helps us prioritize."
+      placeholder: "e.g., When I have many agents open, I can't tell which terminal each character is connected to."
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: "Proposed solution"
+      description: "How should it work? Describe the behavior, UI, or API you envision."
+      placeholder: "e.g., Show the terminal name as a label above each character, toggled via a setting."
+    validations:
+      required: true
+
+  - type: dropdown
+    id: importance
+    attributes:
+      label: "How important is this to you?"
+      options:
+        - "Nice to have"
+        - "Would improve my workflow"
+        - "Critical — blocking my use case"
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: "Alternatives considered"
+      description: "Have you considered other solutions or workarounds?"
+
+  - type: textarea
+    id: context
+    attributes:
+      label: "Additional context"
+      description: "Screenshots, mockups, links to related issues or discussions."

.github/workflows/pr-title.yml

@@ -0,0 +1,31 @@
+name: PR Title
+
+on:
+  pull_request_target:
+    types: [opened, edited, synchronize]
+
+permissions:
+  pull-requests: read
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          types: |
+            feat
+            fix
+            refactor
+            chore
+            docs
+            style
+            perf
+            test
+            ci
+            build
+          requireScope: false
+          subjectPattern: ^[a-z].+$
+          subjectPatternError: "PR title subject must start with a lowercase letter: '{subject}'"

.github/workflows/update-badges.yml

@@ -2,7 +2,7 @@ name: Update Badge Stats
 
 on:
   schedule:
-    - cron: '0 6 * * *'
+    - cron: '0 6,14,22 * * *'
   workflow_dispatch:
 
 jobs:

CONTRIBUTING.md

@@ -106,17 +106,20 @@ These rules are set to `warn` — they won't block your PR but will flag violati
    ```
    CI runs these same checks automatically on every PR.
 4. Open a pull request against `main` with:
+   - A **conventional commit PR title** (e.g. `feat: add zoom controls`, `fix: character freezing on terminal close`, `refactor: extract pathfinding module`). CI enforces this format — see [Conventional Commits](https://www.conventionalcommits.org/).
    - A clear description of what changed and why
    - How you tested the changes (steps to reproduce / verify)
    - **Screenshots or GIFs for any UI changes**
 
+> **Note:** PRs are merged using **squash and merge** — all commits in your PR are combined into a single commit on `main`. Your PR title becomes the commit message, which is why the conventional commit format matters.
+
 ## Reporting Bugs
 
 [Open a bug report](https://github.com/pablodelucca/pixel-agents/issues/new?template=bug_report.yml) — the form will guide you through providing the details we need.
 
 ## Feature Requests
 
-Have an idea? [Start a discussion](https://github.com/pablodelucca/pixel-agents/discussions/categories/ideas) in the Ideas category. We love hearing new ideas, and discussing them first helps us collaborate on the best approach together.
+Have an idea? [Open a feature request](https://github.com/pablodelucca/pixel-agents/issues/new?template=feature_request.yml) — the form will guide you through describing the problem and your proposed solution. You can also browse and join ongoing conversations in [Discussions](https://github.com/pablodelucca/pixel-agents/discussions).
 
 ## Security Issues
 

README.md

@@ -139,9 +139,7 @@ We're actively working on the core module and adapter architecture that makes th
 
 ## Community & Contributing
 
-We use **[GitHub Discussions](https://github.com/pablodelucca/pixel-agents/discussions)** for questions, feature ideas, and conversations. **[Issues](https://github.com/pablodelucca/pixel-agents/issues)** are for bug reports only.
-
-If something is broken, open an issue. For everything else, start a discussion.
+Use **[Issues](https://github.com/pablodelucca/pixel-agents/issues)** to report bugs or request features. Join **[Discussions](https://github.com/pablodelucca/pixel-agents/discussions)** for questions and conversations.
 
 See [CONTRIBUTING.md](CONTRIBUTING.md) for instructions on how to contribute.