Artifact page-data reads now reject unknown schemas up front and list valid options instead.
What's wrong with this entry?
The artifact read_page_data action validates the requested schema against what the session actually offers and fails with a dedicated error code instead of attempting a lookup.
- The check runs before any lookup and throws its own error code on mismatch.
- The tool description is generated with the concrete list of available schema names inlined, so the model sees valid options up front.
read_page_data: the requested interaction schema is not available in this session.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Artifact tool: replies validated, and comment text stripped from stored transcript
Both mention read page data