copilotkit 4.8.4 → 4.9.1

package/onboarding/index.json

@@ -3,6 +3,7 @@
   "prompts": [
     {
       "edges": [
+        "proof/oss-baseline",
         "credentials/plan",
         "unsupported/no-validated-path"
       ],
@@ -19,17 +20,91 @@
     },
     {
       "edges": [
+        "framework/ag2",
+        "framework/agno",
+        "framework/built-in",
+        "framework/claude-sdk-python",
+        "framework/claude-sdk-typescript",
+        "framework/crewai-flows",
+        "framework/deep-agents",
         "framework/langgraph-python",
+        "framework/langgraph-fastapi",
         "framework/langgraph-typescript",
+        "framework/llamaindex",
         "framework/google-adk",
         "framework/ms-agent-python",
         "framework/ms-agent-dotnet",
         "framework/mastra",
+        "framework/ms-agent-harness-dotnet",
+        "framework/pydantic-ai",
+        "framework/strands-python",
+        "framework/strands-typescript",
         "unsupported/no-validated-path"
       ],
       "milestone": "credentials",
       "name": "credentials/plan"
     },
+    {
+      "edges": [],
+      "milestone": "fallback",
+      "name": "fallback/best-effort"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/ag2"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/agno"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/built-in"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/claude-sdk-python"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/claude-sdk-typescript"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/crewai-flows"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/deep-agents"
+    },
     {
       "edges": [
         "frontend/plan",
@@ -38,6 +113,14 @@
       "milestone": "framework",
       "name": "framework/google-adk"
     },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/langgraph-fastapi"
+    },
     {
       "edges": [
         "frontend/plan",
@@ -54,6 +137,14 @@
       "milestone": "framework",
       "name": "framework/langgraph-typescript"
     },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/llamaindex"
+    },
     {
       "edges": [
         "frontend/plan",
@@ -70,6 +161,14 @@
       "milestone": "framework",
       "name": "framework/ms-agent-dotnet"
     },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/ms-agent-harness-dotnet"
+    },
     {
       "edges": [
         "frontend/plan",
@@ -78,6 +177,30 @@
       "milestone": "framework",
       "name": "framework/ms-agent-python"
     },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/pydantic-ai"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/strands-python"
+    },
+    {
+      "edges": [
+        "frontend/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "framework",
+      "name": "framework/strands-typescript"
+    },
     {
       "edges": [
         "credentials/finalize-plan",
@@ -116,6 +239,7 @@
     },
     {
       "edges": [
+        "credentials/finalize-plan",
         "unsupported/no-validated-path"
       ],
       "milestone": "frontend",
@@ -142,6 +266,14 @@
       "milestone": "proof",
       "name": "proof/complete"
     },
+    {
+      "edges": [
+        "credentials/plan",
+        "unsupported/no-validated-path"
+      ],
+      "milestone": "proof",
+      "name": "proof/oss-baseline"
+    },
     {
       "edges": [
         "proof/complete",
@@ -168,10 +300,17 @@
     {
       "edges": [],
       "milestone": "subagent",
-      "name": "subagent/prove-round-trip"
+      "name": "subagent/prove-oss-baseline"
     },
     {
       "edges": [],
+      "milestone": "subagent",
+      "name": "subagent/prove-round-trip"
+    },
+    {
+      "edges": [
+        "fallback/best-effort"
+      ],
       "milestone": "unsupported",
       "name": "unsupported/no-validated-path"
     }

package/onboarding/prompts/authenticate/start.md

@@ -14,19 +14,38 @@ question from the documentation this graph gives you. Another checkout on this m
 not a source. The developer running this has none, so an answer taken from one is an
 answer they cannot get, and it hides the documentation gap that blocks them.
 
-Run `npx copilotkit@4.8.4 login --json` before any project work. This command checks the
-current session. It starts sign-in only as needed.
+Before you run a command or spawn a subagent, send this exact message:
 
-Read its JSON Lines output in order:
+Welcome to CopilotKit. I will check sign-in, inspect your project, recommend a setup, and
+show you a plan before I change files. After you approve the plan, I will build the
+integration, prove the full round trip, and leave the app running with its URLs.
 
-1. If it emits `authentication_url`, show only that URL to the developer.
+Do not ask for separate feedback consent. The feedback commands enforce the developer's
+CLI telemetry setting when a later step tries to send a report.
+
+Run `npx --yes copilotkit@4.9.1 login --json` before any project work. This command
+checks the current session. It starts sign-in only as needed. Treat this as a long-lived
+streaming process. Do not wait for the command to exit before you read its standard output.
+
+Read each JSON Lines record as the running command writes it:
+
+1. If the process emits `authentication_url`, show the `authentication_url` to the
+   developer as soon as that line arrives. The process is still running.
 2. Tell the developer to open the URL and finish sign-in.
-3. Wait for the command to emit `type: completed`.
-4. If it emits `type: failed`, report the error and stop onboarding.
+3. Keep monitoring the same process after you show the URL. Do not start a second login
+   command.
+4. Continue onboarding only after that same process emits `type: completed`.
+5. If that process emits `type: failed`, report the error and stop onboarding.
 
 Do not use `whoami` for this check. It has no JSON output and some failures exit with code
 zero. Do not put account tokens or credentials in the conversation.
 
+Before you ask the developer any setup question, finish every read-only investigation and
+preflight check in this section. Record whether your coding-agent environment has browser
+or device control. Use the control that matches the selected surface later. Do not install
+a browser or device tool during this preflight. Do not ask the developer about this tool
+limit.
+
 Spawn one research subagent. Give it the full text of the research brief at the end of this
 prompt and tell it to follow that brief and return only its findings. Add these tasks:
 
@@ -34,10 +53,18 @@ prompt and tell it to follow that brief and return only its findings. Add these
 - Check whether `.copilotkit/project.json` has `projectId`, `projectSlug`, and `clerkOrgId`.
 - Check whether `.env` has a non-empty `INTELLIGENCE_API_KEY` entry.
 - Record the `.env` file modification time without returning it.
+- Report whether an agent, frontend, and CopilotKit integration are present.
+- Report whether the runtime constructor uses a `runner` option, an `intelligence`
+  option, or neither can be proved from project files.
 
 Do not print either file or any secret value. Return only paths, presence checks, and missing
 field names. Wait for the subagent to finish.
 
+If the findings show an empty project and do not prove its purpose, ask one guided question
+about the user outcome. This asks what the developer wants to build before you select a
+framework. Give two or three short examples and offer a minimal starter. Record the answer
+and give it to each later subagent.
+
 If a repository file exists, each finding must cite it. For an empty project, the subagent
 must cite its directory check and report absent parts.
 
@@ -45,11 +72,16 @@ The findings must cover what the project is for, the agent, frontend, CopilotKit
 authentication, credential names, and validation path. Do not ask the developer for facts
 that the repository answers.
 
-When the evidence is complete, run
-`npx copilotkit@4.8.4 onboard read credentials/plan`.
+Do not infer a working OSS path from packages, imports, project files, or keys. If an
+agent, frontend, and CopilotKit integration are present, prove the live starting state
+before any project file changes. Run
+`npx --yes copilotkit@4.9.1 onboard read proof/oss-baseline`.
+
+For every other inspected state, run
+`npx --yes copilotkit@4.9.1 onboard read credentials/plan`.
 
 If authentication or inspection stops onboarding, run
-`npx copilotkit@4.8.4 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.1 onboard read unsupported/no-validated-path`.
 
 ## Research subagent brief
 
@@ -67,6 +99,10 @@ Inspect the repository without changing it. Find evidence for:
 - current CopilotKit packages and configuration
 - authentication boundaries
 - names of required credential variables, without reading their values
+- package manager and lockfile
+- required toolchains and their installed versions
+- declared ports and whether each port is available
+- CopilotKit package versions and package compatibility risks
 
 A project states what it is for in its `README.md`, in its package description, or in
 the prompt of an agent it already has. Quote that statement rather than rewriting it. An
@@ -75,7 +111,8 @@ evidence. State the purpose as unproved when the project never says.
 
 Gather what you need in as few commands as possible. Combine independent reads into one
 command rather than running them one at a time. Split a command only when its result decides
-what you run next.
+what you run next. Keep this preflight read-only. Do not install packages, stop processes,
+or change a port. Check only the toolchains and ports that repository files require.
 
 Return the file paths and a short finding for each item. State each absent or unproved item.
 Do not read, print, or return secret values. Do not read a file outside the project

package/onboarding/prompts/credentials/finalize-plan.md

@@ -5,6 +5,31 @@ repository findings. Ask the developer only for choices that the repository does
 show. Do not change application code in this phase. Do not read, show, store, or request
 a secret value.
 
+Use a gentle wizard. Ask one short question at a time. Do not combine separate choices in
+one question. Put the recommendation first, give its evidence in one sentence, and keep
+the alternatives short. When project selection is unknown, ask only which Intelligence
+project to use. Keep final plan approval as its own later question.
+
+## Record the audit cell
+
+Use the repository findings and selected choices to record the path before project work
+starts. Choose one starting state: empty, agent-only, frontend-only, both, both-oss.
+
+- `empty`: no agent and no frontend.
+- `agent-only`: an agent and no frontend.
+- `frontend-only`: a frontend and no agent.
+- `both`: an agent and frontend that do not have a proved CopilotKit round trip.
+- `both-oss`: an agent and frontend with the proved OSS CopilotKit baseline.
+
+Run this command with the exact selected slugs:
+
+```text
+npx --yes copilotkit@4.9.1 onboard classify --starting-state <starting-state> --agent-framework <agent-framework> --frontend <frontend>
+```
+
+Do not continue if a value is refused. Fix the value from the choices that the earlier
+prompts gave, then run the command again.
+
 ## Select the Intelligence project
 
 Use the target app or runtime directory from the repository findings. If a nested app owns
@@ -20,31 +45,44 @@ succeeds. Record that state in the plan.
 If the developer needs a project or another project, do the selection yourself from the
 target directory. Do not send the developer to another terminal.
 
-List the choices first:
+Read the choices first:
 
 ```text
-npx copilotkit@4.8.4 project list --json
+npx --yes copilotkit@4.9.1 project list --json
 ```
 
 With `--json` the payload is the only thing on standard output, so it is safe to parse.
-Show the developer the project names and ask which one to use, or ask for a name for a new
-project. This is the same kind of question as the frontend choice, so ask it here rather
-than ending the turn.
+Show the current selection and the five most recent projects. Sort recency by `createdAt`.
+Offer search, create-new, and list-all options. Do not show every project unless the
+developer asks.
+
+If the developer searches, run:
+
+```text
+npx --yes copilotkit@4.9.1 project list --search <query> --json
+```
+
+If the developer asks for all projects, show the result of the first list command. Ask
+which project to use, or ask for a new project name. Do not combine this question with a
+frontend, framework, model, credential, or plan-approval question.
 
 Then record their answer, from the target directory:
 
 ```text
-npx copilotkit@4.8.4 project select --project <slug-or-id> --json
+npx --yes copilotkit@4.9.1 project select --project <slug-or-id> --json
 ```
 
 Use `--create <name> --json` instead when they want a new project. The two flags cannot be
 combined. A slug that does not exist fails and lists the real ones, so a typo cannot record
 a selection that points at nothing.
 
-Read the JSON result. It reports `api_key_provisioned`. Key provisioning is deliberately
-non-fatal, so this command can persist the selection, warn on standard error, and still
-exit zero with no key written. Treat `api_key_provisioned` as false the same way as an
-error and stop onboarding: a scaffold with no key looks finished and is not.
+Read the JSON result. It reports `selected_project_slug`, `api_key_provisioned`,
+`project_file_written`, and `environment_file_written` at the top level. The result does
+not contain a secret. Report `selected_project_slug` as the project slug that the server
+selected or created. Require `api_key_provisioned`, `project_file_written`, and
+`environment_file_written` to be true. If one is false, report the error and stop
+onboarding. Key provisioning is non-fatal, so the command can persist a selection and
+still exit zero with no key. A scaffold with no key looks finished and is not.
 
 Never print the payload or any secret value.
 
@@ -103,10 +141,10 @@ values.
 Show only the selected framework, frontend, model, planned file changes, validation commands, and proof steps.
 
 If the developer approves the plan, run
-`npx copilotkit@4.8.4 onboard read implementation/build-and-validate`.
+`npx --yes copilotkit@4.9.1 onboard read implementation/build-and-validate`.
 
 If no exact supported path or documentation URL exists, run
-`npx copilotkit@4.8.4 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.1 onboard read unsupported/no-validated-path`.
 
 ## Planning subagent brief
 
@@ -120,6 +158,11 @@ Use the selected framework, frontend, model, repository findings, and documentat
 from the main coding agent. Fetch every selected URL in one step rather than one after
 another. Do not use remembered CopilotKit instructions.
 
+A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
+not a fact about the page. Retrieve the same URL a second way before you judge it. Run
+`curl -fsSL <url>`, or read the same page without the `.md` suffix. Report a
+documentation gap only after a second method also fails.
+
 Name the application the project asks for, and plan that application. Each documentation
 page teaches through one worked example, and that example carries a domain of its own.
 The domain belongs to the page. The project's purpose from the repository findings
@@ -135,11 +178,18 @@ Preserve each agent or frontend that already exists.
 
 Plan the runtime to consume the Intelligence credential. The runtime takes an
 `intelligence` option holding a client built from the project key. A runtime given a
-`runner` option instead is the SSE runtime. It never reads the key, threads are not
-durable, and the Inspector reads the project as locked. The two options cannot be
+`runner` option instead is the OSS runtime. It never reads the Intelligence key, and the
+Inspector reads the project as locked. The default in-memory OSS runner is ephemeral.
+SQLite, custom, or framework persistence can be durable. The two options cannot be
 combined. Take the constructor from the connect-your-runtime page. Where a framework
 quickstart shows a `runner` option instead, the connect-your-runtime page wins.
 
+When the starting state is `both-oss`, use its recorded live baseline evidence. Preserve
+the working agent, frontend, CopilotKit integration, and OSS behavior. Plan only the
+project selection, Intelligence runtime configuration, and authenticated proof needed for
+the conversion. Preserve the existing persistence and user-visible request. Do not
+rebuild a path that already works.
+
 Where the SDK requires an application-level value that the repository cannot supply, such
 as an end-user identity for threads, use one clearly marked local placeholder and name what
 production requires instead. Do not stop onboarding to ask the developer for it.

package/onboarding/prompts/credentials/plan.md

@@ -4,16 +4,35 @@ Use the repository findings to select the agent framework. Ask the developer onl
 choices that the repository does not show. Do not change application code in this phase.
 Do not read, show, store, or request a secret value.
 
-This release validates six agent frameworks:
+Use a gentle wizard. Ask one short question at a time. Do not combine separate choices in
+one question. Put the recommendation first, give its evidence in one sentence, and keep
+the alternatives short. When the framework is unknown, ask only whether to use the
+recommended framework. If the developer declines it, ask one follow-up question that lists
+the valid framework choices. Do not ask about the frontend, model, or project in this step.
 
-| Framework                          | Default vendor |
-| ---------------------------------- | -------------- |
-| LangGraph Python                   | OpenAI         |
-| LangGraph TypeScript               | OpenAI         |
-| ADK                                | Google         |
-| Microsoft Agent Framework (Python) | OpenAI         |
-| Microsoft Agent Framework (.NET)   | GitHub Models  |
-| Mastra                             | OpenAI         |
+These are the agent frameworks and their default vendors:
+
+| Framework                          | Default vendor  |
+| ---------------------------------- | --------------- |
+| AG2                                | OpenAI          |
+| ADK                                | Google          |
+| Agno                               | OpenAI          |
+| Built-in CopilotKit agent          | OpenAI          |
+| Claude Agent SDK (Python)          | Anthropic       |
+| Claude Agent SDK (TypeScript)      | Anthropic       |
+| CrewAI Flows                       | Project-defined |
+| Deep Agents                        | OpenAI          |
+| LangGraph FastAPI                  | OpenAI          |
+| LangGraph Python                   | OpenAI          |
+| LangGraph TypeScript               | OpenAI          |
+| LlamaIndex                         | OpenAI          |
+| Mastra                             | OpenAI          |
+| Microsoft Agent Framework (.NET)   | GitHub Models   |
+| Microsoft Agent Framework (Python) | OpenAI          |
+| MS Agent Harness (.NET)            | GitHub Models   |
+| Pydantic AI                        | OpenAI          |
+| Strands Agents (Python)            | OpenAI          |
+| Strands Agents (TypeScript)        | OpenAI          |
 
 If the project already has an agent in a listed framework, preserve that framework and
 its model setup. Ask only about choices that remain unknown.
@@ -21,18 +40,37 @@ its model setup. Ask only about choices that remain unknown.
 If the project needs an agent, show the options and one recommendation based on repository
 evidence. Match the language the repository already uses. Ask the developer to choose.
 
+If the project is empty, state that no repository-based recommendation exists. Give these
+documented defaults: LangGraph TypeScript, LangGraph Python, ADK, Microsoft Agent Framework
+Python, Microsoft Agent Framework .NET, and Mastra. Explain which default matches the
+developer's stated purpose. Show the other listed frameworks as options. Do not describe a
+documented default as a repository-based recommendation.
+
 Do not offer a framework that is not listed above. Do not port an existing agent to
 another framework. Do not show the internal route.
 
 Use exactly one matching internal route:
 
-1. LangGraph Python: `npx copilotkit@4.8.4 onboard read framework/langgraph-python`
-2. LangGraph TypeScript: `npx copilotkit@4.8.4 onboard read framework/langgraph-typescript`
-3. ADK: `npx copilotkit@4.8.4 onboard read framework/google-adk`
-4. Microsoft Agent Framework Python: `npx copilotkit@4.8.4 onboard read framework/ms-agent-python`
-5. Microsoft Agent Framework .NET: `npx copilotkit@4.8.4 onboard read framework/ms-agent-dotnet`
-6. Mastra: `npx copilotkit@4.8.4 onboard read framework/mastra`
+1. AG2: `npx --yes copilotkit@4.9.1 onboard read framework/ag2`
+2. Agno: `npx --yes copilotkit@4.9.1 onboard read framework/agno`
+3. Built-in CopilotKit agent: `npx --yes copilotkit@4.9.1 onboard read framework/built-in`
+4. Claude Agent SDK Python: `npx --yes copilotkit@4.9.1 onboard read framework/claude-sdk-python`
+5. Claude Agent SDK TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/claude-sdk-typescript`
+6. CrewAI Flows: `npx --yes copilotkit@4.9.1 onboard read framework/crewai-flows`
+7. Deep Agents: `npx --yes copilotkit@4.9.1 onboard read framework/deep-agents`
+8. LangGraph Python: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-python`
+9. LangGraph FastAPI: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-fastapi`
+10. LangGraph TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/langgraph-typescript`
+11. LlamaIndex: `npx --yes copilotkit@4.9.1 onboard read framework/llamaindex`
+12. ADK: `npx --yes copilotkit@4.9.1 onboard read framework/google-adk`
+13. Microsoft Agent Framework Python: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-python`
+14. Microsoft Agent Framework .NET: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-dotnet`
+15. Mastra: `npx --yes copilotkit@4.9.1 onboard read framework/mastra`
+16. MS Agent Harness .NET: `npx --yes copilotkit@4.9.1 onboard read framework/ms-agent-harness-dotnet`
+17. Pydantic AI: `npx --yes copilotkit@4.9.1 onboard read framework/pydantic-ai`
+18. Strands Agents Python: `npx --yes copilotkit@4.9.1 onboard read framework/strands-python`
+19. Strands Agents TypeScript: `npx --yes copilotkit@4.9.1 onboard read framework/strands-typescript`
 
 If the project has an agent in another framework, or no listed framework fits, keep the
 developer's current agent and run
-`npx copilotkit@4.8.4 onboard read unsupported/no-validated-path`.
+`npx --yes copilotkit@4.9.1 onboard read unsupported/no-validated-path`.

package/onboarding/prompts/fallback/best-effort.md

@@ -0,0 +1,36 @@
+# Build from the best available official documentation
+
+Tell the implementation subagent which plan steps lack direct documentation. Give it the
+approved plan, repository findings, and all official documentation that you found.
+
+Tell the subagent to preserve the existing project. It must not invent a CopilotKit API.
+It can combine compatible APIs from different official pages when one page omits the
+selected framework and frontend combination.
+
+Run the approved implementation and validation steps. Repair a failure in new work at most
+three times. Stop if the fix requires changes to the developer's existing agent or
+frontend.
+
+After validation passes, prove the runtime, agent round trip, and real frontend path. Use
+the same proof rules from the approved plan. Keep the development servers running after
+proof.
+
+Do not block core proof on CopilotKit Skills or MCP configuration. Try these tools after
+the application passes proof. Report each tool result separately.
+
+Report the documentation gap and each assumption with the proof evidence. Do not claim
+that the selected documentation proved an inferred step.
+
+When the proof is complete, run `npx --yes copilotkit@4.9.1 onboard complete`, carrying the
+surface-check result the proof subagent returned. Pass exactly one flag, matching this
+journey's surface:
+
+```text
+npx --yes copilotkit@4.9.1 onboard complete --visual-check <outcome>
+npx --yes copilotkit@4.9.1 onboard complete --device-check <outcome>
+```
+
+`--visual-check` is for a web frontend and takes `performed`, `skipped-no-browser-tool`, or
+`failed`. `--device-check` is for React Native and takes `performed`, `skipped-no-device`,
+or `failed`. Anything but `performed` ends this run as blocked, and the command's output
+names the evidence that is missing. Report it that way.

package/onboarding/prompts/framework/ag2.md

@@ -0,0 +1,48 @@
+# Configure AG2
+
+Preserve an existing AG2 model setup. Start with OpenAI for a new agent. Offer another
+vendor only after an exact CopilotKit Markdown page names it. The page must name its
+credential variables and setup steps.
+
+Name the default model credential `OPENAI_API_KEY`.
+
+Keep `INTELLIGENCE_API_KEY` separate from model-vendor credentials. Do not read, show,
+store, or request a secret value.
+
+## Documentation
+
+- https://docs.copilotkit.ai/ag2/quickstart.md
+- https://docs.copilotkit.ai/ag2/inspector.md
+- https://docs.copilotkit.ai/ag2/generative-ui/a2ui/fixed-schema.md
+- https://docs.copilotkit.ai/ag2/readables.md
+
+Fetch all four pages in one step rather than one after another.
+
+The documentation scope is `ag2`. Use only the Python examples from these pages.
+Preserve the existing `AGUIStream` endpoint and its route. The quickstart uses a sample
+repository with `uv sync`. It does not name a dependency list for an existing project.
+Do not replace the project's dependency manifest with a guessed list, and do not change
+an existing endpoint to the quickstart's `/weather` sample route.
+
+The fixed-schema page has no AG2 backend schema-loading, render-operations, or runtime
+setup snippet. Do not invent a fixed-schema A2UI backend setup. If the requested work
+needs that missing setup, run the unsupported route below.
+
+The Readables page includes the AG2 backend context path. Use its `ContextVariables` and
+`AGUIStream` examples when the project needs frontend context. Do not substitute another
+framework's context setup.
+
+Record the selected framework, vendor, model, required credential variable names, these
+URLs, and the fixed-schema documentation gap. Do not use remembered CopilotKit
+instructions.
+
+A fetch tool that refuses a URL, or fails to reach it, reports a limit of the tool and
+not a fact about the page. Retrieve the same URL a second way before you judge it. Run
+`curl -fsSL <url>`, or read the same page without the `.md` suffix. Treat a page as
+unavailable only after a second method also fails.
+
+If the pages support the selection, run
+`npx --yes copilotkit@4.9.1 onboard read frontend/plan`.
+
+If a second method also fails, or a page that loads does not support the selection, run
+`npx --yes copilotkit@4.9.1 onboard read unsupported/no-validated-path`.