Architecture review

Use this to find refactors worth considering. Do not produce a grand redesign unless the user asks for one.

Focus

Look for places where the current shape makes change harder:

• One concept is spread across many files.
• A module is mostly pass-through glue.
• Callers must know too many ordering rules, flags, or data-shape details.
• Tests need awkward mocks because behavior has no useful seam.
• Two modules change together often enough that the boundary is probably wrong.
• A dependency points inward toward business logic instead of outward through an adapter.

Review shape

Return a short ranked list. For each candidate include: