just verify-conversation <email> strict asserts a model actually replied, and refuses to run against dataPlane=spritzer because the emulator satisfies every plumbing assertion with no model in the loop. Only the refusal has ever been observed — nothing in this repo has run strict green against the real Sprites API, so its passing path is written down and untried.
Blocked on a real SPRITES_TOKEN, which is a platform credential someone has to provide — it goes in the platform Secret and must never reach tenant-visible config or logs. Done means one green strict run (any target, laptop is fine with dataPlane=sprites), the status page's "A real SPRITES_TOKEN — never used" row updated, and spritzer#18's reattach behaviour re-checked against the real API while we are there.
just verify-conversation <email> strictasserts a model actually replied, and refuses to run against dataPlane=spritzer because the emulator satisfies every plumbing assertion with no model in the loop. Only the refusal has ever been observed — nothing in this repo has run strict green against the real Sprites API, so its passing path is written down and untried.Blocked on a real SPRITES_TOKEN, which is a platform credential someone has to provide — it goes in the platform Secret and must never reach tenant-visible config or logs. Done means one green strict run (any target, laptop is fine with dataPlane=sprites), the status page's "A real SPRITES_TOKEN — never used" row updated, and spritzer#18's reattach behaviour re-checked against the real API while we are there.