chore: unify numbering

Approval/onboarding and denial

package.json

@@ -12,16 +12,16 @@
     "test": "vitest --run"
   },
   "dependencies": {
-    "@astrojs/check": "0.9.6",
-    "@astrojs/starlight": "0.37.1",
-    "astro": "5.16.5",
-    "astro-mermaid": "1.2.0",
-    "mermaid": "11.12.2",
+    "@astrojs/check": "0.9.5",
+    "@astrojs/starlight": "0.36.1",
+    "astro": "5.15.2",
+    "astro-mermaid": "1.1.0",
+    "mermaid": "11.12.1",
     "typescript": "5.9.3"
   },
   "devDependencies": {
-    "cspell": "9.4.0",
+    "cspell": "9.2.2",
     "gray-matter": "4.0.3",
-    "vitest": "4.0.15"
+    "vitest": "4.0.5"
   }
 }

src/content/docs/legal/community-support-policy.md

@@ -24,6 +24,7 @@ This Community Support Policy establishes the framework for how community member
 
 This policy applies to all forms of support exchange within our community platforms, including:
 - Discord channels and direct messages
+- Forums and discussion boards
 - Reddit community spaces
 - Social media interactions
 - GitHub collaborative spaces

src/content/docs/legal/license.md

@@ -1877,7 +1877,7 @@ When We elect to provide notice of termination, such notice may be delivered thr
 
 **(a)** Email to Your last known email address;
 
-**(b)** Posting on Our website or repository;
+**(b)** Posting on Our website, repository, or community forums;
 
 **(c)** Direct communication through any platform or service You use to access Our Software;
 
@@ -1927,7 +1927,7 @@ We reserve the unrestricted right to modify, amend, update, or replace any terms
 
 When We make changes to this Licence, We will make reasonable efforts to notify affected users through:
 
-**(a)** Announcements in Our chat channels;
+**(a)** Announcements in Our community forums and chat channels;
 
 **(b)** Updates and notifications in Our software repositories;
 

src/content/docs/legal/security.md

@@ -272,7 +272,7 @@ While we do not currently offer financial rewards, we deeply appreciate security
 
 **(a)** **Hall of Fame Recognition:** Public acknowledgement in our security contributors hall of fame;
 
-**(b)** **Community Recognition:** Acknowledgement in our social media channels;
+**(b)** **Community Recognition:** Acknowledgement in our community forums and social media channels;
 
 **(c)** **Professional References:** With your consent, we may serve as a reference for your security research activities;
 
@@ -510,9 +510,11 @@ Additional resources available to security researchers:
 
 **(a)** **Documentation:** Comprehensive security policy documentation and guidelines;
 
-**(b)** **Educational Resources:** Links to security research best practices and legal guidelines;
+**(b)** **Community Support:** Access to our community forums for general security discussions;
 
-**(c)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures.
+**(c)** **Educational Resources:** Links to security research best practices and legal guidelines;
+
+**(d)** **Feedback Mechanisms:** Opportunities to provide feedback on our security policies and procedures.
 
 ## 11. POLICY UPDATES AND MAINTENANCE
 
@@ -534,7 +536,7 @@ Changes to this Policy will be communicated through:
 
 **(a)** **Direct Notification:** Email notification to researchers who have previously submitted reports;
 
-**(b)** **Public Announcement:** Updates posted on our website;
+**(b)** **Public Announcement:** Updates posted on our website and community forums;
 
 **(c)** **Documentation Updates:** Version-controlled updates to our official documentation;
 

src/content/docs/legal/subprocessors.md

@@ -384,6 +384,8 @@ We will notify users of changes to subprocessor arrangements through:
 
 **(c)** **Service Notifications:** In-app notifications where technically feasible;
 
+**(d)** **Community Announcements:** Public announcements in community forums.
+
 ### 7.2. Types of Changes Requiring Notification
 
 Changes requiring advance notification include:

src/content/docs/staff/training/cross-platform-coordination.md

@@ -60,6 +60,7 @@ This training operates within our policy framework:
 
 **Examples:**
 - **Discord**: Real-time moderation with immediate response capabilities
+- **Forums**: Considered, documented responses with longer discussion threads
 - **Code Repositories**: Technical focus with professional communication standards
 - **Social Media**: Public-facing brand representation with broader audience considerations
 
@@ -548,7 +549,7 @@ This training operates within our policy framework:
 
 ### 10.1. Scenario 1: Cross-Platform Crisis Coordination
 
-**Situation**: A crisis situation occurs that affects multiple platforms simultaneously. The crisis involves a safety threat that's being discussed across Discord, and social media. Information is spreading rapidly and inconsistently across platforms.
+**Situation**: A crisis situation occurs that affects multiple platforms simultaneously. The crisis involves a safety threat that's being discussed across Discord, forums, and social media. Information is spreading rapidly and inconsistently across platforms.
 
 **Your Response:**
 1. How do you coordinate response across all platforms?