mirror of
https://github.com/AgentSeal/codeburn.git
synced 2026-08-07 07:34:39 +00:00
68ad0be18b
* feat(antigravity): add support for Antigravity IDE storage on Windows CodeBurn previously only detected Antigravity CLI usage (.pb files under .gemini/antigravity/). Antigravity IDE on Windows stores session state in VSCode-style storage at %APPDATA%\Antigravity IDE\User\globalStorage\state.vscdb, which was not detected. Add support for reading Antigravity IDE sessions from the VSCode-style storage: - Extend CONVERSATION_ROOTS to include APPDATA Antigravity IDE path - Refine path classification to properly identify IDE vs CLI sessions - Handle missing per-call timestamps by stamping file mtime as fallback - Bump CACHE_VERSION to 4 for cache invalidation Fixes: CodeBurn reports zero usage when Antigravity IDE is actively used. * fix(antigravity): stamp mtime fallback at emission, tighten path classification - Apply the mtime fallback to a copy at emission instead of mutating and persisting it into the cache, so a later file rewrite can't retro-date a session's history to the new mtime. SQLite gen_metadata rows have no real per-call time; the RPC path still uses chatStartMetadata.createdAt. - Drop the unreachable APPDATA classifier branch (discovery only walks the ~/.gemini roots; APPDATA state.vscdb holds no token usage). This also removes the misroute of base-antigravity paths under an "Antigravity IDE" profile dir. - Bump CACHE_VERSION to invalidate caches that persisted a synthesized mtime. * fix(antigravity): stabilize untimestamped call times across DB rewrites Extract ChatStartMetadata.created_at from proto-encoded data and decode multiple timestamp formats (ISO string, Timestamp submessage, unix varint). Implement assignStableTimestamps() to preserve first-seen timestamps across file rewrites, preventing retro-dating of sessions when .db files are modified. Make conversation roots dynamic (computed per call) to honor environment overrides in tests. Add comprehensive timestamp stability tests verifying that timestamps remain fixed across file mtime changes while respecting date-range filters. * test(antigravity): assert today range excludes first-seen timestamps Adds a test case to verify that the 'today' date range filter correctly excludes sessions based on their first-seen timestamp, not file modification time. This ensures that even if a database file is rewritten with a later mtime, sessions with earlier first-seen dates are properly filtered out. Refs #411 |
||
|---|---|---|
| .. | ||
| design | ||
| providers | ||
| sync | ||
| architecture.md | ||