Python Build Profile's Pyright Rule Disagrees With the Gate's Mypy-Only Acceptance

[ptr727]

Problem

python.pyright.config in spec/project-types.json expects a build-profile directory to configure pyright and run it strict. python.mypy.allowed allows mypy as the only type checker just for a Home Assistant integration or the lint-only profile.

The validator's type-check step does not enforce that split. It accepts any declared directory whose config names mypy or pyright, so a uv build directory with only [tool.mypy] passes the gate while the spec scores it as a finding.

The #1936 work widened this gap. It documents a pyproject.toml beside a requirements*.txt as the build profile, so a mypy-only pip directory now falls under python.pyright.config too.

Decision needed

Should a build directory be allowed to use mypy as its only checker? If yes, relax python.pyright.config and python.mypy.allowed. If no, have the gate or the audit enforce pyright for the build profile.

[ptr727]

Maintainer decision, 2026-09-27: allow mypy as the only type checker of a build directory. Relax python.pyright.config and python.mypy.allowed to match what the gate already accepts. This issue stays open for that change.