You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was generated by AI during triage (#657 sweep housekeeping, T8h batch conversion).
Three mature, well-scoped plugins/toolchain/reference/ecosystems/python.yaml follow-up findings from PR #859's review threads (merged 2026-07-21; codex P2, dispositioned + resolved under delegation — deferred as follow-ups, not fixed in that PR). Folded from #657 lines (checked off there, this issue is the batch).
Site 1 (P1) — per-tool skip granularity
uv run pyright is the first check-cmd tool whose presence is not implied by the ruff-config opt-in gate. A ruff-configured project with pyright absent that hits the rung-4 bundled fallback gets a compound-&& failure (green→red, fail-closed) or an ecosystem-level missing-tool skip that also drops ruff (coverage loss). Root tension: skip granularity is per-ecosystem, not per-tool.
Options: make the skip per-tool, or document pyright as a hard prerequisite of the python default once ruff is opted in.
Site 2 (P2) — detection globs
Detection globs (*.py, pyproject.toml, uv.lock) omit pyrightconfig.json, so a standalone pyright-config-only change is not auto-detected by /toolchain:check / /toolchain:lint local runs (CI still enforces its own check).
Fix direction: add pyright config files to the python globs.
Site 3 (P2) — opt-in wording ambiguity
The second semicolon-separated opt-in clause ("pyright runs in its default standard mode absent …") structurally resembles the multi-tool per-tool opt-in pattern (SKILL.md bash example), risking misread of python's single-condition gate as multi-condition. SKILL.md explicitly designates python single-condition (mitigates runtime risk); reword so the sole gating condition (ruff config) is unambiguous and the pyright-mode note reads as descriptive, not a second gate.
Acceptance: Site 1 resolved per whichever option is implemented (skip-per-tool code change, or an explicit prerequisite line in SKILL.md/python.md — implementer's call, no architectural fork); Site 2's globs include pyrightconfig.json; Site 3's opt-in wording no longer reads as a second gate condition.
Decision defaulted: Site 1 — document pyright as a hard prerequisite of the python default once ruff is opted in (not a per-tool skip-granularity code change) — veto before merge. Rationale: per-tool skip granularity is a larger cross-ecosystem mechanism change (every check-cmd tool would need independent-skip semantics); documenting the prerequisite is the smaller, reversible fix that resolves the reported fail-closed surprise without redesigning the skip model. A maintainer who wants the larger mechanism change can veto and redirect.
Activity
kyle-sexton commentedon Jul 22, 2026
Claim (work lane, work-2 / T5) — dispatching an implementation subagent this cycle. 2026-07-22T16:21:36Z
kyle-sexton commentedon Jul 22, 2026