The artifact tool now accepts a cursor value, groundwork for fetching comments page by page.
A cursor argument is parsed but nothing in this build sends or consumes it.
What's wrong with this entry?
The artifact tool's argument extractor now reads an optional string cursor in addition to thread_id and text.
cursoris returned as part of the parsed argument shape- no schema entry or request consuming it was found in this build, so it appears to be plumbing ahead of paginated comment fetching
"cursor" in e
Strings lifted out of the shipped bundle, so the claim above can be checked against them.