vibe-coding-tracker 1.9.0__tar.gz → 1.10.0__tar.gz

{vibe_coding_tracker-1.9.0 → vibe_coding_tracker-1.10.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: vibe-coding-tracker
-Version: 1.9.0
+Version: 1.10.0
 Summary: Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results
 Keywords: cli,ai,coding-assistant,telemetry,claude,codex,gemini,usage-tracker,analytics
 Author: Wei Lee
@@ -259,7 +259,7 @@ vct usage --table --merge-providers
 ┌─────────────────────────────────────────────────────────────────────────────────────────────┐
 │ Total Cost: $79.33  |  Total Tokens: 49.3M  |  Models: 3  |  Memory: 42.8 MB                │
 └─────────────────────────────────────────────────────────────────────────────────────────────┘
-  ↑/↓ scroll  m merge  r refresh  q quit  |  ★ github.com/Mai0313/VibeCodingTracker
+  ↑/↓ scroll  m merge  r refresh  q quit  |  Star on GitHub
 ```
 
 ### Preview: Table & JSON (`vct usage`)
@@ -410,7 +410,7 @@ vct analysis --output today.json --daily
 ┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
 │ Total Lines: 16.1K  |  Total Tools: 619  |  Models: 3  |  Memory: 41.2 MB                                       │
 └─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
-  ↑/↓ scroll  r refresh  q quit  |  ★ github.com/Mai0313/VibeCodingTracker
+  ↑/↓ scroll  r refresh  q quit  |  Star on GitHub
 ```
 
 ### Preview: Table & JSON (`vct analysis`)
@@ -537,7 +537,7 @@ vct fetch copilot --table
 
 ## Configuration
 
-vct keeps its user settings in `~/.vct/config.toml`. The file is **created with defaults on first run**, so you never have to write it by hand — edit it only when you want to change a default. It is generated from vct's typed settings and carries a `#:schema` directive on the first line, so a schema-aware TOML editor (taplo / VS Code "Even Better TOML") gives you autocomplete and validation. Print the schema yourself with `vct config schema`.
+vct keeps its user settings in `~/.vct/config.toml`. The file is **created with defaults on first run**, so you never have to write it by hand — edit it only when you want to change a default. It is generated from vct's typed settings and carries a `#:schema` directive on the first line, so a schema-aware TOML editor (taplo / VS Code "Even Better TOML") gives you autocomplete and validation. Print the schema yourself with `vct config schema`. A file written by an older vct is upgraded to the current layout in place the next time vct reads it (or on demand with `vct config migrate`), so an upgrade never leaves you on a stale format.
 
 ```toml
 #:schema https://raw.githubusercontent.com/Mai0313/VibeCodingTracker/main/vct.schema.json
@@ -603,6 +603,9 @@ vct config edit
 
 # Print the JSON schema (regenerate with: vct config schema > vct.schema.json)
 vct config schema
+
+# Upgrade a legacy-format file to the current layout in place
+vct config migrate
 ```
 
 ---

{vibe_coding_tracker-1.9.0 → vibe_coding_tracker-1.10.0}/README.md

@@ -233,7 +233,7 @@ vct usage --table --merge-providers
 ┌─────────────────────────────────────────────────────────────────────────────────────────────┐
 │ Total Cost: $79.33  |  Total Tokens: 49.3M  |  Models: 3  |  Memory: 42.8 MB                │
 └─────────────────────────────────────────────────────────────────────────────────────────────┘
-  ↑/↓ scroll  m merge  r refresh  q quit  |  ★ github.com/Mai0313/VibeCodingTracker
+  ↑/↓ scroll  m merge  r refresh  q quit  |  Star on GitHub
 ```
 
 ### Preview: Table & JSON (`vct usage`)
@@ -384,7 +384,7 @@ vct analysis --output today.json --daily
 ┌─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
 │ Total Lines: 16.1K  |  Total Tools: 619  |  Models: 3  |  Memory: 41.2 MB                                       │
 └─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘
-  ↑/↓ scroll  r refresh  q quit  |  ★ github.com/Mai0313/VibeCodingTracker
+  ↑/↓ scroll  r refresh  q quit  |  Star on GitHub
 ```
 
 ### Preview: Table & JSON (`vct analysis`)
@@ -511,7 +511,7 @@ vct fetch copilot --table
 
 ## Configuration
 
-vct keeps its user settings in `~/.vct/config.toml`. The file is **created with defaults on first run**, so you never have to write it by hand — edit it only when you want to change a default. It is generated from vct's typed settings and carries a `#:schema` directive on the first line, so a schema-aware TOML editor (taplo / VS Code "Even Better TOML") gives you autocomplete and validation. Print the schema yourself with `vct config schema`.
+vct keeps its user settings in `~/.vct/config.toml`. The file is **created with defaults on first run**, so you never have to write it by hand — edit it only when you want to change a default. It is generated from vct's typed settings and carries a `#:schema` directive on the first line, so a schema-aware TOML editor (taplo / VS Code "Even Better TOML") gives you autocomplete and validation. Print the schema yourself with `vct config schema`. A file written by an older vct is upgraded to the current layout in place the next time vct reads it (or on demand with `vct config migrate`), so an upgrade never leaves you on a stale format.
 
 ```toml
 #:schema https://raw.githubusercontent.com/Mai0313/VibeCodingTracker/main/vct.schema.json
@@ -577,6 +577,9 @@ vct config edit
 
 # Print the JSON schema (regenerate with: vct config schema > vct.schema.json)
 vct config schema
+
+# Upgrade a legacy-format file to the current layout in place
+vct config migrate
 ```
 
 ---

{vibe_coding_tracker-1.9.0 → vibe_coding_tracker-1.10.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "vibe_coding_tracker"
-version = "1.9.0"
+version = "1.10.0"
 description = "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results"
 authors = [
     { name = "Wei Lee", email = "mai@mai0313.com" }