[eavanvalkenburg]

Motivation & Context

Agents need a common way to persist conversation history in any supported vector store and to expose application-owned vector collections through safe, configurable tools. This completes the generic CRUD-tool and context-provider work in the vector-store rollout while also enabling compacted chat history with scoped retrieval over the full transcript.

Description & Review Guide

• What are the major changes?
  • Add experimental create_upsert_tool, create_get_tool, and create_delete_tool factories, including model-specific get-result mapping.
  • Add VectorStoreHistoryProvider, which owns its history schema and scopes every operation by application, optional tenant/agent, provider source, and session. It supports JSON or MessagePack content encoding, optional embeddings with provider options, post-read compaction, and scoped full-history search.
  • Add VectorCollectionContextProvider, which exposes a caller-supplied collection through configurable CRUD/search tools, condensed approval configuration, and multiple custom search tools.
  • Export the new APIs, register feature-usage bits, and add unit tests, samples, and documentation.
• What is the impact of these changes?
  • The change is additive and experimental. Existing vector collections and search APIs retain their behavior.
  • Applications can reuse current vector-store connectors for conversation persistence and agent-facing collection management without connector-specific providers.
• What do you want reviewers to focus on?
  • The division between provider-owned history and caller-owned domain collections, the isolation filters on history/search operations, and the generated CRUD-tool schemas and output projections.

Related Issue

Fixes microsoft#4170

No other open pull request was found for this issue.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[eavanvalkenburg]

Closing this fork-only PR because the draft has been opened against microsoft/agent-framework instead.