Why does instruction ordering matter even when a multi-stage build is already in use?

Multi-stage builds control what ends up in the final image, but within any single stage, Docker's layer cache still operates instruction-by-instruction. Even a builder stage benefits from ordering — copying dependency manifests and running dependency installation before copying full source code — so that stage's cache is reused across builds that only change application code, independent of whatever happens in the final stage.