Implement Automated Issue Templates for Bug Reports and Feature Requests

[Nitya-003]

📝 Description

Currently, the repository uses a generic issue format. As a multi-service project involving Go, Rust, and Blockchain protocols (x402), this often results in missing information—such as which specific service (Gateway vs. Verifier) is failing or which environment (Docker vs. Local) is being used.

🎯 Proposed Solution

Implement a robust issue template system using GitHub Issue Forms (YAML) or standard Markdown templates in .github/ISSUE_TEMPLATE/.

I propose adding three specific templates:

1. 🐛 Bug Report: Includes fields for Service (Go/Rust/Next.js), Environment, Logs, and "Steps to Reproduce."
2. 🚀 Feature Request: Focuses on the "Why" and "How," asking for the impact on the x402 protocol or performance.
3. 🧪 Research/Optimization: For proposed changes to the cryptographic logic (k256) or latency improvements.

💎 Why this is important for MicroAI Paygate:

• Faster Debugging: Automatically prompts for the OPENROUTER_API status and service logs.
• Polyglot Organization: Filters issues by service type (e.g., a Rust compiler error vs. a Next.js UI glitch).
• Standardization: Aligns the project with professional open-source standards for SWOC'26.

✅ Tasks

• Create .github/ISSUE_TEMPLATE/ directory.
• Add bug_report.md with sections for Service logs and Environment details.
• Add feature_request.md with a focus on architectural impact.
• Add config.yml to direct users to discussions or help channels.

---

I am a contributor from SWOC'26 and would like to handle this enhancement to streamline our issue tracking!

Labels: SWOC'26, SWOC