I work on Dashform, which builds forms for people and AI agents: https://getaiform.com
One integration test I would put beside the usual “can the agent fill the form?” demo is what happens when the form changes after the agent has read it. This is a proposed test plan, not a claim that Dashform currently enforces every safeguard below.
Use a duplicate form and fictional answers, not a live customer intake:
• Let the agent read version A of a project enquiry form, with a question such as “Which month do you want to start?”
• Before it submits, edit the test form. Change that question to “What is the latest acceptable delivery month?”, or add a new required field. The old answer may still look like a valid month while answering a different question.
• Resume the agent and inspect what it does. Does it notice that the question changed? Does it ask for the new information, or silently reuse its earlier answer?
• Compare the final answer preview with the saved response. Include the question wording, not just field labels or values, so a reviewer can tell what was actually answered.
My desired behavior would be to re-read a changed form and get confirmation of the revised answers before submitting. A field identifier alone would not establish that its meaning stayed the same. If the integration has no version check, make that limitation visible and test the race explicitly rather than assuming a fresh-looking preview solves it.
This is also why I would keep “the assistant was told to ask for confirmation” separate from “the submission endpoint enforces a confirmation boundary.” They are different properties, and a successful demo does not establish the second.
For people building agent-facing intake: would you reject any submission from an old form version, or only one where the meaning or required fields changed? How would you let the guest recover without discarding their useful answers?