🔄 Complete the consequences of a change

Complete the consequences of the accepted change across affected code and supporting artifacts, including places outside the initially edited files. Preserve unrelated pre-existing issues. Apply this procedure again to follow-up changes, regardless of where the requirement originated.

1. Establish before and after. Identify the branch's starting point: the most recent commit shared with the branch it will merge into, unless a comparison commit was supplied. Compare it with the current state, including uncommitted work. State what behavior, meaning, or contract changes and identify the intended-use entry points. These may be application entry points, end-to-end scenarios, or library consumers. Distinguish consequences of this branch from pre-existing issues, even within edited files.