[Feature][Windows] Add version number to desktop shortcut name to distinguish multiple installations

[shangxinyu1]

Environment

Platform: Windows
Versions: Multiple versions installed side-by-side (e.g., v0.1.4 and v0.1.10)
Affected Feature: Desktop shortcut naming

Description

When multiple versions of nexu are installed on the same Windows system, the desktop shortcuts have identical names ("Nexu"), making it impossible to distinguish which shortcut launches which version.

Current Behavior

Based on the screenshot:

• Two nexu shortcuts are present on the desktop
• Both shortcuts display the same name: "Nexu"
• Both use the same icon
• Users cannot tell which shortcut corresponds to v0.1.4 and which to v0.1.10
• Must hover or check properties to determine the version
• Easy to accidentally launch the wrong version

Expected Behavior

Desktop shortcuts should be distinguishable when multiple versions are installed:

Option 1: Include version number in shortcut name

• "Nexu v0.1.4"
• "Nexu v0.1.10"
• "Nexu v0.1.11-nightly"

Option 2: Include version series

• "Nexu (0.1.4)"
• "Nexu (0.1.10)"

Option 3: Add version badge/label

• "Nexu - Stable"
• "Nexu - Latest"
• "Nexu - Nightly"

Option 4: Include installation date or sequence

• "Nexu (1)"
• "Nexu (2)"
• Or: "Nexu - 2026-04-07"
• Or: "Nexu - 2026-04-10"

Use Cases

Users may want to keep multiple versions for:

1. Testing - Compare behavior between stable and nightly builds
2. Rollback - Keep old version while testing new one
3. Development - Work with different versions for different projects
4. Stability - Keep a known-good version while trying newer releases

Suggested Implementation

1. During installation:

   • Detect if nexu is already installed
   • If yes, append version identifier to shortcut name
   • Or prompt user: "Nexu is already installed. Name this shortcut: [Nexu v0.1.10]"

2. Post-installation:

   • Provide a way to rename shortcuts from within the app
   • Settings → General → "Rename desktop shortcut"

3. Version detection:

   • Read installed version during shortcut creation
   • Automatically append version to shortcut name
   • Format: "AppName vMajor.Minor.Patch[-nightly]"

Impact

Severity: P2 (Medium) - Usability enhancement

• Confusion when multiple versions are installed
• Risk of launching wrong version
• Poor experience for testers and power users
• Common issue for users who test nightly builds alongside stable

Current Workaround

Users must manually:

1. Right-click each shortcut
2. Select "Properties"
3. Check the "Target" path to identify version
4. Manually rename shortcuts to add version info
5. Repeat after each update/installation

Related Issues

• [Bug] Incorrect application icon displayed on Windows desktop #758 (Windows desktop icon errors) - related to shortcut creation
• Installation/update flow issues

Screenshot

Additional Notes

This is particularly important for:

• Users participating in nightly/beta testing programs
• Developers working on nexu itself
• Support/QA teams comparing versions
• Users rolling back after problematic updates

Consider making this behavior configurable:

• Default: Include version in name when multiple installs detected
• Option: Always include version in shortcut name
• Option: Prompt user for shortcut name during installation