deps: update typescript to 6.0.3

### Explanation

Updating astro so to surpass vite versions that file trust policy check

### Issue

_No response_

### Attestations

- [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/)
- [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/).
- [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/).

### Dependencies

- [x] I have pinned the dependencies to a specific patch version.

### Style

- [x] I have run the linter and resolved any errors.
- [x] My pull request uses an appropriate title, matching the conventional commit standards.
- [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

### Tests

- [ ] My contribution adds new code, and I have added tests to cover it.
- [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes.
- [x] All new and existing tests pass locally with my changes. *
- [ ] Code coverage remains at or above the configured threshold.

* a test fail for missing docs for a new app, unrelated to the changes

### Documentation

_No response_

### Versioning

Patch - My pull request introduces bug fixes ONLY.

Reviewed-on: #37
Reviewed-by: Naomi Carrigan <accounts@nhcarrigan.com>
Co-authored-by: Ilenia <ilenia@nhcarrigan.com>
Co-committed-by: Ilenia <ilenia@nhcarrigan.com>

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",
+    "@astrojs/check": "0.9.9",
+    "@astrojs/starlight": "0.40.0",
+    "astro": "6.4.8",
+    "astro-mermaid": "2.0.4",
     "mermaid": "11.12.2",
-    "typescript": "5.9.3"
+    "typescript": "6.0.3"
   },
   "devDependencies": {
     "cspell": "9.4.0",
     "gray-matter": "4.0.3",
-    "vitest": "4.0.15"
+    "vitest": "4.1.9"
   }
 }

pnpm-workspace.yaml

@@ -15,10 +15,17 @@ strictPeerDependencies: true
 # Prevent transitive dependencies from using exotic sources (git repos, direct tarball URLs)
 blockExoticSubdeps: true
 overrides:
-  vite: 6.1.0
   nanoid: 3.3.11
+packageExtensions:
+  langium@*:
+    dependencies:
+      vscode-jsonrpc: 8.2.1
 
 # Lockfile
 
 # Allow the lockfile to be updated during install (set to true in CI for stricter reproducibility)
 preferFrozenLockfile: false
+
+allowBuilds:
+  esbuild: false
+  sharp: false

src/content.config.ts

@@ -0,0 +1,10 @@
+import { defineCollection } from "astro:content";
+import { glob } from "astro/loaders";
+import { docsSchema } from "@astrojs/starlight/schema";
+
+export const collections = {
+  docs: defineCollection({
+    loader: glob({ pattern: "**/*.{md,mdx}", base: "./src/content/docs" }),
+    schema: docsSchema(),
+  }),
+};

src/content/config.ts

@@ -1,6 +0,0 @@
-import { defineCollection } from 'astro:content';
-import { docsSchema } from '@astrojs/starlight/schema';
-
-export const collections = {
-  docs: defineCollection({ schema: docsSchema() }),
-};

src/content/docs/staff/handbook.md

@@ -36,7 +36,7 @@ We recognise and deeply appreciate that our Team members are volunteers dedicati
 
 While we maintain a flexible approach to activity, we kindly request that you inform us of any anticipated absences:
 
-- For absences exceeding one week, please notify the team via the `#staff-chat` channel on Discord.
+- For absences exceeding one week, please notify the team via the `#sentinel-watch` channel on Discord.
 - This communication helps us manage workload distribution and ensures continued smooth operation of our community.
 
 ### 1.3. Extended Inactivity
@@ -187,7 +187,7 @@ Maintain transparency and accountability to the community:
 
 Maintain open lines of communication with your fellow Team members:
 
-- Use designated channels (e.g., `#staff-chat`) to discuss community issues and seek guidance
+- Use designated channels (e.g., `#sentinel-watch`) to discuss community issues and seek guidance
 - Share experiences and seek advice when facing challenging situations
 - Communicate openly about workload, availability, and support needs
 
@@ -223,7 +223,7 @@ All Team members must know when and how to escalate issues appropriately. Escala
 
 **How to Escalate:**
 
-**(a)** **Use Appropriate Channels**: Escalate through designated staff channels (e.g., `#staff-chat` on Discord) or direct contact with relevant coordinators or senior staff.
+**(a)** **Use Appropriate Channels**: Escalate through designated staff channels (e.g., `#sentinel-watch` on Discord) or direct contact with relevant coordinators or senior staff.
 
 **(b)** **Provide Complete Context**: When escalating, include:
 - Clear description of the situation
@@ -281,8 +281,8 @@ For detailed escalation procedures specific to different situations, refer to th
 
 #### 3.1.1. Primary Communication Platforms
 - Our Discord community serves as a primary communication hub for the staff team
-- A private `staff` category is available for internal discussions
-- Discord `#staff-chat` channel for real-time communication and coordination
+- A private `The Inner Circle` category is available for internal discussions
+- Discord `#sentinel-watch` channel for real-time communication and coordination
 
 #### 3.1.2. Use of Staff Communication Channels
 - Utilise staff channels for: