Skip to content

Burn down direct named import binding resolver residual #666

Description

@jununfly

This was generated by AI during triage.

Parent

Roadmap node 1-6-4. Burn down one high-confidence TypeScript resolver residual in docs/plans/2026-06-27-rust-indexing-debt-to-rust-migration-roadmap.json.

Plan: docs/plans/2026-06-29-rust-direct-named-import-binding-residual-burndown-plan.md

What to build

Burn down one high-confidence Rust resolver residual: direct named import binding disambiguation for single value-symbol targets. For JS/TS direct named imports whose module file target is already resolved and whose target file contains one compatible value symbol with the imported name, Rust should write the existing guarded ESM named imports edge with edgeOrigin=rust-finalization. Ambiguous, missing, type-only, default, namespace, re-export, and interop cases must remain fail-closed.

Acceptance criteria

  • A positive fixture shows the binding-level-symbol-disambiguation fallback bucket decreases while esmNamedImportExportResolvedRefs and guarded edge-write written counts increase.
  • The positive fixture graph contains a Rust finalization imports edge from the source binding/import node to the target value symbol.
  • An ambiguous target fixture writes no graph edge and reports an explicit skip/fallback reason.
  • The implementation reuses existing ESM named guarded edge-write semantics and does not introduce new edge kinds or TypeScript resolver behavior changes.
  • Roadmap node 1-6-4 is updated and completed when the fixture gates pass.

Blocked by

None - can start immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions