feat(dist): package and distribute the plugin (F10)

[liupeirong]

• Add s:ResolvePythonCommand() to auto-discover checkout .venv Python
• Support g:vimai_python, VIMAI_PYTHON, and VIMAI_SCRIPT overrides
• Add doc/vimai.txt Vim help documentation
• Add MANIFEST.in for source distribution inclusion
• Add vimai console script entry point in pyproject.toml
• Document vim-plug, Vundle, lazy.nvim, and release archive installs
• Rewrite Step 5 for auto-venv resolution (no manual activation needed)
• Add tests/test_distribution.py and vader launcher resolution tests
• Update docs/ARCHITECTURE.md with Distribution section

[github-actions]

✅ Looks Good

Overall assessment: This PR cleanly implements the F10 distribution feature with proper security practices, good documentation, and adequate test coverage.

Findings Summary

Dimension	Count
Security	0
Correctness	0
Reliability	0
Testing gaps	0 (minor note below)

Cross-cutting observations

1. shellescape() usage — Correctly applied to both s:python_cmd and s:main_script in all command construction paths. Good security hygiene.

2. Resolution priority chain — g:vimai_python → $VIMAI_PYTHON → checkout .venv → python fallback is well-designed and clearly documented in README, help docs, and ARCHITECTURE.md.

3. Pre-existing gap: no [build-system] in pyproject.toml — Now that [project.scripts] declares a vimai console entry point, a [build-system] section (e.g., requires = ["setuptools"]) would make the package buildable with standard tools (pip install ., python -m build) without deprecation warnings. Not blocking since the project uses uv exclusively, but worth a follow-up if the CLI entry point is intended for external consumption.

4. Tests — test_distribution.py provides structural smoke tests; vimai.vader covers runtime resolution via VimaiTestPythonCommand() and VimaiTestMainScript(). Together they provide reasonable coverage for the feature.

No blocking issues. Ship it. 🚢

Generated by Agentic PR Review for issue #15 · opus46 2.7M · ◷