jif 71ab2ea77b Stop memory dual-write when v2 is selected (#55262) ...

## Why

Dual-write prepares v2 memories while v1 is selected. Once v2 is selected, running the v1 pipeline is no longer needed.

## What changed

Run both memory pipelines only when `memories.dual_write` is enabled and `memories.version` selects v1. Run only v2 when it is selected, even if dual-write remains enabled. Update the configuration documentation and schema to describe this behavior.

## Testing

Extend the startup test to cover both selected versions, checking model request counts, versioned extraction and consolidation state, and the absence of v1 rollout summaries when v2 is selected.

GitOrigin-RevId: 1eb85bd67d7b32883b4ff086514a2acfb6b18f3a

2026-10-19 11:36:21 +00:00

..

src

Stop memory dual-write when v2 is selected (#55262)

2026-10-19 11:36:21 +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