Add issue templates (bug report + feature request)

[VGIL77]

New issues land as a blank textarea right now, and triage usually means asking for repro steps and env info as a follow-up. A couple of YAML templates would tighten that loop.

What I think we need:

• .github/ISSUE_TEMPLATE/bug_report.yml: description, steps to reproduce, expected vs actual, env (OS, Node version, install method)
• .github/ISSUE_TEMPLATE/feature_request.yml: problem, proposal, alternatives considered
• .github/ISSUE_TEMPLATE/config.yml with blank_issues_enabled: false and a contact link pointing at SECURITY.md, so vuln reports don't get filed publicly by accident

No code, just YAML. Good first issue if someone wants to grab it.

[q404365631]

I would like to work on this. I will add the issue templates.

[VGIL77]

Thanks @q404365631, all yours on this one too. Quick spec so the PR lands clean:

• Three files: bug_report.yml, feature_request.yml, config.yml (the last one with blank_issues_enabled: false and a contact link to SECURITY.md)
• YAML form schema, not the older markdown templates
• Add Closes #15 to the PR description

Happy to have you on both. If you'd rather do them as one PR than two, your call.

[OhhJJ]

This makes a lot of sense. Right now the lack of structure in new issues slows down triage and creates unnecessary back-and-forth.

YAML-based issue templates would help standardize incoming reports and ensure we get the essential details upfront (especially repro steps and environment info).

The proposed split between bug reports and feature requests looks solid, and disabling blank issues is a good call to keep things consistent. Also +1 on adding a clear security contact path to avoid accidental public disclosures.

Definitely a good first issue for someone looking to contribute.