Add structured GitHub issue templates

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,88 @@
+name: Bug report
+description: Report a reproducible problem in Opaque Stellar.
+title: "[Bug]: "
+labels:
+  - bug
+  - dx
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping improve Opaque Stellar. Do not report security vulnerabilities here; use the private security advisory link from the issue chooser instead.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: What went wrong, and what did you expect to happen?
+      placeholder: I expected ..., but ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: steps
+    attributes:
+      label: Reproduction steps
+      description: Provide the smallest set of steps or commands that reproduces the issue.
+      placeholder: |
+        1. Run ...
+        2. Open ...
+        3. See ...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Affected area
+      multiple: true
+      options:
+        - Soroban contracts
+        - Frontend wallet
+        - Scanner / WASM
+        - Circuits / proofs
+        - Deployment / CI
+        - Documentation
+        - Not sure
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      placeholder: "macOS 15.5, Ubuntu 24.04, Windows 11, etc."
+    validations:
+      required: true
+
+  - type: input
+    id: node-version
+    attributes:
+      label: Node.js version
+      placeholder: "node --version"
+
+  - type: input
+    id: rust-version
+    attributes:
+      label: Rust version
+      placeholder: "rustc --version"
+
+  - type: input
+    id: stellar-cli-version
+    attributes:
+      label: Stellar CLI version
+      placeholder: "stellar --version"
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs or screenshots
+      description: Paste relevant terminal output, browser console errors, screenshots, or failing test output. Redact secrets and private keys.
+      render: shell
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Link related issues, pull requests, deployments, or docs.
+

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,12 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Report a security vulnerability
+    url: https://github.com/opaquecash/stellar-v1/security/advisories/new
+    about: Please use a private GitHub security advisory instead of a public issue.
+  - name: Security policy
+    url: https://github.com/opaquecash/stellar-v1/blob/main/SECURITY.md
+    about: Read the repository security policy, scope, and reporting guidance.
+  - name: Contributing guide
+    url: https://github.com/opaquecash/stellar-v1/blob/main/.github/CONTRIBUTING.md
+    about: Review contribution expectations before opening a pull request.
+

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,68 @@
+name: Feature request
+description: Suggest a scoped improvement for Opaque Stellar.
+title: "[Feature]: "
+labels:
+  - enhancement
+  - documentation
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this form for product, documentation, DX, testing, and tooling improvements. Please keep requests scoped and avoid including secrets or sensitive wallet information.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem or opportunity
+      description: What user, developer, operator, or maintainer problem should this solve?
+      placeholder: This would help because ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: Describe the change you would like to see.
+      placeholder: |
+        - Add ...
+        - Update ...
+        - Keep ...
+    validations:
+      required: true
+
+  - type: dropdown
+    id: area
+    attributes:
+      label: Affected area
+      multiple: true
+      options:
+        - Soroban contracts
+        - Frontend wallet
+        - Scanner / WASM
+        - Circuits / proofs
+        - Deployment / CI
+        - Documentation
+        - Developer experience
+        - Not sure
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Share any workarounds, rejected approaches, or related designs.
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact and compatibility
+      description: Note any expected effect on contracts, scanner behavior, event ABI, storage layout, frontend UX, deployments, or docs.
+
+  - type: textarea
+    id: references
+    attributes:
+      label: References
+      description: Link related issues, pull requests, specs, docs, or external references.
+