@mai0313/vibe-coding-tracker 2.2.0 → 2.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -342,7 +342,7 @@ A panel appears only for a provider whose credentials are present. When four pan
342
342
  | `--json` | Complete parser results as JSON: one object for `<FILE>`, otherwise an array of objects |
343
343
  | `--daily` / `--weekly` / `--monthly` / `--all` | Time range filter for all-session analysis (see table above; not accepted with `<FILE>`) |
344
344
 
345
- See [`examples/`](examples/) for sample inputs and matching JSON outputs for the four JSONL providers, plus the Grok session fixture under [`examples/grok_session/`](examples/grok_session/).
345
+ See [`tests/fixtures/sessions/`](tests/fixtures/sessions/) for sample inputs and matching JSON outputs for the four JSONL providers, plus the Grok session fixture under [`tests/fixtures/sessions/grok/`](tests/fixtures/sessions/grok/).
346
346
 
347
347
  ### Basic Usage
348
348
 
@@ -400,7 +400,7 @@ vct analysis --json --daily > today.json
400
400
 
401
401
  ### Preview: Table & JSON (`vct analysis`)
402
402
 
403
- `--table` renders the per-model breakdown plus a per-provider summary (with an Active Days column). `--text` and `--table` are compact projections of the same normalized parser records. `--json` keeps the complete records, including per-operation details and token usage. With no `<FILE>`, the outer array contains one `CodeAnalysis` object per session; with `<FILE>`, stdout is that single object and matches the corresponding shape under [`examples/`](examples/).
403
+ `--table` renders the per-model breakdown plus a per-provider summary (with an Active Days column). `--text` and `--table` are compact projections of the same normalized parser records. `--json` keeps the complete records, including per-operation details and token usage. With no `<FILE>`, the outer array contains one `CodeAnalysis` object per session; with `<FILE>`, stdout is that single object and matches the corresponding shape under [`tests/fixtures/sessions/`](tests/fixtures/sessions/).
404
404
 
405
405
  ```text
406
406
  Analysis Statistics
package/README.zh-CN.md CHANGED
@@ -342,7 +342,7 @@ Grok 的 `usage` 是单一时点的本地 context 估算:vct 会把 `signals.j
342
342
  | `--json` | 完整 parser 结果. 搭配 `<FILE>` 时为单一 object, 否则为 object 数组 |
343
343
  | `--daily` / `--weekly` / `--monthly` / `--all` | 所有 session 的时间范围筛选. 不可与 `<FILE>` 同时使用, 其他说明见上方表格 |
344
344
 
345
- 参见 [`examples/`](examples/) 目录,其中包含四种 JSONL provider 的示例输入与对应 JSON 输出,以及 [`examples/grok_session/`](examples/grok_session/) 下的 Grok session fixture。
345
+ 参见 [`tests/fixtures/sessions/`](tests/fixtures/sessions/) 目录,其中包含四种 JSONL provider 的示例输入与对应 JSON 输出,以及 [`tests/fixtures/sessions/grok/`](tests/fixtures/sessions/grok/) 下的 Grok session fixture。
346
346
 
347
347
  ### 基本用法
348
348
 
@@ -400,7 +400,7 @@ vct analysis --json --daily > today.json
400
400
 
401
401
  ### 预览:表格与 JSON(`vct analysis`)
402
402
 
403
- `--table` 会显示各 model 的明细, 并附上各 provider 的汇总, 包含 Active Days 列. `--text` 与 `--table` 都是相同 normalized parser records 的精简 projection. `--json` 会保留完整 records, 包括每次操作的 details 与 token usage. 未提供 `<FILE>` 时, 外层数组中的每个元素都是一个 session 的 `CodeAnalysis` object. 提供 `<FILE>` 时, stdout 只会输出该 object, shape 与 [`examples/`](examples/) 中对应的结果相同.
403
+ `--table` 会显示各 model 的明细, 并附上各 provider 的汇总, 包含 Active Days 列. `--text` 与 `--table` 都是相同 normalized parser records 的精简 projection. `--json` 会保留完整 records, 包括每次操作的 details 与 token usage. 未提供 `<FILE>` 时, 外层数组中的每个元素都是一个 session 的 `CodeAnalysis` object. 提供 `<FILE>` 时, stdout 只会输出该 object, shape 与 [`tests/fixtures/sessions/`](tests/fixtures/sessions/) 中对应的结果相同.
404
404
 
405
405
  ```text
406
406
  Analysis Statistics
package/README.zh-TW.md CHANGED
@@ -342,7 +342,7 @@ Grok 的 `usage` 是單一當下的本地 context 估算:vct 會把 `signals.j
342
342
  | `--json` | 完整 parser 結果. 搭配 `<FILE>` 時為單一 object, 否則為 object 陣列 |
343
343
  | `--daily` / `--weekly` / `--monthly` / `--all` | 所有 session 的時間範圍篩選. 不可與 `<FILE>` 同時使用, 其他說明見上方表格 |
344
344
 
345
- 請參考 [`examples/`](examples/) 目錄,裡面有四種 JSONL provider 的範例輸入與對應的 JSON 輸出,以及 [`examples/grok_session/`](examples/grok_session/) 下的 Grok session fixture。
345
+ 請參考 [`tests/fixtures/sessions/`](tests/fixtures/sessions/) 目錄,裡面有四種 JSONL provider 的範例輸入與對應的 JSON 輸出,以及 [`tests/fixtures/sessions/grok/`](tests/fixtures/sessions/grok/) 下的 Grok session fixture。
346
346
 
347
347
  ### 基本用法
348
348
 
@@ -400,7 +400,7 @@ vct analysis --json --daily > today.json
400
400
 
401
401
  ### 預覽:表格與 JSON(`vct analysis`)
402
402
 
403
- `--table` 會顯示各 model 的明細, 並附上各 provider 的摘要, 包含 Active Days 欄位. `--text` 與 `--table` 都是相同 normalized parser records 的精簡 projection. `--json` 會保留完整 records, 包括每次操作的 details 與 token usage. 未提供 `<FILE>` 時, 外層陣列中的每個元素都是一個 session 的 `CodeAnalysis` object. 提供 `<FILE>` 時, stdout 只會輸出該 object, shape 與 [`examples/`](examples/) 中對應的結果相同.
403
+ `--table` 會顯示各 model 的明細, 並附上各 provider 的摘要, 包含 Active Days 欄位. `--text` 與 `--table` 都是相同 normalized parser records 的精簡 projection. `--json` 會保留完整 records, 包括每次操作的 details 與 token usage. 未提供 `<FILE>` 時, 外層陣列中的每個元素都是一個 session 的 `CodeAnalysis` object. 提供 `<FILE>` 時, stdout 只會輸出該 object, shape 與 [`tests/fixtures/sessions/`](tests/fixtures/sessions/) 中對應的結果相同.
404
404
 
405
405
  ```text
406
406
  Analysis Statistics
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mai0313/vibe-coding-tracker",
3
- "version": "2.2.0",
3
+ "version": "2.2.1",
4
4
  "description": "Vibe Coding Tracker - AI coding assistant telemetry/usage parser, aggregate JSONL events into CodeAnalysis results",
5
5
  "author": "Wei Lee <mai@mai0313.com>",
6
6
  "license": "MIT",