* Extract Antigravity tool calls, bash commands, MCP tools, and skills from SQLite steps
Parse tool execution events from the SQLite steps table (step_type == 132) grouped by turn boundaries (step_type == 15), mapping run_command to bashCommands, call_mcp_tool to mcp__<server>__<tool>, view_file to skills, and invoke_subagent to subagentTypes. Bump CACHE_VERSION to 6 and add synthetic unit test coverage.
* feat(antigravity): index steps via gen_metadata packed varints and support repeated tools
- Decode packed varint stepIndices in gen_metadata Field 2 for direct step lookup, replacing heuristic turn grouping based on step_type 15.
- Read repeated Field 4 ToolCallMetadata entries per step and ignore send_message.
- Retain SQLITE_BUSY error propagation for WAL concurrency during active sessions.
- Bump session cache key to worktree-project-grouping-v6.
- Update docs and unit tests to reflect realistic step types and schema.
* fix(antigravity): drop unused step_type, simplify skill pattern, and loop all stepIndices chunks
os.homedir() reads USERPROFILE on Windows and never HOME, so the
isolation setup and every test that moved home were still resolving the
developer's real home directory. Fixtures came back empty, real sessions
leaked into counts, and the code under test wrote plans, receipts and a
sync ledger into the real ~/.config/codeburn during a run.
USERPROFILE now joins the redirected variables and a shared setHome()
helper moves HOME and USERPROFILE together; every spawn env carries both.
The remaining Windows-only failures were POSIX-shaped fixtures: chmod
tricks that only toggle a read-only attribute on NTFS, pid 1 as an
always-alive lock holder, splitting paths on '/', bare tar, mode-bit
expectations, and per-file timeouts too short for the cost of a tsx spawn.
Each gets a platform-aware equivalent so nothing is skipped on Windows and
the POSIX branches stay byte-for-byte what they were.
Full run on Windows: 267 files passed, 2 skipped, 3592 tests passed.
Mixed-version binaries were clobbering the unsuffixed Codex, Cursor,
and Antigravity result files and each re-parsed the whole corpus.
Write *-results.v<n>.json like the daily cache. Leave the unsuffixed
file for older binaries; adopt a matching-version copy once.
Codex rollout files are append-only and the active ones run to hundreds
of MB, but any growth re-read the file from byte 0 because the cache
keyed only on mtime+size. The parser now records a restart point at every
task_started boundary — the byte offset plus the state the single-pass
decode carries across it — and a grown file with the same dev/ino picks
up from there.
The boundary sits at the task_started line itself, so the task it opens
is re-decoded from the tail; the entry stores how many calls were decoded
before that point so the resumed run starts from exactly those and cannot
double-count the open task. An unusable or absent snapshot falls back to
a full re-parse.
CODEX_CACHE_VERSION is deliberately not bumped: the new fields are
additive and absence-safe both ways, so a bump would discard a warm
cache for nothing.
Clear the per-directory Codex and Antigravity memo maps in the resident RSS
guard; document the single cache-dir rule (XDG_CACHE_HOME no longer
consulted, ledger migrated); stop output-overflow terminations from spending
the resident's unexpected-death budget.
