GnOuGo.Flow.Integrations 0.20.0

GnOuGo.Flow.Integrations

GnOuGo.Flow.Integrations supplies the concrete AI provider and MCP transport implementations used with the provider-neutral GnOuGo.Flow.Core contracts.

Build and test

dotnet build src/GnOuGo.Flow.Integrations/GnOuGo.Flow.Integrations.csproj
dotnet test tests/GnOuGo.Flow.Integrations.Tests/GnOuGo.Flow.Integrations.Tests.csproj

Usage

Create a RoutingLLMClientAdapter from a GnOuGo.AI.Core.RoutingLLMClient and a ConfiguredMcpClientFactory from the host-owned MCP settings. Inject them through WorkflowEngine.LLMClient and WorkflowEngine.McpClientFactory. For cost telemetry, also assign a ModelMetadataUsageCostEstimator to WorkflowEngine.ModelUsageCostEstimator. Pass the effective LLMOptions snapshot to the estimator when host-configured model pricing overrides must participate in telemetry or an enforced LLMUsageBudgetScope.

Currency-aware limits use ModelMetadataUsageCostEstimator.EstimateCostWithCurrency and EcbExchangeRateProvider. The exchange provider first applies fresh static operator quotes, including their inverse, then fetches the official ECB daily reference-rate XML over HTTPS and derives cross-rates through EUR. Configure its HttpClient timeout in the host (Agent.Server uses ten seconds). Quotes older than the configured maximum age are rejected; the default is seven days. Requests contain only the configured ECB URL—never provider, model, prompt, tenant, or credential data. Network, parsing, stale-rate, and unsupported-currency failures return no quote so the Flow.Core budget fails closed.

The integration package owns provider and transport mappings. Flow.Core never references this package or another GnOuGo component.

MCP tool results retain structured JSON when supplied. A single text block keeps its existing JSON-or-string normalization; other responses preserve complete protocol content blocks, including embedded text/binary resources, media, links and metadata. Resource contents are data, not permission to execute instructions.

MCP discovery maps the standard protocol ReturnJsonSchema to Flow.Core's compatible McpToolInfo.OutputSchema and immediately resolves its provider-neutral output-contract provenance. Valid protocol-declared schemas are authoritative; invalid schemas carry validation errors and example/description-derived shapes remain advisory hints. Servers should therefore publish ReturnJsonSchema for every structured result that downstream workflows need to dereference.

RoutingLLMClientAdapter maps AI.Core's redacted LLMProviderException and every LLMProviderFailureKind to Flow.Core's independent LLMClientException and LLMClientFailureKind. It preserves retryability, HTTP status, and safe provider code without copying raw provider response bodies.

Host adapters can reuse RoutingLLMClientAdapter.MapRequest and MapResponse to preserve output ceilings, disabled transport retries, completion status, tool calls, and usage consistently.

Durable planning runtime

Inject HybridWorkflowPlanner and Planning.WorkflowPlanningRuntimeFactory.CreateWorkspace() into the engine. Planning remains separately publishable and depends only on Core.

The factory stores format-10 sessions, reservations, receipts and cumulative budgets through public encrypted KeyVault record APIs in flow-planning-*-v10 collections. Exclusive tenant/session leases live under .GnOuGo/data/flow-planning-v10/leases. Old formats are rejected. Resume the same run ID and request; completed calls replay without a new charge and uncertain dispatches stop without redispatch.

ReadApprovedYamlAsync verifies tenant ownership, stored approval, exact content and current capability contracts before workflow.execute receives YAML. Integrations propagate provider-neutral effect metadata; unknown MCP effects require conservative confirmation. See architecture.

Typed business choices use the encrypted format-10 planning journal and exclusive owner lease. An injected IPlanningInteraction selects recommended alternatives separately from runtime human.input. Old approvals are rejected; regenerate and approve the workflow. Run dotnet test tests/GnOuGo.Flow.Integrations.Tests -m:1 -warnaserror to verify receipt replay, tenant ownership and approval boundaries.