feat(navigation): resolve exact cross-probe targets - #495
Merged
Conversation
This was referenced Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #395.
This is the terminal N6 slice of the approved Navigation MVP. It reconstructs the unique cross-probe work from draft #401 directly on current main after #488, #491, #492, #493, and #494 landed. The rejected #400 activation tool is intentionally absent. Original implementation authorship from @dubesinhower is preserved.
User-visible capability
resolve_cross_probe_targettool with the exact maintainer-approved public name.GetOpenDocumentsIPC readback.Navigation MVP acceptance accounting
C10to exact schematic KIID/instance resolution: feat(navigation): resolve exact editor targets #492.This closes the issue under the smaller five-operation composition explicitly approved in the maintainer decision.
Current-main conflict resolution
The old #401 branch also contained #400's rejected activation API and stale generated counts. The reconstruction keeps current-main board safety and capability-model changes, excludes activation completely, and adds only the cross-probe resolver. Tool counts were regenerated rather than hand-merged.
Evidence
cargo test -p konnect-core cross_probe --lib- 7 passed.cargo test -p konnect-core editor_navigation --lib- 14 passed.cargo test -p konnect-ipc --test mock_server_test- 55 passed, 1 intentionally ignored.missing_duplicate_and_reference_mismatch_destinations_fail_closedfail; restoring it made the test pass.cargo xtask fix-doc-counts --check- 21 toolsets, 226 registered, 233 total; current.cargo fmt --all -- --check- passed.cargo clippy --workspace --locked --all-targets -- -D warnings- passed.cargo test --workspace --locked --lib --tests- passed.cargo test --workspace --locked --doc- passed.git diff --check- passed.Hermetic coverage includes exact forward/reverse mapping, root and nested sheet paths, human
C10resolution, missing/duplicate/mismatched linkage, stale sources, wrong instances, both live-document proofs, and absence of mutation commands.Validation debt and boundaries
No disposable live KiCad GUI endpoint was available for a new manual integration run. The operation is focused and read-only, and its IPC and saved-design behavior is covered deterministically. Saved footprint symbol-path representation remains a KiCad-version compatibility surface. Pin/pad/net expansion remains unsupported until one stable destination can be modeled.