validate-quality-config

# Validate Quality Configuration Validate consistency across quality configuration files. ## When to Use - After running `setup-git-hooks` skill - When debugging "works locally, fails in CI" issues - Before major releases or audits - When onboarding to understand quality setup - After updating any quality-related configuration ## What It Validates The consistency chain: ``` docs/reference/quality-configuration.md ← Single source of truth ↓ must match .editorconfig ← Editor formatting ↓ must match Linter configs ← Code analysis ↓ must match .pre-commit-config.yaml ← Local hooks ↓ must match .github/workflows/*.yml ← CI pipeline .gitlab-ci.yml ``` Plus one axis that is *not* a match but a required **difference**: ``` Language manifest → toolchain FLOOR (go.mod, Cargo.toml, pyproject.toml, package.json, mix.exs) CI config → toolchain BUILD (go-version:, python-version:, node-version:, matrix) these must NOT be the same value ``` **Also validated**: that the toolchain **floor** (language manifest) and **build version** (CI) are deliberately *different*, and that only the floor-compatibility job reads the manifest. This is the one assertion in this skill that checks a difference rather than a match. ## Required Inputs - A project that already has quality configuration in place (run `setup-git-hooks` first) - `d...