[P1][MEM-01] Explicit preferences and memory inspector

Programme: #1
Epic: #29

Objective

Implement inspectable, scoped user memory where preferences/context remain user-owned data rather than an opaque ever-growing prompt.

Scope

• Separate scopes: session context, project knowledge, episodic summaries, explicit durable preferences and optional learned patterns.
• MemoryRecord metadata: origin, evidence/source, confirmation, confidence, sensitivity, scope, expiry and allowed destinations/uses.
• Memory inspector with search, source, usage history, correction, lock, expiry, export and forget.
• Private-session mode that prevents unintended durable carryover.
• Work/personal profile separation.
• Deletion propagation into retrieval indexes, cached summaries and future context eligibility.

Product rules

• Explicit user corrections beat inferred preferences.
• Sensitive inferences do not become durable facts by default.
• Memory does not grant capabilities/permissions.

Acceptance criteria

• User can locate the origin and current scope of a durable preference/memory.
• Correction immediately affects future eligible retrieval/use.
• Forget/delete removes future context eligibility and configured searchable derivatives.
• Private-session material does not enter durable memory without explicit action.
• Work/personal memory remains isolated under provider/context switches.
• Export produces human- and machine-readable memory records without credentials.

Dependencies

• DATA-01
• SEC-03

First phase: P1
Maturity target: P5
Owner: workspace-ui-data

No files, tests, or entry points are identified in the issue; start by reviewing dependencies DATA-01 and SEC-03 and the workspace-ui-data area. Done means the listed acceptance criteria are implemented across scoped memory, inspection, deletion, private sessions, profile isolation, and credential-free export.