github
diff --git a/‎.github/workflows/ci.yml‎
Lines changed: 31 additions & 0 deletions b/‎.github/workflows/ci.yml‎
Lines changed: 31 additions & 0 deletions
diff --git a/‎.github/workflows/dev.lock.yml‎
Lines changed: 250 additions & 8 deletions b/‎.github/workflows/dev.lock.yml‎
Lines changed: 250 additions & 8 deletions
diff --git a/‎.github/workflows/dev.md‎
Lines changed: 30 additions & 6 deletions b/‎.github/workflows/dev.md‎
Lines changed: 30 additions & 6 deletions
diff --git a/‎.github/workflows/smoke-codex.lock.yml‎
Lines changed: 141 additions & 2 deletions b/‎.github/workflows/smoke-codex.lock.yml‎
Lines changed: 141 additions & 2 deletions
diff --git a/‎.github/workflows/smoke-codex.md‎
Lines changed: 12 additions & 0 deletions b/‎.github/workflows/smoke-codex.md‎
Lines changed: 12 additions & 0 deletions
@@ -871,6 +871,37 @@ jobs:
       - name: Run tests
         run: cd actions/setup/js && npm test
 
+  js-qmd-index:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    needs: validate-yaml
+    permissions:
+      contents: read
+    concurrency:
+      group: ci-${{ github.ref }}-js-qmd-index
+      cancel-in-progress: true
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - name: Set up Node.js
+        id: setup-node
+        uses: actions/setup-node@395ad3262231945c25e8478fd5baf05154b1d79f # v6
+        with:
+          node-version: "24"
+          cache: npm
+          cache-dependency-path: actions/setup/js/package-lock.json
+      - name: Report Node cache status
+        run: |
+          if [ "${{ steps.setup-node.outputs.cache-hit }}" == "true" ]; then
+            echo "✅ Node cache hit" >> $GITHUB_STEP_SUMMARY
+          else
+            echo "⚠️ Node cache miss" >> $GITHUB_STEP_SUMMARY
+          fi
+      - name: Install npm dependencies
+        run: cd actions/setup/js && npm ci
+      - name: Run qmd_index.cjs tests
+        run: cd actions/setup/js && npm test -- qmd_index.test.cjs
+
   js-integration-live-api:
     runs-on: ubuntu-latest
     timeout-minutes: 10
 
@@ -1,6 +1,7 @@
 ---
 on:
   workflow_dispatch:
+  label_command: dev
   schedule:
     - cron: '0 9 * * *'  # Daily at 9 AM UTC
 name: Dev
@@ -14,6 +15,22 @@ permissions:
   issues: read
   pull-requests: read
 
+tools:
+  qmd:
+    runs-on: aw-gpu-runner-T4
+    gpu: true
+    checkouts:
+      - name: docs
+        paths:
+          - docs/src/**/*.md
+          - docs/src/**/*.mdx
+        context: "gh-aw project documentation"
+    searches:
+      - name: issues
+        type: issues
+        max: 500
+        github-token: ${{ secrets.GITHUB_TOKEN }}
+
 safe-outputs:
   create-issue:
     expires: 7d
@@ -24,14 +41,21 @@ features:
 
 # Daily Status Report
 
-Generate a daily status report for the gh-aw project.
+Generate a daily status report for the gh-aw project, focusing on documentation quality.
 
 **Requirements:**
-1. Analyze the current state of the repository
-2. Check for recent commits, pull requests, and issues
-3. Identify any potential issues or areas needing attention
-4. Create a comprehensive daily status report
-5. Post the report as an issue with the date in the title
+
+1. **Find documentation problems reported in issues**: Use the `qmd` search tool to query the indexed issues collection for issues that mention documentation bugs, unclear instructions, missing documentation, or incorrect documentation. Look for patterns like "docs", "documentation", "unclear", "wrong", "missing", "broken", "outdated".
+
+2. **Cross-reference with current documentation**: For each documentation problem found in issues, use the `qmd` search tool to query the indexed docs collection to find the relevant documentation section that the issue is referencing or that could answer the question raised.
+
+3. **Compile a report** summarizing:
+   - Issues that report documentation problems (with issue numbers and titles)
+   - The corresponding documentation sections that may need updating
+   - Any issues where the documentation actually already contains the answer (and the issue could be closed with a pointer)
+   - Gaps where no documentation exists for a reported problem
+
+4. Post the report as an issue with the date in the title.
 
 Keep the report informative but concise.
 
 
@@ -34,6 +34,18 @@ tools:
     languages:
       go: {}
   web-fetch:
+  qmd:
+    checkouts:
+      - name: docs
+        paths:
+          - docs/src/**/*.md
+          - docs/src/**/*.mdx
+        context: "gh-aw project documentation"
+    searches:
+      - name: issues
+        type: issues
+        max: 500
+        github-token: ${{ secrets.GITHUB_TOKEN }}
 runtimes:
   go:
     version: "1.25"