Check whether the outcome improved
Define complete versus partial
Write expected state for a full response, an empty collection, an incomplete body, a missing continuation marker, and a documented partial result. Name count, cursor, required field, and parser evidence that must agree before replacement is allowed.
Run transport and parser cases
Feed fixtures through the real client and compare bytes or size, decoder result, completeness flag, error state, and storage action. Confirm a fragment is held or marked incomplete. Check nested objects and large collections, not only one short payload.
Check recovery and regression
Re-read an incomplete result through the approved path, then repeat a normal response and a nearby endpoint. Verify complete known-good data is not overwritten during failure. Retain safe correlation and expected state for each case.
What to carry forward
Accept when full responses remain complete, fragments cannot silently replace data, partial contracts are explicit, and recovery is bounded. Keep coverage open for unobserved intermediary limits. Record fixture shapes, client revision, response metadata, and storage outcomes.
Technical background: RFC Editor reference.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow