jif a390571745 Default fresh memory profiles to v2 (#56211) ...

## Why

Profiles without a v1 memory workspace have no legacy context to preserve or consolidate before using v2.

## What changed

- Select v2 when memories are enabled and the `memories` directory is absent. Preserve explicit `memories.version` settings, the `memories.dual_write = false` opt-out, and the v1 default for existing workspaces or filesystem check errors.
- Report `v2_ready` immediately for profiles without a v1 workspace. Keep the consolidation count and valid-summary requirements for profiles with a v1 workspace.
- Make resetting an absent memory workspace a no-op so it does not create an unused v1 directory.

## Testing

Extend coverage for default and explicit version selection, opt-outs, version-specific memory reads, fresh-profile readiness and reset behavior, and running only the v2 pipeline for fresh profiles.

GitOrigin-RevId: a8fb0844962ae9266ffbe88af97e8dc4a99ac15f

2026-10-22 16:26:03 +00:00

..

examples

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

scripts

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

src

Default fresh memory profiles to v2 (#56211)

2026-10-22 16:26:03 +00:00

BUILD.bazel

Embed defaults in the packaged config layer (#38179)

2026-08-12 12:15:47 +00:00

Cargo.toml

Require managed configuration from the configured server (#56055)

2026-10-22 02:15:00 +00:00

defaults.toml

Make environment context date and timezone configurable (#52164)

2026-10-08 16:27:10 +00:00