Discussion template update

.github/DISCUSSION_TEMPLATE/community-discussions.yml

@@ -0,0 +1,40 @@
+body:
+  - type: markdown
+    attributes:
+      value: |
+        > [!IMPORTANT]
+        > **Stalwart support has moved to [support.stalw.art](https://support.stalw.art).**
+        >
+        > For an official response from the Stalwart maintainers, please post your question on the support portal. You can sign in there with your existing GitHub account; no separate registration is required.
+        >
+        > You are welcome to start a discussion here and other community members may still reply, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it at [support.stalw.art](https://support.stalw.art).
+        >
+        > Before opening a new report, please review the [documentation](https://stalw.art/docs/) and the [FAQ](https://stalw.art/docs/faq). Most reported issues turn out to be configuration problems rather than actual bugs.
+  - type: textarea
+    attributes:
+      label: Topic
+      description: Describe the question, problem, or topic you want to discuss with the community.
+      placeholder: |
+        I am trying to configure SMTP relay with Stalwart and I am running into ...
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: |
+        Optional. Add anything else that may help the community help you, such as:
+        - Stalwart version and installation method
+        - Backend choices (data store, blob storage, directory)
+        - Relevant configuration snippets or log output
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Acknowledgement
+      options:
+        - label: I have reviewed the [documentation](https://stalw.art/docs/) and the [FAQ](https://stalw.art/docs/faq) and confirm that my question is not addressed there.
+          required: true
+        - label: I understand that maintainers no longer answer support questions through GitHub Discussions, and that for an official response from the Stalwart team I need to post my question at [support.stalw.art](https://support.stalw.art).
+          required: true
+        - label: I agree to follow the project's [Code of Conduct](https://github.com/stalwartlabs/.github/blob/main/CODE_OF_CONDUCT.md).
+          required: true

.github/DISCUSSION_TEMPLATE/issue-triage.yml

@@ -1,13 +0,0 @@
-labels: ["triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        > [!IMPORTANT]
-        > **Stalwart support has moved to [support.stalw.art](https://support.stalw.art).**
-        >
-        > For an official response from the Stalwart maintainers, please post your question on the support portal. You can sign in there with your existing GitHub account; no separate registration is required.
-        >
-        > You are welcome to start a discussion here and other community members may still reply, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it at [support.stalw.art](https://support.stalw.art).
-        >
-        > Before opening a new report, please review the [documentation](https://stalw.art/docs/) and the [FAQ](https://stalw.art/docs/faq). Most reported issues turn out to be configuration problems rather than actual bugs.

UPGRADING/v0_16.md

@@ -4,7 +4,7 @@ Stalwart `v0.16.x` introduces **significant breaking changes** that make its con
 
 Before continuing, please read this document in full. Skipping steps will leave the server in an unrecoverable state and will require restoring from a backup.
 
-If any step below raises questions, a dedicated discussion thread for the `v0.16` upgrade is open at https://github.com/stalwartlabs/stalwart/discussions/3004. The earlier design discussion that led to these changes is also public at https://github.com/stalwartlabs/stalwart/discussions/2892 and describes the user-reported problems that motivated each breaking change.
+If any step below raises questions, a dedicated discussion thread for the `v0.16` upgrade is open at https://support.stalw.art. The earlier design discussion that led to these changes is also public at https://github.com/stalwartlabs/stalwart/discussions/2892 and describes the user-reported problems that motivated each breaking change.
 
 ## A note on downtime
 
@@ -593,7 +593,7 @@ If the migration cannot be completed within the available maintenance window, th
 
 ## Questions
 
-If any part of this migration is unclear, or if something does not behave as documented, please post in the dedicated upgrade discussion at https://github.com/stalwartlabs/stalwart/discussions/3004. Include:
+If any part of this migration is unclear, or if something does not behave as documented, please post in the dedicated upgrade discussion at https://support.stalw.art. Include:
 
 - The deployment type (binary / Docker / clustered)
 - The datastore backend (RocksDB / SQLite / PostgreSQL / MySQL / FoundationDB)