feat(vercel_ai): add VAI-017 tool stdout diagnostics rule - #114
feat(vercel_ai): add VAI-017 tool stdout diagnostics rule#114joeymussalli wants to merge 1 commit into
Conversation
Port the OAI-010 observability pattern to Vercel AI execute() handlers via has_print_call (prints_stdout fact for console.log and friends). Co-authored-by: Cursor <cursoragent@cursor.com>
|
Thanks @joeymussalli. Schema-wise this is correct: One change before this ships. The explanation is ported from OAI-010, and both consequences it names are a stretch for this SDK. A Vercel AI tool usually runs in a Next.js route on a platform that captures stdout as its log stream, so the "silently disappears" claim mostly does not hold there, and One note for me rather than for you: on a binary older than trustabl/trustabl#187 this rule loads fine and silently never fires, so I need to decide whether that warrants a Happy to take this once the explanation is reframed and the fixture is updated to match. |
Summary
vercel_ai/observability.yamlwith VAI-017: Vercel AIexecute()writes diagnostics to stdout (has_print_call: true).console.error, etc.) do not fire once the engineprints_stdoutfact is present.Depends on
Test plan