docs: make comment for clear

.github/workflows/ci.yaml

@@ -7,7 +7,7 @@ concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 jobs:
-  validate-contributors:
+  validate-readme-files:
     runs-on: ubuntu-latest
     steps:
       - name: Check out code
@@ -20,3 +20,23 @@ jobs:
         run: go build ./scripts/contributors && ./contributors
       - name: Remove build file artifact
         run: rm ./contributors
+  test-terraform:
+    runs-on: ubuntu-latest/
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v4
+      - name: Set up Terraform
+        uses: coder/coder/.github/actions/setup-tf@main
+      - name: Set up Bun
+        uses: oven-sh/setup-bun@v2
+        with:
+          # We're using the latest version of Bun for now, but it might be worth
+          # reconsidering. They've pushed breaking changes in patch releases
+          # that have broken our CI.
+          # Our PR where issues started to pop up: https://github.com/coder/modules/pull/383
+          # The Bun PR that broke things: https://github.com/oven-sh/bun/pull/16067
+          bun-version: latest
+      - name: Install dependencies
+        run: bun install
+      - name: Run tests
+        run: bun test

registry/coder/modules/windows-rdp/tsconfig.json

@@ -15,10 +15,10 @@
     "module": "ESNext",
 
     "paths": {
-      // 2025-04-16 - This seems to be a Bun-specific bug, where extending the
-      // tsconfig file causes all paths from the base tsconfig file to be
-      // forgotten. Node and the VSCode IDE recognize the path no problem, but
-      // without this, the tests will fail.
+      // 2025-04-16 - This seems to be a Bun-specific bug, where extending a
+      // tsconfig file causes all its paths to be forgotten. The VSCode LSP
+      // recognizes the path just fine without this, but Bun needs the mapping
+      // to be redefined
       "~test": ["../../../../test/test.ts"]
     }
   }