eve 0.7.0 → 0.7.2

package/dist/docs/public/getting-started.mdx

@@ -5,14 +5,7 @@ description: "Install Eve, scaffold your first agent, give it a tool, and run it
 
 Eve is a filesystem-first framework for durable agents: you write capabilities under `agent/`, and Eve runs the model loop, persists every session, and serves the agent over HTTP and platform channels. This guide gets a small app running locally and walks the current request loop end to end: build, run, message, stream, and follow up.
 
-## Prerequisites
-
-- Node `24.x`
-- npm (bundled with Node)
-
-You also need a model credential. Set the provider or gateway key your model string requires (gateway ids like `anthropic/claude-opus-4.8` route through the Vercel AI Gateway), or link a Vercel project that supplies one.
-
-## Create Your Agent
+## Quick start
 
 Run `eve init` with `npx` before Eve is installed locally:
 
@@ -20,30 +13,30 @@ Run `eve init` with `npx` before Eve is installed locally:
 npx eve@latest init my-agent
 ```
 
-The command creates an npm-managed child directory, uses Eve's default model,
-installs dependencies, initializes Git, and starts the development server. Pass
-`--channel-web-nextjs` to add the Web Chat application. Stop the server before
-editing the generated agent. The command does not create a Vercel project or
-deploy.
+The command creates an npm-managed child directory, uses Eve's default model, installs dependencies, initializes Git, and starts the development server — the interactive [terminal UI](./guides/dev-tui) opens; type a message and watch the model loop run. Pass `--channel-web-nextjs` to add the Web Chat application; every app ships the built-in HTTP channel (`agent/channels/eve.ts`) regardless. Stop the server before editing the generated agent. The command does not create a Vercel project or deploy.
+
+## Prerequisites
+
+- Node `24.x`
+- npm (bundled with Node)
+
+You also need a model credential. Set the provider or gateway key your model string requires (gateway ids like `anthropic/claude-opus-4.8` route through the Vercel AI Gateway), or link a Vercel project that supplies one.
+
+## Manual installation
 
-The target can also be an existing project directory (`eve init .`): the
-project must have a `package.json`, the `agent/` files must not exist yet, and
-the missing `eve`, `ai`, and `zod` dependencies are added without touching
-anything else the project owns. Either way the final handoff runs the `eve dev`
-binary through the project's package manager, never the project's own `dev`
-script.
+The quick start uses `eve init` for a guided scaffold. The target can also be an existing project directory (`eve init .`): the project must have a `package.json`, the `agent/` files must not exist yet, and the missing `eve`, `ai`, and `zod` dependencies are added without touching anything else the project owns. Either way the final handoff runs the `eve dev` binary through the project's package manager, never the project's own `dev` script.
 
-To add only the dependency to an existing app instead:
+To wire Eve into an existing app yourself instead, add only the dependency and author the two files the runtime needs:
 
 ```bash
 npm install eve@latest
 ```
 
-## What's In Your Project
+### Project files
 
-The scaffold writes two files; you add tools as you need them.
+A minimal agent is two files; you add tools as you need them.
 
-`agent/instructions.md` (generated) is the always-on system prompt:
+`agent/instructions.md` is the always-on system prompt:
 
 ```md
 You are a concise assistant. Use tools when they are available.
