Roger Barreto

.Net: Harden structured data mutation boundaries (#14718) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> Structured data mutation functions need a clear boundary between model-provided request data and Entity Framework persistence entities. Applications also need to control how update and delete targets are resolved before a mutation runs. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> - Makes the convenience plugin factory query-only by default and rejects mutation operations that lack explicit application configuration. - Keeps the legacy direct-entity mutation overloads for compatibility, but makes them fail closed. - Adds safe mutation overloads that use separate request types, explicit insert/update mapping, and application-scoped tracked-entity resolution for update and delete. - Updates the structured data sample to demonstrate explicit safe function composition. - Adds regression coverage for request mapping, scoped resolution, detached entities, and the fail-closed legacy surface. Validation: - `dotnet build dotnet\src\Plugins\Plugins.StructuredData.EntityFramework\Plugins.StructuredData.EntityFramework.csproj -c Debug --tl:off --warnaserror --no-restore` — passed for `net10.0`, `net8.0`, and `net462` with 0 warnings and 0 errors. - `dotnet build dotnet\src\Plugins\Plugins.UnitTests\Plugins.UnitTests.csproj -c Debug -f net10.0 --tl:off --warnaserror --no-restore` — passed with 0 warnings and 0 errors. - `dotnet test dotnet\src\Plugins\Plugins.UnitTests\Plugins.UnitTests.csproj -c Debug -f net10.0 --no-build --no-restore -v Normal --logger trx` — 592 passed, 15 skipped, 0 failed. - `dotnet build dotnet\samples\Demos\StructuredDataPlugin\StructuredDataPlugin.csproj -c Debug --tl:off --warnaserror --no-restore` — passed with 0 warnings and 0 errors. - Scoped `dotnet format --verify-no-changes` — passed natively and with `mcr.microsoft.com/dotnet/sdk:10.0` for all affected projects. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone :smile:

.Net: Bind validated HTTP addresses to connections (#14719) ### Motivation and Context <!-- Thank you for your contribution to the semantic-kernel repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> `HttpPlugin` validated resolved addresses before sending a request, but the built-in HTTP transport did not retain that address set when opening the connection. This change keeps the validation decision and the resulting connection consistent. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> - Moves the existing validated-address connection handling into the shared internal HTTP client provider. - Passes the addresses validated by `HttpPlugin` to the built-in transport while preserving the original HTTP and TLS hostname. - Keeps validated and explicitly unchecked requests in separate connection pools. - Fails closed for hostname requests when a caller-supplied client or target framework cannot guarantee address binding. - Adds deterministic request projection, connection, and custom-client regression coverage. Validation: - `dotnet build dotnet\src\Plugins\Plugins.Core\Plugins.Core.csproj -c Debug --tl:off --warnaserror --no-restore` — passed for `net10.0`, `net8.0`, and `netstandard2.0` with no warnings. - `dotnet build dotnet\src\Functions\Functions.OpenApi\Functions.OpenApi.csproj -c Debug --tl:off --warnaserror --no-restore` — passed for `net10.0`, `net8.0`, and `netstandard2.0` with no warnings. - `dotnet build dotnet\src\Plugins\Plugins.UnitTests\Plugins.UnitTests.csproj -f net10.0 -c Debug --tl:off --warnaserror --no-restore` — passed with no warnings. - `dotnet build dotnet\src\Functions\Functions.UnitTests\Functions.UnitTests.csproj -f net10.0 -c Debug --tl:off --warnaserror --no-restore` — passed with no warnings. - `dotnet test dotnet\src\Plugins\Plugins.UnitTests\Plugins.UnitTests.csproj -f net10.0 -c Debug --no-restore -v Normal --logger trx` — passed: 583 passed, 15 environment-specific skips, 0 failed. - `dotnet test dotnet\src\Functions\Functions.UnitTests\Functions.UnitTests.csproj -f net10.0 -c Debug --no-restore --filter FullyQualifiedName~OpenApiHttpClientProviderTests -v Normal --logger trx` — passed: 11 passed, 0 failed. - Container-based `dotnet format --verify-no-changes` for the affected projects — passed. ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone :smile:

.Net: Bound element nesting depth in XML prompt parsing (#14504) ## Motivation and Context `XmlPromptParser` converts chat prompts such as `<message role="user">...</message>` into `PromptNode` trees that `ChatPromptParser` turns into a `ChatHistory`. Each `PromptNode` stores the serialized inner XML of its element, so the parser re-serializes and decodes the whole remaining subtree at every nesting level. Parse work therefore grows with nesting depth multiplied by prompt size, and the recursive node builder had no depth bound. Supported chat prompt structure is shallow: message elements with optional `text`, `image`, `audio`, and `binary` children, plus encoded or CDATA text. This change bounds element nesting so parsing cost stays proportional to prompt size. ## Description - Add `XmlPromptParser.MaxElementDepth` (internal, `64`, top-level prompt elements count as depth 1, matching the `System.Text.Json` default maximum depth). - After the prompt is loaded and before any `PromptNode` is built, a single non-recursive walk checks element depth. Prompts nested deeper than the limit return `false` from `TryParse`. - A rejected prompt takes the existing invalid-XML path: callers such as `GetChatMessageContentsAsync(string)` send the whole prompt as one user text message, exactly as they already do for malformed XML. - Parse work for accepted prompts is bounded by the depth limit times prompt size, and recursion in `GetPromptNode` is bounded. - No public API change. Prompts within the limit, including content items, CDATA, and encoded content, parse exactly as before. Tests: - `XmlPromptParserTests`: parses two prompts at exactly the maximum depth; rejects one level over and far over the limit; rejects when only a later top-level node exceeds the limit (covers sibling traversal after a max-depth subtree). - `ChatPromptParserTests`: a user message whose content exceeds the limit makes `ChatPromptParser.TryParse` return `false`. ## Validation All local runs use `-c Debug` on .NET SDK 10.0.401. - Build with `--warnaserror`: `SemanticKernel.Abstractions` (`net10.0`, `net8.0`, `netstandard2.0`), `SemanticKernel.UnitTests`, `Extensions.UnitTests`, `PromptTemplates.Liquid.UnitTests`, `Agents.UnitTests`, `IntegrationTests`: 0 warnings, 0 errors. - `dotnet format --verify-no-changes` in `mcr.microsoft.com/dotnet/sdk:10.0` for both changed projects: clean. - `SemanticKernel.UnitTests`: 1614/1614 pass, including the 5 new tests. The new over-limit tests fail without the parser change. - `Extensions.UnitTests` (Handlebars) 90/90, `PromptTemplates.Liquid.UnitTests` 16/16, `Agents.UnitTests` 504/504 executed tests pass, `IntegrationTests` CrossLanguage (offline, stubbed HTTP request shape) 37/37. - Normal chat prompts produce the same `ChatHistory` on `net10.0`, `net8.0`, and .NET Framework 4.8 (`netstandard2.0` asset), and the largest prompts still accepted parse in time proportional to their size. ## Contribution Checklist - [x] The code builds clean without any errors or warnings - [x] The PR follows the [SK Contribution Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [x] All unit tests pass, and I have added new tests where possible - [x] I didn't break anyone :smile: