Nits adversary

Non-blocking style and taste nits — naming, stale comments, unfinished renames, and similar maintainer cleanup. Not correctness; not a full design review.

Goals

The adversary is designed to produce a small number of high-confidence, actionable findings grounded in concrete repository evidence. Its review should be deterministic where possible, explicit about impact, and quiet when the available evidence does not justify a finding.

Scope

It evaluates changed lines for non-blocking maintainer cleanup such as stale comments, unfinished renames, redundant masking, indentation outliers, unactionable TODO markers, and error names that contradict strongly established local operation vocabulary.

The complete detector or review inventory is maintained in CHECKS.md.

Boundaries

It reports non-blocking taste only. Correctness, security, architecture, and domain-specific defects belong to specialist adversaries.

The error-domain check is deliberately narrow: it requires a changed error construction, an error-mapping boundary, a nearby diagnostic, and a second same-scope operation signal that agree on a different domain. Generic/shared errors, compatibility aliases, uncertain abbreviations, legacy code, tests, generated code, and weak one-clue matches remain quiet.

SDK source coverage

This release uses SDK 0.1.43. This reviewer uses deterministic prepared evidence rather than repository-tool model retrieval, so it has no model coverage result to reinterpret. Existing evidence gates and deterministic findings are preserved.

SDK 0.1.43

This release rebuilds with SDK 0.1.43. SDK PR #73 adds a tested neutral fallback to formatOpinionAsync when concern wording validation is exhausted, preserving completed findings and the ship decision. Reviewers that do not call this API retain their existing opinion behavior. Provider and transport failures remain errors. Domain rules and evidence requirements are unchanged.