VibeLign v2.1.11 Release Notes

VibeLign v2.1.11 improves the Rust scan path, fixes GUI Explain classification for Tauri backend command files, and brings the CLI help/manual surfaces back in sync with the visible command set.

What changed

  • project_scan now has a Rust IPC path and the Python CLI routes source-file scanning through Rust by default, while preserving the existing Python/fd fallback and VIBELIGN_PROJECT_SCAN_RUST=0 opt-out.
  • scan_cache.incremental_scan() can reuse Rust-provided category and imports metadata, reducing duplicated Python-side classification work.
  • GUI Explain now classifies vibelign-gui/src-tauri/src/commands/*.rs as 명령/설정 instead of 화면, even when a stale project map says those files are UI modules.
  • Explain renderers now label command files consistently, including .mcp.json, pyproject.toml, vib.spec, /commands/, and /cli/ paths.
  • vib -h and vib manual now include all visible recent commands, including backup DB helpers, show, doc-sources, docs-enhance, bench, and manual itself.
  • Tauri command modules now have explicit VibeLign anchor boundaries so future AI edits and explain reports can target backend command files more safely.

Why

  • The Rust scan path makes the GUI/CLI less dependent on Python traversal details and creates a faster, typed metadata bridge for future scan-heavy features.
  • The Explain report should distinguish GUI screens from backend commands; treating Tauri command handlers as UI made risk summaries noisier than necessary.
  • Users discover commands through vib -h and vib manual, so newly added visible commands must be documented in both places before release.

Verified

  • Focused Rust project_scan consumer/fallback tests passed locally during implementation.
  • Explain/GUI contract tests passed locally.
  • CLI help/manual coverage tests passed locally.
  • Diff whitespace check passed with GIT_MASTER=1 git diff --check.