docs(integrations): sync from rivet-dev/rivet

vendor/integrations/docs/content/docs/flue.mdx

@@ -48,7 +48,7 @@ npx flue init --target node
 <Step title="Install the integrations">
 
 ```sh
-npm add @rivet-dev/flue @rivet-dev/agentos @rivet-dev/agentos-flue rivetkit@next
+npm add @rivet-dev/flue @rivet-dev/agentos @rivet-dev/agentos-flue rivetkit
 ```
 
 - `@rivet-dev/labs-flue-*`: Rivet-maintained preview builds of Flue's proposed extension APIs.

vendor/integrations/docs/content/docs/turso.mdx

@@ -56,7 +56,16 @@ npm install rivetkit @libsql/client @tursodatabase/api
 
 Create `.env` with your organization slug and token:
 
-<CodeSnippet file="examples/turso/.env.example" title=".env" />
+```sh title=".env"
+# Your Turso organization slug from `turso org list`.
+TURSO_ORG=
+
+# Platform API token from `turso auth api-tokens mint rivet-todos`.
+TURSO_PLATFORM_TOKEN=
+
+# Group to create each actor's database in. Defaults to "default".
+# TURSO_GROUP=default
+```
 
 </Step>
 
@@ -118,12 +127,6 @@ The Platform API token can create and delete every database in its organization,
 
 `createVars` must finish within `createVarsTimeout`, which defaults to 5 seconds. Its first query opens the connection to Turso, so a node far from the database's region spends part of that budget on the round trip. Raise `options.createVarsTimeout` if starts time out. See [Options](/actors/docs/lifecycle#options).
 
-## Testing
-
-The test creates real Turso databases, so it reads the same environment variables and is skipped without them. It checks that each list gets its own database and that destroying a list deletes it:
-
-<CodeSnippet file="examples/turso/tests/turso.test.ts" title="tests/turso.test.ts" />
-
 See the [Turso Platform API](https://docs.turso.tech/api-reference/introduction) and [TypeScript reference](https://docs.turso.tech/sdk/ts/reference) for the full APIs.
 
 ## Local disk

vendor/integrations/docs/content/docs/vercel-eve.mdx

@@ -38,7 +38,7 @@ cd my-agent
 <Step title="Install the integrations">
 
 ```sh
-npm add @rivet-dev/agentos @rivet-dev/agentos-eve @rivet-dev/workflow-world@next
+npm add @rivet-dev/agentos @rivet-dev/agentos-eve @rivet-dev/workflow-world
 ```
 
 - `@rivet-dev/agentos`: Provides the agentOS VM.

vendor/integrations/docs/content/docs/workflow-sdk.mdx

@@ -29,7 +29,7 @@ Start, and Vite.
 <Step title="Install the World">
 
 ```sh
-npm install workflow @rivet-dev/workflow-world@next
+npm install workflow @rivet-dev/workflow-world
 ```
 
 </Step>
@@ -141,7 +141,13 @@ npm test
 
 Select the World and point it at your own HTTP server:
 
-<CodeSnippet file="examples/workflow-sdk/.env.example" title=".env" />
+```sh title=".env"
+WORKFLOW_TARGET_WORLD=@rivet-dev/workflow-world
+WORKFLOW_RUNTIME_URL=http://127.0.0.1:3000
+
+# The Rivet connection uses the standard RivetKit environment variables. Local
+# development needs none of them.
+```
 
 | Variable | Required | Purpose |
 | --- | --- | --- |
@@ -169,7 +175,7 @@ rejects requests without it.
 
 ## Deploying
 
-Deploy the app as a Rivet node like any other. See [Deploy nodes](/docs/deploy/self-host/nodes/).
+Deploy the app as a Rivet node like any other. See [Deploy nodes](/docs/deploy/self-host/workers/).
 Two constraints come from this World specifically:
 
 - **The process must be long-lived.** The first World operation opens a
@@ -198,9 +204,41 @@ SDK.
 
 ## Testing
 
-<CodeSnippet file="examples/workflow-sdk/vitest.integration.config.ts" title="vitest.integration.config.ts" />
+```ts title="vitest.integration.config.ts"
+import { workflow } from "@workflow/vitest";
+import { defineConfig } from "vitest/config";
+
+export default defineConfig({
+	plugins: [workflow()],
+	test: {
+		include: ["workflows/**/*.integration.test.ts"],
+		setupFiles: ["./vitest.setup.ts"],
+		testTimeout: 60_000,
+	},
+});
+```
+
+```ts title="workflows/order.integration.test.ts"
+import { waitForSleep } from "@workflow/vitest";
+import { expect, test } from "vitest";
+import { getRun, start } from "workflow/api";
 
-<CodeSnippet file="examples/workflow-sdk/workflows/order.integration.test.ts" title="workflows/order.integration.test.ts" />
+import { processOrder } from "./order.ts";
+
+test("runs the workflow end to end", async () => {
+	const run = await start(processOrder, ["42"]);
+	const sleepId = await waitForSleep(run);
+
+	await getRun(run.runId).wakeUp({ correlationIds: [sleepId] });
+
+	await expect(run.returnValue).resolves.toEqual({
+		id: "42",
+		reservationId: "reservation-42",
+		status: "charged",
+	});
+	expect(await run.status).toBe("completed");
+});
+```
 
 `waitForSleep` observes the durable sleep, `wakeUp` resumes that exact
 correlation, and the assertions wait for the final persisted result.

vendor/integrations/examples/docs/actors-quickstart-react/Counter.tsx → vendor/integrations/examples/docs/actors-quickstart-react/frontend/Counter.tsx

@@ -1,16 +1,16 @@
 import { createRivetKit } from "@rivetkit/react";
 import { useState } from "react";
-import type { registry } from "./index";
+import type { registry } from "../backend/index";
 
 const { useActor } = createRivetKit<typeof registry>("http://localhost:6420");
 
-function Counter() {
+export function Counter() {
 	const [count, setCount] = useState(0);
 
 	// Get or create a counter actor for the key "my-counter"
 	const counter = useActor({
 		name: "counter",
-		key: ["my-counter"]
+		key: ["my-counter"],
 	});
 
 	// Listen to realtime events

vendor/integrations/examples/docs/actors-quickstart-react/frontend/main.tsx

@@ -0,0 +1,9 @@
+import { StrictMode } from "react";
+import { createRoot } from "react-dom/client";
+import { Counter } from "./Counter";
+
+createRoot(document.getElementById("root")!).render(
+	<StrictMode>
+		<Counter />
+	</StrictMode>,
+);