Carry versioned extraction profiles through compatible DICE entry points

[jimador]

Goal

Carry a trusted, versioned extraction profile through compatible DICE entry points without
changing legacy extraction behavior.

Context

Perspective describes conversational input, not content policy. DICE needs an opaque
profile reference on SourceAnalysisContext and additive rememberText inputs so host applications can
select durable policy without connector branches inside DICE.

Acceptance criteria

• ExtractionContentProfileRef has stable name and version identity.
• SourceAnalysisContext carries an optional profile reference.
• Additive rememberText entry points accept profile and optional run inputs.
• Legacy callers compile and retain current default behavior.
• Profiles do not directly select arbitrary providers, models, or credentials.
• Profile, perspective, schema, and tenant remain independent context dimensions.
• Java and Kotlin compatibility tests cover absent and present profiles.

Constraints

• Keep the public interface small and additive.
• DICE carries profile identity; the host authorizes and binds it.
• Preserve current extraction, resolution, and revision ordering.

Out of scope

• Host profile catalog ownership.
• Durable run persistence.
• Multi-product plans.

Original request

Give source-independent extraction behavior a stable, versioned identity without encoding
content policy in perspective or hard-coding connectors.