@@ -59,9 +52,9 @@ export default defineAgent({
 });
 ```
 
-Even at this size the agent can already do real work. The default harness gives it file, shell, web, and delegation tools out of the box. See [Default harness](./advanced/default-harness) for the full set and how to override or disable any of them.
+Even at this size the agent can already do real work. The default harness gives it file, shell, web, and delegation tools out of the box. See [Default harness](./concepts/default-harness) for the full set and how to override or disable any of them.
 
-### Add Your First Tool
+### Add your first tool
 
 Whatever you name the file becomes the tool name the model sees. Create `agent/tools/get_weather.ts`:
 
@@ -82,7 +75,7 @@ export default defineTool({
 
 Tools run in your app runtime with full `process.env`, not inside the [sandbox](./sandbox). More in [Tools](./tools).
 
-## Run The App
+## Run the app
 
 From the app root:
 
@@ -95,13 +88,13 @@ Useful commands:
 - `eve info`: show the active routes and compiled artifacts
 - `eve build`: compile the agent into `.eve/` and build the host output
 - `eve start`: serve the built output
-- `eve dev`: start the local runtime and open the interactive [terminal UI](./advanced/dev-tui)
+- `eve dev`: start the local runtime and open the interactive [terminal UI](./guides/dev-tui)
 
 In the dev TUI, type a message and watch it happen in order: the `get_weather` call, its result, then the reply.
 
-The same CLI can point at a deployment. `eve dev https://your-app.vercel.app` drives a deployed app, which is handy for preview and production smoke tests. See [Deployment](./advanced/deployment).
+The same CLI can point at a deployment. `eve dev https://your-app.vercel.app` drives a deployed app, which is handy for preview and production smoke tests. See [Deployment](./guides/deployment).
 
-## Send A Message
+## Send a message
 
 Every Eve app exposes the same stable HTTP API. Start a durable session:
 
@@ -116,7 +109,7 @@ The response comes back with two things you'll reuse:
 - a `continuationToken` in the JSON body, to resume this conversation
 - an `x-eve-session-id` header that identifies the run to stream
 
-## Stream The Session
+## Stream the session
 
 Attach to the session stream:
 
@@ -148,7 +141,7 @@ The stream is NDJSON. Expect lifecycle events such as:
 
 `message.completed.data.finishReason` tells you whether assistant text is interim tool-call narration or a terminal reply, and `step.completed.data.usage` carries token usage. When a parent delegates to a subagent, `subagent.called.data.childSessionId` gives you the child session id, so you can subscribe to that child stream and watch the delegated work.
 
-## Send A Follow-Up Message
+## Send a follow-up message
 
 When the session is waiting for the next user message, post a follow-up with the token:
 
@@ -158,7 +151,7 @@ curl -X POST http://127.0.0.1:3000/eve/v1/session/<sessionId> \
   -d '{"continuationToken":"<token>","message":"Now do Queens."}'
 ```
 
-See [Sessions, runs & streaming](./advanced/sessions-runs-and-streaming) for the full contract.
+See [Sessions, runs & streaming](./concepts/sessions-runs-and-streaming) for the full contract.
 
 ## Setting up with a coding agent
 
@@ -182,7 +175,7 @@ Once `eve` is a dependency, the full docs are bundled in the package, so the age
 
 - [Instructions](./instructions) and [Tools](./tools): the core building blocks
 - [Channels](./channels/overview): reach the agent from Slack, Discord, or a web UI
-- [Frontend](./frontend/overview): browser chat with `useEveAgent`
-- [TypeScript Client](./client/overview): call the agent from scripts or server-side code
-- [Sessions, runs & streaming](./advanced/sessions-runs-and-streaming): the durable session model
+- [Frontend](./guides/frontend/overview): browser chat with `useEveAgent`
+- [TypeScript SDK](./guides/client/overview): call the agent from scripts or server-side code
+- [Sessions, runs & streaming](./concepts/sessions-runs-and-streaming): the durable session model
 - [Build an agent](./tutorial/first-agent): the full end-to-end walkthrough

package/dist/docs/public/{advanced → guides}/auth-and-route-protection.md

@@ -1,5 +1,5 @@
 ---
-title: "Auth & route protection"
+title: "Auth & Route Protection"
 description: "Secure your agent's HTTP routes with an ordered auth walk, verifier helpers, and connection OAuth via Vercel Connect."
 ---
 
@@ -267,6 +267,6 @@ By default the sign-in affordance title-cases the tool's path-derived name — a
 
 ## What to read next
 
-- [Security model](./security-model): trust boundaries and the pre-production checklist
+- [Security model](../concepts/security-model): trust boundaries and the pre-production checklist
 - [Connections](../connections): connection auth shapes (`connect()` vs static token)
 - [Deployment](./deployment): where route-auth secrets live in production

package/dist/docs/public/{client → guides/client}/continuations.mdx

@@ -122,5 +122,5 @@ for await (const event of session.stream({ startIndex: 0 })) {
 ## What to read next
 
 - [Streaming](./streaming): stream events and reconnect by index
-- [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming): the raw HTTP contract
-- [Eve channel](../channels/eve): where continuation tokens come from
+- [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming): the raw HTTP contract
+- [Eve channel](../../channels/eve): where continuation tokens come from

package/dist/docs/public/{client → guides/client}/messages.mdx

@@ -149,4 +149,4 @@ Don't do both on the same response. Once the stream is consumed, the `ClientSess
 
 - [Continuations](./continuations): how the session cursor advances
 - [Streaming](./streaming): handle events live instead of using `result()`
