An Evidence-Aware Agent Framework Upgrade Tracker in .NET
A public NuGet evidence tracker compares three actual function-invocation contracts across two pinned packages while leaving general compatibility unknown.
THE READING ROOM
THE READING ROOM
A public NuGet evidence tracker compares three actual function-invocation contracts across two pinned packages while leaving general compatibility unknown.
One compiled C# assembly, two pinned runtimes, and nine allocation scenarios. Real IL, JIT listings and measurements show when an object disappears, when nullable boxing moves off the managed heap, and why a local delegate can still allocate.
Runtime async changes where suspension is represented. A real two-library .NET 11 lab shows smaller compiler artifacts and lower allocation on some paths, while a controlled suspension case resists a universal speedup claim.
A small local reference makes admission, retry, journal state and shutdown observable; a compiled Azure candidate preserves the distinction between mapping and deployment.
A versioned local deployment recipe records its prerequisites, owned resources, observed HTTP results and cleanup, making its verification date a claim about an actual run.
Controlled HTTP streaming tests show what happens when access or resource version changes after retrieval but before protected content is emitted.
Separate deployment, runtime and operator authority with actual local JWT checks, then inspect an explicitly undeployed Azure identity mapping.
A real Direct Line client meets a local HTTP fixture to separate replay, partial results, errors and cancellation from business completion.
Real TLS, trusted forwarded headers, PathBase and a missing artifact produce different deployment failures; a bounded Nginx/ASP.NET fixture separates them with actual HTTP evidence.
Six deliberately broken executor variants show whether independent effect assertions detect missing actor, scope, replay, expiry, digest and version controls.
A bounded evidence-driven controller uses real Microsoft AI function invocation with a scripted provider, while keeping progress and stop conditions in deterministic application code.
A bounded C# lab separates the lifetime of an operation, its waiting caller and its timer, with deterministic correctness tests and measured cleanup behavior.