.NET: Published packages are still built from `microsoft/agent-framework`, so fixes merged here don't reach NuGet

Summary

Fixes merged in this repository since the migration (#12) are not reaching the published
Microsoft.Agents.AI.DurableTask packages. The newest package on NuGet still carries the pre-fix code, and
its own metadata says why: it is built from the old repository.

Evidence

#15 ("Fix DurableTask CustomStatus 16 KB overflow on multi-executor workflows") merged to this repo's
main on 2026-07-15 as 3d801fe0. It adds DurableWorkflowLiveStatus.EventsStartIndex and publishes a
bounded trailing window instead of the full accumulated event log.

The newest published package is Microsoft.Agents.AI.DurableTask 1.16.0-preview.260730.1, built on
2026-07-30 — two weeks after that merge. Decompiling it (and 1.15.0-preview.260722.1) shows no
EventsStartIndex, no windowing, and no cost accounting: PublishEventsToLiveStatus assigns the full
AccumulatedEvents to LiveStatus.Events and calls SetCustomStatus. That is exactly the pre-#15 shape.

The package's own .nuspec points at the old repository:

<repository type="git" url="https://github.com/microsoft/agent-framework" />

So the preview packages are produced from microsoft/agent-framework, not from this repository's main.

Impact

Every NuGet consumer is still on the unbounded custom-status write. We hit it in production on Durable Task
Scheduler:

Orchestration response failed validation: Custom status length exceeds the limit of 1048576 UTF8-encoded bytes

The secondary effect is worse than the primary one: reading this repository's source is currently not a
reliable way to reason about installed behaviour. We initially diagnosed an unfixed bug, then found the fix
on main, then found it absent from the package — three passes to establish what our own dependency does.

Ask

1. Confirm which repository and branch the preview packages are built from today.
2. Ship a preview package built from this repository's main (or cherry-pick #15 into whatever branch does
   feed the release), so EventsStartIndex reaches consumers.
3. If the migration is still in progress, say so in the README — "packages are still built from
   microsoft/agent-framework; code here is ahead of the latest release" would have saved us the round trip,
   and would tell anyone else reading this repo how far to trust it.

Related

• #15 — the fix that has not shipped.
• #12 — the migration that appears to have split source from release.
• #69 — DurableWorkflowResult.Events retaining the full event stream: that one is about the accumulation
  that survives #15 on main, and is independent of this release-pipeline problem.

Start by confirming the repository and branch used to build the preview packages, then inspect the published package’s .nuspec repository metadata against this repository and its main branch. Review #12 and #15 for the migration and missing fix. Done means a preview package includes the #15 behavior, or the README clearly documents that releases still come from microsoft/agent-framework.