Phase 11: bounded corrected drift-target VS-1 smoke artifact

[jununfly]

This was generated by AI during triage.

Parent

• PRD: Rust indexing core vertical slice #49
• Phase 10: VS Code VS-1 corrected target re-baseline tracker #130

What to build

Run one bounded corrected VS Code drift-target sufficiency smoke using the improved harness. The run may use reuse-indexed pair mode if suitable indexed TypeScript/Rust projects exist; otherwise one bounded rebuild attempt is allowed. The required outcome is a machine-readable artifact, not a passing TypeScript-vs-Rust comparison.

The target wording must remain downgraded: this is a corrected large VS Code sparse checkout with explicit commit drift, not exact-commit VS Code validation.

Acceptance criteria

• Run the Phase 10 target validator first, or record validator-failed in the smoke artifact.
• Attempt exactly one bounded corrected drift-target VS-1 smoke using the improved harness.
• Save the raw artifact under docs/benchmarks or docs/design with command provenance.
• The artifact records Flow section, flowConnected, missing expected symbols, deterministic Read/Grep fallback risk, Rust-specific regression, and TypeScript-vs-Rust comparison status when available.
• If unavailable, the artifact uses the Phase 11 taxonomy and identifies the blocking stage.
• Do not claim Rust matcher default readiness, Rust indexer default readiness, or default rollout readiness.

Blocked by

• Phase 11: reuse indexed TypeScript and Rust sufficiency smoke pairs #133

[jununfly]

This was generated by AI during triage.

Resolved with a bounded corrected-target smoke artifact.

Validator artifact:

docs/benchmarks/2026-06-15-rust-indexing-core-phase-11-vs1-target-validation.raw.json

Smoke artifact:

docs/benchmarks/2026-06-15-rust-indexing-core-phase-11-vscode-sufficiency.raw.json

Result summary:

• The corrected VS Code target is now exact commit 4ac5322601c6985aba4cd9349c23f4ef22dc3e65.
• The validator passed with missingSymbols: [].
• The smoke produced machine-readable JSON.
• The smoke did not reach TypeScript-vs-Rust comparison because it stopped at TypeScript indexing under unsupported Node.js 26.
• unavailableKind: unsupported-runtime.

This does not claim Rust matcher default readiness, Rust indexer default readiness, or default rollout readiness.