Implement one bounded finalization-tail mechanics candidate

[jununfly]

This was generated by AI during triage.

Parent

• Optimization tracker: Post-PRD optimization tracker for Rust indexing performance #165
• Plan: docs/plans/2026-06-22-rust-hybrid-finalization-tail-implementation-sequence.md
• Blocker: Finalization tail candidate selection and baseline #416

What to build

Implement the single finalization-tail mechanics candidate selected by #416. The implementation must preserve reference target ids, edge kind semantics, confidence/resolved-by semantics, and fallback taxonomy. Unknown or unsupported lifecycle states must fail closed by preserving existing behavior or retaining fallback evidence.

This issue is mechanics-only. It must not change every-reference disambiguation, broad resolver semantics, framework post-extract ordering, dynamic-dispatch synthesis, SQLite schema, package behavior, or release workflow behavior.

Acceptance criteria

• Exactly one candidate from Finalization tail candidate selection and baseline #416 is implemented.
• Deterministic parity tests cover the changed mechanics surface.
• Target ids, edge kind semantics, confidence/resolved-by semantics, and fallback taxonomy remain unchanged unless Finalization tail candidate selection and baseline #416 explicitly classified a non-semantic mechanics-only difference.
• Unsupported or unknown lifecycle states preserve fallback evidence or existing TypeScript behavior.
• No schema, framework post-extract ordering, dynamic-dispatch synthesis, package, or release workflow changes are introduced.

Blocked by

• Finalization tail candidate selection and baseline #416

[jununfly]

This was generated by AI during triage.

Implemented the bounded mechanics candidate. Batched intentionally-unresolved cleanup now uses the same rowid-range cleanup helper as batched resolved cleanup.

Production change: src/resolution/index.ts.
Test coverage: __tests__/resolution.test.ts verifies resolved and intentionally-unresolved terminal refs are cleaned while preserving cleanup counts and using rowid-range deletion.

[jununfly]

This was generated by AI during triage.

Closing as implemented. Batched intentionally-unresolved cleanup now uses rowid-range cleanup mechanics, with deterministic resolver cleanup coverage.