jif e6ebdfe00b Support memory v2 in external-agent memory imports (#56414) ...

## Why

External-agent memory imports previously wrote only to the v1 workspace and queued only v1 consolidation, leaving the v2 pipeline without imported resources.

## What changed

- Always import selected resources into `memories_v2`. Also update `memories` when v1 is selected or a legacy workspace exists.
- Read `memories.version` for detection and import, detect pending changes across the applicable namespaces, and enqueue consolidation separately for each updated namespace.
- Combine project results across namespaces so cleanup in either can succeed while failures in either are reported.
- Adapt imported-memory consolidation instructions to the active pipeline's output format.

## Testing

Expand app-server integration coverage for v2 profiles, explicit v1 selection, default profiles, and existing legacy workspaces. Verify resource copies, consolidation queues, repeat detection, and cleanup of deleted or unscoped projects.

GitOrigin-RevId: 7e9206942d63fd55b7f2a7f5f9210b687da6a973

2026-10-23 09:06:13 +00:00

..

src

Support memory v2 in external-agent memory imports (#56414)

2026-10-23 09:06:13 +00:00

BUILD.bazel

Support detect and import MCP, Subagents, hooks, commands from external (#19949)

2026-04-29 00:45:24 +00:00

Cargo.toml

Preserve URLs and email addresses during external agent migration (#53706)

2026-10-13 16:15:41 +00:00