Specify complete-target mixed rename planning and resource bounds

This commit is contained in:
2026-09-24 16:02:54 -07:00
parent 852a79b566
commit dc87babf0f
6 changed files with 425 additions and 0 deletions
+5
View File
@@ -265,6 +265,11 @@ prior outcomes and failure bodies unchanged; formatting retains the identical
eight inherited blocks. Initial9-pass/4-fail fixture evidence and exact test-only
repairs are preserved. Both occurrence families now retain complete original
authority, but no rename composition or public edit capability follows yet.
The next [whole-target rename planning contract](analysis-mixed-rename-plan-contract-20260924.md)
is accepted after source mapping and independent critique. It specifies complete
non-name equality, simultaneous qualified namespaces, one original-coordinate
edit map and explicit comparison scratch. Implementation and output execution
remain unverified; live ownership and acceptance belong in issue7.
The preceding Project [Windows evidence](experiments/analysis-mixed-project-20260924/README.md)
distinguishes runtime source **71cadfa0cd0e112caa29588d2494753301f3cb6c** from
the formatting-only aaec successor. Strict core all-target Clippy, actual listing