[alex09x]

Problem

code_schema_rename with repos calls schema::rename_across, which renames in each repository's own session (#1425). The session records a "still loading/indexing" note under each root it asks, but only the originating root's notes were ever drained (with_indexing_notes). Notes from secondary repositories were never shown. A plan built from a half-indexed repository passed as complete and could be applied, and the stale note could surface in a later, unrelated answer.

Change

In schema/across.rs::rename_across:

• stale notes of every root are drained before planning;
• after planning, each root's new notes go into the new AcrossRepos::incomplete field.

Then:

• clean() is false while any note exists, so the MCP result is an error result;
• render lists each note with its repository;
• apply refuses without force, writing nothing in any repository, as it already does for analyzer errors.

Reproduce and verify

New a_secondary_repository_still_indexing_is_reported_and_blocks_the_write in crates/prod-code-mcp/tests/tool_handlers_1_b_codemod.rs. A scripted gateway answers the second textDocument/rename (the secondary repository's; roots are asked in order) while "indexing":

• the dry run is an error result naming that repository's note;
• apply fails with the rename's evidence is incomplete;
• both files are unchanged.

Before (main's schema/across.rs/types.rs, a Linux build node):

incomplete evidence is not a clean result: ## /tmp/.tmp8MlPZr
`order_id` → `trade_id`
- rust: 1 occurrence(s) found, 1 renamed by the analyzer, ...
test result: FAILED. 0 passed; 1 failed

After:

tool_handlers_1_b_codemod: test result: ok. 8 passed; 0 failed
lib schema::: test result: ok. 32 passed; 0 failed

Measurements

None; correctness fix.

Checks

On a Linux build node, default stable toolchain:

• cargo clippy -p prod-code-mcp --all-targets: exit 0, no warning in the changed files.
• cargo test -p prod-code-mcp --no-fail-fast: exit 101. 130 test binaries ok; failed targets: only --test encapsulate_preservation, whose test needs a compiler missing on this node (Two prod-code-mcp tests depend on the build node: /tmp as a workspace root and an unconditional zig probe #1567).
• cargo fmt --all -- --check: clean for this PR's files after the two wraps it reported (after the test run).

Closes #1425