Reconcile topology matrix coverage for Memory Core deployment

Context

Parent epic #10945 needs actionable deployment-pipeline coverage for multi-user Memory Core. Topology is already tracked at the architecture level by #10015 and related #10008/#10009 work, but the deployment-product test lane still needs a concrete matrix: what is product-path default, what is diagnostic-only, and what gets tested in CI.

Duplicate sweep before filing:

• gh issue list --search "unified federated topology Memory Core Playwright" found #10015 plus adjacent parents, but no focused #10945 integration child.
• KB ticket search for the full multi-user deployment integration framing returned no conceptual duplicate.
• This ticket links to #10015 instead of replacing it.

The Problem

The current Docker integration stack exercises a narrow unified deployment shape. That may be correct for the product path, but the repo still carries unified/federated topology vocabulary and older topology-coverage tickets. If the matrix is not explicit, agents can either over-test non-product diagnostic paths or under-test product claims.

The Architectural Reality

Relevant surfaces:

• #10015 — Dynamic Topology: Unified vs Federated Routing.
• #10008/#10009 — existing topology coverage tracks.
• ai/deploy/docker-compose.test.yml — current deployed test topology.
• test/playwright/integration/** — current integration suite.
• learn/agentos/SharedDeployment.md and deployment cookbook topology language.

The Fix

Define and implement the minimal topology matrix for Memory Core deployment integration:

• unified mode as product-path default, with hard assertions for expected routing and data visibility;
• federated mode either as diagnostic-only with explicit integration coverage or as a consciously deferred/retired product claim;
• CI behavior that makes the selected matrix visible.

This can be a docs + test-fixture PR if the architectural decision is mostly clarification, but it must leave executable evidence for the chosen default.

Contract Ledger Matrix

Acceptance Criteria

• Current topology claims are audited against #10015/#10008/#10009.
• Unified product-path deployment coverage is explicit and executable.
• Federated behavior is either covered as diagnostic-only or explicitly deferred with rationale.
• CI or local command names the topology shape under test.
• Documentation and tests agree; no stale topology claim remains without evidence.
• Native links and Related section preserve #10015/#10008/#10009 context.

Out of Scope

• Rewriting the topology architecture in this ticket.
• Retiring federated topology without maintainer approval.
• Adding every possible multi-region cloud layout to CI.

Related

Parent: #10945 Adjacent: #10015, #10008, #10009, #9999

Origin Session ID: c02fbf4e-870c-44c0-ba7e-e9ffacce094b

Retrieval Hint: query_raw_memories(query="unified federated topology Memory Core deployment integration matrix")