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

[hivecommons-hive]

Outreach Content

This adds issue forms under .github/ISSUE_TEMPLATE/. Today a pluk user who clicks New issue sees only the org-inherited "Propose a project to join Hive Commons" form or a blank issue.

• bug_report.yml asks for the pluk version, environment (OS, Node, tmux), command, --cli pattern set, repro steps, expected and actual behaviour, and JSONL output.
• pattern_request.yml covers output a pattern set misclassifies and requests for a new CLI pattern set. It asks for sample terminal lines and the expected event, links the README "Pattern File Format" section and patterns/, and suggests testing a fix with --patterns-dir.
• feature_request.yml asks for the use case, the proposal, and its impact on the JSONL schema, flags and pattern format.
• config.yml keeps blank issues enabled and adds contact links to SECURITY.md, the Hive Commons Discord, and the org project-proposal form. That form would otherwise be hidden once the repo has its own template folder.

Only .github/ISSUE_TEMPLATE/ changes. There is no code change and no changelog fragment, since this is not part of the npm package. All four files parse as YAML and only use labels that already exist (bug, enhancement).

Claim evidence

• Version, environment and command fields:
  • pluk version prints the version: src/cli.ts usage text and case 'version'.
  • Node 22 or newer: package.json engines.node: ">=22".
  • tmux is needed for attach, watch --capture and send: CONTRIBUTING.md "Local development".
  • The command list matches the usage text in src/cli.ts.
• --cli options claude, copilot, gemini, goose, codex, aider, omp come from README.md (--cli flag row and "Supported CLIs") and patterns/*.patterns. Custom sets via --patterns-dir are documented in the README "Supported CLIs" section.
• Event type names (rate_limit, state_change, tool_call_started) come from the README.md "Event Types" table. The KEY='regex' format comes from the README.md "Pattern File Format" section.
• The JSONL schema and pattern format compatibility wording follows the README.md "Event Schema" section.
• The security link points to SECURITY.md, which says not to file public issues. Private vulnerability reporting is disabled for this repo (GET /repos/hivecommons/pluk/private-vulnerability-reporting returns enabled: false).
• The Discord URL is the same as the contact link in hivecommons/hive .github/ISSUE_TEMPLATE/config.yml.
• The project-proposal link targets hivecommons/.github .github/ISSUE_TEMPLATE/join-hive-commons.yml.

Closes #299

---

Filed by outreach agent (ACMM L6 — full mode)

— hive: agent=outreach backend=copilot model=claude-opus-5.5 copilot=1.0.88

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hivecommons-hive]

Evidence bundle `#30089cd699` sha256:151dbeb3e8e30a0f1ba22239be0d75879201173cee9986e1e68032e19f708e42 — download from the dashboard or `hivectl review evidence #300`.

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback