Complete .github/ISSUE_TEMPLATE/ set — bug_report form is missing

[N-thnI]

Description

Round out the issue-template set to include a structured bug report form.

Problem Statement

.github/ISSUE_TEMPLATE/ exists with feature_request.md but no bug report form, so bug reports currently start as a blank freeform box while feature requests are structured. Inconsistent triage quality across issue types.

Proposed Changes

• Add .github/ISSUE_TEMPLATE/bug_report.yml (issue-forms format) with fields for affected module (engine-core, engine-bridge, dashboard), expected/actual behavior, repro steps
• Add .github/ISSUE_TEMPLATE/config.yml pointing security reports to SECURITY.md's process instead of the public tracker

Technical Implementation Scaffolding

• Target Repository: vero-core-engine
• Target Path: .github/ISSUE_TEMPLATE/
• Branch Naming: chore/issue--add-bug-report-template
• Authority Context: Repository hygiene / non-code

Acceptance Criteria

• New issue creation shows a template chooser including a structured bug report form
• Security-report path routes to SECURITY.md, not the public tracker

Definition of Done

• Reviewed by lead maintainer
• Pull request merged via verified status check

[ABEEGOLD]

Hello Maintainer,

I've reviewed the issue and have experience with GitHub repository maintenance, issue forms, contributor workflows, and open-source project governance. I understand the goal is to complete the repository's issue management setup by introducing a structured bug-report workflow and directing security disclosures through the appropriate private channel.

My approach will be to create a bug_report.yml issue form using GitHub Issue Forms, with clear and actionable fields for affected module, expected behavior, actual behavior, reproduction steps, environment details, and supporting evidence. This will improve issue quality, reduce triage time, and ensure bug reports contain the information maintainers need to investigate problems effectively.

I'll also add a config.yml configuration file to enable the issue template chooser and route security-related reports to the process documented in SECURITY.md, preventing sensitive vulnerabilities from being disclosed publicly. Finally, I'll verify that the template chooser displays correctly, that the new bug-report workflow integrates cleanly with the existing feature-request template, and that the overall contributor experience remains simple and consistent.

[grantfox-oss]

🦊 GrantFox — @ABEEGOLD has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #211)
2. Your PR will be reviewed by the Vero-protocol maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@ABEEGOLD's PR #216 was approved and merged by @N-thnI.

🏆 @ABEEGOLD: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (764 total points). Track your full progress on GrantFox.

👏 Great work, @ABEEGOLD! Keep contributing to Vero-protocol.