Provider middleware 

Implement Netresearch\NrLlm\Provider\Middleware\ProviderMiddlewareInterface for a provider-call concern. Its method is handle(ProviderCallContext $context, callable $next): mixed. The current configuration is on $context->configuration; when replacing it, derive a new context with withConfiguration(). Pass that context to $next.

<?php

declare(strict_types=1);

namespace MyVendor\MyExtension\Provider;

use Netresearch\NrLlm\Provider\Middleware\ProviderCallContext;
use Netresearch\NrLlm\Provider\Middleware\ProviderMiddlewareInterface;

final class ObserveCall implements ProviderMiddlewareInterface
{
    public static function getDefaultPriority(): int
    {
        return 80;
    }

    public function handle(ProviderCallContext $context, callable $next): mixed
    {
        return $next($context);
    }
}

The interface supplies the nr_llm.provider_middleware autoconfiguration tag. Priority comes from the static getDefaultPriority() convention; omitting it means priority 0. Do not rely on a duplicate tag's attribute priority. Higher priority enters first and exits last.

This order explains short circuits: a cache hit does not become another paid provider request. A retry or fallback changes which inner layers execute; observe the actual context rather than inferring the serving model from a stored fixed-model relation. Streaming has its own dispatcher lifecycle; see Streaming support. The historical design is ADR-026: Provider Middleware Pipeline and its context change is ADR-096: The pipeline configuration lives on the call context.