Run ESM named binding fallback diagnostics map evidence

[jununfly]

This was generated by AI during triage.

Parent

• Plan: docs/plans/2026-06-21-rust-hybrid-esm-named-binding-fallback-diagnostics-map.md
• Resolver migration tracker: Plan: Rust-hybrid resolver migration decision #296
• Architecture/performance PRD tracker: PRD: Rust-hybrid architecture and performance optimization #295
• Optimization tracker: Post-PRD optimization tracker for Rust indexing performance #165

What to build

Run targeted current-repo and VS Code sparse profile evidence after ESM named fallback samples and taxonomy artifacts exist. The evidence should lift the fallback map enough to choose a next implementation slice or say no-go.

This is evidence-only. Do not pursue a performance win, do not change resolver behavior, and do not clone replacement corpora automatically.

Acceptance criteria

• Current repo targeted profile/taxonomy artifacts are generated.
• VS Code sparse targeted profile/taxonomy artifacts are generated, or evidence is marked needs-human-setup if /private/tmp/codegraph-corpus/vscode-sparse is missing or not hydrated.
• Evidence sidecars record wall time and RSS or rssUnavailableReason.
• Evidence compares ESM named fallback reason distribution and top actionable blockers.
• No README, release note, public API, or performance claim is made from this evidence.

Blocked by

• Add ESM named fallback reason samples to Rust profile #363
• Add ESM named fallback taxonomy artifact generator #364

[jununfly]

This was generated by AI during triage.

Closing with current-repo and VS Code sparse evidence recorded under docs/benchmarks/2026-06-21-esm-named-fallback-diagnostics-*. VS Code sparse evidence identifies directExportCandidateGap as the dominant actionable ESM named fallback group. RSS remains unavailable due to sandboxed process-list access and is recorded in measurement sidecars.