ci: verify generated type definitions in CI and release gates

npm test intentionally excludes the d.ts-build-dependent type audits, so
they were not exercised in CI — meaning a change to the style inventory
or a mixin could break the published .d.ts surface unnoticed. Add a
"Verify type definitions" step running `npm run test:types:all` (build
the declarations once, then the tsc consumer test + docmaker and css
surface audits) to the push/PR workflow and both release workflows. Bump
the tests workflow timeout 5->10m to accommodate the extra build.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: maxkfranz

.github/workflows/feature-release.yml

@@ -26,6 +26,8 @@ jobs:
       - name: Run tests
         run : |
           npm test
+      - name: Verify type definitions
+        run: npm run test:types:all
       - name: Determine version for the release
         id: get_new_patch_version
         run: |

.github/workflows/patch-release.yml

@@ -28,7 +28,9 @@ jobs:
         run: npx playwright install --with-deps
       - name: Run tests
         run : |
-          npm test 
+          npm test
+      - name: Verify type definitions
+        run: npm run test:types:all
       - name: Get new version string
         id: get_new_patch_version
         run: |

.github/workflows/tests.yml

@@ -5,7 +5,7 @@ permissions:
 jobs:
   ci:
     runs-on: ubuntu-latest
-    timeout-minutes: 5
+    timeout-minutes: 10
     steps:
     - uses: actions/checkout@v6
     - uses: actions/setup-node@v6
@@ -17,3 +17,5 @@ jobs:
       run: npx playwright install --with-deps
     - name: Run tests
       run: npm test
+    - name: Verify type definitions
+      run: npm run test:types:all