Finalization tail candidate selection and baseline

[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
• Consolidated decision: docs/benchmarks/2026-06-22-rust-hybrid-architecture-performance-consolidated-decision.md

What to build

Select exactly one bounded finalization-tail mechanics candidate from the completed boundary map and record the baseline gates needed before implementation. This slice should choose from mechanics-only areas such as edge materialization, endpoint validation, edge write attribution/batching, resolved cleanup, intentionally unresolved cleanup, or metadata preservation around write/cleanup.

The output should name the candidate, explain why it is the first Plan A bet, and define keep/no-go/needs-architecture gates. Semantic target selection remains out of scope.

Acceptance criteria

• Exactly one candidate is selected from the allowed mechanics classes in the Plan A document.
• Semantic target selection, broad disambiguation, framework post-extract migration, dynamic-dispatch synthesis, schema changes, and package/release workflow changes remain out of scope.
• Baseline identifies relevant tail profile sub-buckets and graph parity checks.
• The issue records candidate-specific keep, no-go, and needs-architecture gates.
• The selected candidate is ready for one bounded implementation issue.

Blocked by

None - can start immediately.

[jununfly]

This was generated by AI during triage.

Candidate selection completed. Plan A selected intentionally-unresolved cleanup rowid-range mechanics as the single bounded finalization-tail candidate.

Artifact: docs/benchmarks/2026-06-22-finalization-tail-plan-a-candidate-selection.md.

The selected candidate is mechanics-only: it does not change reference target selection, edge kind semantics, confidence, resolved-by semantics, framework post-extract ordering, dynamic-dispatch synthesis, or SQLite schema.

[jununfly]

This was generated by AI during triage.

Closing as completed. Candidate selection artifact is recorded in docs/benchmarks/2026-06-22-finalization-tail-plan-a-candidate-selection.md.