chore(rivetkit): make execute generic

[NathanFlurry]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[railway-app]

🚅 Deployed to the rivet-pr-4231 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
ladle	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 10:40 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 7:23 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Feb 19, 2026 at 7:23 pm
website	😴 Sleeping (View Logs)	Web	Feb 19, 2026 at 8:24 am
mcp-hub	✅ Success (View Logs)	Web	Feb 19, 2026 at 8:13 am

[NathanFlurry]

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

• fix(rivetkit): fix run workflow teardown #4239
• feat(rivetkit): canInvoke #4237
• chore(rivetkit): make execute generic #4231 👈 (View in Graphite)
• chore: update workflow queues api #4230
• chore: simplify queue api #4229
• refactor(rivetkit): add typed event and queue schemas for actors #4209 : 1 other dependent PR (#4224 )
• feat: configure rivetkit storage path #4233
• chore(rivetkit): migrate file system driver to sqlite #4206
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• custom-serverless-vercel
• example-elysia
• example-elysia-vercel
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-hono-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• example-sqlite-raw-vercel
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc
• example-trpc-vercel

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@4231

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@4231

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@4231

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@4231

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@4231

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@4231

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4231

@rivetkit/traces

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/traces@4231

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4231

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@4231

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@4231

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@4231

commit: 886fc35

[claude]

PR Review: chore(rivetkit): make execute generic

This PR makes the c.db.execute method generic so callers can specify the row type (e.g., execute<{ id: number }>(...)) instead of using post-hoc as type assertions. The change is clean and idiomatic TypeScript.

---

Positive Changes

Generic API over type assertions: Replacing (await c.db.execute(...)) as Array<{ id: number }> with await c.db.execute<{ id: number }>(...) is strictly better style. Type assertions bypass the type checker at the call site; generic inference keeps the type parameter explicit and correctly typed.

Drizzle execute implementation fix: The old drizzle path called callback(query, args, "all"), which returned positional row arrays (unknown[][]) based on how createProxyCallback is written (the comment even says "drizzle's mapResultRow accesses rows by column index (positional arrays)"). But the fixture code accessed rows as objects (results[0].id, results[0].value), so this was likely broken at runtime. The new implementation explicitly maps rows to objects via column names, consistent with src/db/mod.ts. This looks like a real bug fix bundled into this PR.

Workflow context variable fix (workflow.ts): The fix from actorLoopCtx to loopCtx inside the "access-step" step handler is correct. The step callback should operate on its own step context, not the outer actor loop context. The added loopCtx.client<typeof registry>() typing is also an improvement.

Type test: The actor-types.test.ts addition that uses expectTypeOf to validate execute<{ foo: string }>() returns Array<{ foo: string }> is a good compile-time guard.

---

Issues and Observations

1. The drizzle behavior change deserves a callout

The switch from callback(query, args, "all") to waDb.query / waDb.exec directly is a meaningful implementation change that the PR description does not mention. If this fixes a runtime bug (returning positional arrays instead of objects), that should be called out explicitly in the PR description. It also bypasses the createProxyCallback layer, so any future changes to that proxy will not affect the raw execute path.

2. SQL injection in test fixtures (pre-existing)

The fixtures extensively use interpolated string SQL:

`INSERT INTO test_data (value, payload, created_at) VALUES ('${value}', ''  , ${Date.now()})`

This is pre-existing and these are test-only fixtures, so the risk is low. But since the execute API already supports parameterized queries (...args path), updating fixtures to use placeholders would make them better examples of how the API should be used in production.

3. Inconsistency in null-safety between files (pre-existing)

In actor-db-raw.ts, rawSelectCount uses results[0].count without optional chaining, while actor-db-drizzle.ts uses results[0]?.count ?? 0. COUNT(*) always returns exactly one row so this will not crash, but the divergence between the two files is a minor inconsistency worth aligning.

4. Type safety note

Both the old as Array<{ id: number }> and the new execute<{ id: number }>() are compile-time-only assertions with no runtime validation. This is expected TypeScript behavior and the new form is strictly more idiomatic, but worth understanding: the generic parameter does not add any runtime type guarantee over what was there before.

---

Summary

The primary change (making execute generic) is correct and improves the API. The drizzle implementation change and the workflow.ts context fix are meaningful runtime fixes that should be mentioned in the PR description. No blocking issues.

[graphite-app]

Merge activity

• Feb 19, 10:44 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 19, 10:45 PM UTC: CI is running for this pull request on a draft pull request (#4238) due to your merge queue CI optimization settings.
• Feb 19, 10:45 PM UTC: Merged by the Graphite merge queue via draft PR: #4238.