Module auto-fill is suggest-only: each solve recomputes the per-row suggested fill and the block page shows a sparkle hint when a row's stored modules differ from it. Because the suggestion depends on the solved building count, a row hovering right at a whole-building boundary (say 1.98–2.02 buildings) can flip its suggested speed/efficiency split while the user drags a goal rate — the modules themselves no longer change (that was the point of the suggest-only model), but the hint icon can blink in and out during editing.
Worth a session of live editing to see whether it's actually distracting. If it is, candidates: a small hysteresis band around the whole-count floor before the suggestion flips, or debouncing the hint's appearance so it only shows after the count settles.
Module auto-fill is suggest-only: each solve recomputes the per-row suggested fill and the block page shows a sparkle hint when a row's stored modules differ from it. Because the suggestion depends on the solved building count, a row hovering right at a whole-building boundary (say 1.98–2.02 buildings) can flip its suggested speed/efficiency split while the user drags a goal rate — the modules themselves no longer change (that was the point of the suggest-only model), but the hint icon can blink in and out during editing.
Worth a session of live editing to see whether it's actually distracting. If it is, candidates: a small hysteresis band around the whole-count floor before the suggestion flips, or debouncing the hint's appearance so it only shows after the count settles.