Phase 17.3: cross-platform focused validation and packaging/CLI smoke

[jununfly]

This was generated by AI during triage.

Parent

• PRD: Rust indexing core vertical slice #49
• Post-PRD optimization tracker for Rust indexing performance #165
• Phase 17.1: Phase 17.1: final-flush default path design and failure-safety tests #183
• Phase 17.2: Phase 17.2: production final-flush default for Rust opt-in indexing #184

What to build

Validate the production final-flush path with focused cross-platform coverage and affected-path smoke tests. macOS and Linux Docker validation are required. Windows validation is required only if the implementation changed platform-sensitive replace, locking, path, or file-handle behavior; otherwise record a concrete not-required or unavailable reason.

Packaging and release validation should remain smoke-level unless the implementation touches packaging, bundled binary selection, CLI status, or related release paths.

Acceptance criteria

• macOS focused validation runs against the production final-flush default path.
• Linux Docker focused validation runs against the production final-flush default path.
• Windows validation is either run, or explicitly recorded as not required/unavailable with a reason tied to the implementation.
• CLI smoke confirms --engine rust uses production final-flush and --sqlite-write-mode disk remains selectable.
• Packaging/release smoke is run only to the depth justified by touched paths, with the rationale recorded.
• Validation records include pass/fail status, command or script names, and artifact paths where applicable.
• Any failure is categorized as blocking, non-blocking, or follow-up before the issue is closed.

Blocked by

• Phase 17.2: production final-flush default for Rust opt-in indexing #184

[jununfly]

This was generated by AI during triage.

Partial validation completed; this issue should remain open because Linux Docker focused validation could not be run in the current environment.

Completed:

• macOS focused validation passed:
  • cargo test --package zcodegraph-core
  • npm run build
  • npx vitest run __tests__/rust-index-engine-cli.test.ts
  • npx vitest run __tests__/rust-indexing-experiment.test.ts
• macOS CLI smoke passed for default --engine rust final-flush.
• macOS CLI smoke passed for explicit --sqlite-write-mode disk.
• Packaging/CLI smoke was limited to npm run build because no packaging or bundled binary selection path changed.
• Windows validation was marked not required because this phase did not change replace, locking, path, or file-handle semantics.

Blocked:

• Linux Docker focused validation was not run because docker --version returned command not found on this machine.

Artifact:

• docs/benchmarks/2026-06-17-rust-indexing-core-phase-17-validation-and-decision.md

[jununfly]

This was generated by AI during triage.

Status reaffirmed during post-#193 issue hygiene.

This remains an environment validation reserve item, not a blocker for the current Rust indexing optimization path:

• macOS focused validation and CLI smoke were already recorded.
• Windows was recorded as not required for the relevant phase because no platform-sensitive replace/locking/path/file-handle behavior changed.
• Linux Docker validation remains open only because Docker was unavailable in the local environment.

Do not use #185 to block #165 or the next post-#193 profiling slice unless new packaging/CLI/status/platform-sensitive code changes require it.

[jununfly]

This was generated by AI during triage.

Status update on 2026-06-18:

Keeping this open as an environment validation retained item. It remains non-blocking for current rust-hybrid first-user release progress.

Current context:

• Phase 5 now covers local release-like packaged rust-hybrid smoke for extracted bundle and staged npm shim.
• This issue still represents broader cross-platform focused validation / packaging-CLI environment checks, not a reason to block the current completed Phase 5 work.
• Treat as a retained validation item unless a future release readiness plan explicitly promotes it to a release blocker.

No code changes were made for this issue in the latest update.

[jununfly]

This was generated by AI during triage.

Closing this retained environment-validation item. The original Linux Docker focused validation was kept open because the local environment lacked Docker, but later release-path validation superseded this as a blocker: multi-platform Rust core builds, bundle assembly, GitHub Release assets, and npm package publishing have all exercised the relevant packaging/release path.

This closure does not claim the original Docker-only acceptance criterion was retroactively run; it records that #185 is no longer useful as an open tracker.