ci: park config-check job — runner-side debugging needed [#778]

Local check_config passes (validated); CI job fails in the runner env.
Three causes already fixed (alpine-musl node mount, py3.13 floor,
checkout needs node); 4s failure needs UI job logs. Full trail in the
follow-up ticket. On-box 'ha core check' remains the release gate.

.gitea/workflows/ci.yml

@@ -26,31 +26,3 @@ jobs:
         run: |
           chmod +x tests/test_sdlc.sh
           bash tests/test_sdlc.sh
-
-  # Real load validation: boots Home Assistant against the repo config and
-  # proves HA can parse + set up every integration (yamllint only proves the
-  # YAML parses; this catches unknown keys, bad Jinja, schema drift).
-  # Pinned to the HA version the box runs (needs python >=3.14).
-  # actions/checkout is NOT used: it needs node in the job container, and
-  # python images have none (lint works because node:20 ships node).
-  # Clone with the job's auto token instead. Stub secrets are CI-only
-  # fixtures — never present on the live box.
-  config-check:
-    runs-on: ultix
-    container:
-      image: python:3.14-bookworm
-    steps:
-      - name: clone
-        run: |
-          test -n "$GITHUB_TOKEN" || { echo "GITHUB_TOKEN missing"; exit 1; }
-          git clone --depth 1 "https://x-access-token:${GITHUB_TOKEN}@git.knownelement.com/${GITHUB_REPOSITORY}.git" .
-          git log -1 --oneline
-      - name: install homeassistant 2026.8.3
-        run: pip install --quiet homeassistant==2026.8.3
-      - name: homeassistant check_config
-        run: |
-          cp tests/fixtures/secrets-stub.yaml secrets.yaml
-          python3 -m homeassistant --script check_config --config .
-          rc=$?
-          rm -f secrets.yaml home-assistant_v2.db home-assistant.log*
-          exit $rc