fix: moving components between files is breaking (#929)

* fix: moving components between files is breaking

* fix: clarification

Co-authored-by: Noah Dietz <noahdietz@users.noreply.github.com>

* fix: make the sentence make more sense

* fix: suggested wording

* fix: changelog

Co-authored-by: Noah Dietz <noahdietz@users.noreply.github.com>

Author: alexander-fenster

aip/general/0180.md

@@ -86,6 +86,15 @@ add the new component, but **must not** remove the existing one. In situations
 where this can allow users to specify conflicting values for the same semantic
 idea, the behavior **must** be clearly specified.
 
+### Moving components between files
+
+Existing components **must not** be moved between files.
+
+Moving a component from one proto file to another within the same package is
+wire compatible, however, the code generated for languages like C++ or Python
+will result in breaking change since `import` and `#include` will no longer
+point to the correct code location.
+
 ### Moving into oneofs
 
 Existing fields **must not** be moved into or out of a oneof. This is a
@@ -140,7 +149,8 @@ this guidance could ostensibly prevent _any_ change (which is not the intent).
 
 ## Changelog
 
-- **2022-06-??**: Added more links to other AIPs with compatibility concerns
+- **2022-08-11**: Added "Moving components between files" section.
+- **2022-06-01**: Added more links to other AIPs with compatibility concerns
 - **2019-12-16**: Clarified that moving existing fields into oneofs is
   breaking.