-- [Tools](../tools): configure approvals and question prompts
+- [Tools](../../tools): configure approvals and question prompts

package/dist/docs/public/{client → guides/client}/meta.json

@@ -1,4 +1,4 @@
 {
-  "title": "TypeScript Client",
+  "title": "TypeScript SDK",
   "pages": ["overview", "messages", "continuations", "streaming", "output-schema"]
 }

package/dist/docs/public/{client → guides/client}/output-schema.mdx

@@ -126,10 +126,10 @@ const followUp = await followUpResponse.result();
 console.log(followUp.data); // undefined unless this turn also requested a schema
 ```
 
-For task-mode output that belongs to the agent or subagent definition itself, see [`agent.ts`](../agent-config#outputschema) and [Subagents](../subagents).
+For task-mode output that belongs to the agent or subagent definition itself, see [`agent.ts`](../../agent-config#outputschema) and [Subagents](../../subagents).
 
 ## What to read next
 
 - [Messages](./messages): send turns with `send()`
 - [Streaming](./streaming): handle `result.completed` live
-- [`agent.ts`](../agent-config#outputschema): configured task-mode output
+- [`agent.ts`](../../agent-config#outputschema): configured task-mode output

package/dist/docs/public/{client → guides/client}/overview.mdx

@@ -1,11 +1,11 @@
 ---
-title: "TypeScript Client"
+title: "Overview"
 description: "Call an Eve agent from TypeScript with Client, sessions, auth, and health checks."
 ---
 
 The `eve/client` entrypoint is the typed client for Eve's default HTTP API. Use it from scripts, server-to-server integrations, tests, evals, backend jobs, or custom UIs that want the session protocol without hand-writing the POST and NDJSON stream loop.
 
-For browser chat UIs, start with [`useEveAgent`](../frontend/overview). For wire-level details, read [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming). The client sits between those two: lower level than the frontend hooks, higher level than raw HTTP.
+For browser chat UIs, start with [`useEveAgent`](../frontend/overview). For wire-level details, read [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming). The client sits between those two: lower level than the frontend hooks, higher level than raw HTTP.
 
 ## Create a client
 
@@ -34,7 +34,7 @@ Non-2xx responses throw `ClientError`, which carries the HTTP `status` and respo
 
 ## Authentication
 
-Pass `auth` when the [Eve channel](../channels/eve) route requires credentials:
+Pass `auth` when the [Eve channel](../../channels/eve) route requires credentials:
 
 ```ts
 const client = new Client({
@@ -111,6 +111,6 @@ The next pages cover the session lifecycle:
 
 ## What to read next
 
-- [Eve channel](../channels/eve): the HTTP API this client calls
-- [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming): the raw HTTP contract
+- [Eve channel](../../channels/eve): the HTTP API this client calls
+- [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming): the raw HTTP contract
 - [Frontend](../frontend/overview): browser UI with `useEveAgent`

package/dist/docs/public/{client → guides/client}/streaming.mdx

@@ -74,7 +74,7 @@ The most common UI events are:
 | `session.completed`  | Mark the conversation terminal.                                  |
 | `session.failed`     | Mark the conversation failed.                                    |
 
-For the complete event table, see [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming).
+For the complete event table, see [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming).
 
 ## Reconnection
 

package/dist/docs/public/{advanced → guides}/deployment.md

@@ -66,7 +66,7 @@ The deployed app serves the same stable health, session, and stream routes you'v
 
 ## How Eve sits behind a host framework
 
-You can deploy an Eve app on its own, or mount it inside a host web framework that owns the rest of the site (marketing pages, a dashboard, other API routes). The host keeps its own routing and serves Eve's routes through the framework integration. For mounting Eve in Next.js (`withEve`) and the other supported frameworks, see [Frontend](../frontend/nextjs). Either way, the agent surface and HTTP contract are identical.
+You can deploy an Eve app on its own, or mount it inside a host web framework that owns the rest of the site (marketing pages, a dashboard, other API routes). The host keeps its own routing and serves Eve's routes through the framework integration. For mounting Eve in Next.js (`withEve`) and the other supported frameworks, see [Frontend](./frontend/nextjs). Either way, the agent surface and HTTP contract are identical.
 
 ## 7. Verify the deployment
 
@@ -98,6 +98,14 @@ eve dev https://<your-app>
 
 (Set `VERCEL_AUTOMATION_BYPASS_SECRET` locally first if the deployment uses preview protection.)
 
+## View runs in the dashboard
+
+Once the agent is deployed, the platform auto-detects `eve` as the framework and surfaces an **Agent Runs** tab under your project's **Observability** view in the Vercel dashboard. From there you can browse sessions and drill into each conversation's trace.
+
+> The Agent Runs tab is currently gated: your Vercel team needs the feature enabled before it appears. If you don't see it, reach out to your Vercel contact to get your team enabled.
+
+Agent Runs is separate from the OpenTelemetry exporters configured in [`instrumentation.ts`](./instrumentation). Those still work and are the recommended path if you want spans in Braintrust, Datadog, or another third-party backend.
+
 ## Checklist
 
 - [ ] `eve build` succeeds and writes `.vercel/output`.

package/dist/docs/public/{advanced → guides}/dynamic-capabilities.md

@@ -124,6 +124,6 @@ Both resolve before the prompt is assembled, so the model sees the right instruc
 ## What to read next
 
 - The static tool basics this builds on → [Tools](../tools)
-- The built-in tools and how to override them → [Default harness](./default-harness)
+- The built-in tools and how to override them → [Default harness](../concepts/default-harness)
 - Authenticate a tool or connection to an external service → [Auth & route protection](./auth-and-route-protection)
 - Durable per-session memory for resolvers to read → [State](./state)

package/dist/docs/public/{advanced → guides}/dynamic-workflows.md

@@ -52,4 +52,4 @@ Code mode is the broader version: the model drives _all_ of an agent's tools (fi
 
 - Declare the subagents a workflow orchestrates → [Subagents](../subagents)
 - Call another deployment as one of those agents → [Remote agents](./remote-agents)
-- The `agent/tools/` opt-in mechanism → [Default harness](./default-harness)
+- The `agent/tools/` opt-in mechanism → [Default harness](../concepts/default-harness)

package/dist/docs/public/{frontend → guides/frontend}/nextjs.mdx

@@ -56,7 +56,7 @@ const agent = useEveAgent({
 });
 ```
 
-Before deploying a user-facing app, add `agent/channels/eve.ts` so production requests run your app's auth policy. See [Channels](../channels/overview) and [Auth & route protection](../advanced/auth-and-route-protection).
+Before deploying a user-facing app, add `agent/channels/eve.ts` so production requests run your app's auth policy. See [Channels](../../channels/overview) and [Auth & route protection](../auth-and-route-protection).
 
 ## Dev vs deploy topology
 
@@ -84,5 +84,5 @@ Before deploying a user-facing app, add `agent/channels/eve.ts` so production re
 ## What to read next
 
 - [Frontend overview](./overview): the `useEveAgent` API
-- [Auth & route protection](../advanced/auth-and-route-protection)
-- [Deployment](../advanced/deployment)
+- [Auth & route protection](../auth-and-route-protection)
+- [Deployment](../deployment)

package/dist/docs/public/{frontend → guides/frontend}/nuxt.mdx

@@ -52,7 +52,7 @@ async function handleSubmit() {
 </template>
 ```
 
-Out of the box the module gives Eve a framework default channel. When you want to pick the route auth policy yourself, add `agent/channels/eve.ts` and swap `none()` for a helper like `vercelOidc()` on protected apps. See [Channels](../channels/overview) and [Auth & route protection](../advanced/auth-and-route-protection).
+Out of the box the module gives Eve a framework default channel. When you want to pick the route auth policy yourself, add `agent/channels/eve.ts` and swap `none()` for a helper like `vercelOidc()` on protected apps. See [Channels](../../channels/overview) and [Auth & route protection](../auth-and-route-protection).
 
 ## Dev vs deploy topology
 
@@ -78,5 +78,5 @@ Out of the box the module gives Eve a framework default channel. When you want t
 ## What to read next
 
 - [`useEveAgent` (Vue)](./use-eve-agent-vue): the composable API
-- [Auth & route protection](../advanced/auth-and-route-protection)
-- [Deployment](../advanced/deployment)
+- [Auth & route protection](../auth-and-route-protection)
+- [Deployment](../deployment)

package/dist/docs/public/{frontend → guides/frontend}/overview.mdx

@@ -7,14 +7,14 @@ The frontend helpers put a browser chat or agent UI on top of an Eve agent. `use
 
 ## The integration model
 
-A browser UI is just a client of the agent's HTTP routes (the [Eve channel](../channels/overview)). Two layers wire it up:
+A browser UI is just a client of the agent's HTTP routes (the [Eve channel](../../channels/overview)). Two layers wire it up:
 
 - **The framework integration** mounts the Eve routes on your app's origin, so the browser never crosses a CORS boundary or reads an env var to find the agent. Pick yours: [Next.js](./nextjs) (`withEve`), [Nuxt](./nuxt) (the `eve/nuxt` module), or [SvelteKit](./sveltekit) (the `eveSvelteKit` Vite plugin). On any other stack the hook talks to same-origin `/eve/v1/*` routes directly, or you pass an explicit `host`.
 - **The hook** (`useEveAgent`) holds the session state, streaming, errors, and composer status. It defaults to same-origin Eve routes such as `/eve/v1/session`.
 
 For a guided setup, the [Guides](/docs/skills/eve-add-next) walk through the wiring step by step: [add a Next.js frontend to an existing Eve agent](/docs/skills/eve-add-next), or [add Eve to an existing Next.js app](/docs/skills/eve-add-agent).
 
-For scripts, server-to-server calls, evals, tests, or custom clients that do not need framework UI state, use the [TypeScript Client](../client/overview) directly.
+For scripts, server-to-server calls, evals, tests, or custom clients that do not need framework UI state, use the [TypeScript SDK](../client/overview) directly.
 
 ## Basic chat (React)
 
@@ -100,7 +100,7 @@ Assistant text, reasoning, tool calls, and tool results stream into `data` as th
 
 ## Human-in-the-loop prompts
 
-Tools opt into approval with `needsApproval` on the [server side](../tools), and the model can also ask a question with `ask_question`. Either way the stream emits an `input.requested` event, and the pending request rides on a `dynamic-tool` part of the latest message at `part.toolMetadata?.eve?.inputRequest`. Read it, then answer through the same session with `send()`:
+Tools opt into approval with `needsApproval` on the [server side](../../tools), and the model can also ask a question with `ask_question`. Either way the stream emits an `input.requested` event, and the pending request rides on a `dynamic-tool` part of the latest message at `part.toolMetadata?.eve?.inputRequest`. Read it, then answer through the same session with `send()`:
 
 ```tsx
 const request = agent.data.messages
@@ -228,7 +228,7 @@ const agent = useEveAgent({
 
 ## What to read next
 
-- [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming): the event stream and session cursor
-- [Channels](../channels/overview): the HTTP routes the hook talks to
-- [TypeScript Client](../client/overview): the lower-level client underneath the frontend hooks
+- [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming): the event stream and session cursor
+- [Channels](../../channels/overview): the HTTP routes the hook talks to
+- [TypeScript SDK](../client/overview): the lower-level client underneath the frontend hooks
 - [Guides](/docs/skills/eve-add-next): step-by-step guides for wiring Eve into Next.js

package/dist/docs/public/{frontend → guides/frontend}/sveltekit.mdx

@@ -61,7 +61,7 @@ With the plugin in `vite.config.ts`, components call [`useEveAgent`](./use-eve-a
 </form>
 ```
 
-Out of the box the plugin uses a framework default channel. To set the route auth policy yourself, add `agent/channels/eve.ts` and swap `none()` for a helper like `vercelOidc()` on protected apps. See [Channels](../channels/overview) and [Auth & route protection](../advanced/auth-and-route-protection).
+Out of the box the plugin uses a framework default channel. To set the route auth policy yourself, add `agent/channels/eve.ts` and swap `none()` for a helper like `vercelOidc()` on protected apps. See [Channels](../../channels/overview) and [Auth & route protection](../auth-and-route-protection).
 
 ## Dev vs deploy topology
 
@@ -90,5 +90,5 @@ Out of the box the plugin uses a framework default channel. To set the route aut
 ## What to read next
 
 - [`useEveAgent` (Svelte)](./use-eve-agent-svelte): the binding API
-- [Auth & route protection](../advanced/auth-and-route-protection)
-- [Deployment](../advanced/deployment)
+- [Auth & route protection](../auth-and-route-protection)
+- [Deployment](../deployment)

package/dist/docs/public/{frontend → guides/frontend}/use-eve-agent-svelte.mdx

@@ -75,7 +75,7 @@ await agent.send({
 
 ## Human-in-the-loop prompts
 
-A tool opts into approval with `needsApproval` ([Tools](../tools)). When one fires, the pending request rides along on a `dynamic-tool` part of the latest message. Read it, then answer with `agent.send({ inputResponses })`. This find-and-answer flow is identical across frameworks, so the full example lives in the [Frontend overview](./overview#human-in-the-loop-prompts).
+A tool opts into approval with `needsApproval` ([Tools](../../tools)). When one fires, the pending request rides along on a `dynamic-tool` part of the latest message. Read it, then answer with `agent.send({ inputResponses })`. This find-and-answer flow is identical across frameworks, so the full example lives in the [Frontend overview](./overview#human-in-the-loop-prompts).
 
 ## Stop, reset, and resume
 
@@ -108,4 +108,4 @@ const agent = useEveAgent({
 
 - [SvelteKit](./sveltekit): Vite plugin setup
 - [Frontend overview](./overview): the shared integration model
-- [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming)
+- [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming)

package/dist/docs/public/{frontend → guides/frontend}/use-eve-agent-vue.mdx

@@ -87,7 +87,7 @@ async function onFileChange(event: Event) {
 
 ## Human-in-the-loop prompts
 
-A tool opts into approval with `needsApproval` ([Tools](../tools)). When it triggers, the pending request shows up as a `dynamic-tool` part on the latest message. Read it and answer with `send({ inputResponses })`. That find-and-answer flow is the same across every framework, so the full example lives in the [Frontend overview](./overview#human-in-the-loop-prompts).
+A tool opts into approval with `needsApproval` ([Tools](../../tools)). When it triggers, the pending request shows up as a `dynamic-tool` part on the latest message. Read it and answer with `send({ inputResponses })`. That find-and-answer flow is the same across every framework, so the full example lives in the [Frontend overview](./overview#human-in-the-loop-prompts).
 
 ## Stop, reset, and resume
 
@@ -120,4 +120,4 @@ const agent = useEveAgent({
 
 - [Nuxt](./nuxt): module setup
 - [Frontend overview](./overview): the shared integration model
-- [Sessions, runs & streaming](../advanced/sessions-runs-and-streaming)
+- [Sessions, runs & streaming](../../concepts/sessions-runs-and-streaming)

package/dist/docs/public/{advanced → guides}/hooks.md

@@ -149,6 +149,6 @@ Stream-event hooks and channel adapter event handlers are structurally identical
 ## What to read next
 
 - [Tools](../tools)
-- [Context control](./context-control)
+- [Context control](../concepts/context-control)
 - [Session context](./session-context)
-- [Sessions, runs & streaming](./sessions-runs-and-streaming)
+- [Sessions, runs & streaming](../concepts/sessions-runs-and-streaming)

package/dist/docs/public/{advanced → guides}/instrumentation.md

@@ -134,6 +134,8 @@ Per-turn usage tags are written on each step of a turn, accumulating cumulative
 
 Tag writes are best-effort: a failure is logged once per process and then swallowed, so a broken tag emit never breaks the agent.
 
+These tags power the **Agent Runs** tab in the Vercel dashboard. When you deploy on Vercel, the platform auto-detects `eve` as the framework and surfaces an Agent Runs view under your project's **Observability** tab, where you can browse sessions and drill into each conversation's trace — no `instrumentation.ts` required. The tab is currently gated per team; see [Deployment](./deployment#view-runs-in-the-dashboard) for enablement. Agent Runs is separate from the OpenTelemetry export above: use OTel when you want spans in Braintrust, Datadog, or another third-party backend.
+
 ## Debugging
 
 `eve info` is the fastest way to see what Eve actually picked up: the active tools, skills, subagents, schedules, routes, and discovery diagnostics. Eve also writes inspectable artifacts under `.eve/`, kept even when discovery hits errors:

package/dist/docs/public/{advanced → guides}/meta.json

@@ -1,20 +1,17 @@
 {
-  "title": "Advanced",
+  "title": "Guides",
   "pages": [
-    "default-harness",
-    "context-control",
-    "dynamic-capabilities",
-    "dynamic-workflows",
+    "deployment",
+    "auth-and-route-protection",
+    "instrumentation",
     "hooks",
     "session-context",
     "state",
+    "dynamic-capabilities",
+    "dynamic-workflows",
     "remote-agents",
-    "auth-and-route-protection",
-    "security-model",
-    "deployment",
-    "instrumentation",
     "dev-tui",
-    "execution-model-and-durability",
-    "sessions-runs-and-streaming"
+    "frontend",
+    "client"
   ]
 }

package/dist/docs/public/{advanced → guides}/session-context.md

@@ -1,5 +1,5 @@
 ---
-title: "Session context"
+title: "Session Context"
 description: "Runtime helpers: ctx.session, ctx.getSandbox, ctx.getSkill, and defineState."
 ---
 
@@ -144,6 +144,6 @@ This lifecycle is fully managed by the framework. Authored code only needs to us
 ## What to read next
 
 - [State](./state)
-- [Sessions, runs & streaming](./sessions-runs-and-streaming)
+- [Sessions, runs & streaming](../concepts/sessions-runs-and-streaming)
 - [Subagents](../subagents)
 - [Skills](../skills)

package/dist/docs/public/{advanced → guides}/state.md

@@ -58,5 +58,5 @@ Every [subagent](../subagents) starts with its own fresh state, whether it's a b
 ## What to read next
 
 - Read state inside dynamic resolvers → [Dynamic capabilities](./dynamic-capabilities)
-- How step durability works → [Execution model & durability](../advanced/execution-model-and-durability)
+- How step durability works → [Execution model & durability](../concepts/execution-model-and-durability)
 - The `ctx` accessors available alongside state → [Tools](../tools)

package/dist/docs/public/instructions.mdx

@@ -49,10 +49,10 @@ Instructions never run code. When you need typed executable behavior, reach for
 
 ## Dynamic instructions
 
-Need the prompt resolved at runtime from session context (auth, tenant, channel)? Wrap `defineInstructions` in a `defineDynamic` resolver. See [Dynamic capabilities](./advanced/dynamic-capabilities).
+Need the prompt resolved at runtime from session context (auth, tenant, channel)? Wrap `defineInstructions` in a `defineDynamic` resolver. See [Dynamic capabilities](./guides/dynamic-capabilities).
 
 ## What to read next
 
 - [Tools](./tools): typed actions, the next capability to add
-- [Context control](./advanced/context-control): all the levers for what the model sees
+- [Context control](./concepts/context-control): all the levers for what the model sees
 - [Skills](./skills): on-demand procedures, the counterpart to always-on instructions

package/dist/docs/public/introduction.md

@@ -1,6 +1,6 @@
 ---
 title: "Introduction"
-description: "Meet Eve and the small set of ideas behind an Eve agent."
+description: "How an Eve agent is laid out as files, what runs when a message arrives, and the building blocks you add as it grows."
 ---
 
 Eve is a framework for building durable agents as ordinary files in a TypeScript project.
@@ -87,7 +87,7 @@ As the agent grows, each concern still has a predictable home:
 | Path                            | Add it when you need...                          |
 | ------------------------------- | ------------------------------------------------ |
 | [`connections/`](./connections) | Tools from external MCP servers                  |
-| [`hooks/`](./advanced/hooks)    | Code that reacts to lifecycle and stream events  |
+| [`hooks/`](./guides/hooks)      | Code that reacts to lifecycle and stream events  |
 | [`sandbox/`](./sandbox)         | A controlled workspace for files and commands    |
 | [`subagents/`](./subagents)     | Specialist agents the root agent can delegate to |
 | [`schedules/`](./schedules)     | Recurring or scheduled work                      |
@@ -99,4 +99,7 @@ The result stays readable before it runs: the directory tells you what the agent
 
 - [Getting started](./getting-started): scaffold and run your first agent
 - [Tools](./tools): the typed actions your agent calls
+- [Instructions](./instructions): the always-on system prompt that shapes behavior
+- [Channels](./channels/overview): reach the agent from Slack, Discord, or a web UI
+- [Connections](./connections): pull in tools from external MCP servers
 - [Project layout](./reference/project-layout): every authored slot under `agent/`

package/dist/docs/public/meta.json

@@ -13,9 +13,9 @@
     "subagents",
     "schedules",
     "evals",
-    "advanced",
-    "frontend",
-    "client",
+    "---",
+    "guides",
+    "concepts",
     "---",
     "reference",
     "tutorial"

package/dist/docs/public/reference/cli.md

@@ -136,10 +136,10 @@ See [Evals](../evals/overview) for authoring evals.
 4. `eve build` before shipping.
 5. `eve start` to smoke-test the built output locally.
 
-Related: [Project layout](./project-layout) · [instrumentation.ts](../advanced/instrumentation).
+Related: [Project layout](./project-layout) · [instrumentation.ts](../guides/instrumentation).
 
 ## What to read next
 
 - [Project layout](./project-layout): what `eve info` discovers
-- [instrumentation.ts](../advanced/instrumentation): tracing and the error catalog
-- [Deployment](../advanced/deployment): `eve build` and `eve start` in production
+- [instrumentation.ts](../guides/instrumentation): tracing and the error catalog
+- [Deployment](../guides/deployment): `eve build` and `eve start` in production

package/dist/docs/public/reference/meta.json

@@ -1,4 +1,4 @@
 {
   "title": "Reference",
-  "pages": ["typescript-api", "cli", "project-layout", "faqs"]
+  "pages": ["typescript-api", "cli", "project-layout"]
 }

package/dist/docs/public/reference/project-layout.md

@@ -1,5 +1,5 @@
 ---
-title: "Project layout"
+title: "Project Layout"
 description: "Authored slots under agent/ and the path-derived naming rule."
 ---
 
@@ -104,6 +104,10 @@ my-agent/
 
 Prefer the nested layout. It keeps the app root separate from the authored surface.
 
+## Why didn't Eve discover my file?
+
+Run `eve info`. It lists the discovered surface and prints discovery diagnostics. From there, check that the file sits in the right authored slot (per the slot table above) and that the root-vs-subagent boundary is valid. Eve also writes inspectable artifacts under `.eve/` — see the debugging artifacts in [instrumentation.ts](../guides/instrumentation) and the [CLI](./cli) reference.
+
 ## What to read next
 
 - [`agent.ts`](../agent-config): the runtime config at the root