Easy wins

Find one bounded change that makes the whole system simpler, safer, faster, or harder to regress. Prefer finishing work over starting another cleanup thread.

Operating rule

A proposal is an easy win only when all are true:

• scope is concrete: named files, symbols, dependency, asset, test, or migration step;
• the benefit reaches users or many maintainers, not only the author;
• evidence supports the problem and the proposed fix;
• change can be reviewed and tested in one small PR;
• risk is understood and has a verification plan;
• the result reduces entropy: fewer concepts, dependencies, paths, exceptions, stale facts, or ways for the old state to return.

Do not turn this into a general architecture review. Produce fixable candidates, not themes such as “improve modularity” or “add more tests.”

Run