dhruvgupta-oai 333d7bde0f Bound memory baseline files and recover incomplete snapshots (#57240) ...

## Why

Memory baseline snapshots need bounded file reads, and recovery must keep existing memory files visible to consolidation rather than treating them as already processed.

## What changed

- Limit baseline files to 10 MiB, skip oversized working files, and check stored blob sizes before reading them.
- Version baselines and replace missing, outdated, or unusable metadata with an empty baseline, preserving working files as additions. Also invalidate the baseline when a tracked file grows beyond the limit.
- Serialize baseline initialization, resets, and diffs with a cross-process lock. Isolate repository access and pin index writes to the baseline worktree.

## Testing

Add coverage for oversized files, legacy baseline migration, interrupted resets, cross-process locking, and consolidation with unchanged inputs after baseline recovery.

GitOrigin-RevId: 34ecc9e5700a88ed37eff83a90f08d8a9b0d9f29

2026-10-26 20:40:53 +00:00

..

src

Bound memory baseline files and recover incomplete snapshots (#57240)

2026-10-26 20:40:53 +00:00

templates

Add dedicated memory v2 consolidation and read prompts (#43813)

2026-09-08 12:58:11 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

feat: use provider defaults for memory models (#27129)

2026-06-09 23:49:09 +00:00