docs: update imports from @rivetkit/actor to rivetkit

site/src/content/docs/actors/actions.mdx

@@ -15,7 +15,7 @@ For advanced use cases that require direct access to HTTP requests or WebSocket
 Actions are defined in the `actions` object when creating an actor:
 
 ```typescript
-import { actor } from "@rivetkit/actor";
+import { actor } from "rivetkit";
 
 const mathUtils = actor({
   state: {},
@@ -53,7 +53,7 @@ Learn more about [communicating with actors from the frontend](/docs/actors/comm
 <Tab title="Backend (registry.runServer)">
 
 ```typescript {{"title":"server.ts"}}
-import { setup } from "@rivetkit/actor";
+import { setup } from "rivetkit";
 
 const registry = setup({
   use: { counter }
@@ -101,7 +101,7 @@ The actor client includes type safety out of the box. When you use `createClient
 <CodeGroup>
 
 ```typescript {{"title":"registry.ts"}}
-import { setup } from "@rivetkit/actor";
+import { setup } from "rivetkit";
 
 // Create simple counter
 const counter = actor({
@@ -152,7 +152,7 @@ For example:
 <CodeGroup>
 
 ```typescript {{"title":"actor.ts"}}
-import { actor, UserError } from "@rivetkit/actor";
+import { actor, UserError } from "rivetkit";
 
 const user = actor({
   state: { users: [] },
@@ -200,7 +200,7 @@ If passing data to an actor from the frontend, use a library like [Zod](https://
 For example, to validate action parameters:
 
 ```typescript {{"title":"actor.ts"}}
-import { actor, UserError } from "@rivetkit/actor";
+import { actor, UserError } from "rivetkit";
 import { z } from "zod";
 
 // Define schema for action parameters
@@ -246,7 +246,7 @@ When writing complex logic for actions, you may want to extract parts of your im
 Rivet provides the `ActionContextOf` utility type for exactly this purpose:
 
 ```typescript
-import { actor, ActionContextOf } from "@rivetkit/actor";
+import { actor, ActionContextOf } from "rivetkit";
 
 const counter = actor({
   state: { count: 0 },

site/src/content/docs/actors/authentication.mdx

@@ -11,7 +11,7 @@ Rivet provides multiple authentication methods to secure your actors. Use `onAut
 The `onAuth` hook runs on the HTTP server before clients can access actors. This is the preferred method for most authentication scenarios.
 
 ```typescript
-import { actor, UserError } from "@rivetkit/actor";
+import { actor, UserError } from "rivetkit";
 
 const chatRoom = actor({
   onAuth: async (params: { authToken?: string }, { request, intents }) => {
@@ -156,7 +156,7 @@ const secureActor = actor({
 Use specific error types for different authentication failures:
 
 ```typescript
-import { UserError, Unauthorized, Forbidden } from "@rivetkit/actor/errors";
+import { UserError, Unauthorized, Forbidden } from "rivetkit/errors";
 
 const protectedActor = actor({
   onAuth: async (params: { authToken?: string }) => {
@@ -219,7 +219,7 @@ try {
 ### JWT Authentication
 
 ```typescript
-import { actor, UserError } from "@rivetkit/actor";
+import { actor, UserError } from "rivetkit";
 import jwt from "jsonwebtoken";
 
 const jwtActor = actor({

site/src/content/docs/actors/clients.mdx

@@ -47,7 +47,7 @@ There are several ways to create a client for communicating with actors:
 		For frontend applications or external services connecting to your Rivet backend:
 
 		```typescript {{"title":"client.ts"}}
-		import { createClient } from "@rivetkit/actor/client";
+		import { createClient } from "rivetkit/client";
 		import type { registry } from "./registry";  // IMPORTANT: Must use `type`
 
 		const client = createClient<typeof registry>("http://localhost:8080");
@@ -393,7 +393,7 @@ const result = await chat.sendMessage("Hello world!");
 Actors can validate authentication using the `onAuth` hook:
 
 ```typescript
-import { actor, UserError } from "@rivetkit/actor";
+import { actor, UserError } from "rivetkit";
 
 const protectedActor = actor({
   onAuth: async (opts) => {

site/src/content/docs/actors/communicating-between-actors.mdx

@@ -13,7 +13,7 @@ We recommend reading the [clients documentation](/docs/actors/clients) first. Th
 The server-side actor client allows actors to call other actors within the same registry. Access it via `c.client()` in your actor context:
 
 ```typescript
-import { actor } from "@rivetkit/actor";
+import { actor } from "rivetkit";
 
 const orderProcessor = actor({
   state: { orders: [] },
@@ -46,7 +46,7 @@ const orderProcessor = actor({
 Use a coordinator actor to manage complex workflows:
 
 ```typescript
-import { actor } from "@rivetkit/actor";
+import { actor } from "rivetkit";
 
 const workflowActor = actor({
   state: { workflows: [] },
@@ -79,7 +79,7 @@ const workflowActor = actor({
 Collect data from multiple actors:
 
 ```typescript
-import { actor } from "@rivetkit/actor";
+import { actor } from "rivetkit";
 
 const analyticsActor = actor({
   state: { reports: [] },
@@ -118,7 +118,7 @@ const analyticsActor = actor({
 Use connections to listen for events from other actors:
 
 ```typescript
-import { actor } from "@rivetkit/actor";
+import { actor } from "rivetkit";
 
 const auditLogActor = actor({
   state: { logs: [] },