fix(parser): preserve Antigravity CLI effort for experimental serving variants - #1594
mariusvniekerk merged 6 commits into
Conversation
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
roborev: Combined Review (
|
bcf1a59 to
31ea14d
Compare
roborev: Combined Review (
|
31ea14d to
b537ea5
Compare
roborev: Combined Review (
|
… variants Google's Cloud Code API returns 'gemini-3.7-flash-exp-b' in generation metadata field 19 while executor metadata field 28 contains 'gemini-3.7-flash-high'. Normalize base models for both the executor and generation model by stripping '-exp-b' and '-exp' suffixes so the effort-qualified executor model is properly applied instead of leaking the raw serving variant. Closes kenn-io#1593.
In ongoing Antigravity CLI sessions, new steps beyond the latest executor checkpoint range should inherit the latest executor's model instead of dropping down to the un-effort-qualified generation model. Also ensure generationModel is normalized when executorModel is absent.
…cutors Keep generationModel intact when executorModel is empty or when the executor has a different base model. This avoids inadvertently stripping effort suffixes or experimental variant identifiers when no matching executor metadata applies.
…lization guidance
b537ea5 to
b5a5a00
Compare
|
Rebased onto latest |
roborev: Combined Review (
|
Antigravity CLI 1.1.24 can store an experimental serving identifier such as
gemini-3.7-flash-exp-bin generation metadata while the covering executor metadata records the effort-qualified product model, such asgemini-3.7-flash-high. The parser previously required the generation value to equal the executor's base slug, so the serving identifier leaked into usage events and split one model's dashboard accounting.This change applies the executor range to both SQLite
gen_metadataand preferred.trajectory.jsonsidecar generations. It recognizes only the observed-exp-bserving suffix when matching generation metadata to a covering executor range. Complete display labels and explicitly effort-qualified generation models remain authoritative, unmatched or missing executors preserve the raw generation model, and steps outside every declared executor range are not guessed. Existing archived rows are reparsed through data version 98 so historical message and usage records receive the correction.The Antigravity format inventory now pins the official CLI 1.1.24 release and records the observed field 19 variant. Generic
-expand hypothetical serving suffixes remain distinct until evidence supports normalizing them.The shared model-resolution and executor-range behavior is in
internal/parser/antigravity.go; sidecar attribution is ininternal/parser/antigravity_cli.go; regression coverage is ininternal/parser/antigravity_test.go. The archive reparse boundary is ininternal/db/db.go, and provenance is documented indocs/internal/session-format-sources.md.Closes #1593.