Maintainer Review

Objective

Make a maintainer decision, not a generic diff summary. Separate these questions:

1. Is the claimed behavior real?
2. Can supported users plausibly reach it?
3. What happens when they do?
4. Is it important enough to act on now?
5. For a PR, is this solution worth merging and maintaining?
6. If competing PRs exist, which single implementation path should maintainers pursue?
7. What concise maintainer message should communicate closure, an evidence request, or required changes?

Lead with the current review state. Use Preliminary assessment while runtime approval or evidence is pending, and Maintainer decision only when the review can be concluded. Use the diff, issue narrative, and contributor effort as evidence, not as proxies for impact.

Workflow

1. Establish the exact remote target