Refresh repository presentation and contribution metadata

.github/FUNDING.yml

@@ -1,2 +1,2 @@
+open_collective: wave-lang
 github: [wavefnd, LunaStev]
-open_collective: wave-lang

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,57 @@
+name: Bug report
+description: Report a reproducible compiler, language, code generation, or toolchain defect.
+title: "[Bug]: "
+labels:
+  - bug
+body:
+  - type: checkboxes
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues for the same problem.
+          required: true
+        - label: I can reproduce this with a supported Wave compiler build.
+          required: true
+  - type: input
+    attributes:
+      label: Wave version
+      description: Paste the complete output of `wavec --version`.
+      placeholder: wavec ...
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Host environment
+      description: Operating system, architecture, and relevant toolchain versions.
+      placeholder: Fedora Linux, x86_64, LLVM ...
+    validations:
+      required: true
+  - type: input
+    attributes:
+      label: Target triple
+      description: The selected target, or `host default` if no target was passed.
+      placeholder: riscv64-unknown-linux-gnu
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Reproduction
+      description: Include the smallest Wave source and the exact command needed to reproduce the problem.
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected behavior
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Actual behavior and diagnostics
+      description: Include complete stdout, stderr, exit status, and backtrace when available.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add related files, regressions, linker/sysroot details, or anything else that may help.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Design discussions and questions
+    url: https://github.com/wavefnd/Wave/discussions
+    about: Discuss language design, usage questions, and ideas before opening an implementation issue.
+  - name: Wave community
+    url: https://wave-lang.dev/community
+    about: Get help and talk with other Wave users and contributors.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,46 @@
+name: Feature request
+description: Propose a focused language, compiler, target, standard library, or tooling improvement.
+title: "[Proposal]: "
+labels:
+  - enhancement
+body:
+  - type: checkboxes
+    attributes:
+      label: Before submitting
+      options:
+        - label: I searched existing issues and discussions for this proposal.
+          required: true
+  - type: dropdown
+    attributes:
+      label: Area
+      options:
+        - Language and semantics
+        - Parser and frontend
+        - LLVM code generation
+        - Target and ABI support
+        - CLI and diagnostics
+        - Standard library
+        - Testing and CI
+        - Documentation
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Problem
+      description: Describe the concrete limitation or use case this proposal addresses.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Proposed contract
+      description: Explain the expected syntax, semantics, CLI behavior, or target contract with examples where useful.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Alternatives and compatibility
+      description: Describe alternatives considered and any compatibility, migration, ABI, or platform impact.
+  - type: textarea
+    attributes:
+      label: Additional context