Phase 23.2: Inventory performance experiment candidates

[jununfly]

This was generated by AI during triage.

Parent

• Phase 23: Optimization architecture cleanup #218
• Post-PRD optimization tracker for Rust indexing performance #165

What to build

Create an inventory of Rust indexing performance-related production paths, retained diagnostics, experiment flags, and dead candidates so future agents can tell which paths are normal behavior, which are diagnostic-only, and which should no longer remain in runtime code.

This inventory should support the next #165 candidate decision rather than becoming general documentation cleanup.

Acceptance criteria

• Add an inventory document under docs/benchmarks/ or docs/design/.
• Classify each entry as production path, retained diagnostic, or dead candidate.
• Cover final-flush / SQLite write-mode paths.
• Cover Rust core graph-write and FTS rebuild paths.
• Cover finalization/reference-resolution diagnostic fields.
• Cover candidate replay or equivalence diagnostics.
• Cover edge materialization/write candidates.
• Cover local exact reference lookup cache.
• Cover evidence pipeline scripts and generated artifacts.
• For each entry, record owning issue/artifact, why it exists, whether it can affect default behavior, whether it can support future Post-PRD optimization tracker for Rust indexing performance #165 optimization, and what cleanup or documentation is needed.
• Do not update Phase 17.3: cross-platform focused validation and packaging/CLI smoke #185 unless packaging, CLI, status, release, or npm smoke paths are actually touched.

Blocked by

• Phase 23.1: Clean up evidence pipeline contract #219

[jununfly]

This was generated by AI during triage.

Completed as part of Phase 23.

Summary:

• Evidence output now includes an explicit local-only Evidence Contract section.
• RSS unavailable reasons are now surfaced in generated comparison output.
• Performance experiment paths are inventoried as production path, retained diagnostic, or dead candidate.
• Production cleanup stayed on the benchmark/evidence boundary and did not change default indexing behavior.
• Targeted smoke/profile artifacts were generated from existing Phase 22 evidence; no full VS Code sparse scoreboard was run.
• Profile Rust parseExtractionMs before next optimization #224 was created as the next Post-PRD optimization tracker for Rust indexing performance #165 step for parseExtractionMs profiling.

Artifacts:

• docs/benchmarks/2026-06-18-rust-indexing-core-phase-23-experiment-inventory.md
• docs/benchmarks/2026-06-18-rust-indexing-core-phase-23-targeted-evidence-smoke-comparison.md
• docs/benchmarks/2026-06-18-rust-indexing-core-phase-23-targeted-evidence-smoke-decision-draft.md
• docs/benchmarks/2026-06-18-rust-indexing-core-phase-23-closeout-decision.md

Validation:

• npx vitest run __tests__/rust-indexing-evidence.test.ts
• npx vitest run __tests__/rust-indexing-evidence.test.ts __tests__/rust-indexing-experiment.test.ts
• npm run build

#165 remains open. Rust default rollout readiness is not claimed.