docs: add issue forms for bugs, pattern requests and features

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,88 @@
+name: Bug report
+description: Report a reproducible problem in pluk
+title: "bug: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a problem. If an agent CLI's output was classified as the
+        wrong event type (or not classified at all), use the **Pattern request** form instead.
+        Redact tokens and private data from any output you paste.
+  - type: input
+    id: version
+    attributes:
+      label: pluk version
+      description: Output of `pluk version`.
+      placeholder: "0.10.0"
+    validations:
+      required: true
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: Operating system, `node --version` (pluk requires Node.js 22 or newer), and `tmux -V` if you used `attach`, `watch --capture`, or `send`.
+      placeholder: "Ubuntu 24.04, Node v22.11.0, tmux 3.4"
+    validations:
+      required: true
+  - type: dropdown
+    id: command
+    attributes:
+      label: Command
+      description: Which pluk command shows the problem?
+      options:
+        - attach
+        - watch
+        - subscribe
+        - send
+        - sessions
+        - patterns
+        - library API (import from @hivecommons/pluk)
+        - other
+    validations:
+      required: true
+  - type: dropdown
+    id: cli
+    attributes:
+      label: Agent CLI (`--cli`)
+      options:
+        - claude
+        - copilot
+        - gemini
+        - goose
+        - codex
+        - aider
+        - omp
+        - custom pattern set (`--patterns-dir`)
+        - not applicable
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Steps to reproduce
+      description: The exact commands you ran, including flags.
+      placeholder: |
+        1. pluk attach my-agent --cli=claude
+        2. ...
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behavior
+    validations:
+      required: true
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual behavior
+      description: What happened instead, including any stderr output.
+    validations:
+      required: true
+  - type: textarea
+    id: events
+    attributes:
+      label: JSONL events or logs
+      description: Relevant lines from `pluk watch` / `pluk subscribe` output or the session log.
+      render: shell

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Report a security vulnerability
+    url: https://github.com/hivecommons/pluk/blob/main/SECURITY.md
+    about: Please do not file vulnerabilities as public issues. Follow SECURITY.md instead.
+  - name: Join our Discord
+    url: https://hivecommons.dev/discord
+    about: Ask setup, contributor, and community questions in the Hive Commons Discord.
+  - name: Propose a project to join Hive Commons
+    url: https://github.com/hivecommons/.github/issues/new?template=join-hive-commons.yml
+    about: Project proposals for the Hive Commons family are handled in the hivecommons/.github repository.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,29 @@
+name: Feature request
+description: Suggest an improvement or new capability for pluk
+title: "feature: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: use-case
+    attributes:
+      label: Use case
+      description: What problem are you trying to solve, and who is affected?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: The command, flag, event type, or library API change you want.
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Workarounds or other designs you have considered.
+  - type: textarea
+    id: compatibility
+    attributes:
+      label: Compatibility
+      description: Would this change the JSONL event schema, existing flags, or pattern file format?

.github/ISSUE_TEMPLATE/pattern_request.yml

@@ -0,0 +1,57 @@
+name: Pattern request
+description: An agent CLI's output was misclassified, or you want a pattern set for a new CLI
+title: "patterns: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        pluk classifies terminal output with per-CLI regex pattern files in
+        [`patterns/`](https://github.com/hivecommons/pluk/tree/main/patterns). See the
+        [Pattern File Format](https://github.com/hivecommons/pluk#pattern-file-format) section of the README
+        for the recognized keys. You can try a fix locally with `--patterns-dir`.
+        Redact tokens and private data from any terminal output you paste.
+  - type: dropdown
+    id: kind
+    attributes:
+      label: Request type
+      options:
+        - Existing pattern set misclassifies output
+        - New pattern set for a CLI pluk does not support yet
+    validations:
+      required: true
+  - type: input
+    id: cli
+    attributes:
+      label: Agent CLI and version
+      description: For example `claude` / Claude Code 2.x, or the name and version of the new CLI.
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: pluk version
+      description: Output of `pluk version`.
+    validations:
+      required: true
+  - type: textarea
+    id: sample
+    attributes:
+      label: Sample terminal output
+      description: The exact lines (or `--capture` screen) that should produce an event.
+      render: text
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected event
+      description: Which event type should these lines produce (for example `rate_limit`, `state_change`, `tool_call_started`), and what did pluk emit instead?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed pattern (optional)
+      description: A `KEY='regex'` line you tested with `--patterns-dir`, if you have one.
+      render: shell