[IronAdamant]

The 3 Nov review's wikifier findings are fixed at the cause, after checking each one in this tree.

Rust imports

resolve_rust only kept mod and crate::, so use wikifier::... from src/main.rs and tests/*.rs never became an edge. The resolver now reads the root Cargo.toml package name and lib name (hyphens become underscores), and it resolves crate::, self::, and super:: from the file. crate:: stays inside that file's crate (tests/*.rs and src/bin/*.rs included). The package or lib name points at the library. Path expressions with the same shape count too.

A Cargo-layout fixture (src/lib.rs, src/main.rs, src/bin/, tests/) is part of accuracy_fixtures_match_frozen_edges. A dogfood test copies this repo, runs update_maps, and checks prepare_edit on src/api.rs. The dependents are src/lib.rs, src/mcp.rs, src/main.rs, tests/cli_surface.rs, tests/contract_gaps.rs, tests/protocol_v07.rs, tests/robustness.rs, and tests/skip_maps.rs.

README benchmark

The "Does it pay off?" section cited scripts/benchmark_lookup.py and numbers from the Python package. That script is not in this repo, so the section is gone. The performance table that remains already says those numbers are from the Python package.

Rust Green

mark-green now checks top-level Rust pub items: fn, struct, enum, trait, mod, type, const, static, and pub use names. pub(crate) and items inside impl are not in that set. A Rust file can be verified. Go, C/C++, C#, and Java stay unchecked. On this repo, verify-wikis checked 29 Green wikis with 0 failures. health --summary reports 16 verified, 9 unchecked, 0 red.

Behaviour tests

tests/behaviour_gaps.rs covers:

• WIKIFIER_MCP_DEADLINE_S: a health call finishes, a blocking monitor call returns DeadlineExceeded with timed_out and may_still_complete, and 0 still waits at least one second.
• WIKIFIER_CHECK_CHANGES_MAX: a cap of 1 sets truncated and names the variable. A larger cap and a non-numeric value do not.
• sqlite import: a corrupt file warns sqlite_present_unread. When the sqlite3 CLI is on PATH, an empty cache imports files and edges with hash sha256:legacy, and a filled cache is left alone.
• actionable_low_conf_edges: a conditional import is included at confidence 0.55 (conditional_guard). A dynamic import_module is not.

CI

.github/workflows/ci.yml and publish.yml pin dtolnay/rust-toolchain@1.83.0. Ubuntu, macOS, and Windows all run cargo test --locked. The Windows job is required. The sqlite import assertions run where sqlite3 is installed; the unread warning runs everywhere, so a Windows image without the CLI still exercises that path.

Tidy

Deleted tests/test_gap_closure.py.wiki.md. Cleared the clippy warnings (cargo clippy --all-targets -- -D warnings is clean), including the unused import in tests/parity.rs. Moved MODULARIZATION_PLAN.md and SIMPLIFICATION_PLAN_AND_LOG.md to Findings/archive/. Refreshed library.md (74 edges, map_complete true).

Measured here

• cargo build: success
• cargo test --locked: 47 passed, 0 failed, 0 ignored
• cargo clippy --all-targets -- -D warnings: success
• CI steps run locally: cargo test --locked, the empty-dependency awk check, and cargo run --quiet -- --version (wikifier 4.7.0)
• verify-wikis: 29 checked, 0 failed
• Windows and macOS GitHub runners were not executed on this machine