use inline: true in workflows

[ianmacartney]

For lightweight operations, run queries / mutations inline in Workflows, to avoid the workpool overhead.

This enables using Workflow + Agent more idiomatically, creating threads & saving messages before kicking out to an action to do generation, which likely saves ~1s or more per workflow

Risk:

1. adds a peer dependency on Workflow
2. If they had workflowId on ctx incidentally and had some custom ctx.run* functions that didn't expect an extra param (unlikely)
3. Maybe they expected it to run in a separate transaction and that was impotant for some reason?

[ianmacartney]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• use inline: true in workflows #279 👈 (View in Graphite)
• use ActionCtx versions of runQuery/runMutation for compatibility #277
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@convex-dev/agent@279

commit: 8f3f66b

[robelest]

small consistency q: should the other lightweight helpers that accept
MutationCtx use the new wrappers too?

Right now createThread / saveMessages go inline in workflows, but
listMessages, searchThreadTitles, and delete helpers still call ctx.run*
directly. Maybe intentional, but it feels a little mixed.

[ianmacartney]

search might require vector search, which isn't available in workflows. listing messages I guess is harmless - it's not reading more data than it's returning, so may as well inline it