install.py has misleading uninstall docs / behavior around --full

[atifislam3]

The docstring says --full is for “remove .venv and built vector index,” but the actual uninstall already removes the entire target directory, making --full effectively a no-op.
Evidence:
install.py:(632-646)
install.py:679-682
Why it matters:
Confusing CLI semantics.
Users may think --full does something special when it doesn’t.
Fix:
Remove --full, or redefine it clearly and align it with actual behavior.

[MobiusQuant]

Confirmed. This was introduced by the standalone per-platform installation refactor.

Each platform target is now self-contained, and the default uninstall removes the entire target directory, including .venv and knowledge_base/_index. As a result, --full no longer
performs any additional cleanup.

Temporary workaround: simply omit --full:

  python install.py --uninstall

Use the following only if the shared Playwright and Nomic caches should also be removed:

  python install.py --uninstall --purge --yes-i-know

I prepared a backward-compatible fix that:

• keeps --full accepted so existing scripts do not break;
• marks it as a deprecated no-op in CLI help and runtime output;
• updates the English and Chinese documentation;
• adds regression tests confirming that standard uninstall removes the complete self-contained target.

The flag can be removed completely in a future major release

[atifislam3]

i found few other issues too but i can say they are also just small bugs,