fix(antigravity): repair SQLite usage accounting

Decode the real Antigravity ModelUsageStats buckets and collect usage from generation, step, and retry metadata. Preserve model and source identity across continuation and duplicate rows, keep Gemini and Antigravity discovery independent, and surface SQLite/protobuf failures instead of reporting partial data. Add real-schema fixtures and production report snapshots, restore Gemini diagnostics, and remove the unrelated Gemini pricing feature. Co-authored-by: Tanmay Vivek Dani <[email protected]>
ryoppippi · Aug 31, 2026 · Aug 30, 2026 · Aug 30, 2026 · Aug 30, 2026 · Aug 30, 2026
commit a3a435bffba6925196a47cc8072952f17fcf6bfc
diff --git a/docs/guide/antigravity/index.md b/docs/guide/antigravity/index.md
@@ -41,23 +41,27 @@ ANTIGRAVITY_DATA_DIR="$HOME/.gemini/antigravity-cli,/backup/antigravity" \
 ```
 
 Only `.db` files are read. ccusage opens them read-only and reads the
-`gen_metadata` rows in ascending `idx` order.
+`gen_metadata` rows in ascending `idx` order. When present, the real `steps`
+schema contributes step and retry usage, and `trajectory_metadata_blob` supplies
+the timestamp fallback. SQLite, row-iteration, and protobuf failures are
+reported instead of becoming empty or partial reports.
 
 ## What Gets Calculated
 
-- **Input tokens** - The system-prompt and fresh-input buckets are combined.
-- **Cache reads** - The cache-read bucket remains separate from uncached input.
-- **Output and reasoning** - Visible output and thinking tokens are reported in
-  their corresponding output and reasoning fields.
+- **Input tokens** - The fresh-input bucket is reported independently.
+- **Cache writes and reads** - Both cache buckets remain separate from uncached input.
+- **Output and reasoning** - Total output is split into visible output and
+  thinking/reasoning tokens.
 - **Model names** - Antigravity display names and known internal aliases are
   normalized to pricing model IDs. For example, `Gemini 3 Pro` is reported as
   `gemini-3-pro`.
 - **Costs** - `calculate` and `auto` use the embedded pricing catalog when a
   matching model is available. Use `--offline` to avoid a pricing refresh.
 
 Continuation rows inherit the most recently observed model in their database.
-Rows with a response ID are deduplicated when the same conversation is found in
-multiple configured roots.
+Usage in generation metadata and step metadata is combined, including retry
+records. Successful, retry, and source copies are deduplicated by their response,
+provider-assigned message, or message identity.
 
 ## Configuration
 

diff --git a/rust/Cargo.lock b/rust/Cargo.lock
diff --git a/rust/adapters/antigravity/Cargo.toml b/rust/adapters/antigravity/Cargo.toml
@@ -14,3 +14,4 @@ sqlite.workspace = true
 [dev-dependencies]
 ccusage-core = { workspace = true, features = ["fetch-litellm-pricing"] }
 ccusage-test-support.workspace = true
+insta.workspace = true
diff --git a/rust/adapters/antigravity/README.md b/rust/adapters/antigravity/README.md
@@ -6,8 +6,8 @@ from the Gemini CLI adapter so unified reports preserve source attribution.
 
 ## Owns
 
-- `loader.rs` — database discovery, ordered parallel reads, and response-ID deduplication.
-- `parser.rs` — SQLite row handling, GeneratorMetadata protobuf decoding, token buckets, and model naming.
+- `loader.rs` — database discovery, bounded ordered reads, and identity-based deduplication.
+- `parser.rs` — SQLite row handling, GeneratorMetadata/CortexStepMetadata protobuf decoding, token buckets, retries, and model naming.
 - `paths.rs` — environment variables, default roots, and `.db` discovery.
 - `report.rs` — the JSON and table shapes where they differ from the shared ones.
 
@@ -24,7 +24,10 @@ The adapter reads `.db` files below these default roots:
 `ANTIGRAVITY_DATA_DIR` accepts one or more comma-separated data roots. Each
 root may contain a `conversations/` child or be the conversation directory
 itself. Databases are opened read-only and must provide the `gen_metadata`
-table.
+table. When present, the real `steps` schema contributes step and retry usage,
+and `trajectory_metadata_blob` supplies the timestamp fallback. SQLite,
+row-iteration, and protobuf failures are reported instead of becoming empty or
+partial reports.
 
 ## Public surface