docs: update scripts/linting/README.md — Invoke-PythonTests.ps1 description still says "verifies pytest availability" instead of uv-fi [Content truncated due to length]

[github-actions]

Component

Documentation

Bug Description

scripts/linting/README.md describes Invoke-PythonTests.ps1 with the feature bullet: "Verifies pytest availability before running". After PR #1938, the script now primarily checks for uv availability and uses uv run pytest. Only when uv is not found does the script fall back to locating pytest directly (.venv or global).

Current (stale):

• Verifies pytest availability before running

Expected:

• Prefers uv run pytest when uv is available; falls back to venv or global pytest

Additionally, the section heading "Runs pytest across Python skills." is slightly misleading — it now runs tests via uv run pytest in the common case.

Expected Behavior

The feature list for Invoke-PythonTests.ps1 should state that uv is the primary executor (syncing dev dependencies with uv sync --dev before running), with pytest as a fallback only when uv is unavailable.

Steps to Reproduce

1. Open scripts/linting/README.md at the Invoke-PythonTests.ps1 section (around line 431–444).
2. Compare the "Features" list against the current script logic in scripts/linting/Invoke-PythonTests.ps1.
3. The change was introduced by: fix(scripts): npm run test:py fails when skills have uv-managed dev dependencies #1938

Additional Context

• Stale documentation file: scripts/linting/README.md (lines 431–444)
• Changed code file: scripts/linting/Invoke-PythonTests.ps1
• PR that introduced the change: fix(scripts): npm run test:py fails when skills have uv-managed dev dependencies #1938

Generated by Documentation Update Check · 178.7 AIC · ⌖ 12.6 AIC · ⊞ 33.4K · ◷