Both shutdown chunks from retrieval include the deadline condition. Dropping one as redundant can mean losing cancellation guidance present only in that chunk. Passing both without changes leads to paying for the same paragraph twice.

Context assembly decides which retrieved text enters the request. We'll add this step to the .NET and Qdrant example from Payload Modeling and Metadata Filters , then review the request before calling the model.

A complete, standalone version of this example is available in the sample repository .

Preserve the deadline condition in model context

The current sample asks: “Should I drain all queued work during shutdown?” The published runbook yields these chunks:

Chunk Evidence

shutdown/p0 Stop accepting work; drain the queue while the deadline allows it

shutdown/p1 The same deadline condition; pass cancellation to asynchronous operations

capacity/p0 Use a bounded channel; handle writer completion

Each shutdown chunk includes the following paragraph:

Drain the remaining…