docs: Add GitHub issue templates

[Akatenvictor]

CONTRIBUTING.md notes no formal issue template exists.

Acceptance Criteria: Add bug report and feature request templates

[kingdavid0016]

@kingdavid0016 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good day maintainer I'll like to work on this kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @kingdavid0016 to this issue.

[samuelelijah585]

@samuelelijah585 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I've reviewed the issue and its acceptance criteria, and I'm confident I can deliver a solution that meets the requirements. I'd appreciate it if you could assign this issue to me. Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @samuelelijah585 to this issue.

[manchesternews98-jpg]

@manchesternews98-jpg has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I’d like to work on Issue #261 because the repository currently does not provide formal GitHub issue templates, even though CONTRIBUTING.md identifies this as a gap. Standardized templates will help contributors provide the information maintainers need to reproduce bugs and evaluate feature requests.

I will first review CONTRIBUTING.md, the existing repository documentation, and the current GitHub configuration to make sure the templates follow the project's terminology and contribution workflow.

I will then add two GitHub issue templates under .github/ISSUE_TEMPLATE/: one for bug reports and one for feature requests.

The bug report template will prompt contributors to provide a clear description, reproduction steps, expected and actual behavior, relevant environment information, and supporting logs or screenshots where appropriate.

The feature request template will guide contributors to explain the problem or motivation, the proposed solution, relevant alternatives, and the expected impact. It will encourage enough context for maintainers to assess the request without forcing unnecessary detail.

I will keep both templates simple and practical so contributors are more likely to complete them while still providing useful information for triage.

I will also check the templates for valid GitHub issue-template formatting and verify that they render correctly when creating a new issue.

Finally, I will ensure the new templates do not conflict with the existing contribution guidelines and make any small documentation adjustment needed to point contributors toward them.

My goal is to give the repository a consistent and easy-to-use issue reporting process that improves bug reproduction, feature evaluation, and overall maintainer triage.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @manchesternews98-jpg to this issue.

[bade22brazy]

@bade22brazy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

hello maintainer, kindly assign these issues to me. i am sure of handling thenm after careful and thorough review

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bade22brazy to this issue.

[drips-wave]

Congratulations, @bade22brazy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @bade22brazy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