[Windows] Impossible to update from v4.2.1 to v4.3.0 - Persistent Entry Point Issue (Python 3.14 / pipx)

[chelebyy]

Describe the bug
I am unable to update SuperGemini from v4.2.1 to v4.3.0 on Windows. Despite successful installation logs via pipx or pip, the system persistently executes v4.2.1. This issue is reproducible on 2 different Windows PCs.

Environment

• OS: Windows 10/11
• Python Version: 3.14.2 (Pre-release/New)
• Installation Method: Tried both pip and pipx
• Current Behavior: Stuck on v4.2.1

Steps to Reproduce

1. Existing installation was v4.2.1.
2. Ran pipx install git+https://github.com/SuperClaude-Org/SuperGemini_Framework.git@V4.3.0 --force.
3. Log shows: "installed package supergemini 4.3.0".
4. Ran pipx ensurepath --force.
5. Restarted terminal.
6. Ran supergemini --version.
7. Result: Output is still SuperGemini 4.2.1.

Troubleshooting Attempts
I have tried the following without success:

• pip uninstall SuperGemini -y (Multiple times)
• pipx uninstall supergemini
• Manual deletion of C:\Users\IT\.local\bin\supergemini.exe
• Manual deletion of C:\Users\IT\.local\bin\sg.exe
• Manual deletion of C:\Users\IT\pipx\venvs\supergemini
• Get-Command supergemini shows the path is cleared, but upon re-install, it reverts to the old behavior or Windows keeps caching the old entry point.

Logs

C:\Users\IT>pipx install SuperGemini --force
⚠️  Overwriting file ...\supergemini.exe
installed package supergemini 4.3.0, installed using Python 3.14.2
done! ✨ 🌟 ✨

C:\Users\IT>supergemini --version
SuperGemini 4.2.1