rust-analyzer SCIP ingest for the Rust reference corpus
Goal
Bring compiler-precise CALLS to the Rust reference corpus via rust-analyzer’s own SCIP emitter, reusing the section-03 importer.
Implementation Sketch
rust-analyzer scip <project-root>emits an index.scip for a Rust workspace (rust-analyzer’s built-in subcommand; no wiring exists in intel_repo today — grounded:grep -rn 'rust-analyzer scip' intel_repo/is empty).- Add a sync step that runs the real CLI over a reference Rust repo, then feeds the resulting index.scip into the section-03 importer with
provenance='rust-analyzer-scip'. - The importer is format-identical (SCIP protobuf) so only the provenance tag + the corpus-selection wiring are new.
Spec References
SCIP protobuf (same schema as oric emission — rust-analyzer and the scip crate share it). rust-analyzer scip subcommand CLI contract.
Work Items
- Ingest
rust-analyzer scip-emitted SCIP for the Rust reference corpus through the section-03 importer, tagging edgesprovenance=rust-analyzer-scip. The Rust path is verified independently (NOT folded into the oriprovenance=scipcount).
Test Coverage
- L12 Production entry point — COVERED: the criterion runs the REAL
rust-analyzer scipCLI on a real Rust target, imports via the section-03 importer, and asserts the Rust path resolved end-to-end (provenance=rust-analyzer-scipCALLS present + a Rust symbol SCIP-resolved, not tree-sitter) — not a seeded graph-state fixture. - L1 Parse .. L11 Spec — N/A: this is external-tool ingest + Python/Neo4j import, not an Ori compiler pipeline stage; no Ori compiler layer applies. test-all.sh does not exercise it; the intel_repo / CLI end-to-end is the gate.