maintainability-reviewlisted

# Maintainability Review <!-- include: _common/dimension-scope.md --> <!-- include: _common/tool-usage.md --> <!-- include: _common/reviewer-grounding.md --> In `rag-reviewer:review-pr` use the PR-session tools above. Standalone (no PR session): use the session-less tools per the reviewer-grounding block when reviewer is connected and the index is fresh; otherwise fall back to grep/Read. ## Goal Look only for maintainability risks in the selected changes. Ignore performance, security, and general correctness unless they directly explain a maintainability concern. Prioritize findings such as: - unnecessary branching, flag combinations, and deep nesting that increase cognitive load; - large or mixed-responsibility functions that became harder to understand; - duplication or near-duplication that should likely be consolidated; - abstractions, wrappers, or indirection layers that hide a simple flow without a clear payoff; - hidden side effects, implicit contracts, or unclear data flow; - naming or structure that materially harms readability or makes intent harder to recover; - changes that drift away from established repository patterns or documented contributor rules; - behavior changes that should likely carry nearby tests according to project practice; - edits to generated artifacts when the repository expects source changes plus regeneration. ## Repository Context Before raising project-practice findings, read the repository-local guidance that governs the