@helyx/core 0.2.1 → 0.2.3

package/dist/help-collection.js

@@ -0,0 +1,4124 @@
+export const BUNDLED_HELP_COLLECTION = {
+    schemaVersion: 2,
+    revision: "b81f1560739cdeba0a8a269ae32f6c4ff92e84c937774e4c208b1c587bd9d8b2",
+    faqs: [
+        {
+            id: "100001",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "The command is not visible",
+            answerMarkdown: "Confirm Feedback is enabled, the command update has completed and the channel permits members to use application commands.",
+            answerText: "Confirm Feedback is enabled, the command update has completed and the channel permits members to use application commands.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/#help-faq-100001",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "4466bcbe22caad9ce324b0bdce65f187a3733be51783d03c5c5775598ff16b07",
+        },
+        {
+            id: "100002",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "The form opens but cannot be submitted",
+            answerMarkdown: "Ask a server manager to confirm the destination is still configured, the member's `feedback.participate` policy allows submission and Helyx can view and send messages in the destination. For the slash-command route, also check `feedback.send`.",
+            answerText: "Ask a server manager to confirm the destination is still configured, the member's feedback.participate policy allows submission and Helyx can view and send messages in the destination. For the slash-command route, also check feedback.send.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/#help-faq-100002",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "e00945d313f3aa617ae7af8832ef90d5aad23d578a1f71851f342f9f54261f39",
+        },
+        {
+            id: "100003",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "A panel button works but the slash command does not",
+            answerMarkdown: "The persistent panel and Discord command deployment are separate entry points. Check the command update status, channel-level command restrictions and `feedback.send`; both paths still apply `feedback.participate` and the same submission limits.",
+            answerText: "The persistent panel and Discord command deployment are separate entry points. Check the command update status, channel-level command restrictions and feedback.send; both paths still apply feedback.participate and the same submission limits.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/#help-faq-100003",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "2e466e0319461904e8a20327ebb2b176619dc63a80958c8c734a970534aba762",
+        },
+        {
+            id: "100004",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "This module is disabled in this server",
+            answerMarkdown: "A server manager must enable Feedback. Existing panel messages stay in Discord, but their buttons cannot bypass the disabled-module check.",
+            answerText: "A server manager must enable Feedback. Existing panel messages stay in Discord, but their buttons cannot bypass the disabled-module check.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100004",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "9f8206122b0d75291514c2daa9926de8561ef0b25389225b9c0571cf9fee5001",
+        },
+        {
+            id: "100005",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "You do not have permission to use this command",
+            answerMarkdown: "Your `feedback.send` permission does not allow this command. A server manager can review the module default, command override and denied roles under [Permissions](https://docs.helyx.gg/modules/feedback/permissions/).",
+            answerText: "Your feedback.send permission does not allow this command. A server manager can review the module default, command override and denied roles under Permissions.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100005",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "502db527b4dd053d07fcaebbb7ee038811bbd396132832844de2c1ab4227bcb7",
+        },
+        {
+            id: "100006",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "You do not have permission to submit feedback",
+            answerMarkdown: "Your `feedback.participate` permission does not allow submission. A\nserver manager can review the operation under\n[Permissions](https://docs.helyx.gg/modules/feedback/permissions/). This operation applies to both\ncommand and panel forms.",
+            answerText: "Your feedback.participate permission does not allow submission. A server manager can review the operation under Permissions. This operation applies to both command and panel forms.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100006",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "ad5ecd3432b32f6c57dc3b2b84b8ad6138e237c2ead42d6bc8de5efbae463b21",
+        },
+        {
+            id: "100007",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Feedback has not been configured",
+            answerMarkdown: "A server manager must save a destination in the dashboard. Enabling Feedback does not create a destination automatically.",
+            answerText: "A server manager must save a destination in the dashboard. Enabling Feedback does not create a destination automatically.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100007",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "f87bc0637eecb8466182745ac73ec4da7d1d15f955c6827825ccd672ed88217f",
+        },
+        {
+            id: "100008",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Please provide a longer subject or feedback message",
+            answerMarkdown: "The values are too short after surrounding spaces are removed. Use at least 3 visible characters for the subject and 10 for the feedback.",
+            answerText: "The values are too short after surrounding spaces are removed. Use at least 3 visible characters for the subject and 10 for the feedback.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100008",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "2b52149c18001834aa21cb2814c42ceb816ff821bd2ecd7289339ac7c323755e",
+        },
+        {
+            id: "100009",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "You have reached the feedback limit",
+            answerMarkdown: "Wait until the private Discord timestamp. Opening a new form, switching entry path or changing channels does not reset either submission window.",
+            answerText: "Wait until the private Discord timestamp. Opening a new form, switching entry path or changing channels does not reset either submission window.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100009",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "67a27889e83954c4c0d289c73fa06c030afb0e30eabeaf8dca07675fb27f21f5",
+        },
+        {
+            id: "100010",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Feedback is no longer configured",
+            answerMarkdown: "The saved configuration changed or became invalid while the form was open. Ask a server manager to check Settings, then open a fresh form.",
+            answerText: "The saved configuration changed or became invalid while the form was open. Ask a server manager to check Settings, then open a fresh form.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100010",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "b4ce1cd9a7972812022be81fe5f0ebf2a87fdaa1461f57f25847229565452ca6",
+        },
+        {
+            id: "100011",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "The form submits but no card appears",
+            answerMarkdown: "Check that the destination still exists and Helyx has **View Channel** and **Send Messages** there. Do not repeatedly submit the same text while a Discord or permission problem is being investigated, because valid submission attempts are rate limited.",
+            answerText: "Check that the destination still exists and Helyx has View Channel and Send Messages there. Do not repeatedly submit the same text while a Discord or permission problem is being investigated, because valid submission attempts are rate limited.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/commands/send/#help-faq-100011",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/commands/send.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+            ],
+            contentHash: "7579958de1463e7a03a8a8af0331d069a9cb546dbfe27632350e3dc39212c87f",
+        },
+        {
+            id: "100012",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Why does Feedback say it is not configured after I enabled it?",
+            answerMarkdown: "Enabling the module makes its commands and interactions available; it does not choose a destination channel. Choose **Destination channel** under [Settings](https://docs.helyx.gg/modules/feedback/settings/) and save.",
+            answerText: "Enabling the module makes its commands and interactions available; it does not choose a destination channel. Choose Destination channel under Settings and save.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100012",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "424e9efbfac32611e195b30b57a3e85424fad44a0d0ef1188c530d97cb482d4c",
+        },
+        {
+            id: "100013",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "What Discord permissions does Helyx need?",
+            answerMarkdown: "Feedback needs **View Channel** and **Send Messages** in its destination and panel channels. Helyx does not need Discord Administrator for this module.\n\nThese bot permissions are separate from member command policies. If a member is allowed to run `/submit feedback` but Helyx cannot post the result, repair the channel permissions rather than widening the member's command access.",
+            answerText: "Feedback needs View Channel and Send Messages in its destination and panel channels. Helyx does not need Discord Administrator for this module. These bot permissions are separate from member command policies. If a member is allowed to run /submit feedback but Helyx cannot post the result, repair the channel permissions rather than widening the member's command access.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100013",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "df55d63b0a57bdd66e8e567c4375b66a27819526c1cbb3495d0c1517416afbba",
+        },
+        {
+            id: "100014",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Is anonymous feedback completely anonymous?",
+            answerMarkdown: "No. **Anonymous public posts** hides the member's display name on the public Feedback card. Helyx retains the Discord user ID for abuse handling.\n\nIf the `feedback-submitted` event is enabled, the configured staff log channel also receives that member ID. The [Logging guide](https://docs.helyx.gg/modules/feedback/logging/) explains what the logs contain.",
+            answerText: "No. Anonymous public posts hides the member's display name on the public Feedback card. Helyx retains the Discord user ID for abuse handling. If the feedback-submitted event is enabled, the configured staff log channel also receives that member ID. The Logging guide explains what the logs contain.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100014",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "3a57244a5bc4d7fe5a665b4a248b244b74500150209766a57d14c58cbd312ee8",
+        },
+        {
+            id: "100015",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Can other members see a form while it is being completed?",
+            answerMarkdown: "No. The form and its confirmation are private to the member. After submission, the subject, feedback message and public attribution are posted in the configured destination and become visible to people who can view that channel.",
+            answerText: "No. The form and its confirmation are private to the member. After submission, the subject, feedback message and public attribution are posted in the configured destination and become visible to people who can view that channel.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100015",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "4e786884404af3cff9d21eccdd027b6236c94a88881489ede8b267d42099a1e9",
+        },
+        {
+            id: "100016",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Why does the form warn against private or sensitive information?",
+            answerMarkdown: "The submitted content becomes a Discord message in a server channel. Anonymous mode changes attribution but does not turn Feedback into an encrypted private-support system. Members should submit only content appropriate for the destination's audience.",
+            answerText: "The submitted content becomes a Discord message in a server channel. Anonymous mode changes attribution but does not turn Feedback into an encrypted private-support system. Members should submit only content appropriate for the destination's audience.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100016",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "3a71580e77eaa5910adc4ff7744545a9e136edfd84f6121a120850f2bf0eee6c",
+        },
+        {
+            id: "100017",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Does Helyx store the subject and feedback message?",
+            answerMarkdown: "The Feedback module does not copy those fields into its own submission record or activity log. It keeps the IDs and settings needed to identify the server, destination, Discord message, attribution mode and submitter.\n\nDiscord retains the posted Feedback card according to the server's normal message handling.",
+            answerText: "The Feedback module does not copy those fields into its own submission record or activity log. It keeps the IDs and settings needed to identify the server, destination, Discord message, attribution mode and submitter. Discord retains the posted Feedback card according to the server's normal message handling.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100017",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "a21088c3c002fdb89d3190e8cec370a2bd23a4dcd5edfdbd6436cb7c7777c5e1",
+        },
+        {
+            id: "100018",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Why can a member open the form but not submit more feedback?",
+            answerMarkdown: "Each completed form submission must pass two limits: 10 per member per 60 seconds and 3 per member per hour. Both limits apply to forms opened from `/submit feedback` and persistent panels; opening a form does not count towards either limit.\n\nHelyx returns a private Discord timestamp when a limit is reached. Wait for it rather than changing channels or repeatedly opening new forms.",
+            answerText: "Each completed form submission must pass two limits: 10 per member per 60 seconds and 3 per member per hour. Both limits apply to forms opened from /submit feedback and persistent panels; opening a form does not count towards either limit. Helyx returns a private Discord timestamp when a limit is reached. Wait for it rather than changing channels or repeatedly opening new forms.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100018",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "3b453564aea65b304fcb9b639cfb05963c512c8c019ee2f7ae774df4f4e61d68",
+        },
+        {
+            id: "100019",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Can I make /submit feedback staff-only?",
+            answerMarkdown: "Yes. Set the module default or the command's individual override to **Server moderators** or **Selected roles**.\n\nSee [Feedback permissions](https://docs.helyx.gg/modules/feedback/permissions/) for step-by-step examples and denied-role behaviour.",
+            answerText: "Yes. Set the module default or the command's individual override to Server moderators or Selected roles. See Feedback permissions for step-by-step examples and denied-role behaviour.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100019",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "17418e9247396c3da8b8cef9147fa7eec890aed17a0944abe1de52ca8045f920",
+        },
+        {
+            id: "100020",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Why can Helyx not post to the chosen channel?",
+            answerMarkdown: "The channel may have been deleted, its permissions may have changed or Helyx may no longer be able to see it. Confirm that the saved channel still exists and grant Helyx **View Channel** and **Send Messages** there.\n\nIf the failure affects only persistent panels, check the **Panel channel** as well as the Feedback destination.",
+            answerText: "The channel may have been deleted, its permissions may have changed or Helyx may no longer be able to see it. Confirm that the saved channel still exists and grant Helyx View Channel and Send Messages there. If the failure affects only persistent panels, check the Panel channel as well as the Feedback destination.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100020",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "7cf4ba569ae5cbf42a729838d2c1d91a0f2bdc0a8db15554642921df78da21e2",
+        },
+        {
+            id: "100021",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Can the panel channel and Feedback destination be different?",
+            answerMarkdown: "Yes. The panel is only an entry point. Its button opens the form, and the completed card is sent to the separately configured destination.\n\nThis is useful when members should find the button in a rules or information channel while completed feedback belongs elsewhere.",
+            answerText: "Yes. The panel is only an entry point. Its button opens the form, and the completed card is sent to the separately configured destination. This is useful when members should find the button in a rules or information channel while completed feedback belongs elsewhere.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100021",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "774ca8c6610303e99280008c39d2e0f036264b86ad30ff4d4b71191b3813d742",
+        },
+        {
+            id: "100022",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Can I post more than one Feedback panel?",
+            answerMarkdown: "Yes. Every successful **Post feedback panel** action creates a new Discord message. Helyx does not replace an earlier panel automatically.\n\nKeep only the panels your members need. Remove duplicates manually in Discord.",
+            answerText: "Yes. Every successful Post feedback panel action creates a new Discord message. Helyx does not replace an earlier panel automatically. Keep only the panels your members need. Remove duplicates manually in Discord.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100022",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "819c28947de12968aa66f7085430af49c0e5b3306f54f079f469eeca9809209f",
+        },
+        {
+            id: "100023",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "What happens to old panels after I change settings?",
+            answerMarkdown: "The old Discord message keeps its original heading, guidance, button label and attribution notice. Its button still reads the current saved configuration, so future forms use the latest destination and anonymity mode.\n\nAfter changing visible panel wording or public attribution, post a replacement and remove the old message so the displayed notice remains accurate.",
+            answerText: "The old Discord message keeps its original heading, guidance, button label and attribution notice. Its button still reads the current saved configuration, so future forms use the latest destination and anonymity mode. After changing visible panel wording or public attribution, post a replacement and remove the old message so the displayed notice remains accurate.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100023",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "377279e42158c62d4b358946f8eed54f6319c24981f664195dd02f6b40e7b540",
+        },
+        {
+            id: "100024",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Does changing the destination move existing Feedback cards?",
+            answerMarkdown: "No. The new destination applies to future submissions. Existing Discord messages remain in the channel where they were posted.",
+            answerText: "No. The new destination applies to future submissions. Existing Discord messages remain in the channel where they were posted.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100024",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "0b6a9b7891137ba8614eb937e82492e71b3e913ae719542255791b9fd02df629",
+        },
+        {
+            id: "100025",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "What happens to panel buttons while Feedback is disabled?",
+            answerMarkdown: "The panel messages remain visible, but Helyx rejects new button, form and command work with a private disabled-module message. Re-enabling Feedback restores the interactions if their saved channels and permissions are still valid.",
+            answerText: "The panel messages remain visible, but Helyx rejects new button, form and command work with a private disabled-module message. Re-enabling Feedback restores the interactions if their saved channels and permissions are still valid.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100025",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "24460b4e54c93227db06b1269ad3272b5bba9a4a1e3b563a0b5fd96c40e72684",
+        },
+        {
+            id: "100026",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Why does Logging show a member ID for an anonymous card?",
+            answerMarkdown: "Public anonymity and staff activity logging have different audiences. The public card hides the display name; the optional restricted log includes the Discord user ID for abuse handling.\n\nDisable **Feedback submitted** if your server does not want that staff record, and restrict the Logging destination whenever it is enabled.",
+            answerText: "Public anonymity and staff activity logging have different audiences. The public card hides the display name; the optional restricted log includes the Discord user ID for abuse handling. Disable Feedback submitted if your server does not want that staff record, and restrict the Logging destination whenever it is enabled.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100026",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "f75178b45ff64771a9fec1a8365e97753f465da13ff22475bf86a41ff4167fdd",
+        },
+        {
+            id: "100027",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Does Logging copy the feedback text?",
+            answerMarkdown: "No. It records that a submission occurred, the member ID, destination ID and public-attribution mode. It does not copy the subject or feedback message.",
+            answerText: "No. It records that a submission occurred, the member ID, destination ID and public-attribution mode. It does not copy the subject or feedback message.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100027",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "1fa65f3d1fce5d620aea7cd99932c0a3236c8a114772ce7b3e2dd2edc9ad37dd",
+        },
+        {
+            id: "100028",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "What happens after a privacy erasure?",
+            answerMarkdown: "Helyx can remove the link to your account from saved submissions and panels you created. The remaining records no longer identify you.\n\nThe request does not automatically delete Discord messages already posted in channels controlled by the server. Server managers must handle those messages according to their own responsibilities and policies.",
+            answerText: "Helyx can remove the link to your account from saved submissions and panels you created. The remaining records no longer identify you. The request does not automatically delete Discord messages already posted in channels controlled by the server. Server managers must handle those messages according to their own responsibilities and policies.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100028",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "602b6544d281aa5194de007d4987d126e433f8fd1ed65cac573a505431c24223",
+        },
+        {
+            id: "100029",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Does deleting a channel delete retained Feedback records?",
+            answerMarkdown: "No. Deleting a Discord channel or message does not itself erase Feedback's saved submission details. It can leave the saved destination invalid, so choose a replacement channel before accepting new submissions.\n\nUse the Helyx Privacy Centre for supported personal-data requests rather than deleting Discord resources as a substitute.",
+            answerText: "No. Deleting a Discord channel or message does not itself erase Feedback's saved submission details. It can leave the saved destination invalid, so choose a replacement channel before accepting new submissions. Use the Helyx Privacy Centre for supported personal-data requests rather than deleting Discord resources as a substitute.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100029",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "b26cfc60fab67a2a17ea7ebc90e6770e19d13f6e2c26d3baebf28e564632e73b",
+        },
+        {
+            id: "100030",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "What if someone else changed the settings while I was editing?",
+            answerMarkdown: "Refresh the dashboard, review the latest saved settings or policy, reapply your intended change and save once. This prevents your older page from overwriting their changes.",
+            answerText: "Refresh the dashboard, review the latest saved settings or policy, reapply your intended change and save once. This prevents your older page from overwriting their changes.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100030",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "8b0ab77a3dbb9a11130029f39a972229f854fe5787cd311fc69f9c4ef4ff0b0d",
+        },
+        {
+            id: "100031",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "Can a member edit or withdraw submitted feedback?",
+            answerMarkdown: "Feedback does not provide a member edit or withdrawal command. The posted card is a Discord message controlled by the server. A member can contact the server team or use the appropriate privacy route if removal or correction is needed.",
+            answerText: "Feedback does not provide a member edit or withdrawal command. The posted card is a Discord message controlled by the server. A member can contact the server team or use the appropriate privacy route if removal or correction is needed.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/faq/#help-faq-100031",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "See the Feedback overview for setup and limits.",
+            ],
+            contentHash: "30579d5d6910eb3db47130c12822662dc7522897c7e6213333a839bcf9ceef43",
+        },
+        {
+            id: "100032",
+            moduleCode: "100",
+            area: "feedback",
+            areaName: "Feedback",
+            moduleId: "helyx.feedback",
+            question: "The event is enabled but no record arrives",
+            answerMarkdown: "Check that Logging itself is enabled, has a destination and can view and send messages there. Then confirm Feedback was delivered successfully; failed or rejected forms do not create a completed submission event.",
+            answerText: "Check that Logging itself is enabled, has a destination and can view and send messages there. Then confirm Feedback was delivered successfully; failed or rejected forms do not create a completed submission event.",
+            sourceUrl: "https://docs.helyx.gg/modules/feedback/logging/#help-faq-100032",
+            sourcePath: "apps/docs/src/content/docs/modules/feedback/logging.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Feedback: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Public anonymity: Anonymous public posts hide the display name on the public Feedback card. Helyx still retains the member's Discord user ID for abuse handling. If your server enables the Feedback logging event, that member ID is also sent to the configured staff log channel.",
+                "Anonymous submissions: The log event includes the submitting member's Discord user ID even when the public Feedback card is anonymous. Keep the Logging destination restricted to appropriate staff.",
+            ],
+            contentHash: "c595300694ca86b801ccd6dcffa0cb6560973d8c458af22153d74a1fbafe5170",
+        },
+        {
+            id: "101001",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "Why did a new member receive no welcome message?",
+            answerMarkdown: "Welcome must be enabled and have a saved valid configuration before the account joins. Check the selected channel and Helyx's **View Channel** and **Send Messages** permissions. Welcome does not replay an event that happened earlier.",
+            answerText: "Welcome must be enabled and have a saved valid configuration before the account joins. Check the selected channel and Helyx's View Channel and Send Messages permissions. Welcome does not replay an event that happened earlier.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101001",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "23e988be151f1fecdefa4042b186a3f5d088deac5017568544cfe69427a3cf87",
+        },
+        {
+            id: "101002",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "Why did the message work but the starting role fail?",
+            answerMarkdown: "The actions are intentionally independent. Helyx still attempts the message when Discord rejects the role. Check **Manage Roles**, move Helyx's role above the starting role, and avoid roles managed by integrations.",
+            answerText: "The actions are intentionally independent. Helyx still attempts the message when Discord rejects the role. Check Manage Roles, move Helyx's role above the starting role, and avoid roles managed by integrations.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101002",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "973913136f1c74a9c28127f24977913c2f4c40a7c786c5b8502dd35444e0b987",
+        },
+        {
+            id: "101003",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "Why was the role assigned when no welcome card appeared?",
+            answerMarkdown: "A channel failure does not cancel the role attempt. Restore Helyx's channel access or select a current Welcome channel under [Settings](https://docs.helyx.gg/modules/welcome/settings/).",
+            answerText: "A channel failure does not cancel the role attempt. Restore Helyx's channel access or select a current Welcome channel under Settings.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101003",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "b27cae6b7383956e3aadc1c4e3023ab5ecce619a87badcce0d5c3cdb333f7629",
+        },
+        {
+            id: "101004",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "What Discord permissions does Welcome need?",
+            answerMarkdown: "It needs **View Channel** and **Send Messages** for the card. A configured starting role also needs **Manage Roles** and a valid role below Helyx in Discord's hierarchy.",
+            answerText: "It needs View Channel and Send Messages for the card. A configured starting role also needs Manage Roles and a valid role below Helyx in Discord's hierarchy.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101004",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "12e36110d34b3a782e232a182e02f04f8b506ce4a749a712ebfecdface98701a",
+        },
+        {
+            id: "101005",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "Why can I select a role that Discord later refuses to assign?",
+            answerMarkdown: "Discord role state can change after the dashboard loads or after Settings are saved. The role may have moved above Helyx, become integration-managed or been deleted. Restore the role and move it below Helyx. The corrected setup applies to future joins.",
+            answerText: "Discord role state can change after the dashboard loads or after Settings are saved. The role may have moved above Helyx, become integration-managed or been deleted. Restore the role and move it below Helyx. The corrected setup applies to future joins.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101005",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "a5134c560fd9b6c6d1228d4d3d4bf0289a6b121e49bd261ead67c1a4f5c131f5",
+        },
+        {
+            id: "101006",
+            moduleCode: "101",
+            area: "welcome",
+            areaName: "Welcome",
+            moduleId: "helyx.welcome",
+            question: "Does Welcome greet bot accounts?",
+            answerMarkdown: "Not by default. Enable **Welcome bot accounts** to include bot joins in both the message and starting-role actions. The setting affects future joins only.",
+            answerText: "Not by default. Enable Welcome bot accounts to include bot joins in both the message and starting-role actions. The setting affects future joins only.",
+            sourceUrl: "https://docs.helyx.gg/modules/welcome/faq/#help-faq-101006",
+            sourcePath: "apps/docs/src/content/docs/modules/welcome/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Welcome: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Welcome overview for setup and limits.",
+            ],
+            contentHash: "bd1eb7eecf1444680a5e40986ccc24a6fc4181640dfb01e263ce5f28e30e2eda",
+        },
+        {
+            id: "102001",
+            moduleCode: "102",
+            area: "access-control",
+            areaName: "Access Control",
+            moduleId: "helyx.account-gate",
+            question: "The bot or connector does not support Channel audit",
+            answerMarkdown: "Update Helyx and Cloud Connect to a release that supports Channel audit, then reconnect and reload the page. Changing Discord permissions will not add support to an older connector.",
+            answerText: "Update Helyx and Cloud Connect to a release that supports Channel audit, then reconnect and reload the page. Changing Discord permissions will not add support to an older connector.",
+            sourceUrl: "https://docs.helyx.gg/modules/access-control/channel-audit/#help-faq-102001",
+            sourcePath: "apps/docs/src/content/docs/modules/access-control/channel-audit.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Access Control: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds - **Documentation reviewed against:** module version `2.1.0`",
+                "Upcoming feature: This guide describes an unreleased dashboard update. Channel audit is advisory and read-only. It will be available for eligible Hosted and Self-Hosted installations with compatible Cloud Connect support, including while Access Control is disabled.",
+            ],
+            contentHash: "6744a23c8eb02a24a6b5c7f3295f8c867fda629af111f72a94a90f9bd419e716",
+        },
+        {
+            id: "102002",
+            moduleCode: "102",
+            area: "access-control",
+            areaName: "Access Control",
+            moduleId: "helyx.account-gate",
+            question: "The result is incomplete or a role cannot be managed",
+            answerMarkdown: "Read the specific channel, permission or hierarchy reason. Check current resources and Helyx's access, then run a fresh audit. Unknown data is not a recommendation to delete a role or channel.",
+            answerText: "Read the specific channel, permission or hierarchy reason. Check current resources and Helyx's access, then run a fresh audit. Unknown data is not a recommendation to delete a role or channel.",
+            sourceUrl: "https://docs.helyx.gg/modules/access-control/channel-audit/#help-faq-102002",
+            sourcePath: "apps/docs/src/content/docs/modules/access-control/channel-audit.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Access Control: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds - **Documentation reviewed against:** module version `2.1.0`",
+                "Upcoming feature: This guide describes an unreleased dashboard update. Channel audit is advisory and read-only. It will be available for eligible Hosted and Self-Hosted installations with compatible Cloud Connect support, including while Access Control is disabled.",
+            ],
+            contentHash: "9836ada1b4ec2e4ff4dd74cd2640b8f528b61583c475bfc67c19d2acc2a95f6a",
+        },
+        {
+            id: "102003",
+            moduleCode: "102",
+            area: "access-control",
+            areaName: "Access Control",
+            moduleId: "helyx.account-gate",
+            question: "There is no current pending check",
+            answerMarkdown: "The member may already hold the access role, may not be a current human server member, or may not have an unfinished Access Control check. Ask a manager to inspect [Members](https://docs.helyx.gg/modules/access-control/members/).",
+            answerText: "The member may already hold the access role, may not be a current human server member, or may not have an unfinished Access Control check. Ask a manager to inspect Members.",
+            sourceUrl: "https://docs.helyx.gg/modules/access-control/commands/#help-faq-102003",
+            sourcePath: "apps/docs/src/content/docs/modules/access-control/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Access Control: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds - **Documentation reviewed against:** module version `2.1.0`",
+            ],
+            contentHash: "9fa3a6bef824155069755db090cc0f1021e23d803de62d6fe90208fbf2cbc283",
+        },
+        {
+            id: "102004",
+            moduleCode: "102",
+            area: "access-control",
+            areaName: "Access Control",
+            moduleId: "helyx.account-gate",
+            question: "The panel is no longer available",
+            answerMarkdown: "The saved Discord message was removed or the panel was replaced. Use the newest published panel or ask a manager to [repair or repost it](https://docs.helyx.gg/modules/access-control/resources/gate-panels/).",
+            answerText: "The saved Discord message was removed or the panel was replaced. Use the newest published panel or ask a manager to repair or repost it.",
+            sourceUrl: "https://docs.helyx.gg/modules/access-control/commands/#help-faq-102004",
+            sourcePath: "apps/docs/src/content/docs/modules/access-control/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Access Control: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds - **Documentation reviewed against:** module version `2.1.0`",
+            ],
+            contentHash: "cdbff83e84977e63b19f45e081c404ec2df9b1324c5cfcd84f8941c51556f682",
+        },
+        {
+            id: "102005",
+            moduleCode: "102",
+            area: "access-control",
+            areaName: "Access Control",
+            moduleId: "helyx.account-gate",
+            question: "The server setup fails validation",
+            answerMarkdown: "Run `/access control status`, then repair the reported role, channel, panel, intent or enabled-question problem before asking members to retry.",
+            answerText: "Run /access control status, then repair the reported role, channel, panel, intent or enabled-question problem before asking members to retry.",
+            sourceUrl: "https://docs.helyx.gg/modules/access-control/commands/#help-faq-102005",
+            sourcePath: "apps/docs/src/content/docs/modules/access-control/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Access Control: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds - **Documentation reviewed against:** module version `2.1.0`",
+            ],
+            contentHash: "92e8a0ba32e3470388cbdfc7dd2eb859c59ba383109e804a361f2049dbc534b5",
+        },
+        {
+            id: "103001",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "The commands are not visible",
+            answerMarkdown: "Check that Achievements is enabled and its commands have finished updating in Discord. In **Permissions**, check access to the command the member needs.",
+            answerText: "Check that Achievements is enabled and its commands have finished updating in Discord. In Permissions, check access to the command the member needs.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/commands/#help-faq-103001",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "bafbd01b63a47a0a8fe7aa624343d36be38b8d02db6bf2c2a47e45cadacb098b",
+        },
+        {
+            id: "103002",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "An earned award has an archived label",
+            answerMarkdown: "The original achievement definition is no longer available. The member keeps their award and the score earned at the time. A server manager can check what happened to the definition.",
+            answerText: "The original achievement definition is no longer available. The member keeps their award and the score earned at the time. A server manager can check what happened to the definition.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/commands/#help-faq-103002",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "9a60cd36cd0c384fcec9b89773b502fc38f85346db7c7a71e3bd9817627b14ba",
+        },
+        {
+            id: "103003",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "The page buttons expired",
+            answerMarkdown: "Run the command again. Page buttons work only for the person who requested them and expire after 10 minutes.",
+            answerText: "Run the command again. Page buttons work only for the person who requested them and expire after 10 minutes.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/commands/#help-faq-103003",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "06a6204688e914bd69441dacf338bbb9c7519884994fa49edd1a7d7460ecf26e",
+        },
+        {
+            id: "103004",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "An event is visible but cannot accept a Nexus reward",
+            answerMarkdown: "Some triggers do not allow a fixed Nexus reward because they are too easy to repeat. Also check that Nexus Rewards is enabled and its **Achievement rewards** setting is on.",
+            answerText: "Some triggers do not allow a fixed Nexus reward because they are too easy to repeat. Also check that Nexus Rewards is enabled and its Achievement rewards setting is on.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/cross-modules/#help-faq-103004",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/cross-modules.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "4f23320b59c685b1ca5011d9fad0bc9b9dd86495e0c6bbfd98fa57f3b7180d81",
+        },
+        {
+            id: "103005",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "An award exists but a reward effect is missing",
+            answerMarkdown: "The achievement has been earned; only its reward is missing. Check the reward role, announcement channel or Nexus settings. Use a retry option if one is offered, rather than creating another award.",
+            answerText: "The achievement has been earned; only its reward is missing. Check the reward role, announcement channel or Nexus settings. Use a retry option if one is offered, rather than creating another award.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/cross-modules/#help-faq-103005",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/cross-modules.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "55bfe739646644ee5e364925c009244cee8b0068077399f5647a54cffac6198c",
+        },
+        {
+            id: "103006",
+            moduleCode: "103",
+            area: "achievements",
+            areaName: "Achievements",
+            moduleId: "helyx.achievements",
+            question: "Does repeatable progress reset?",
+            answerMarkdown: "Repeatable achievements award again whenever the member completes the target another time. Helyx keeps their total progress and recognises activity it has already counted, so retrying delivery does not give an extra award.",
+            answerText: "Repeatable achievements award again whenever the member completes the target another time. Helyx keeps their total progress and recognises activity it has already counted, so retrying delivery does not give an extra award.",
+            sourceUrl: "https://docs.helyx.gg/modules/achievements/faq/#help-faq-103006",
+            sourcePath: "apps/docs/src/content/docs/modules/achievements/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Achievements: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "Find setup instructions in the Achievements overview.",
+            ],
+            contentHash: "ae8b3674f73ec1472dcf17c1ede8cbe001626aa5ccc0ece43e336fb07e62b2c0",
+        },
+        {
+            id: "104001",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "The command is not visible",
+            answerMarkdown: "Confirm AFK is enabled and review the server command state in the dashboard. Normal updates may take about two minutes. Resolve a **Failed**, **Blocked** or **Migration hold** state before retrying.",
+            answerText: "Confirm AFK is enabled and review the server command state in the dashboard. Normal updates may take about two minutes. Resolve a Failed, Blocked or Migration hold state before retrying.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/commands/#help-faq-104001",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "b593a3bfafe3c7e1d66ce913e09597b0342a628f8ddb478ab9600004e9489131",
+        },
+        {
+            id: "104002",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "The command says access is denied",
+            answerMarkdown: "Review **Modules > AFK > Permissions** and the shared [access rules](https://docs.helyx.gg/modules/access/). The server owner and Discord Administrators retain policy access; other members' explicit user rules are checked before role rules. Remove an obsolete applicable deny, or remove the command override to use the module's default permissions again.",
+            answerText: "Review Modules > AFK > Permissions and the shared access rules. The server owner and Discord Administrators retain policy access; other members' explicit user rules are checked before role rules. Remove an obsolete applicable deny, or remove the command override to use the module's default permissions again.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/commands/#help-faq-104002",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "5b3788b121e3598400d128dee4713a0fd75e028e5f4d67bf09c0e249317155f0",
+        },
+        {
+            id: "104003",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "Why is /afk not visible?",
+            answerMarkdown: "AFK must be installed, globally available and enabled for the current Discord server. Command updates may take about two minutes. Check the module's command state in the dashboard; a failed or blocked update needs to be resolved there rather than by repeatedly disabling and enabling the module.\n\nAFK is Live in both the hosted and self-host catalogues.",
+            answerText: "AFK must be installed, globally available and enabled for the current Discord server. Command updates may take about two minutes. Check the module's command state in the dashboard; a failed or blocked update needs to be resolved there rather than by repeatedly disabling and enabling the module. AFK is Live in both the hosted and self-host catalogues.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/faq/#help-faq-104003",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "See the AFK overview for setup and limits.",
+            ],
+            contentHash: "0a2d5b7411363ae06f525b658dd9c691a6ff506372afdc9abcbeca9782c44290",
+        },
+        {
+            id: "104004",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "Why did a mention not produce a notice?",
+            answerMarkdown: "Check these conditions in order:\n\n1. the mentioned member still has an active AFK status in this server;\n2. the source is a normal human message, not a bot, webhook or system event;\n3. Helyx can view the channel and send messages there;\n4. the same away member has not already produced a notice in that channel during the last 60 seconds; and\n5. Helyx's notice cooldown service is working.\n\nIf Helyx cannot check the cooldown, it skips the notice to avoid duplicates. It will not send that notice later.",
+            answerText: "Check these conditions in order: the mentioned member still has an active AFK status in this server; the source is a normal human message, not a bot, webhook or system event; Helyx can view the channel and send messages there; the same away member has not already produced a notice in that channel during the last 60 seconds; and Helyx's notice cooldown service is working. If Helyx cannot check the cooldown, it skips the notice to avoid duplicates. It will not send that notice later.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/faq/#help-faq-104004",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "See the AFK overview for setup and limits.",
+            ],
+            contentHash: "fc5e7f98fb4a6a2de5bc6e044fe6bb4ccb6b215fd180cc6ed78db99545ada9f1",
+        },
+        {
+            id: "104005",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "Will Helyx read my message to find mentions?",
+            answerMarkdown: "No. Discord tells Helyx which users were mentioned, so AFK does not need to read or store the message text. It checks up to 25 different mentioned users.",
+            answerText: "No. Discord tells Helyx which users were mentioned, so AFK does not need to read or store the message text. It checks up to 25 different mentioned users.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/faq/#help-faq-104005",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "See the AFK overview for setup and limits.",
+            ],
+            contentHash: "5ce56d585a9950a3e047b6af8b054213c4c7a3bfb88374163c2cd7edd8640f5b",
+        },
+        {
+            id: "104006",
+            moduleCode: "104",
+            area: "afk",
+            areaName: "AFK",
+            moduleId: "helyx.afk",
+            question: "When is a status cleared automatically?",
+            answerMarkdown: "With **New message**, the away member's next normal human message in the server clears the status before notices for people they mentioned are calculated. With **Manual**, messages do not clear it; the member must use `/afk clear` or set an optional expiry. An expiry clears either rule silently. Bot, webhook and Discord system messages do not clear a status.",
+            answerText: "With New message, the away member's next normal human message in the server clears the status before notices for people they mentioned are calculated. With Manual, messages do not clear it; the member must use /afk clear or set an optional expiry. An expiry clears either rule silently. Bot, webhook and Discord system messages do not clear a status.",
+            sourceUrl: "https://docs.helyx.gg/modules/afk/faq/#help-faq-104006",
+            sourcePath: "apps/docs/src/content/docs/modules/afk/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "AFK: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "See the AFK overview for setup and limits.",
+            ],
+            contentHash: "e0f5d584ee25b66a03b0ac5e976ae51dc6454844ee89ff720955a6f1d32a896f",
+        },
+        {
+            id: "105001",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "Does Analytics continuously record server activity?",
+            answerMarkdown: "No. Helyx scans Discord only when an authorised manager starts a report in the dashboard. It works within the time period and limits chosen for that report.",
+            answerText: "No. Helyx scans Discord only when an authorised manager starts a report in the dashboard. It works within the time period and limits chosen for that report.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105001",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "6b6ba2cd58c81c6316696aaf4f648ea355c7473279c7714d97465c8017739b32",
+        },
+        {
+            id: "105002",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "Does Analytics store message content?",
+            answerMarkdown: "No. It does not store message text, embeds, attachments or components. It stores timestamps, Discord user IDs and activity counts needed for the report.\n\nMessage Content is not required.",
+            answerText: "No. It does not store message text, embeds, attachments or components. It stores timestamps, Discord user IDs and activity counts needed for the report. Message Content is not required.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105002",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "e0e3799c2f65998770ec9dd8b6135df50e0e5a620af066bf0e31107d2f207940",
+        },
+        {
+            id: "105003",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "Does Analytics retain member-level activity?",
+            answerMarkdown: "Yes, within each retained report. The **Most active users** and related result rows keep Discord user IDs with message and channel counts. This is why report viewing defaults to administrators.\n\nDisplay names are resolved from Discord when viewed rather than stored. Delete the report when those retained rows are no longer required.",
+            answerText: "Yes, within each retained report. The Most active users and related result rows keep Discord user IDs with message and channel counts. This is why report viewing defaults to administrators. Display names are resolved from Discord when viewed rather than stored. Delete the report when those retained rows are no longer required.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105003",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "3ece00ea3108dc246c3cc3e67a45bd6499ab166578d3bef01c435253bfc7d235",
+        },
+        {
+            id: "105004",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "Is a report a complete history?",
+            answerMarkdown: "No. Message results are limited by the selected period, per-channel message cap, current Discord availability, exclusions and Helyx permissions. Join figures come from people who are current members when the report runs.",
+            answerText: "No. Message results are limited by the selected period, per-channel message cap, current Discord availability, exclusions and Helyx permissions. Join figures come from people who are current members when the report runs.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105004",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "8c97a54ca0a7b1f65a63da098380dff2c414eee0cd347e3fa6fc3d683552d6a0",
+        },
+        {
+            id: "105005",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "Why is a channel missing rather than shown as zero?",
+            answerMarkdown: "Analytics inventory includes only channels Helyx can currently view and whose history it can read. A missing channel can mean inaccessible or excluded, not inactive.\n\nCheck the report's scope, saved exclusions and channel permissions before assuming a missing channel had no activity.",
+            answerText: "Analytics inventory includes only channels Helyx can currently view and whose history it can read. A missing channel can mean inaccessible or excluded, not inactive. Check the report's scope, saved exclusions and channel permissions before assuming a missing channel had no activity.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105005",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "1353141ce5c0a967a36b831af6480036588839f190cd73460e874950aa2e4e3e",
+        },
+        {
+            id: "105006",
+            moduleCode: "105",
+            area: "analytics",
+            areaName: "Analytics",
+            moduleId: "helyx.analytics",
+            question: "How does role scope work?",
+            answerMarkdown: "It includes channels the selected role can currently view and write in, provided Helyx can also view and read them. It does not recreate historical role access.",
+            answerText: "It includes channels the selected role can currently view and write in, provided Helyx can also view and read them. It does not recreate historical role access.",
+            sourceUrl: "https://docs.helyx.gg/modules/analytics/faq/#help-faq-105006",
+            sourcePath: "apps/docs/src/content/docs/modules/analytics/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Analytics: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Live module: Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds.",
+                "For setup, report workspaces and limits, start with the Analytics overview. :::note[Live module] Analytics is available for Hosted Helyx and supported Helyx Self-Hosted builds. :::",
+            ],
+            contentHash: "1e84326fe8c8d97aaf80e6da2ba0f216c2cbe13ab82e03b157df2bfcab7e7220",
+        },
+        {
+            id: "106001",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "Why are the rule types so limited?",
+            answerMarkdown: "An automatic ban has an immediate and serious effect. The first release therefore accepts only an exact server-owned deny-list match or a signed, approved high-confidence signal.\n\nHelyx will not let server managers approximate unsupported risk scoring through arbitrary conditions.",
+            answerText: "An automatic ban has an immediate and serious effect. The first release therefore accepts only an exact server-owned deny-list match or a signed, approved high-confidence signal. Helyx will not let server managers approximate unsupported risk scoring through arbitrary conditions.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106001",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "3c892e2e1aee0d9030a626d9c15f48a45283be714ba0ea15ac1add68a5cbd6c7",
+        },
+        {
+            id: "106002",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "What is Monitor only?",
+            answerMarkdown: "Monitor mode records a match for review but sends no direct message and requests no ban. Every new policy starts in this mode.\n\nEnforcement requires a fresh confirmation showing current permissions, provider health, entry count and recent simulation.",
+            answerText: "Monitor mode records a match for review but sends no direct message and requests no ban. Every new policy starts in this mode. Enforcement requires a fresh confirmation showing current permissions, provider health, entry count and recent simulation.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106002",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "a5fe24dbc036dbaa843bc8b81c06283de0de57689215732cf684ed362469cc00",
+        },
+        {
+            id: "106003",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "Why does Auto-ban require Moderation?",
+            answerMarkdown: "Moderation creates the case, checks permissions and role positions, applies the ban and checks uncertain results against Discord. Auto-ban asks Moderation to act rather than banning directly.\n\nEnforcement cannot be enabled unless Moderation is working.",
+            answerText: "Moderation creates the case, checks permissions and role positions, applies the ban and checks uncertain results against Discord. Auto-ban asks Moderation to act rather than banning directly. Enforcement cannot be enabled unless Moderation is working.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106003",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "fd1e778addbec39804b614cc4b404cc9ac15b8c463662715c0b1cd1d97dfe723",
+        },
+        {
+            id: "106004",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "What happens if a dependency is unavailable?",
+            answerMarkdown: "Helyx does not ban. A missing database, cache, provider or Moderation service creates an urgent Server Health problem and an honest failed match result.\n\nUncertain evidence always fails safely for the member.",
+            answerText: "Helyx does not ban. A missing database, cache, provider or Moderation service creates an urgent Server Health problem and an honest failed match result. Uncertain evidence always fails safely for the member.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106004",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "54e7ebcbeef8d61bebc631118afc938adbf3b7e9b38eeb5e1ee2df77f317cb6d",
+        },
+        {
+            id: "106005",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "Can several matching policies ban the same member more than once?",
+            answerMarkdown: "No. Helyx recognises repeated requests for the same member and incident, and Moderation prevents duplicate actions.\n\nSeveral matches may link to one outcome without producing several bans or cases.",
+            answerText: "No. Helyx recognises repeated requests for the same member and incident, and Moderation prevents duplicate actions. Several matches may link to one outcome without producing several bans or cases.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106005",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "1555e0eca0ff5e437e4f97351ec79d602ca92d30dcde7bae3d8fb1558cb3dc76",
+        },
+        {
+            id: "106006",
+            moduleCode: "106",
+            area: "auto-ban",
+            areaName: "Auto-ban",
+            moduleId: null,
+            question: "How are approved signals validated?",
+            answerMarkdown: "The signal must come from an installed, core-approved provider, be verified, carry **High confidence**, be unexpired and use a recognised reason.\n\nUnknown, forged, old or lower-confidence signals are rejected.",
+            answerText: "The signal must come from an installed, core-approved provider, be verified, carry High confidence, be unexpired and use a recognised reason. Unknown, forged, old or lower-confidence signals are rejected.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-ban/faq/#help-faq-106006",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-ban/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-ban: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-ban is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Auto-ban overview for the planned rules and setup.",
+            ],
+            contentHash: "3aaf84ee311470fee32bfff2f53d5c6bfaa1b90ac3f443a2c11800b68b1d622e",
+        },
+        {
+            id: "107001",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "Can Helyx restore a deleted message?",
+            answerMarkdown: "No. Discord message deletion is permanent from the module's perspective. Helyx will warn about this before a rule is activated and will not describe the feature as reversible.",
+            answerText: "No. Discord message deletion is permanent from the module's perspective. Helyx will warn about this before a rule is activated and will not describe the feature as reversible.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107001",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "711aa7a8aa1b5cebda712bd37beabdef3c8df06fa5eb991eeb1b73f7ec92d2dd",
+        },
+        {
+            id: "107002",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "Will Auto-delete remove old channel history?",
+            answerMarkdown: "No. It will schedule only newly observed eligible messages. It will not scan a channel, bulk-delete history or apply new rules to older messages.",
+            answerText: "No. It will schedule only newly observed eligible messages. It will not scan a channel, bulk-delete history or apply new rules to older messages.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107002",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "8dd107bd9b94ad72e07d1b5a87c8d1420bc53b88165814d7f7a10c9c04fc4f93",
+        },
+        {
+            id: "107003",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "Will pinned messages be protected?",
+            answerMarkdown: "The first release will not inspect pinned state, so pinning a message must not be treated as a way to cancel its pending deletion. Do not enable Auto-delete in a channel where messages may need to be preserved by pinning them.",
+            answerText: "The first release will not inspect pinned state, so pinning a message must not be treated as a way to cancel its pending deletion. Do not enable Auto-delete in a channel where messages may need to be preserved by pinning them.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107003",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "1a9f75c90474b51dc2e9094814ef1d07fd437f79166a0a7b333f76585de4bf87",
+        },
+        {
+            id: "107004",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "Will Helyx read or store message content?",
+            answerMarkdown: "No. Rules apply by channel, message source and excluded roles, not by words or patterns. Queued work will store only the IDs and timing information needed for the deletion.\n\nMessage bodies, filenames, URLs and author IDs will not be stored.",
+            answerText: "No. Rules apply by channel, message source and excluded roles, not by words or patterns. Queued work will store only the IDs and timing information needed for the deletion. Message bodies, filenames, URLs and author IDs will not be stored.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107004",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "b065b85adbc03ae9db469ca598401b029c4bbc5908b57fd341a618f2b5c4103c",
+        },
+        {
+            id: "107005",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "What permissions will Helyx need?",
+            answerMarkdown: "Helyx will need **View Channel**, **Read Message History** and **Manage Messages** in the configured channel. It will not need Message Content.\n\nRule activation will validate current access. A later permission failure will retry a limited number of times, then mark the deletion for review.",
+            answerText: "Helyx will need View Channel, Read Message History and Manage Messages in the configured channel. It will not need Message Content. Rule activation will validate current access. A later permission failure will retry a limited number of times, then mark the deletion for review.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107005",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "18959e20aefcebefc3d3a3651f6be246e8f005c8ae9b744f87a6342b2c3ed762",
+        },
+        {
+            id: "107006",
+            moduleCode: "107",
+            area: "auto-delete",
+            areaName: "Auto-delete",
+            moduleId: null,
+            question: "What happens when I change a rule’s delay?",
+            answerMarkdown: "The new delay applies only to messages sent after the change. Pending deletions from the previous rule are cancelled.\n\nAn edit will never reinterpret an old message under a new delay.",
+            answerText: "The new delay applies only to messages sent after the change. Pending deletions from the previous rule are cancelled. An edit will never reinterpret an old message under a new delay.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-delete/faq/#help-faq-107006",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-delete/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-delete: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                "Deleted messages cannot be restored: Helyx cannot recover a Discord message after Auto-delete removes it. Every rule will show this warning and require confirmation before activation.",
+                ":::caution[Planned module] Auto-delete is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For setup, supported rules and planned limits, start with the Auto-delete overview.",
+            ],
+            contentHash: "32787210349e6af1fafb464b99b0e416aa1cdad1483b23781ef64151e403d61c",
+        },
+        {
+            id: "108001",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "What can I schedule, and can it mention a role?",
+            answerMarkdown: "Auto-message sends recurring messages on interval, daily or weekly schedules. It manages those schedules directly; you do not need to configure the Scheduler module. Use [Reminders](https://docs.helyx.gg/modules/reminders/) for a one-time personal or server message. Mentions are disabled, so a scheduled message cannot ping a role.",
+            answerText: "Auto-message sends recurring messages on interval, daily or weekly schedules. It manages those schedules directly; you do not need to configure the Scheduler module. Use Reminders for a one-time personal or server message. Mentions are disabled, so a scheduled message cannot ping a role.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/faq/#help-faq-108001",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Use these answers when deciding whether Auto-message fits your server or checking an existing schedule. Auto-message is in Testing and is not available to Hosted or Self-Hosted users. See the module overview for the current feature details.",
+            ],
+            contentHash: "fbac3414f6ba2d13b07c7d61a12f008a323ea82c17c81942966b8ff0fbbce7dd",
+        },
+        {
+            id: "108002",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "Who can manage schedules, and what access does Helyx need?",
+            answerMarkdown: "Schedules are managed in the dashboard, with access controlled by the **auto-message.manage** policy. That policy defaults to administrators; creating a schedule does not give its author a separate personal permission to edit or delete it.\n\nHelyx needs **View Channel**, **Send Messages** and **Embed Links** in the destination text or announcement channel. It does not need Discord Administrator or Message Content access. See [Permissions](https://docs.helyx.gg/modules/auto-message/permissions/) for access settings.",
+            answerText: "Schedules are managed in the dashboard, with access controlled by the auto-message.manage policy. That policy defaults to administrators; creating a schedule does not give its author a separate personal permission to edit or delete it. Helyx needs View Channel, Send Messages and Embed Links in the destination text or announcement channel. It does not need Discord Administrator or Message Content access. See Permissions for access settings.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/faq/#help-faq-108002",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Use these answers when deciding whether Auto-message fits your server or checking an existing schedule. Auto-message is in Testing and is not available to Hosted or Self-Hosted users. See the module overview for the current feature details.",
+            ],
+            contentHash: "968451b6db8189a33a5077091dcdbea3f5d93cb376f34fc9280b099fdf41a61c",
+        },
+        {
+            id: "108003",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "How do I stop a schedule or remove its saved data?",
+            answerMarkdown: "Use **Pause** to stop future deliveries while keeping the definition. Pause an Active schedule before editing or deleting it. Review schedules can be edited, but deletion still requires Paused status. Deleting the paused schedule removes its saved definition; disabling the module is not deletion.\n\nPrivacy requests can include the schedule's creator and last editor. Names and message text may need a person to review them because they can also refer to other people. See [Privacy and retention](https://docs.helyx.gg/modules/auto-message/privacy/) for that distinction.",
+            answerText: "Use Pause to stop future deliveries while keeping the definition. Pause an Active schedule before editing or deleting it. Review schedules can be edited, but deletion still requires Paused status. Deleting the paused schedule removes its saved definition; disabling the module is not deletion. Privacy requests can include the schedule's creator and last editor. Names and message text may need a person to review them because they can also refer to other people. See Privacy and retention for that distinction.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/faq/#help-faq-108003",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Use these answers when deciding whether Auto-message fits your server or checking an existing schedule. Auto-message is in Testing and is not available to Hosted or Self-Hosted users. See the module overview for the current feature details.",
+            ],
+            contentHash: "fa561b4aa09078bee34a6ab0c59033e9b61b971e7b87069b6eb99d36d7b6d94b",
+        },
+        {
+            id: "108004",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "Why did nothing arrive, and can I test without changing the next run?",
+            answerMarkdown: "Check the saved status, next-run time, destination permissions and latest delivery result. Daily and weekly schedules use the saved timezone. After downtime, at most one occurrence within the 24-hour recovery window may run; older occurrences are skipped.\n\n**Send private test** sends the current message to the manager using it and leaves the schedule unchanged. If that test fails, check that your direct messages are open. A successful private test does not prove Helyx can post in the destination channel. Follow [Troubleshooting](https://docs.helyx.gg/modules/auto-message/troubleshooting/) for the matching failure rather than repeatedly publishing the same schedule.",
+            answerText: "Check the saved status, next-run time, destination permissions and latest delivery result. Daily and weekly schedules use the saved timezone. After downtime, at most one occurrence within the 24-hour recovery window may run; older occurrences are skipped. Send private test sends the current message to the manager using it and leaves the schedule unchanged. If that test fails, check that your direct messages are open. A successful private test does not prove Helyx can post in the destination channel. Follow Troubleshooting for the matching failure rather than repeatedly publishing the same schedule.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/faq/#help-faq-108004",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Use these answers when deciding whether Auto-message fits your server or checking an existing schedule. Auto-message is in Testing and is not available to Hosted or Self-Hosted users. See the module overview for the current feature details.",
+            ],
+            contentHash: "ac86e0722158835d70092d8841a521b8f85b0c96ebb1d726efd7d85e7755c8e8",
+        },
+        {
+            id: "108005",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "The message arrived but its log did not",
+            answerMarkdown: "Check Logging enablement, its destination, the matching event switch and Helyx's destination permissions. Keep the successful schedule; there is no need to recreate it.",
+            answerText: "Check Logging enablement, its destination, the matching event switch and Helyx's destination permissions. Keep the successful schedule; there is no need to recreate it.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/logging/#help-faq-108005",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/logging.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Testing module: Auto-message is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow.",
+            ],
+            contentHash: "94f235daafdf618042ac7804a5f5f8856d66049bbe79b25d21548cd779807b6f",
+        },
+        {
+            id: "108006",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "I can see the channel but a schedule cannot use it",
+            answerMarkdown: "Check Helyx's own effective permissions, including inherited denies, and confirm the destination is a text or announcement channel. Your account's channel access does not prove the bot can post there.",
+            answerText: "Check Helyx's own effective permissions, including inherited denies, and confirm the destination is a text or announcement channel. Your account's channel access does not prove the bot can post there.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/permissions/#help-faq-108006",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/permissions.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Testing module: Auto-message is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow.",
+            ],
+            contentHash: "473940fcee4cc7f8a4e3a8741ba198ad78c110ebabb7de3a145112bdcd4cc0d3",
+        },
+        {
+            id: "108007",
+            moduleCode: "108",
+            area: "auto-message",
+            areaName: "Auto-message",
+            moduleId: "helyx.auto-message",
+            question: "Send private test fails",
+            answerMarkdown: "Allow direct messages from Helyx and retry once. A private test does not check the scheduled destination; verify the first actual occurrence separately.",
+            answerText: "Allow direct messages from Helyx and retry once. A private test does not check the scheduled destination; verify the first actual occurrence separately.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-message/permissions/#help-faq-108007",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-message/permissions.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Auto-message: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing; unavailable to Hosted and Self-Hosted users - Availability may change in the future; no public release date is confirmed.",
+                "Testing module: Auto-message is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow.",
+            ],
+            contentHash: "589faa02101a9f0b9c95b45ff26a68e6008d3885b464fbe2fb2e77e7c7963c54",
+        },
+        {
+            id: "110001",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "Why does Auto-responder need Message Content?",
+            answerMarkdown: "Auto-responder needs to read message text to check whether it matches a trigger. Discord requires the bot to have **Message Content** enabled for this.\n\nServer Health will show when the capability is missing. Helyx will not claim active rules are working when it cannot inspect eligible text.",
+            answerText: "Auto-responder needs to read message text to check whether it matches a trigger. Discord requires the bot to have Message Content enabled for this. Server Health will show when the capability is missing. Helyx will not claim active rules are working when it cannot inspect eligible text.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110001",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "f5709cf916ef2f7ea27251e3fc469562cbe6863b2420633b643f7d3d8a4d9840",
+        },
+        {
+            id: "110002",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "Will Helyx store the messages it checks?",
+            answerMarkdown: "No. Helyx will check the text and then discard it. The module will not save the messages, attachments or the author's activity history.",
+            answerText: "No. Helyx will check the text and then discard it. The module will not save the messages, attachments or the author's activity history.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110002",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "501290a383d581f97aebb2a8ddd06a9fb1b39135090e5942b6966086e4dd5cfc",
+        },
+        {
+            id: "110003",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "How is the winning rule chosen?",
+            answerMarkdown: "Rules will be checked in priority order, with a consistent order for ties. Only the first rule whose channel, role and text conditions match will respond.",
+            answerText: "Rules will be checked in priority order, with a consistent order for ties. Only the first rule whose channel, role and text conditions match will respond.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110003",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "133bc4d3bc3ed20b88affe3804162047f5753d10fb89397d566bd147ebffafa4",
+        },
+        {
+            id: "110004",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "Why will a failed high-priority rule not fall back to another rule?",
+            answerMarkdown: "Using a lower rule only when Discord or another service fails would make the visible response depend on an outage. Auto-responder will therefore keep the selected winner and report its failure rather than changing the intended answer.",
+            answerText: "Using a lower rule only when Discord or another service fails would make the visible response depend on an outage. Auto-responder will therefore keep the selected winner and report its failure rather than changing the intended answer.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110004",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "364be2a5c7fe1eafe38a647720a7389ee96a00607cb8585caeb9cd54741f2a87",
+        },
+        {
+            id: "110005",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "Which messages are ignored?",
+            answerMarkdown: "Messages from bots, webhooks, Discord system events and Helyx itself will be ignored. Only eligible human messages in the configured server and channel scopes can match.",
+            answerText: "Messages from bots, webhooks, Discord system events and Helyx itself will be ignored. Only eligible human messages in the configured server and channel scopes can match.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110005",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "853f23396c6f396f1032c34077e2ca9091ef0344d4a3a74fd8528faae746de7d",
+        },
+        {
+            id: "110006",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "How do cooldowns work?",
+            answerMarkdown: "After a rule matches, it will have to wait before responding again. You will choose whether that wait applies to the member, channel or whole server, for between five seconds and 24 hours.\n\nIf Helyx cannot check the cooldown, it will send no response, to avoid repeated replies.",
+            answerText: "After a rule matches, it will have to wait before responding again. You will choose whether that wait applies to the member, channel or whole server, for between five seconds and 24 hours. If Helyx cannot check the cooldown, it will send no response, to avoid repeated replies.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110006",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "76e7f1b7645e90c3d6f4517ba8397af5129a6a8007bc77bbb6d871119812a4aa",
+        },
+        {
+            id: "110007",
+            moduleCode: "110",
+            area: "auto-responder",
+            areaName: "Auto-responder",
+            moduleId: null,
+            question: "Can one source message receive two responses?",
+            answerMarkdown: "No. Only one rule will respond, and Helyx will recognise the message if Discord delivers the same event again.",
+            answerText: "No. Only one rule will respond, and Helyx will recognise the message if Discord delivers the same event again.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-responder/faq/#help-faq-110007",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-responder/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-responder: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-responder is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For matching modes, setup and planned limits, start with the Auto-responder overview.",
+            ],
+            contentHash: "87a62299ddf5a9e4ec792dbeba44374bd8ae91ce2aca030ce67fc8585d4fffaa",
+        },
+        {
+            id: "111001",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "Does enabling Auto-roles immediately assign something?",
+            answerMarkdown: "No. The module can be enabled with no rules and remains safely idle. Publishing the first valid active rule makes that trigger operational without another enablement cycle.\n\nA membership-age rule can check existing members as well. Other rules wait for someone to join, post or enter the selected channel.",
+            answerText: "No. The module can be enabled with no rules and remains safely idle. Publishing the first valid active rule makes that trigger operational without another enablement cycle. A membership-age rule can check existing members as well. Other rules wait for someone to join, post or enter the selected channel.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111001",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "4a14683b3f9fbaa05b8fbd3bc47c33bdd337b537ec8b3c19520b1724c322f35c",
+        },
+        {
+            id: "111002",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "Which triggers are planned?",
+            answerMarkdown: "The first release plans member join, a message in one selected channel, creation of a post in one selected forum, entry into one selected voice or Stage channel and reaching a configured number of days in the server.\n\nHelyx only needs to know the activity happened; it does not need to read the message or forum post.",
+            answerText: "The first release plans member join, a message in one selected channel, creation of a post in one selected forum, entry into one selected voice or Stage channel and reaching a configured number of days in the server. Helyx only needs to know the activity happened; it does not need to read the message or forum post.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111002",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "b5effdd0ba101e7cf60902d73bbbbe5a5cee8b89cc62072751e66e20196d5394",
+        },
+        {
+            id: "111003",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "Can a rule detect someone following an announcement channel?",
+            answerMarkdown: "No. Discord does not provide a dependable member-level event telling Helyx which individual followed an announcement channel. Helyx will not guess from webhooks, channel changes or audit-log activity.",
+            answerText: "No. Discord does not provide a dependable member-level event telling Helyx which individual followed an announcement channel. Helyx will not guess from webhooks, channel changes or audit-log activity.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111003",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "290dc7c97c747782ab9dd68bdc3203d69211b0bb6db5c865c650e741806f5227",
+        },
+        {
+            id: "111004",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "Will a voice or Stage role be removed when the member leaves?",
+            answerMarkdown: "No. Version one awards permanent roles only. Leaving the channel does not remove the role.\n\nTemporary roles that disappear when someone leaves a channel are not planned for the first release.",
+            answerText: "No. Version one awards permanent roles only. Leaving the channel does not remove the role. Temporary roles that disappear when someone leaves a channel are not planned for the first release.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111004",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "7dc56749b631976f27938163ffd647a889d289858d0827c1ff1490602f7eb621",
+        },
+        {
+            id: "111005",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "Will Auto-roles process existing members?",
+            answerMarkdown: "Membership-age rules will check existing members in batches and can resume after a restart. Eligibility uses the date the member joined the server.\n\nOther triggers do not reconstruct history. Existing messages, forum posts and past voice activity do not count.",
+            answerText: "Membership-age rules will check existing members in batches and can resume after a restart. Eligibility uses the date the member joined the server. Other triggers do not reconstruct history. Existing messages, forum posts and past voice activity do not count.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111005",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "8d33e5ad027c677d94ab1e49c8c8abe078530c96e58a62432132ea4407500972",
+        },
+        {
+            id: "111006",
+            moduleCode: "111",
+            area: "auto-roles",
+            areaName: "Auto-roles",
+            moduleId: null,
+            question: "What Discord permissions and capabilities will Helyx need?",
+            answerMarkdown: "Helyx needs **Manage Roles**, and its highest Discord role must be above every role it is expected to assign. Depending on configured rules, the application also needs Server Members, structural guild-message and Voice States events.\n\nThe module does not need Message Content, Presence or a Discord command.",
+            answerText: "Helyx needs Manage Roles, and its highest Discord role must be above every role it is expected to assign. Depending on configured rules, the application also needs Server Members, structural guild-message and Voice States events. The module does not need Message Content, Presence or a Discord command.",
+            sourceUrl: "https://docs.helyx.gg/modules/auto-roles/faq/#help-faq-111006",
+            sourcePath: "apps/docs/src/content/docs/modules/auto-roles/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Auto-roles: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Auto-roles is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: For its purpose, triggers, setup and limits, start with the Auto-roles overview.",
+            ],
+            contentHash: "4d45fa04c928e9eb8f30eb747a53ba86a086600e83e4d6b6015cccddfa0c20c3",
+        },
+        {
+            id: "112001",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "Does Helyx store my age or birth year?",
+            answerMarkdown: "No. It stores only the month and day supplied by the member, along with your Discord user ID and the time the entry was saved.",
+            answerText: "No. It stores only the month and day supplied by the member, along with your Discord user ID and the time the entry was saved.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112001",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "9b834632df76a1000f07b42fce89d81f83ac09fdb006f29c552d24082ac1de27",
+        },
+        {
+            id: "112002",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "Who can set my birthday?",
+            answerMarkdown: "Only you can set or replace your entry. Managers can delete but cannot create or edit it, and there is no bulk import.",
+            answerText: "Only you can set or replace your entry. Managers can delete but cannot create or edit it, and there is no bulk import.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112002",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "b14b17df806f5d77d945ae7c363acfac6f7c75c2634aedc24422df246df14489",
+        },
+        {
+            id: "112003",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "Who can see upcoming birthdays?",
+            answerMarkdown: "Anyone allowed by `birthdays.view` can receive a private list of up to 20 opted-in current members. It defaults to Everyone, so managers should review it.",
+            answerText: "Anyone allowed by birthdays.view can receive a private list of up to 20 opted-in current members. It defaults to Everyone, so managers should review it.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112003",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "83c4a1919bdce852fb7046c149310a23868d35b04f19cb3b8d152160b27a3a61",
+        },
+        {
+            id: "112004",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "Will the announcement ping me?",
+            answerMarkdown: "No. The message shows your Discord name without sending you a notification ping.",
+            answerText: "No. The message shows your Discord name without sending you a notification ping.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112004",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "095f36a0a3c7406bc47bbf578ddff850f459c94eb1e289432c2b7af2faeb9e50",
+        },
+        {
+            id: "112005",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "How does 29 February work?",
+            answerMarkdown: "The stored date remains 29 February. A server chooses 28 February or 1 March for non-leap years; leap years use 29 February.",
+            answerText: "The stored date remains 29 February. A server chooses 28 February or 1 March for non-leap years; leap years use 29 February.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112005",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "694e58e6fd9be75833c8b23e109f77bd0a1f7777608e0995274c5c4616238240",
+        },
+        {
+            id: "112006",
+            moduleCode: "112",
+            area: "birthdays",
+            areaName: "Birthdays",
+            moduleId: "helyx.birthdays",
+            question: "What happens across daylight-saving changes?",
+            answerMarkdown: "Helyx uses the saved timezone. If clocks go back and the chosen time happens twice, it uses the first. If clocks go forward past that time, it uses the next valid minute that day.",
+            answerText: "Helyx uses the saved timezone. If clocks go back and the chosen time happens twice, it uses the first. If clocks go forward past that time, it uses the next valid minute that day.",
+            sourceUrl: "https://docs.helyx.gg/modules/birthdays/faq/#help-faq-112006",
+            sourcePath: "apps/docs/src/content/docs/modules/birthdays/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Birthdays: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: - **Status:** Testing - **Availability:** Not available to Hosted or Self-Hosted users Controls and behaviour may change while verification continues. There is no confirmed Live date.",
+                "Testing module: Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour.",
+                "For setup, availability and limits, start with the Birthdays overview. :::caution[Testing module] Birthdays is in Testing and is not available to Hosted or Self-Hosted users. These answers describe its current behaviour. :::",
+            ],
+            contentHash: "ac939ded4064c765dae6223fc590b5d514ef9f24b590cf59d501d96f1afd89b0",
+        },
+        {
+            id: "113001",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "The command is missing or access is denied",
+            answerMarkdown: "Check that the module is enabled and its server command update has completed in **Commands**. Review the module default and exact command override in **Permissions**. A manager needs separate access for publication, review and reset; one management permission does not grant all of them. If the goal appears but rejects participation, check its eligibility and schedule too.",
+            answerText: "Check that the module is enabled and its server command update has completed in Commands. Review the module default and exact command override in Permissions. A manager needs separate access for publication, review and reset; one management permission does not grant all of them. If the goal appears but rejects participation, check its eligibility and schedule too.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/commands/#help-faq-113001",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/commands.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "7f5834ab5eca4ef89fc91cfb65ba85297700e01857ef62ff9368aeda99642e88",
+        },
+        {
+            id: "113002",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "The amount is rejected",
+            answerMarkdown: "Use a positive value matching the goal's whole-number or two-decimal setting. Helyx does not round extra decimal places.",
+            answerText: "Use a positive value matching the goal's whole-number or two-decimal setting. Helyx does not round extra decimal places.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/commands/#help-faq-113002",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/commands.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "61582f2c55344084b77edb96a8c3e5aa6696b74c7f906e0fbd01a3a0fadec40f",
+        },
+        {
+            id: "113003",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "A selected goal became unavailable",
+            answerMarkdown: "Run the command again. The goal may have paused, completed, reset or reached a configured limit after autocomplete.",
+            answerText: "Run the command again. The goal may have paused, completed, reset or reached a configured limit after autocomplete.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/commands/#help-faq-113003",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/commands.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "a4041a958e47b21d8a7375333ccfad47b45414952cc215f0625f7f52500bfc50",
+        },
+        {
+            id: "113004",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "How is this different from Guild Quests?",
+            answerMarkdown: "Community Goals uses manager-defined numeric targets and member-owned submissions. Guild Quests is a separate planned module; the two do not share progress or control each other.",
+            answerText: "Community Goals uses manager-defined numeric targets and member-owned submissions. Guild Quests is a separate planned module; the two do not share progress or control each other.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/faq/#help-faq-113004",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For setup, availability and limits, start with the Community Goals overview. :::caution[Testing module] Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "e67d9ba8be18f447fad254f7f6c2125b3519b72e8434aead4ffc57704a2655c8",
+        },
+        {
+            id: "113005",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "Can a manager submit for another member?",
+            answerMarkdown: "No. `/goal add` always belongs to its caller. A manager may create an unassigned community adjustment with a required private reason, but it never appears as a member submission or rank.",
+            answerText: "No. /goal add always belongs to its caller. A manager may create an unassigned community adjustment with a required private reason, but it never appears as a member submission or rank.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/faq/#help-faq-113005",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For setup, availability and limits, start with the Community Goals overview. :::caution[Testing module] Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "27e68511669ff6c07805ca7168e516de8b419a921f2ea851a2df4084db913c18",
+        },
+        {
+            id: "113006",
+            moduleCode: "113",
+            area: "community-goals",
+            areaName: "Community Goals",
+            moduleId: "helyx.community-goals",
+            question: "Does Helyx verify evidence?",
+            answerMarkdown: "No. The module accepts no evidence text, URL, attachment or screenshot. Manual approval lets staff apply the server's own rules without claiming Helyx verified the activity.",
+            answerText: "No. The module accepts no evidence text, URL, attachment or screenshot. Manual approval lets staff apply the server's own rules without claiming Helyx verified the activity.",
+            sourceUrl: "https://docs.helyx.gg/modules/community-goals/faq/#help-faq-113006",
+            sourcePath: "apps/docs/src/content/docs/modules/community-goals/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Community Goals: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Community Goals is in Testing and cannot currently be used by Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For setup, availability and limits, start with the Community Goals overview. :::caution[Testing module] Community Goals is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "dad58f52b5a89646bb005cc1ef3f894c74ff9859d7c611da656ec709dedb867a",
+        },
+        {
+            id: "114001",
+            moduleCode: "114",
+            area: "confessions",
+            areaName: "Confessions",
+            moduleId: null,
+            question: "Will confessions be truly anonymous?",
+            answerMarkdown: "No. Public readers and ordinary reviewers will not see the submitter, but Helyx temporarily retains the Discord user ID for abuse controls, member withdrawal, privacy handling and tightly controlled safety escalation.\n\nThe module will never promise end-to-end encryption, legal privilege or complete anonymity.",
+            answerText: "No. Public readers and ordinary reviewers will not see the submitter, but Helyx temporarily retains the Discord user ID for abuse controls, member withdrawal, privacy handling and tightly controlled safety escalation. The module will never promise end-to-end encryption, legal privilege or complete anonymity.",
+            sourceUrl: "https://docs.helyx.gg/modules/confessions/faq/#help-faq-114001",
+            sourcePath: "apps/docs/src/content/docs/modules/confessions/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Confessions: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Confessions overview for the planned workflow and limits.",
+            ],
+            contentHash: "5b82c13d6a126d4a0984bd08283539c1dc27a247ee255c39b43e7e58cbf37de2",
+        },
+        {
+            id: "114002",
+            moduleCode: "114",
+            area: "confessions",
+            areaName: "Confessions",
+            moduleId: null,
+            question: "Who can reveal a submitter?",
+            answerMarkdown: "Only the current Discord server owner can use **Reveal submitter for safety review**. An administrator, ordinary reviewer, support user or delegated dashboard manager cannot use it.\n\nThe owner must also hold the specific Helyx permission, have authenticated with Discord within the previous five minutes, confirm that anonymity will be broken and provide a 20–500 character reason. Reveal is impossible after the identity has expired or been detached.",
+            answerText: "Only the current Discord server owner can use Reveal submitter for safety review. An administrator, ordinary reviewer, support user or delegated dashboard manager cannot use it. The owner must also hold the specific Helyx permission, have authenticated with Discord within the previous five minutes, confirm that anonymity will be broken and provide a 20–500 character reason. Reveal is impossible after the identity has expired or been detached.",
+            sourceUrl: "https://docs.helyx.gg/modules/confessions/faq/#help-faq-114002",
+            sourcePath: "apps/docs/src/content/docs/modules/confessions/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Confessions: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Confessions overview for the planned workflow and limits.",
+            ],
+            contentHash: "eddc0efc3261547aaa15e2902664dff4812bddfc42800d7d2a7c18abfe691220",
+        },
+        {
+            id: "114003",
+            moduleCode: "114",
+            area: "confessions",
+            areaName: "Confessions",
+            moduleId: null,
+            question: "Is identity reveal recorded?",
+            answerMarkdown: "Yes. The action creates a restricted Audit record with the owner, confession, reason, timestamp and outcome. The identity is returned once in the protected response and is not copied into a reveal table or cache.\n\nThe reveal reason and identity are excluded from customer Logging, ordinary support views and operational logs.",
+            answerText: "Yes. The action creates a restricted Audit record with the owner, confession, reason, timestamp and outcome. The identity is returned once in the protected response and is not copied into a reveal table or cache. The reveal reason and identity are excluded from customer Logging, ordinary support views and operational logs.",
+            sourceUrl: "https://docs.helyx.gg/modules/confessions/faq/#help-faq-114003",
+            sourcePath: "apps/docs/src/content/docs/modules/confessions/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Confessions: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Confessions overview for the planned workflow and limits.",
+            ],
+            contentHash: "591701d0293409e98a4cd1c64c2741b182bca3a4adbbb44717c616d1336fa80d",
+        },
+        {
+            id: "114004",
+            moduleCode: "114",
+            area: "confessions",
+            areaName: "Confessions",
+            moduleId: null,
+            question: "What can ordinary reviewers see?",
+            answerMarkdown: "The queue shows the confession reference, age and status. Its detail shows the plain-text body, submission time and review state, but not the submitter ID, display name, avatar, account age or roles.\n\nReviewers can act on one record at a time and cannot search by identity or confession body.",
+            answerText: "The queue shows the confession reference, age and status. Its detail shows the plain-text body, submission time and review state, but not the submitter ID, display name, avatar, account age or roles. Reviewers can act on one record at a time and cannot search by identity or confession body.",
+            sourceUrl: "https://docs.helyx.gg/modules/confessions/faq/#help-faq-114004",
+            sourcePath: "apps/docs/src/content/docs/modules/confessions/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Confessions: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Confessions overview for the planned workflow and limits.",
+            ],
+            contentHash: "5f3099f8c0345dda72df30e3fc7b32e81a827b41a825b6c30f7a4baf553a4d27",
+        },
+        {
+            id: "114005",
+            moduleCode: "114",
+            area: "confessions",
+            areaName: "Confessions",
+            moduleId: null,
+            question: "Can a reviewer edit a confession before publishing it?",
+            answerMarkdown: "No. Staff may approve the exact submitted text or reject it, but cannot rewrite the member's words.\n\nIf the content cannot be published safely within Discord's current limits, approval fails instead of silently changing or splitting it.",
+            answerText: "No. Staff may approve the exact submitted text or reject it, but cannot rewrite the member's words. If the content cannot be published safely within Discord's current limits, approval fails instead of silently changing or splitting it.",
+            sourceUrl: "https://docs.helyx.gg/modules/confessions/faq/#help-faq-114005",
+            sourcePath: "apps/docs/src/content/docs/modules/confessions/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Confessions: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed.",
+                ":::caution[Planned module] Confessions is planned and is not currently available. This page describes the current design, which may change before release. No release date has been confirmed. ::: See the Confessions overview for the planned workflow and limits.",
+            ],
+            contentHash: "3d791ed99989a4a9f7144be91f55d6a85bc38e0d34c69917d4137df30ce7e58b",
+        },
+        {
+            id: "115001",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "A correct entry did not award progress",
+            answerMarkdown: "Check that Counting and Achievements are enabled and the achievement is Active. The entry must be accepted in the configured Counting channel and match the chosen trigger. Progress may take a moment to appear; refresh the member view.",
+            answerText: "Check that Counting and Achievements are enabled and the achievement is Active. The entry must be accepted in the configured Counting channel and match the chosen trigger. Progress may take a moment to appear; refresh the member view.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/achievements/#help-faq-115001",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/achievements.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "4715851c9e857dc30133c3246d26a5dd9dd9662a99015cf96877039f02cbd512",
+        },
+        {
+            id: "115002",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "The Nexus reward field is unavailable",
+            answerMarkdown: "The selected event may be ineligible, or Nexus Rewards/Achievement rewards may not be enabled. A trigger that does not allow direct Nexus rewards cannot be used to pay one.",
+            answerText: "The selected event may be ineligible, or Nexus Rewards/Achievement rewards may not be enabled. A trigger that does not allow direct Nexus rewards cannot be used to pay one.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/achievements/#help-faq-115002",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/achievements.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "f77ca9957e0a495c4f7d47e7ee3e332f10495aba46e1bfb123a0f1ec5409dda4",
+        },
+        {
+            id: "115003",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "The command is not visible",
+            answerMarkdown: "Check that Counting is enabled and its command has finished appearing in Discord. If only some members cannot use it, review the `counting` command permissions.",
+            answerText: "Check that Counting is enabled and its command has finished appearing in Discord. If only some members cannot use it, review the counting command permissions.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/commands/#help-faq-115003",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "5bca8fa95c96b4fb0abd8d43eae3929177f8cb950883237d8ac369da273ea3b4",
+        },
+        {
+            id: "115004",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "The command says Counting is not configured",
+            answerMarkdown: "Save a valid channel and sequence in [Settings](https://docs.helyx.gg/modules/counting/settings/), then reload the module page.",
+            answerText: "Save a valid channel and sequence in Settings, then reload the module page.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/commands/#help-faq-115004",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "2bcf73e7eeff94e99fec1bdd1f3600111345fe9efd018b3511540049beda4bbc",
+        },
+        {
+            id: "115005",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "The displayed state is Locked",
+            answerMarkdown: "The game reached a target configured to lock. Open **Game** and use **Reset game**. If counting should continue after future targets, change the saved goal behaviour first; the reset applies those settings and starts a new round.",
+            answerText: "The game reached a target configured to lock. Open Game and use Reset game. If counting should continue after future targets, change the saved goal behaviour first; the reset applies those settings and starts a new round.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/commands/#help-faq-115005",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "dde20f012f26d5ab46a1486a2a22c24b3823c6b4be0b0265b63f5a7aa3b8468e",
+        },
+        {
+            id: "115006",
+            moduleCode: "115",
+            area: "counting",
+            areaName: "Counting",
+            moduleId: "helyx.counting",
+            question: "Can the same member count twice in a row?",
+            answerMarkdown: "Yes by default. Turn-taking is optional: enable the member cooldown to prevent the last accepted member from posting another accepted number for 5 to 86,400 seconds. This rule is independent of Discord slowmode.",
+            answerText: "Yes by default. Turn-taking is optional: enable the member cooldown to prevent the last accepted member from posting another accepted number for 5 to 86,400 seconds. This rule is independent of Discord slowmode.",
+            sourceUrl: "https://docs.helyx.gg/modules/counting/faq/#help-faq-115006",
+            sourcePath: "apps/docs/src/content/docs/modules/counting/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Counting: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "For setup and current rules, start with the Counting overview.",
+            ],
+            contentHash: "a2c0b593f296e33f8a3b0fc64257076a01f1c3a0663b5908cc9d39429d6eb258",
+        },
+        {
+            id: "116001",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "Does Creator Connections require Helyx Premium?",
+            answerMarkdown: "Yes. Creator Connections is included in Helyx Premium and runs only on the\nhosted Helyx bot. A subscriber can assign a Premium slot in Billing or use\n`/activate` in a hosted server they manage. Losing the final Premium source\ndisables the module but keeps its saved settings and records.",
+            answerText: "Yes. Creator Connections is included in Helyx Premium and runs only on the hosted Helyx bot. A subscriber can assign a Premium slot in Billing or use /activate in a hosted server they manage. Losing the final Premium source disables the module but keeps its saved settings and records.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116001",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "1f89eaafa930cb2bfea65ed677e12c552fb9f09d01c113faf379d7173ac146c7",
+        },
+        {
+            id: "116002",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "Is Creator Connections an announcement module?",
+            answerMarkdown: "No. It connects a member's provider account, checks that member against a saved creator target and can grant a role. It does not announce uploads, streams, social posts or offline events.",
+            answerText: "No. It connects a member's provider account, checks that member against a saved creator target and can grant a role. It does not announce uploads, streams, social posts or offline events.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116002",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "d9efac293f79823557e436fab3cdc00d92f80869f054f3affa3b374e36c417e4",
+        },
+        {
+            id: "116003",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "How many panels can a server publish?",
+            answerMarkdown: "Up to five. Each panel represents one creator and can contain one YouTube target, one Twitch target or both. Helyx does not claim that targets on the same panel have a verified common owner.",
+            answerText: "Up to five. Each panel represents one creator and can contain one YouTube target, one Twitch target or both. Helyx does not claim that targets on the same panel have a verified common owner.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116003",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "4cc3470723f3fce4a698017c91dd7c66cb9a84c47f509fc1dd8615baf015796f",
+        },
+        {
+            id: "116004",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "Are the welcome invite and Helyx overview the same invite?",
+            answerMarkdown: "No. **Invites** manages one normal Discord invite that gives every joining member a community role. **Integrated invites** creates a separate Discord invite without an automatic role and a Helyx page with its exact code, such as `helyx.gg/CVyBgWAJvW` and `discord.com/invite/CVyBgWAJvW`. Its rules do not need an existing Discord panel.",
+            answerText: "No. Invites manages one normal Discord invite that gives every joining member a community role. Integrated invites creates a separate Discord invite without an automatic role and a Helyx page with its exact code, such as helyx.gg/CVyBgWAJvW and discord.com/invite/CVyBgWAJvW. Its rules do not need an existing Discord panel.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116004",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "199d3fc3d79e8fcebf5f6971fa3f81fb7f6af75bbb60c949d6c07461aaa4b77f",
+        },
+        {
+            id: "116005",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "Can the overview award a follower role and a subscriber role?",
+            answerMarkdown: "Yes. One overview supports two independent Twitch rules, each with one safe role. A visitor can qualify for either or both. Up to four customisable text blocks describe the community; bracketed `[tags]` appear below each block's normal text. Drafts can be previewed in desktop/mobile views before publication.",
+            answerText: "Yes. One overview supports two independent Twitch rules, each with one safe role. A visitor can qualify for either or both. Up to four customisable text blocks describe the community; bracketed [tags] appear below each block's normal text. Drafts can be previewed in desktop/mobile views before publication.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116005",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "387a190443c32ea09b90c08870202dde233d5f7a21931a2f9470c80635a7a4df",
+        },
+        {
+            id: "116006",
+            moduleCode: "116",
+            area: "creator-connections",
+            areaName: "Creator Connections",
+            moduleId: "helyx.creator-connections",
+            question: "Does connecting Discord or Twitch automatically join the server?",
+            answerMarkdown: "No. Both main overview join choices require Discord's separate **Join servers for you** permission and the visitor's explicit join confirmation. Connecting or checking accounts does not join. The normal Discord-invite text link skips Helyx OAuth and gives no creator role.\n\nScheduled rechecks and the progress-recovery action never automatically rejoin someone who left. A successful join can still wait for screening, Access Control or Verification before eligible roles arrive.",
+            answerText: "No. Both main overview join choices require Discord's separate Join servers for you permission and the visitor's explicit join confirmation. Connecting or checking accounts does not join. The normal Discord-invite text link skips Helyx OAuth and gives no creator role. Scheduled rechecks and the progress-recovery action never automatically rejoin someone who left. A successful join can still wait for screening, Access Control or Verification before eligible roles arrive.",
+            sourceUrl: "https://docs.helyx.gg/modules/creator-connections/faq/#help-faq-116006",
+            sourcePath: "apps/docs/src/content/docs/modules/creator-connections/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Creator Connections: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted Premium module: Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider.",
+                "See the Creator Connections overview for setup and member instructions. :::note[Hosted Premium module] Creator Connections requires the hosted Helyx bot, an assigned Premium slot and an enabled module. It is unavailable in Self-Hosted and Cloud Connect. Google/YouTube remains disabled pending approval; Twitch is the enabled provider. :::",
+            ],
+            contentHash: "de20280c2bbd518f6761c16eec92ad50583bc2b6841708d5af9ed5a8c5144633",
+        },
+        {
+            id: "117001",
+            moduleCode: "117",
+            area: "custom-commands",
+            areaName: "Custom Commands",
+            moduleId: null,
+            question: "Can I enable Custom Commands?",
+            answerMarkdown: "No. There is no supported public setup workflow yet.",
+            answerText: "No. There is no supported public setup workflow yet.",
+            sourceUrl: "https://docs.helyx.gg/modules/custom-commands/faq/#help-faq-117001",
+            sourcePath: "apps/docs/src/content/docs/modules/custom-commands/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Custom Commands: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Custom Commands is not currently available. Its design is being revised and no release date is confirmed.",
+                "For current availability, start with the Custom Commands overview. :::caution[Planned module] Custom Commands is not currently available. Its design is being revised and no release date is confirmed. :::",
+            ],
+            contentHash: "3b3c2394fa8890183bf3822a19085e6feb28629c3e3c4c3df110e12f180ea8ff",
+        },
+        {
+            id: "117002",
+            moduleCode: "117",
+            area: "custom-commands",
+            areaName: "Custom Commands",
+            moduleId: null,
+            question: "Are the earlier command names and limits final?",
+            answerMarkdown: "No. The earlier response-only design has been superseded. Treat old command names, fixed limits, cooldowns and excluded actions as withdrawn design details rather than a release contract.",
+            answerText: "No. The earlier response-only design has been superseded. Treat old command names, fixed limits, cooldowns and excluded actions as withdrawn design details rather than a release contract.",
+            sourceUrl: "https://docs.helyx.gg/modules/custom-commands/faq/#help-faq-117002",
+            sourcePath: "apps/docs/src/content/docs/modules/custom-commands/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Custom Commands: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Custom Commands is not currently available. Its design is being revised and no release date is confirmed.",
+                "For current availability, start with the Custom Commands overview. :::caution[Planned module] Custom Commands is not currently available. Its design is being revised and no release date is confirmed. :::",
+            ],
+            contentHash: "077e765bab5bf1d40fd6ae0c1bbba2af473fe400b7ba0057858ae98fd2888bed",
+        },
+        {
+            id: "117003",
+            moduleCode: "117",
+            area: "custom-commands",
+            areaName: "Custom Commands",
+            moduleId: null,
+            question: "When will setup instructions be available?",
+            answerMarkdown: "The documentation will be updated when the replacement implementation is ready for public review. No release date is confirmed.",
+            answerText: "The documentation will be updated when the replacement implementation is ready for public review. No release date is confirmed.",
+            sourceUrl: "https://docs.helyx.gg/modules/custom-commands/faq/#help-faq-117003",
+            sourcePath: "apps/docs/src/content/docs/modules/custom-commands/faq.md",
+            releaseStatus: "planned",
+            deploymentSupport: "not_declared",
+            context: [
+                "Custom Commands: planned. Deployment compatibility: not_declared. Release status does not by itself mean customer availability.",
+                "Planned module: Custom Commands is not currently available. Its design is being revised and no release date is confirmed.",
+                "For current availability, start with the Custom Commands overview. :::caution[Planned module] Custom Commands is not currently available. Its design is being revised and no release date is confirmed. :::",
+            ],
+            contentHash: "abb9c1b68a294bfdbb02caeec767cce71e3f96c88d8d66f159a38aa5a5557738",
+        },
+        {
+            id: "118001",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "No `/event` command appears",
+            answerMarkdown: "Confirm the module is enabled for this server, the command update has completed and the member is permitted by `events.view`.",
+            answerText: "Confirm the module is enabled for this server, the command update has completed and the member is permitted by events.view.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/commands/#help-faq-118001",
+            sourcePath: "apps/docs/src/content/docs/modules/events/commands.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "31584d9b29e9adb5b0fcfb8047a4e6f676c73fa15628dd9c0075438e8354634e",
+        },
+        {
+            id: "118002",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "A selected event is no longer available",
+            answerMarkdown: "Run `/event list` again. The earlier autocomplete value may refer to an event that has since become unavailable.",
+            answerText: "Run /event list again. The earlier autocomplete value may refer to an event that has since become unavailable.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/commands/#help-faq-118002",
+            sourcePath: "apps/docs/src/content/docs/modules/events/commands.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "9662577a7d674cd2748a1dedb4b1cf0ea248a0fd9bf0618b2a5c0c52770fb0bc",
+        },
+        {
+            id: "118003",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "The tracked post was deleted",
+            answerMarkdown: "Open the event detail. Confirm the destination is still eligible, then use **Repair post**. Retrying the same repair does not create extra replacement posts.",
+            answerText: "Open the event detail. Confirm the destination is still eligible, then use Repair post. Retrying the same repair does not create extra replacement posts.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/events/#help-faq-118003",
+            sourcePath: "apps/docs/src/content/docs/modules/events/events.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+            ],
+            contentHash: "f73e8e5e94e111f73f2937a811a69da44b28be0bf3755e1b0a06e86946597970",
+        },
+        {
+            id: "118005",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "Why does Events not create Discord Scheduled Events?",
+            answerMarkdown: "The first release keeps Helyx as the single editable source of event time, cancellation, responses and repair. Mirroring a second Discord-managed event could create conflicting state.",
+            answerText: "The first release keeps Helyx as the single editable source of event time, cancellation, responses and repair. Mirroring a second Discord-managed event could create conflicting state.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/faq/#help-faq-118005",
+            sourcePath: "apps/docs/src/content/docs/modules/events/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For the normal workflow and current limits, start with the Events overview. :::caution[Testing module] Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "ccfbb00f9b647eb050d02323866e21970e8d6ef07801453e3591ba6410c864d4",
+        },
+        {
+            id: "118006",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "Does Going mean a member attended?",
+            answerMarkdown: "No. A Going member must explicitly check in during the 30-minute-before-start through end window. Helyx never infers attendance from voice or presence.",
+            answerText: "No. A Going member must explicitly check in during the 30-minute-before-start through end window. Helyx never infers attendance from voice or presence.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/faq/#help-faq-118006",
+            sourcePath: "apps/docs/src/content/docs/modules/events/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For the normal workflow and current limits, start with the Events overview. :::caution[Testing module] Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "457da2439bfd18e2785c72a541414a9227b069a7260799a2af871fd30f553da1",
+        },
+        {
+            id: "118007",
+            moduleCode: "118",
+            area: "events",
+            areaName: "Events",
+            moduleId: "helyx.events",
+            question: "How is the final place assigned?",
+            answerMarkdown: "Capacity applies only to **Going**. If two members try to take the last place at the same time, only one can get it. **Maybe** and **Can't go** remain available.",
+            answerText: "Capacity applies only to Going. If two members try to take the last place at the same time, only one can get it. Maybe and Can't go remain available.",
+            sourceUrl: "https://docs.helyx.gg/modules/events/faq/#help-faq-118007",
+            sourcePath: "apps/docs/src/content/docs/modules/events/faq.md",
+            releaseStatus: "testing",
+            deploymentSupport: "both",
+            context: [
+                "Events: testing. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Testing module: Events is in Testing and is not available to Hosted or Self-Hosted users. This may change in the future; no release date is confirmed.",
+                "Testing module: Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed.",
+                "For the normal workflow and current limits, start with the Events overview. :::caution[Testing module] Events is unavailable to Hosted and Self-Hosted users. This guide describes the implemented Testing workflow; no public release date is confirmed. :::",
+            ],
+            contentHash: "b55f6b757e192cf75c92c789f55534fd31d3c9c06bfca59b3ea9ac1bf231b2d0",
+        },
+        {
+            id: "119001",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "The command is not visible",
+            answerMarkdown: "Check that FAQ is enabled and its commands have finished updating in Discord. In **Permissions**, check the affected command's allowed and denied roles or users.",
+            answerText: "Check that FAQ is enabled and its commands have finished updating in Discord. In Permissions, check the affected command's allowed and denied roles or users.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/commands/#help-faq-119001",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "a6d548ce5ba9b12ee56b4102094ff4235bedd41b5122f3d04430c30ba80004df",
+        },
+        {
+            id: "119002",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "An autocomplete choice expired",
+            answerMarkdown: "Start typing the question or trigger again and select the new result. Selections expire after two minutes.",
+            answerText: "Start typing the question or trigger again and select the new result. Selections expire after two minutes.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/commands/#help-faq-119002",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "4e36f62c19488dcffd00ec8b9041445aee5168c502b0b6e1271dab5443b5d204",
+        },
+        {
+            id: "119003",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "A form edit reports newer changes",
+            answerMarkdown: "Reload or search for the FAQ again. Helyx will not overwrite a newer dashboard or command edit with an older revision.",
+            answerText: "Reload or search for the FAQ again. Helyx will not overwrite a newer dashboard or command edit with an older revision.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/commands/#help-faq-119003",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "45d203869b9128481b57e9725b177d45eb1794c085731beda7d8c2fa0db9854e",
+        },
+        {
+            id: "119004",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "Why does an enabled FAQ not respond?",
+            answerMarkdown: "Confirm the entry itself is enabled, the trigger matches exactly, and Helyx can view and send messages in that channel. The running bot must also have Message Content enabled.\n\nTriggers are compared after trimming and normalising case. A valid message contains the exact trigger by itself or followed by one user mention. Role mentions, `@everyone` and extra text do not work as a target.",
+            answerText: "Confirm the entry itself is enabled, the trigger matches exactly, and Helyx can view and send messages in that channel. The running bot must also have Message Content enabled. Triggers are compared after trimming and normalising case. A valid message contains the exact trigger by itself or followed by one user mention. Role mentions, @everyone and extra text do not work as a target.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/faq/#help-faq-119004",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "For setup, presentation choices and limits, start with the FAQ overview.",
+            ],
+            contentHash: "d6376660caed6a21f163802ce90d96a63cd0878de91f261010c63135823a92a8",
+        },
+        {
+            id: "119005",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "Why is the trigger rejected?",
+            answerMarkdown: "Triggers must be unique and use a 1-50 character suffix containing lowercase letters, numbers, hyphens or underscores. The `faq-` prefix is added when omitted and does not count towards the suffix limit.",
+            answerText: "Triggers must be unique and use a 1-50 character suffix containing lowercase letters, numbers, hyphens or underscores. The faq- prefix is added when omitted and does not count towards the suffix limit.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/faq/#help-faq-119005",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "For setup, presentation choices and limits, start with the FAQ overview.",
+            ],
+            contentHash: "7891f709a9926fdbb96b6f05a62b2694893be3945eba3724471553f6ea7240ce",
+        },
+        {
+            id: "119006",
+            moduleCode: "119",
+            area: "faq",
+            areaName: "FAQ",
+            moduleId: "helyx.faq",
+            question: "Why was the trigger message left behind?",
+            answerMarkdown: "Helyx posts the answer before attempting cleanup. If **Manage Messages** is missing, the answer can succeed while deletion fails. Restore the permission or turn off **Delete trigger message**.",
+            answerText: "Helyx posts the answer before attempting cleanup. If Manage Messages is missing, the answer can succeed while deletion fails. Restore the permission or turn off Delete trigger message.",
+            sourceUrl: "https://docs.helyx.gg/modules/faq/faq/#help-faq-119006",
+            sourcePath: "apps/docs/src/content/docs/modules/faq/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "FAQ: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "For setup, presentation choices and limits, start with the FAQ overview.",
+            ],
+            contentHash: "948fafe4d9739fdb1f38607f7d3d109cbc751b50f8eabe4ada154ec8f2cf375f",
+        },
+        {
+            id: "120001",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "The command is not visible",
+            answerMarkdown: "Check that Forms is enabled and its commands have appeared in Discord. If a command is unavailable to one member, check their Forms command permissions.",
+            answerText: "Check that Forms is enabled and its commands have appeared in Discord. If a command is unavailable to one member, check their Forms command permissions.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/#help-faq-120001",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "8731cc7cf06133b2c0dc5237a8dddd5717502c669876e3e27cb9db225ed9b4aa",
+        },
+        {
+            id: "120002",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "Autocomplete is empty",
+            answerMarkdown: "For publish, create or restore an active reusable form. For repost, check that the run is still open. Only forms from the current server are listed.",
+            answerText: "For publish, create or restore an active reusable form. For repost, check that the run is still open. Only forms from the current server are listed.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/#help-faq-120002",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "78e9056758d21f041a3c61fd96f0604d9c3657b0fbb1067f8c984553da0280ae",
+        },
+        {
+            id: "120003",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "The command works but the post does not",
+            answerMarkdown: "Check Helyx's View Channel, Send Messages and Read Message History permissions in the destination channel, including category overrides. The private reply should explain whether publication succeeded.",
+            answerText: "Check Helyx's View Channel, Send Messages and Read Message History permissions in the destination channel, including category overrides. The private reply should explain whether publication succeeded.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/#help-faq-120003",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "b3cda9eaeaecc292706390ecad0991176ed8cb5e33dc2a700a196666924e5664",
+        },
+        {
+            id: "120004",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "The form is missing from autocomplete",
+            answerMarkdown: "Only active reusable forms are offered. Restore an archived form, or use the dashboard to publish a one-time form.",
+            answerText: "Only active reusable forms are offered. Restore an archived form, or use the dashboard to publish a one-time form.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/publish/#help-faq-120004",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands/publish.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "bc22f4c42da34559f008bf3a1d67237b272412837bb93fbeedcd3165201b1956",
+        },
+        {
+            id: "120005",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "The public post was not created",
+            answerMarkdown: "Check the current channel and its category overrides for View Channel, Send Messages and Read Message History. If publication fails after a message was sent, Helyx tries to remove that message and marks the run as failed.",
+            answerText: "Check the current channel and its category overrides for View Channel, Send Messages and Read Message History. If publication fails after a message was sent, Helyx tries to remove that message and marks the run as failed.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/publish/#help-faq-120005",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands/publish.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "3efca7417f03995589317cdfae96870d58537db7f03b508f64a2a0f0e3f19113",
+        },
+        {
+            id: "120006",
+            moduleCode: "120",
+            area: "forms",
+            areaName: "Forms",
+            moduleId: "helyx.forms",
+            question: "The confirmation says the form changed",
+            answerMarkdown: "The definition was edited, archived or removed after autocomplete. Start `/forms publish` again and choose the current record.",
+            answerText: "The definition was edited, archived or removed after autocomplete. Start /forms publish again and choose the current record.",
+            sourceUrl: "https://docs.helyx.gg/modules/forms/commands/publish/#help-faq-120006",
+            sourcePath: "apps/docs/src/content/docs/modules/forms/commands/publish.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Forms: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "26e04e7cc39665515836cce144cecd17cfd87d1bd868ecf90d8b4b6366806f44",
+        },
+        {
+            id: "128001",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "The command is not visible",
+            answerMarkdown: "Confirm Levels is enabled, command deployment has completed and the member satisfies the matching command policy. Also check Discord channel-level command restrictions.",
+            answerText: "Confirm Levels is enabled, command deployment has completed and the member satisfies the matching command policy. Also check Discord channel-level command restrictions.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/#help-faq-128001",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "d26ed89744e08650f0594776fbc2c25506fc170054c0b37cbc5c3550abd9b246",
+        },
+        {
+            id: "128002",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "The response says the member cannot be used",
+            answerMarkdown: "Choose a current human member of this Discord server. Bots and members who have left cannot be command targets.",
+            answerText: "Choose a current human member of this Discord server. Bots and members who have left cannot be command targets.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/#help-faq-128002",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "db3b30407500aeb19adca0c64f8d2fb2126141caa78078e2ad077d27dfabab52",
+        },
+        {
+            id: "128003",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "Rank works but leaderboard reports missing settings",
+            answerMarkdown: "Save valid Levels settings. Rank can read one retained record without configuration, but leaderboard needs the saved result-count setting.",
+            answerText: "Save valid Levels settings. Rank can read one retained record without configuration, but leaderboard needs the saved result-count setting.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/#help-faq-128003",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "73bb751a3343bd306e2edcb333a36ee3db27d4e8882a4babde047d5ebe1d076e",
+        },
+        {
+            id: "128004",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "The response does not match an earlier screenshot",
+            answerMarkdown: "Ranks use current saved XP and current Discord membership. Later awards, dashboard adjustments, member departures and display-name changes can alter the result.",
+            answerText: "Ranks use current saved XP and current Discord membership. Later awards, dashboard adjustments, member departures and display-name changes can alter the result.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/#help-faq-128004",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "f1c07b64b5703ece93750961eba26c0c86f91771df6c643cd0e236462df7eb82",
+        },
+        {
+            id: "128005",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "No current members have earned XP yet",
+            answerMarkdown: "Confirm Settings exist and ordinary messages pass the channel, role, cooldown and message-type checks. Retained departed records do not make a current member appear.",
+            answerText: "Confirm Settings exist and ordinary messages pass the channel, role, cooldown and message-type checks. Retained departed records do not make a current member appear.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/leaderboard/#help-faq-128005",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands/leaderboard.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "2b0ae230dd954295b4df1d4f1cbf173ddca096f140906544fad047bb208d780b",
+        },
+        {
+            id: "128008",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "No XP has been earned in this server yet",
+            answerMarkdown: "The member has not earned XP yet. Check that Settings have been saved and that their messages meet the channel, role, message-type and cooldown rules.",
+            answerText: "The member has not earned XP yet. Check that Settings have been saved and that their messages meet the channel, role, message-type and cooldown rules.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/rank/#help-faq-128008",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands/rank.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "e54c421a6253f8109dacc9e567bee4eb4f7d64a8d7147a7db081e74c1208e3a2",
+        },
+        {
+            id: "128009",
+            moduleCode: "128",
+            area: "levels",
+            areaName: "Levels",
+            moduleId: "helyx.levels",
+            question: "A recent message did not change the rank",
+            answerMarkdown: "The message may have been inside the cooldown or excluded by channel, role or custom message-type settings. Review [Settings](https://docs.helyx.gg/modules/levels/settings/) and module health.",
+            answerText: "The message may have been inside the cooldown or excluded by channel, role or custom message-type settings. Review Settings and module health.",
+            sourceUrl: "https://docs.helyx.gg/modules/levels/commands/rank/#help-faq-128009",
+            sourcePath: "apps/docs/src/content/docs/modules/levels/commands/rank.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Levels: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "fea61b9e227a7af5027885f2cb7fde9b9a150de893660e01fb22ad0bbbdecdac",
+        },
+        {
+            id: "129001",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "Is this Helyx’s operational log?",
+            answerMarkdown: "No. This module sends activity summaries to a Discord channel chosen by your server manager. Turning it off does not stop Helyx's own security, audit or error records.",
+            answerText: "No. This module sends activity summaries to a Discord channel chosen by your server manager. Turning it off does not stop Helyx's own security, audit or error records.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129001",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "917e1ede7ba6fe2aed1234829c39f868d9ce168ce66721455809f5bf030404b8",
+        },
+        {
+            id: "129002",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "Why did an action complete without a log message?",
+            answerMarkdown: "The source action and log delivery are separate. Confirm Logging is enabled, its destination is valid and the specific source event is enabled. A delivery failure does not reverse a completed action, and the missed event is not queued for replay.",
+            answerText: "The source action and log delivery are separate. Confirm Logging is enabled, its destination is valid and the specific source event is enabled. A delivery failure does not reverse a completed action, and the missed event is not queued for replay.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129002",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "6195a169dc9944239965a20faea0bcc9cab4a5751493eb8d750eb0b080ded4f9",
+        },
+        {
+            id: "129003",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "Why is an event missing from the switches?",
+            answerMarkdown: "The list depends on the events supported by your installed module version. Check that the module is installed and enabled, then reload its **Logging** tab.",
+            answerText: "The list depends on the events supported by your installed module version. Check that the module is installed and enabled, then reload its Logging tab.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129003",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "42911459bd9f2cd93d23e56aeec8e8bc1993670e58512d4b3f3c13234287fc83",
+        },
+        {
+            id: "129004",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "Does Logging store message, feedback or suggestion text?",
+            answerMarkdown: "Logging stores the destination and event switches, without keeping a second copy of the messages it sends. Each module decides what its events include; delivered messages stay in Discord.\n\nAlways check the source module's Logging guide for its exact included and excluded fields before enabling an event.",
+            answerText: "Logging stores the destination and event switches, without keeping a second copy of the messages it sends. Each module decides what its events include; delivered messages stay in Discord. Always check the source module's Logging guide for its exact included and excluded fields before enabling an event.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129004",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "35d6ab9a6e5b08b4e47469f1b61989c368f77515767db65f9799bd4a02f0d4d6",
+        },
+        {
+            id: "129005",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "Can a delivered log mention members or roles?",
+            answerMarkdown: "Logging renders plain text and disables implicit Discord mentions. An identifier may be displayed for support or audit context when the source event permits it, but it does not ping the referenced account or role.",
+            answerText: "Logging renders plain text and disables implicit Discord mentions. An identifier may be displayed for support or audit context when the source event permits it, but it does not ping the referenced account or role.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129005",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "6673bb105f3e5a7821e74036602c568da421830571d06fdf8ef11214ab9707c6",
+        },
+        {
+            id: "129006",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "What happens when I change the destination?",
+            answerMarkdown: "Future events use the newly saved channel. Existing Discord messages remain where they were originally delivered; Helyx does not move or duplicate them.",
+            answerText: "Future events use the newly saved channel. Existing Discord messages remain where they were originally delivered; Helyx does not move or duplicate them.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129006",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "2e7c1694d6cf610e5af966611828f2ed914bf89807a1fabf6f8c51426860cfda",
+        },
+        {
+            id: "129007",
+            moduleCode: "129",
+            area: "logging",
+            areaName: "Logging",
+            moduleId: "helyx.logging",
+            question: "What happens when Logging is disabled or removed?",
+            answerMarkdown: "Customer-visible delivery stops and missed activity is not backfilled. Discord messages already sent remain under Discord's retention and channel controls. Helyx's own security and error records continue separately.",
+            answerText: "Customer-visible delivery stops and missed activity is not backfilled. Discord messages already sent remain under Discord's retention and channel controls. Helyx's own security and error records continue separately.",
+            sourceUrl: "https://docs.helyx.gg/modules/logging/faq/#help-faq-129007",
+            sourcePath: "apps/docs/src/content/docs/modules/logging/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Logging: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Available on:** Hosted Helyx and Helyx Self-Hosted",
+                "For setup, requirements and delivery behaviour, start with the Logging overview.",
+            ],
+            contentHash: "9c43b1f8349dcb93ca4613b54104d9ae6f422ce6423fa4ceebb2b4f4d2c14827",
+        },
+        {
+            id: "135001",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "An expected item is missing",
+            answerMarkdown: "Confirm the item is enabled and currently available to that member. Check stock, dates, cooldown, member limit and role rules; autocomplete and browse intentionally omit ineligible items.",
+            answerText: "Confirm the item is enabled and currently available to that member. Check stock, dates, cooldown, member limit and role rules; autocomplete and browse intentionally omit ineligible items.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/#help-faq-135001",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "f0a74e7661187b050ffae26f519fe2c89a0806b552026e2618e9668821ac147f",
+        },
+        {
+            id: "135002",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "A confirmation says the item or balance changed",
+            answerMarkdown: "The preview is stale and nothing new is charged by that attempt. Start `/nexus redeem` again and review the current values.",
+            answerText: "The preview is stale and nothing new is charged by that attempt. Start /nexus redeem again and review the current values.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/#help-faq-135002",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "67a2ec755f8b866ed14b89d2c5ecf64c64625f3060efb8339739a93f28817e61",
+        },
+        {
+            id: "135003",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "No items are available",
+            answerMarkdown: "The Exchange may be empty for this member even when managers have saved items. Check enabled state, stock, availability dates, cooldown, limits and role eligibility.",
+            answerText: "The Exchange may be empty for this member even when managers have saved items. Check enabled state, stock, availability dates, cooldown, limits and role eligibility.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/exchange/#help-faq-135003",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands/exchange.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "2316ad4de23cc76cfc69cf5f984425c5c040f97fcf477ff13310252fe476a549",
+        },
+        {
+            id: "135004",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "A page button says it belongs to another member or expired",
+            answerMarkdown: "Run `/nexus exchange` again. The buttons only work for the member who opened that result, and for a limited time.",
+            answerText: "Run /nexus exchange again. The buttons only work for the member who opened that result, and for a limited time.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/exchange/#help-faq-135004",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands/exchange.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "563969a8a31c041738ed259ff8b338927e7a48642f5fabeedc0a7eeba986b90b",
+        },
+        {
+            id: "135005",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "I can view only my own inventory",
+            answerMarkdown: "That is the default private visibility. A server manager can make inventory public, but should do so only if members expect ownership to be visible.",
+            answerText: "That is the default private visibility. A server manager can make inventory public, but should do so only if members expect ownership to be visible.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/inventory-requests/#help-faq-135005",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands/inventory-requests.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "612034649c074df522cdb5e1ac9f408a8f8a8313c3b222f4cfa4f94f40470e58",
+        },
+        {
+            id: "135006",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "A request has no cancel button",
+            answerMarkdown: "Only the caller's current Pending review requests can be cancelled through this flow. Once staff approval or fulfilment has begun, contact the server team and ask them to review its current status and available actions in the dashboard.",
+            answerText: "Only the caller's current Pending review requests can be cancelled through this flow. Once staff approval or fulfilment has begun, contact the server team and ask them to review its current status and available actions in the dashboard.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/inventory-requests/#help-faq-135006",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands/inventory-requests.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "311eb9d3cf3a04d32e32cdd2633e82b13203f421dda9eefad8ecb2c3ad190bf8",
+        },
+        {
+            id: "135007",
+            moduleCode: "135",
+            area: "nexus-economy",
+            areaName: "Nexus Economy",
+            moduleId: "helyx.nexus-economy",
+            question: "The Custom request form does not open",
+            answerMarkdown: "Confirm the selected item is a currently available Custom request. Helyx rejects slow, missing, disabled or changed items privately; run the command again to load current details. Role and collectible items go directly to the five-minute review because they need no request answer.",
+            answerText: "Confirm the selected item is a currently available Custom request. Helyx rejects slow, missing, disabled or changed items privately; run the command again to load current details. Role and collectible items go directly to the five-minute review because they need no request answer.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-economy/commands/redeem/#help-faq-135007",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-economy/commands/redeem.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Economy: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "a13315e9440942bbfb0bdca7550ca9a1cc4a665f20a343b3253650cbc265b759",
+        },
+        {
+            id: "136001",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "The `/nexus` command or a path is missing",
+            answerMarkdown: "Confirm a Nexus customer module is enabled in this server and the command deployment has completed. Only commands supported by your enabled Nexus modules appear.",
+            answerText: "Confirm a Nexus customer module is enabled in this server and the command deployment has completed. Only commands supported by your enabled Nexus modules appear.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/#help-faq-136001",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "0fdd851e58e14e1371ca2920a0dbc8daf00d99b7dc59f2a15c06121ec45733c8",
+        },
+        {
+            id: "136002",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "A member cannot view another balance",
+            answerMarkdown: "Set **Balance visibility** to public if that is appropriate for the server. Private visibility always allows a member to view their own balance; owners and administrators can still investigate.",
+            answerText: "Set Balance visibility to public if that is appropriate for the server. Private visibility always allows a member to view their own balance; owners and administrators can still investigate.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/#help-faq-136002",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "b2b82cedcfd11665f3d13b3545ee68b42745ad25a936d9c7d51a954191125048",
+        },
+        {
+            id: "136003",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "A staff command says the balance changed",
+            answerMarkdown: "The balance changed after the preview was created. Start the command again, review the new before-and-after values and confirm only if the change is still correct.",
+            answerText: "The balance changed after the preview was created. Start the command again, review the new before-and-after values and confirm only if the change is still correct.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/#help-faq-136003",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "dc227679e800d929357208d5e5e1a0895804728f75fd74251637df21cb445053",
+        },
+        {
+            id: "136004",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "The preview expired",
+            answerMarkdown: "Start the command again. A preview is valid for five minutes and cannot be reused after cancellation or completion.",
+            answerText: "Start the command again. A preview is valid for five minutes and cannot be reused after cancellation or completion.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/administration/#help-faq-136004",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands/administration.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "d94b68e95c920761320992634b8bfb08578a9a4889da794b35ac05d7a6c9c4ec",
+        },
+        {
+            id: "136005",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "The balance changed after the preview",
+            answerMarkdown: "No correction is posted. Reload the account, inspect the newer transaction and create a fresh preview using the current balance.",
+            answerText: "No correction is posted. Reload the account, inspect the newer transaction and create a fresh preview using the current balance.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/administration/#help-faq-136005",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands/administration.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "8c17d5598fe435a50e9e5263bdea8271e2b5405d826e29d11ef7a4131f435f92",
+        },
+        {
+            id: "136006",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "The member erased their Nexus data",
+            answerMarkdown: "Helyx prevents an award from recreating an account removed through a Privacy deletion request. Contact support if the member needs help with their data choices.",
+            answerText: "Helyx prevents an award from recreating an account removed through a Privacy deletion request. Contact support if the member needs help with their data choices.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/administration/#help-faq-136006",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands/administration.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "9c470c9c2d8c408a5ad4dc73629bf6d6dc1f9a02ad4c9a818b87a721d85d6c57",
+        },
+        {
+            id: "136007",
+            moduleCode: "136",
+            area: "nexus-rewards",
+            areaName: "Nexus Rewards",
+            moduleId: "helyx.nexus-rewards",
+            question: "Helyx cannot list server members",
+            answerMarkdown: "For Hosted Helyx, use [dashboard Support](https://docs.helyx.gg/contact/support/) so Helyx staff can check the application capability. Server managers cannot enable it through channel permissions. For Self-Hosted Helyx, the deployment operator must check Server Members Intent in the Discord application and the matching runtime intent configuration; follow [Discord requirements](https://docs.helyx.gg/hosted/discord-requirements/) and [Self-Hosted environment setup](https://docs.helyx.gg/self-host/environment-and-database/). Restore the capability before starting either bulk path.",
+            answerText: "For Hosted Helyx, use dashboard Support so Helyx staff can check the application capability. Server managers cannot enable it through channel permissions. For Self-Hosted Helyx, the deployment operator must check Server Members Intent in the Discord application and the matching runtime intent configuration; follow Discord requirements and Self-Hosted environment setup. Restore the capability before starting either bulk path.",
+            sourceUrl: "https://docs.helyx.gg/modules/nexus-rewards/commands/bulk-awards/#help-faq-136007",
+            sourcePath: "apps/docs/src/content/docs/modules/nexus-rewards/commands/bulk-awards.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Nexus Rewards: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+            ],
+            contentHash: "1aa442e02c98a432755d76e214f092e7c87599915859ca8f23a17144942c8c76",
+        },
+        {
+            id: "139001",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "A member control says the role cannot be managed",
+            answerMarkdown: "Check that the role still exists, remains below Helyx and no longer grants administrative or moderation permissions. Repair the panel after correcting Discord.",
+            answerText: "Check that the role still exists, remains below Helyx and no longer grants administrative or moderation permissions. Repair the panel after correcting Discord.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/commands/#help-faq-139001",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "abaab634b90437db6a911cc2bdc1a9da6751565628c18c54dd316a9bef0c8c43",
+        },
+        {
+            id: "139002",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "A panel cannot publish",
+            answerMarkdown: "Check the target-channel permissions, every role's hierarchy and the required emoji. Embed and reaction panels need additional Discord permissions described under [Permissions](https://docs.helyx.gg/modules/reaction-roles/permissions/).",
+            answerText: "Check the target-channel permissions, every role's hierarchy and the required emoji. Embed and reaction panels need additional Discord permissions described under Permissions.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/commands/#help-faq-139002",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "9329c931f063e8848260f0530966412f964e4aedcec9cf4b48b3d9a295219b03",
+        },
+        {
+            id: "139003",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "There is no `/reaction-role` command",
+            answerMarkdown: "This is expected in the current Live module. Use **Modules > Reaction Roles > Settings** to create a panel and **Panels** to manage it.",
+            answerText: "This is expected in the current Live module. Use Modules > Reaction Roles > Settings to create a panel and Panels to manage it.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/commands/#help-faq-139003",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "e17b837868549276b72c813a8f5e5ac0749d6bc91e8228c2314cfbb9e0b81df4",
+        },
+        {
+            id: "139004",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "Why did Helyx refuse a role?",
+            answerMarkdown: "It is managed, above Helyx, or carries unsafe permissions. Checks run both when publishing and when a member clicks.",
+            answerText: "It is managed, above Helyx, or carries unsafe permissions. Checks run both when publishing and when a member clicks.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/faq/#help-faq-139004",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Reaction Roles overview for setup and limits.",
+            ],
+            contentHash: "48a0ce69a31a0d8ebda7a9b2e733818de14dbcea7a8cecd15d5a75adba1a7ffe",
+        },
+        {
+            id: "139005",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "What is the difference between persistent and non-persistent reactions?",
+            answerMarkdown: "Persistent reactions remain visible and unreacting removes the role. Non-persistent mode assigns the role then clears that member's reaction; it needs Manage Messages.",
+            answerText: "Persistent reactions remain visible and unreacting removes the role. Non-persistent mode assigns the role then clears that member's reaction; it needs Manage Messages.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/faq/#help-faq-139005",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Reaction Roles overview for setup and limits.",
+            ],
+            contentHash: "0f8f3cae75519d924945b1868885ce60a42a73c248c74d27ad3fc1a2e45c70a3",
+        },
+        {
+            id: "139006",
+            moduleCode: "139",
+            area: "reaction-roles",
+            areaName: "Reaction Roles",
+            moduleId: "helyx.reactionroles",
+            question: "Does one-role-only affect roles outside the panel?",
+            answerMarkdown: "No. Selecting a role only removes other roles offered by that same panel.",
+            answerText: "No. Selecting a role only removes other roles offered by that same panel.",
+            sourceUrl: "https://docs.helyx.gg/modules/reaction-roles/faq/#help-faq-139006",
+            sourcePath: "apps/docs/src/content/docs/modules/reaction-roles/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Reaction Roles: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: **Status:** Live **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Reaction Roles overview for setup and limits.",
+            ],
+            contentHash: "00626f890878845790442ad359640446a768ba1a3fd7b70a89effdf6e7b5e049",
+        },
+        {
+            id: "156001",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "A completed answer did not advance progress",
+            answerMarkdown: "Confirm both modules are enabled, the definition is Active and its source event still exists. The answer must have been accepted before the private session expired.",
+            answerText: "Confirm both modules are enabled, the definition is Active and its source event still exists. The answer must have been accepted before the private session expired.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/achievements/#help-faq-156001",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/achievements.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "7ff9da3c8115a78dc7f21dba424c057c0a354b66daef4fb47f422c94ed53f3ba",
+        },
+        {
+            id: "156002",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "A category achievement did not progress",
+            answerMarkdown: "Category triggers count correct answers only. Confirm the question's actual packaged category, not merely the broad filter used to start the round.",
+            answerText: "Category triggers count correct answers only. Confirm the question's actual packaged category, not merely the broad filter used to start the round.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/achievements/#help-faq-156002",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/achievements.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "2e4e089e981414c33da8490821ca84404126c89e1b6ab1792f78c67f94d65a66",
+        },
+        {
+            id: "156003",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "The command is not visible",
+            answerMarkdown: "Confirm Trivia is enabled, the command has appeared in Discord and the member matches the `trivia` policy.",
+            answerText: "Confirm Trivia is enabled, the command has appeared in Discord and the member matches the trivia policy.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/commands/#help-faq-156003",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "2b13132698a0eabce1e4862dba3afd3f97ceffc75840a84fe996bd7ee76a0df3",
+        },
+        {
+            id: "156004",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "The round says too few questions matched",
+            answerMarkdown: "Reduce `questions` or remove one of category, difficulty, niche or type. Helyx preserves uniqueness instead of filling the round with duplicates.",
+            answerText: "Reduce questions or remove one of category, difficulty, niche or type. Helyx preserves uniqueness instead of filling the round with duplicates.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/commands/#help-faq-156004",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "2c2c3f85874be7fb7a8103ff7277d0fec4e042fa82619fb5c81d3aa8504d76ce",
+        },
+        {
+            id: "156005",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "A control says the round was replaced or already answered",
+            answerMarkdown: "Use the newest private response. Starting another round replaces the old controls, and each question can only be answered once.",
+            answerText: "Use the newest private response. Starting another round replaces the old controls, and each question can only be answered once.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/commands/#help-faq-156005",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/commands.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+            ],
+            contentHash: "76cecb3fa7faafa1b1e1f6bed5d45fd767cfa922a328ecc64b3b85aa01239226",
+        },
+        {
+            id: "156006",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "Where do questions come from?",
+            answerMarkdown: "They are installed with the module. Gameplay does not call an external trivia provider. Module updates may replace changes made directly to the question database.",
+            answerText: "They are installed with the module. Gameplay does not call an external trivia provider. Module updates may replace changes made directly to the question database.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/faq/#help-faq-156006",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Trivia overview for setup and limits.",
+            ],
+            contentHash: "b510e8951a99f6231fccb0a9d76309731e442f4138b94b01ddd5a16a7ce93d90",
+        },
+        {
+            id: "156007",
+            moduleCode: "156",
+            area: "trivia",
+            areaName: "Trivia",
+            moduleId: "helyx.trivia",
+            question: "Are Guess answers stored?",
+            answerMarkdown: "No. Input is trimmed, compared locally and discarded. Logs, Achievement events and statistics exclude the submitted text.",
+            answerText: "No. Input is trimmed, compared locally and discarded. Logs, Achievement events and statistics exclude the submitted text.",
+            sourceUrl: "https://docs.helyx.gg/modules/trivia/faq/#help-faq-156007",
+            sourcePath: "apps/docs/src/content/docs/modules/trivia/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "both",
+            context: [
+                "Trivia: live. Deployment compatibility: both. Release status does not by itself mean customer availability.",
+                "Availability: - **Status:** Live - **Current deployment:** Hosted Helyx and supported Self-Hosted builds",
+                "See the Trivia overview for setup and limits.",
+            ],
+            contentHash: "bc229984c27e605c7e273dd3ba00d396a5d5af299ef8707c7650f00636509407",
+        },
+        {
+            id: "158001",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "An action says the attempt changed",
+            answerMarkdown: "Another manager or system outcome updated it. Reload the detail, review the newest timeline and use only a currently offered action.",
+            answerText: "Another manager or system outcome updated it. Reload the detail, review the newest timeline and use only a currently offered action.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/attempts/#help-faq-158001",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/attempts.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "764f30f8a35563cf36ed206a9108de14302d807bb872b54864dea21d10a9f096",
+        },
+        {
+            id: "158002",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "The risk check passed but the role was not applied",
+            answerMarkdown: "The result remains Action failed rather than Pass. Check that the verified role exists, give Helyx **Manage Roles** and move its role above it. Then use the recovery action offered for that attempt.",
+            answerText: "The result remains Action failed rather than Pass. Check that the verified role exists, give Helyx Manage Roles and move its role above it. Then use the recovery action offered for that attempt.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/attempts/#help-faq-158002",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/attempts.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "5b5883b17f8dba71e9be138c00f2712f591d5cacb3282906fae71e9133556100",
+        },
+        {
+            id: "158003",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Search returns no result for a display name",
+            answerMarkdown: "Attempts search accepts an exact Discord user ID, not a display name. Use the member's Discord user ID and keep the date range within 366 days.",
+            answerText: "Attempts search accepts an exact Discord user ID, not a display name. Use the member's Discord user ID and keep the date range within 366 days.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/attempts/#help-faq-158003",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/attempts.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "3f14f25f5ced1c88d10da776473c9bc6e397b792ebc8d8f3e11d32c14da29415",
+        },
+        {
+            id: "158004",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "The audit is missing or access is denied",
+            answerMarkdown: "Confirm that you are using Hosted Helyx with current dashboard and module access. Investigation-only access lets you review attempts but not inspect channels or change settings. You can audit a disabled module, provided it is still installed and available.",
+            answerText: "Confirm that you are using Hosted Helyx with current dashboard and module access. Investigation-only access lets you review attempts but not inspect channels or change settings. You can audit a disabled module, provided it is still installed and available.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/channel-audit/#help-faq-158004",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/channel-audit.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Upcoming feature · Hosted only: This guide describes an unreleased dashboard update. Verification's audit remains Hosted-only and is unavailable to investigation-only accounts. Eligible managers can inspect while the installed module is disabled; no provider credentials or verification results are exposed.",
+            ],
+            contentHash: "ab8acd4f735a256c140268d28b19be3cff8675678bc205c3f1fd5430be40ab89",
+        },
+        {
+            id: "158009",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Details are temporarily unavailable",
+            answerMarkdown: "Retry later or use the Attempts dashboard. The failure does not change the member's current role or attempt decision.",
+            answerText: "Retry later or use the Attempts dashboard. The failure does not change the member's current role or attempt decision.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/commands/investigate/#help-faq-158009",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/commands/investigate.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "c09edd9fb9a2890cf93bf5f702f97cbdf0319bb8da58077c85161e7ec2da6331",
+        },
+        {
+            id: "158012",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "The action is no longer available",
+            answerMarkdown: "Reload the attempt. Another decision, expiry or state change made the old control invalid; use only the actions currently offered.",
+            answerText: "Reload the attempt. Another decision, expiry or state change made the old control invalid; use only the actions currently offered.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/commands/staff-actions/#help-faq-158012",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/commands/staff-actions.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "04f6752ebe80162be5cadfcccd7fbf29e0148bb039757c900aa595bb62a5f714",
+        },
+        {
+            id: "158013",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Approve passed but the role could not be applied",
+            answerMarkdown: "Helyx records an action failure rather than a completed Pass. Restore **Manage Roles**, hierarchy and the role, then use the authorised recovery offered by the current attempt.",
+            answerText: "Helyx records an action failure rather than a completed Pass. Restore Manage Roles, hierarchy and the role, then use the authorised recovery offered by the current attempt.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/commands/staff-actions/#help-faq-158013",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/commands/staff-actions.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "fc7865e80c5b911b9c7ec7c989f657631423c808ea97c276527d10760220df0e",
+        },
+        {
+            id: "158015",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "The link expired or was already used",
+            answerMarkdown: "Run Start again after the applicable cooldown. A used or expired link cannot be reactivated.",
+            answerText: "Run Start again after the applicable cooldown. A used or expired link cannot be reactivated.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/commands/start-status/#help-faq-158015",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/commands/start-status.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "104f2f08055c64e897733176ec0be878723f186a4575367cac2e27e2d986be85",
+        },
+        {
+            id: "158016",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Verification is temporarily unavailable",
+            answerMarkdown: "Wait and retry. No enforcement action is taken merely because the managed service, provider or Discord action could not complete.",
+            answerText: "Wait and retry. No enforcement action is taken merely because the managed service, provider or Discord action could not complete.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/commands/start-status/#help-faq-158016",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/commands/start-status.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+            ],
+            contentHash: "df9e6f1cee103723f73ba9c4e159743fdf2ee3969c86d7dd8da610a7face2627",
+        },
+        {
+            id: "158017",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Why is Verification Hosted only?",
+            answerMarkdown: "Verification uses Helyx's hosted service to check account, connection and device risk. Helyx keeps the credentials and sensitive evidence within that service rather than sharing them with individual bot installations.\n\nSelf-Hosted and Cloud Connect use [Access Control](https://docs.helyx.gg/modules/access-control/) for a Discord-native entry check instead.",
+            answerText: "Verification uses Helyx's hosted service to check account, connection and device risk. Helyx keeps the credentials and sensitive evidence within that service rather than sharing them with individual bot installations. Self-Hosted and Cloud Connect use Access Control for a Discord-native entry check instead.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/faq/#help-faq-158017",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+                "See the Verification overview for setup and limits. :::caution[Hosted only] Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect. :::",
+            ],
+            contentHash: "bdeee98f92219861b1e59dd4ff100d7f7ba376b01cb41897720ee5b12d998eb1",
+        },
+        {
+            id: "158018",
+            moduleCode: "158",
+            area: "verification",
+            areaName: "Verification",
+            moduleId: "helyx.verification",
+            question: "Can Verification and Access Control run together?",
+            answerMarkdown: "No. Both own the entry-role workflow, so activation rejects the second module. Disable Access Control before enabling Verification, or keep Access Control and leave Verification disabled.",
+            answerText: "No. Both own the entry-role workflow, so activation rejects the second module. Disable Access Control before enabling Verification, or keep Access Control and leave Verification disabled.",
+            sourceUrl: "https://docs.helyx.gg/modules/verification/faq/#help-faq-158018",
+            sourcePath: "apps/docs/src/content/docs/modules/verification/faq.md",
+            releaseStatus: "live",
+            deploymentSupport: "hosted",
+            context: [
+                "Verification: live. Deployment compatibility: hosted. Release status does not by itself mean customer availability.",
+                "Hosted only: - **Status:** Live - **Available on:** Hosted Helyx only Verification is not included in Self-Hosted or Cloud Connect. Use [Access Control](/modules/access-control/) for a Discord-native entry check. The two modules cannot be enabled together because both own the entry-role workflow.",
+                "Hosted only: Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect.",
+                "See the Verification overview for setup and limits. :::caution[Hosted only] Verification is available only on Hosted Helyx. These controls are unavailable in Self-Hosted and Cloud Connect. :::",
+            ],
+            contentHash: "3128edc6a7b9118477076e5ce7f3c51c8242cdb8556a09ba6e761a34690ca65b",
+        },
+        {
+            id: "996001",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A manager cannot open the dashboard after a role change",
+            answerMarkdown: "Confirm the role is still assigned, is not also in **Denied roles** and remains\nallowed by the saved policy. Sign out and sign in again so Helyx can refresh\ncurrent Discord membership and roles.",
+            answerText: "Confirm the role is still assigned, is not also in Denied roles and remains allowed by the saved policy. Sign out and sign in again so Helyx can refresh current Discord membership and roles.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/access/#help-faq-996001",
+            sourcePath: "apps/docs/src/content/docs/dashboard/access.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Dashboard access"],
+            contentHash: "d55d05df84cfdf2363f13baf67670da2444eae193de6adc79bb769b986aecb90",
+        },
+        {
+            id: "996002",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A command is denied even though dashboard access works",
+            answerMarkdown: "Dashboard access and module command policies are separate. Open the affected\nmodule entry under **Module commands** and check its preset, allowed roles,\ndenied roles and any required Discord permission.",
+            answerText: "Dashboard access and module command policies are separate. Open the affected module entry under Module commands and check its preset, allowed roles, denied roles and any required Discord permission.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/access/#help-faq-996002",
+            sourcePath: "apps/docs/src/content/docs/dashboard/access.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Dashboard access"],
+            contentHash: "3f0aeede0ecdd19ae2940b15174d45907448f34762867db36cf9d617991e3837",
+        },
+        {
+            id: "996003",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A permission remains missing after changing the bot role",
+            answerMarkdown: "Refresh the page, then check channel and category overrides for the exact\ndestination. For role actions, move Helyx's role above the target role without\nplacing it above trusted staff roles it must never manage.",
+            answerText: "Refresh the page, then check channel and category overrides for the exact destination. For role actions, move Helyx's role above the target role without placing it above trusted staff roles it must never manage.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/audit/#help-faq-996003",
+            sourcePath: "apps/docs/src/content/docs/dashboard/audit.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Dashboard audit"],
+            contentHash: "e6b3bc132323a13284adac6fc8440ea276bb6bd273b6b78580332eb0365da41d",
+        },
+        {
+            id: "996004",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A command rebuild reports the creation allowance is used",
+            answerMarkdown: "Do not repeatedly rebuild. Only newly created command roots use the server's\nrolling 24-hour allowance; updates and removals can still proceed. The status\npanel shows when older usage leaves the window.",
+            answerText: "Do not repeatedly rebuild. Only newly created command roots use the server's rolling 24-hour allowance; updates and removals can still proceed. The status panel shows when older usage leaves the window.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/audit/#help-faq-996004",
+            sourcePath: "apps/docs/src/content/docs/dashboard/audit.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Dashboard audit"],
+            contentHash: "09822a9974aba4324bd7a9994b2715bee65eb977ecb5d204002c46b8ee1c2973",
+        },
+        {
+            id: "996005",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A slot cannot be moved or the saved version changed",
+            answerMarkdown: "Refresh Billing and review the latest allocation before trying again. Confirm access to the source/target server and that Hosted Helyx is active there. Do not repeat a plan/payment action simply because a summary has not refreshed.",
+            answerText: "Refresh Billing and review the latest allocation before trying again. Confirm access to the source/target server and that Hosted Helyx is active there. Do not repeat a plan/payment action simply because a summary has not refreshed.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/billing/#help-faq-996005",
+            sourcePath: "apps/docs/src/content/docs/dashboard/billing.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: [
+                "Documentation guide: Premium and billing",
+                "Availability: These instructions describe the supported controls when billing is offered to your account. They are not an offer to purchase or a promise that checkout is currently open. Use only the availability, quantity, price and terms shown in the signed-in flow; no public price or launch date is established by this guide.",
+            ],
+            contentHash: "ef02dd8df8d21ca84bd7feff4489542215d88da58e80180ffb8737c694fed362",
+        },
+        {
+            id: "996006",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "Change slots is unavailable",
+            answerMarkdown: "Quantity changes require an **Active** plan without cancellation at the end of the period or a pending quantity change. Review the current state and any scheduled change first. Use **Cancel scheduled change** only if you intend to remove that quantity change; check the secure billing portal for subscription cancellation.",
+            answerText: "Quantity changes require an Active plan without cancellation at the end of the period or a pending quantity change. Review the current state and any scheduled change first. Use Cancel scheduled change only if you intend to remove that quantity change; check the secure billing portal for subscription cancellation.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/billing/#help-faq-996006",
+            sourcePath: "apps/docs/src/content/docs/dashboard/billing.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: [
+                "Documentation guide: Premium and billing",
+                "Availability: These instructions describe the supported controls when billing is offered to your account. They are not an offer to purchase or a promise that checkout is currently open. Use only the availability, quantity, price and terms shown in the signed-in flow; no public price or launch date is established by this guide.",
+            ],
+            contentHash: "6fc70b833d9896705e3563d28181ab0f9c58a75b78a46753bc16c227fd8d75ad",
+        },
+        {
+            id: "996007",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "A payment or quantity change is still processing",
+            answerMarkdown: "Check Billing and the secure provider portal for the actual result before retrying. If the result remains unclear, contact Support with the action, approximate time and safe status text; never send card details or payment credentials.",
+            answerText: "Check Billing and the secure provider portal for the actual result before retrying. If the result remains unclear, contact Support with the action, approximate time and safe status text; never send card details or payment credentials.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/billing/#help-faq-996007",
+            sourcePath: "apps/docs/src/content/docs/dashboard/billing.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: [
+                "Documentation guide: Premium and billing",
+                "Availability: These instructions describe the supported controls when billing is offered to your account. They are not an offer to purchase or a promise that checkout is currently open. Use only the availability, quantity, price and terms shown in the signed-in flow; no public price or launch date is established by this guide.",
+            ],
+            contentHash: "70ff42bd15e87b22b8c34ff922d8862a215a540c37203232b6bc58a8a23eadc5",
+        },
+        {
+            id: "996008",
+            moduleCode: "996",
+            area: "platform:dashboard",
+            areaName: "dashboard",
+            moduleId: null,
+            question: "The Enable module button is blocked",
+            answerMarkdown: "The message beside the button explains what is missing, such as a required setting, another module or an installed package. For Self-Hosted bots, a module must be included in the bot before you can enable it for a server.",
+            answerText: "The message beside the button explains what is missing, such as a required setting, another module or an installed package. For Self-Hosted bots, a module must be included in the bot before you can enable it for a server.",
+            sourceUrl: "https://docs.helyx.gg/dashboard/modules/#help-faq-996008",
+            sourcePath: "apps/docs/src/content/docs/dashboard/modules.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Dashboard modules"],
+            contentHash: "bd5aa59f24da78ebe03d27a213bf28165bb6412ef371206456b2f3cb390cea61",
+        },
+        {
+            id: "999001",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "The code is rejected",
+            answerMarkdown: "Create a fresh code, confirm it has not expired or been used, and run the command as a configured deployment owner or Discord application owner or team member. A bot DM is sufficient.",
+            answerText: "Create a fresh code, confirm it has not expired or been used, and run the command as a configured deployment owner or Discord application owner or team member. A bot DM is sufficient.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/link/#help-faq-999001",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/link.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Link your bot"],
+            contentHash: "a774e04b26411aeb1e6cf74842ef1039f2c323924b6384846322abf01d727ff6",
+        },
+        {
+            id: "999002",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "The command is denied",
+            answerMarkdown: "Only a configured deployment owner or the Discord application owner or team\ncan link the bot. If using `HELYX_OWNER_USER_IDS`, check that it includes your Discord user ID.",
+            answerText: "Only a configured deployment owner or the Discord application owner or team can link the bot. If using HELYX_OWNER_USER_IDS, check that it includes your Discord user ID.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/link/#help-faq-999002",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/link.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Link your bot"],
+            contentHash: "fff0fb67fc074d0b297bd23a0cfca0e9b0f6499747afb32e40bb8c6626a80e8c",
+        },
+        {
+            id: "999003",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "The dashboard does not show a server after enrolment",
+            answerMarkdown: "Run `/helyx cloud status`, refresh the server chooser and confirm the signed-in\nDiscord account can still manage that server. Enrolment and dashboard server\naccess are separate checks.",
+            answerText: "Run /helyx cloud status, refresh the server chooser and confirm the signed-in Discord account can still manage that server. Enrolment and dashboard server access are separate checks.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/link/#help-faq-999003",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/link.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Link your bot"],
+            contentHash: "04ca5f920bcf92495c608ce40d143844e405cf6a33fc3adb18a56b4c164d61c4",
+        },
+        {
+            id: "999004",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "The hosted dashboard is unavailable",
+            answerMarkdown: "Local Discord features should continue. Do not restart or rotate credentials\nonly because the dashboard is temporarily unreachable. Check\n`/helyx cloud status` and the public Helyx status page before recovery work.",
+            answerText: "Local Discord features should continue. Do not restart or rotate credentials only because the dashboard is temporarily unreachable. Check /helyx cloud status and the public Helyx status page before recovery work.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/overview/#help-faq-999004",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/overview.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: [
+                "Documentation guide: Cloud Connect overview",
+                "Availability: Cloud Connect is optional and requires a compatible Helyx Self-Hosted project. If **Self-host** does not offer a connection code in the dashboard, linking is not yet available.",
+            ],
+            contentHash: "de780d816c44dfa93b94547206141b9460c831f46ccdd4679680b4f2da46b7e3",
+        },
+        {
+            id: "999005",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "I need direct access to the local database through Cloud Connect",
+            answerMarkdown: "Cloud Connect has no database browser or remote terminal. Ask the person who hosts the bot to use their database or hosting tools.",
+            answerText: "Cloud Connect has no database browser or remote terminal. Ask the person who hosts the bot to use their database or hosting tools.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/overview/#help-faq-999005",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/overview.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: [
+                "Documentation guide: Cloud Connect overview",
+                "Availability: Cloud Connect is optional and requires a compatible Helyx Self-Hosted project. If **Self-host** does not offer a connection code in the dashboard, linking is not yet available.",
+            ],
+            contentHash: "1a24744e20e7247972295190ad78d97b303839074fda63bc6b72aab439c3404b",
+        },
+        {
+            id: "999006",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "The connector repeatedly reports that its identity cannot be decrypted",
+            answerMarkdown: "Stop retrying with the changed key. Restore the original data-encryption key\nfrom backup, or revoke the old installation and enrol a new connector identity\nwith a fresh one-use code.",
+            answerText: "Stop retrying with the changed key. Restore the original data-encryption key from backup, or revoke the old installation and enrol a new connector identity with a fresh one-use code.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/recovery/#help-faq-999006",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/recovery.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Disconnect or recover Cloud Connect"],
+            contentHash: "69a7eff66c6ee464c0a418807d2016f9d3e2aa883a4d42f99639938e1a5c0331",
+        },
+        {
+            id: "999007",
+            moduleCode: "999",
+            area: "platform:cloud-connect",
+            areaName: "cloud connect",
+            moduleId: null,
+            question: "Disconnecting did not remove local module data",
+            answerMarkdown: "This is expected. Cloud Connect disconnection removes hosted management access\nonly. Use each module's documented deletion or privacy workflow for its local\nrecords, and use the Privacy Centre separately for Helyx-owned records.",
+            answerText: "This is expected. Cloud Connect disconnection removes hosted management access only. Use each module's documented deletion or privacy workflow for its local records, and use the Privacy Centre separately for Helyx-owned records.",
+            sourceUrl: "https://docs.helyx.gg/cloud-connect/recovery/#help-faq-999007",
+            sourcePath: "apps/docs/src/content/docs/cloud-connect/recovery.md",
+            releaseStatus: "reference",
+            deploymentSupport: "not_declared",
+            context: ["Documentation guide: Disconnect or recover Cloud Connect"],
+            contentHash: "43387cbc8ee321af9f97be6c9a1241687a403100fba202054ebe18d360cf1406",
+        },
+    ],
+};
+//# sourceMappingURL=help-collection.js.map