Trace the change across the project
Search for the relevant route, message key, configuration field, or component and identify consumers, tests, and documentation. Confirm which files are authoritative and whether generated files should be edited directly or regenerated from a source.
Keep naming, defaults, and behavior aligned. If a field changes meaning or becomes optional, check every reader and writer rather than changing only the declaration.
Review the whole result
After editing, inspect the diff as a set: look for stale references, missing locale entries, inconsistent examples, and documentation that describes old behavior. Use targeted checks that match the change when available.
Summarize any intentional differences between files so future maintainers can understand them. If a dependent area is out of scope, state the boundary rather than implying it was updated.