@mai0313/vct 0.5.3 → 0.5.5

package/README.md

@@ -12,6 +12,7 @@
 [![tests](https://img.shields.io/github/actions/workflow/status/Mai0313/VibeCodingTracker/test.yml?label=tests&logo=github&style=flat-square)](https://github.com/Mai0313/VibeCodingTracker/actions/workflows/test.yml)
 [![code-quality](https://img.shields.io/github/actions/workflow/status/Mai0313/VibeCodingTracker/code-quality-check.yml?label=code-quality&logo=github&style=flat-square)](https://github.com/Mai0313/VibeCodingTracker/actions/workflows/code-quality-check.yml)
 [![license](https://img.shields.io/badge/License-MIT-green.svg?labelColor=gray&style=flat-square)](https://github.com/Mai0313/VibeCodingTracker/tree/master?tab=License-1-ov-file)
+[![Star on GitHub](https://img.shields.io/github/stars/Mai0313/VibeCodingTracker?style=social&label=Star)](https://github.com/Mai0313/VibeCodingTracker)
 [![PRs](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/Mai0313/VibeCodingTracker/pulls)
 
 </center>
@@ -640,30 +641,65 @@ vct version --text
 
 **Keep your installation up-to-date automatically.**
 
-The update command checks GitHub releases and downloads the latest version for your platform.
+The update command works for **all installation methods** (npm/pip/cargo/manual) by directly downloading and replacing the binary from GitHub releases.
 
 ### Basic Usage
 
 ```bash
+# Check for updates
+vct update --check
+
 # Interactive update with confirmation
 vct update
 
-# Check for updates without installing
-vct update --check
-
-# Force update without confirmation prompt
+# Force update - always downloads latest version (even if already up-to-date)
 vct update --force
 ```
 
-### How It Works
+### ✨ How It Works
 
 1. **Check Latest Version**: Fetches the latest release from GitHub API
-2. **Compare Versions**: Compares current version with the latest available
+2. **Compare Versions**: Compares current version with the latest available (skipped with `--force`)
 3. **Download Binary**: Downloads the appropriate binary for your platform (Linux/macOS/Windows)
 4. **Smart Replacement**:
    - **Linux/macOS**: Automatically replaces the binary (backs up old version to `.old`)
    - **Windows**: Downloads as `.new` and creates a batch script for safe replacement
 
+### 🔄 Force Update Mode
+
+The `--force` flag bypasses version checking and **always downloads** the latest release:
+
+```bash
+# Force reinstall the latest version (useful for corrupted installations)
+vct update --force
+```
+
+**Use cases**:
+
+- Reinstall after corrupted binary
+- Force download latest release without version check
+- Troubleshooting installation issues
+
+**Only fails if**: No binary is found for your platform (OS/architecture)
+
+### 🎯 Works for All Installation Methods
+
+Whether you installed via **npm**, **pip**, **cargo**, or **manually**, `vct update` will work the same way:
+
+```bash
+$ vct update --check
+🔍 Checking for updates...
+📌 Current version: 0.1.6
+📌 Latest version:  v0.1.7
+
+🆕 New version available: v0.1.7
+
+💡 To update, run:
+vct update
+```
+
+**Why does this work?** All installation methods (npm/pip/cargo/manual) use the **same pre-compiled binaries** from GitHub releases. The update command simply downloads the latest binary and replaces your current installation.
+
 ### Platform Support
 
 The update command automatically detects your platform and downloads the correct archive:
@@ -682,19 +718,6 @@ On Windows, the binary cannot be replaced while running. The update command:
 
 Run the batch script after closing the application to finish the update.
 
-### Automatic Update Notifications
-
-**Stay informed of new releases automatically.**
-
-When you start `vct`, it automatically checks for updates once every 24 hours and displays a notification if a new version is available. The notification intelligently detects your installation method and shows the appropriate update command:
-
-- **npm**: `npm update -g @mai0313/vct`
-- **pip**: `pip install --upgrade vibe_coding_tracker`
-- **cargo**: `cargo install vibe_coding_tracker --force`
-- **manual**: `vct update` or re-run installation script
-
-This ensures you always use the correct update method and prevents version conflicts. The check runs silently in the background and won't disrupt your workflow if updates aren't available.
-
 ---
 
 ## 💡 Smart Pricing System

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mai0313/vct",
-  "version": "0.5.3",
+  "version": "0.5.5",
   "description": "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results",
   "author": "Wei Lee <mai@mai0313.com>",
   "license": "MIT",