feat(eve): Getting Started with Eve on Runpod — self-hosted LLM agent + web UI

[TimPietruskyRunPod]

Getting Started with Eve on Runpod

Adds a new eve/ example: an image-generating AI agent built with Eve whose brain is an open LLM self-hosted on Runpod Serverless (Qwen/Qwen3.6-27B-FP8 on vLLM, OpenAI-compatible), with a generate_image tool backed by a Runpod image model, behind a Next.js web chat UI.

Browser ─ Next.js chat UI ─ Eve agent
                              ├─ brain: self-deployed Qwen3.6-27B-FP8 (Runpod Serverless, vLLM)
                              └─ tool:  generate_image → Runpod image model

Agent-first

The setup is encoded as an agent runbook in eve/getting-started/AGENTS.md, written to be executed by an AI coding agent (e.g. Claude Code) using the eve and runpodctl skills. Open the folder, say "read AGENTS.md and get this running", and the agent deploys the vLLM endpoint, wires it in, starts the UI, and verifies the full chain against the runbook's Checks section. It also works as a normal step-by-step guide.

What's included

• agent/ — defineAgent using @runpod/ai-sdk-provider (brain = self-deployed endpoint), generate_image tool, instructions, web channel.
• app/, components/, lib/ — the Next.js chat UI.
• AGENTS.md — deploy runbook + a Checks section capturing the non-obvious gotchas found while building this:
  • served-model-name vs MODEL_NAME (uses OPENAI_SERVED_MODEL_NAME_OVERRIDE; see Served model name becomes snapshot path when HF cache dir is lowercased (MODEL_NAME 404 regression, FDE-174) runpod-workers/worker-vllm#310),
  • qwen3_xml tool-call parser for Qwen3.6,
  • modelContextWindowTokens for a custom (non-gateway) model,
  • images served from public/generated/,
  • cold-start / single-DC A100 capacity notes.
• README.md (folder landing doc) + .env.example.

Verified

• Fresh npm ci + npm run typecheck pass (Node 24); example is self-contained.
• End-to-end confirmed: web UI → agent on the self-deployed Qwen3.6-27B-FP8 endpoint → generate_image → image rendered inline.
• No secrets, endpoint ids, node_modules, or build artifacts committed; .env.example is the only env file tracked.

Also adds the eve entry to the root examples/README.md.