@agent-native/core 0.93.0 → 0.94.0

package/docs/content/workspace-connections.mdx

@@ -387,14 +387,7 @@ Workspace connection provider metadata answers: "Which provider is this, what ca
 
 </Diagram>
 
-Use both together:
-
-1. Dispatch (or another workspace setup flow) creates the underlying vault secret or OAuth credential reference.
-2. The workspace connection store records the provider account, safe metadata, credential refs, and app grants.
-3. Each app reads provider metadata from the catalog and connection/grant summaries from the shared store.
-4. The app UI shows readiness: connected, granted but unhealthy, needs grant, missing credentials, or metadata-only.
-5. App-specific SQL stores only app-specific source ids, cursors, filters, sync windows, metric definitions, review rules, and user choices.
-6. App actions resolve credentials at execution time through granted connection refs and the vault, and never return secret values.
+In practice, the vault secret gets created first (by Dispatch or another workspace setup flow), then the connection row and its grants point at it — the [four concepts](#the-four-concepts) above cover the rest of the lifecycle. The one thing worth calling out here: app-specific SQL (source ids, cursors, filters, sync windows, metric definitions, review rules, user choices) never moves into the connection store — that stays app-local even after a provider is shared. See [Credential resolution](#credential-resolution) below for exactly how an action turns a granted ref into a usable secret at execution time.
 
 ### Provider reader runtime
 
@@ -415,20 +408,13 @@ Brain's Sources page is the reference implementation. It shows reusable workspac
 
 ### Building a reusable connector
 
-When a new provider should work across multiple templates:
-
-1. **Provider metadata:** add or reuse a provider in `@agent-native/core/connections`. This is the stable id, display label, capability list, recommended template uses, and credential key names.
-2. **Workspace connection:** Dispatch or another workspace setup surface stores the connected account's safe metadata, status, scopes, `credentialRefs`, and app grants through `@agent-native/core/workspace-connections`.
-3. **App-local source:** Brain, Analytics, Mail, or another app stores only the app-specific choices it owns, such as Slack channels, GitHub repositories, HubSpot object filters, sync cursors, or polling cadence.
-
-Do not duplicate OAuth/token storage in each app. The connection record says "this is Acme Slack and its token lives at `SLACK_BOT_TOKEN`"; the app-local source says "Brain may ingest `#product` and `#dev-fusion` from that Slack connection."
+When a new provider should work across multiple templates, add it at each of the three layers once: register the id/label/capabilities in `@agent-native/core/connections` (**Provider metadata**), store the connected account through `upsertWorkspaceConnection()` (the **Connection**), and let each consuming app keep only its own app-local source config (Slack channels, GitHub repositories, HubSpot object filters, sync cursors, polling cadence) — never a second copy of the OAuth/token storage. The connection record says "this is Acme Slack and its token lives at `SLACK_BOT_TOKEN`"; the app-local source says "Brain may ingest `#product` and `#dev-fusion` from that Slack connection."
 
 ### Dispatch control-plane setup
 
-Dispatch exposes control-plane actions that write the same shared store functions an app could call directly:
+Dispatch exposes control-plane actions that write the same shared store functions an app could call directly — its `upsert-workspace-connection` action validates input against the provider catalog, then delegates to the same `upsertWorkspaceConnection()` shown throughout this page:
 
 ```ts
-// templates/dispatch/actions/upsert-workspace-connection.ts delegates to this.
 await upsertWorkspaceConnection({
   id: "team-slack",
   provider: "slack",
@@ -472,24 +458,31 @@ App execution code resolves credential values from granted `credentialRefs` thro
 
 ### App-local boundary
 
-The boundary between shared connections and app-local sources is intentional. What is reusable today is provider identity, credential-reference resolution, per-app grants, provider readiness, safe account metadata, and the normalized provider-reader contract. What is not yet generic is most live provider API reading, OAuth flow ownership, ingestion cursors, source filters, sync cadence, and domain interpretation. Those stay in the app that owns the workflow unless a reader implementation is explicitly promoted to shared.
+Two rules follow from the [reusable-vs-app-local boundary](#building-a-reusable-connector) above:
 
-App source connectors should not read deploy-level environment variables as a fallback for user/org source credentials. Env vars are global to the deployment and do not express workspace grants.
-
-Agents should follow a simple rule: if a user asks to connect Slack, GitHub, HubSpot, Gmail, Google Drive, Granola, or another shared provider, inspect the workspace connection catalog first. If the provider is `connected`, use it. If it is `needs_grant`, ask for or perform the app grant. If it is `needs_credentials`, ask for the missing vault key. Only ask for a new raw key when no reusable connection exists.
+- **Never fall back to deploy-level environment variables** for user/org source credentials in an app connector — env vars are global to the deployment and do not express workspace grants.
+- **Agents check the catalog before asking for a new key.** If a user asks to connect Slack, GitHub, HubSpot, Gmail, Google Drive, Granola, or another shared provider, inspect the workspace connection catalog first: use it if `connected`, ask for or perform the app grant if `needs_grant`, ask for the missing vault key if `needs_credentials`. Only ask for a brand-new raw key when no reusable connection exists.
 
 ### Path to "connect once, use everywhere"
 
 The provider catalog and grant store are the foundation for a broader workspace layer:
 
 - Shared provider ids and capability names keep templates aligned.
-- Workspace-level inventory can show which providers are configured across Brain, Mail, Analytics, Dispatch, and future apps.
+- Workspace-level inventory can show which providers are configured across [Brain](/docs/template-brain), Mail, Analytics, [Dispatch](/docs/dispatch), and future apps.
 - Connection rows record account labels, status, allowed apps, credential refs, and health checks without changing template-facing provider ids.
 - Grant rows let a workspace owner connect once, then enable individual apps as the workspace adopts them.
 - Agents can route work across apps knowing which providers are already connected and which apps have grants.
 - Federated search can ask for providers with `search`, `docs`, `messages`, `meetings`, `crm`, or `code` capabilities instead of hardcoding every app's connector list.
 - Provider-specific readers, OAuth refresh flows, ingestion checkpoints, and app-owned data models can become shared later, but they are not implied by a workspace connection today.
 
-Keep the boundary strict: provider metadata is safe to show; credential values stay in the vault.
+Keep the boundary strict: provider metadata is safe to show; credential values stay in the [vault](/docs/security).
 
 </details>
+
+## What's next {#whats-next}
+
+- [**Dispatch**](/docs/dispatch) — the app that typically owns workspace connection setup and the vault
+- [**Security**](/docs/security) — the credential vault, secret scoping, and access model connections point at
+- [**Onboarding**](/docs/onboarding#checking-workspace-connections-in-onboarding) — checking connection readiness from a template's setup checklist
+- [**MCP Clients**](/docs/mcp-clients) — sharing MCP server credentials across a workspace, a sibling reusable-config pattern
+- [**Brain**](/docs/template-brain) — the reference implementation of a provider Sources page built on this model

package/docs/content/workspace-management.mdx

@@ -5,7 +5,11 @@ description: "Branching, CODEOWNERS, PR review, and how Dispatch handles runtime
 
 # Workspace Governance
 
-> **Which workspace doc?** This page covers **governance** — who reviews, approves, and owns what across many apps in one repo. For what a workspace _is_ (the customization layer) see [Workspace](/docs/workspace); for the deployment shape (one monorepo, many apps) see [Multi-App Workspaces](/docs/multi-app-workspace).
+<Callout tone="info">
+
+**Which workspace doc?** This page covers **governance** — who reviews, approves, and owns what across many apps in one repo. For what a workspace _is_ (the customization layer) see [Workspace](/docs/workspace); for the deployment shape (one monorepo, many apps) see [Multi-App Workspaces](/docs/multi-app-workspace).
+
+</Callout>
 
 This guide covers the operational side of running an agent-native workspace — how to branch, who reviews what, how to set up code ownership, and how the Dispatch control plane fits into your governance model.
 
@@ -68,7 +72,7 @@ This guide covers the operational side of running an agent-native workspace —
 
 Use short-lived feature branches for all work:
 
-```
+```text
 main                         ← production
 ├── feat/mail-filters        ← single-app change
 ├── feat/core-oauth-refresh  ← framework change
@@ -118,7 +122,7 @@ Code governance is configured by a handful of files at the repo root:
 
 GitHub's CODEOWNERS file auto-assigns reviewers to PRs based on which files changed. Create `.github/CODEOWNERS` at the repo root:
 
-```
+```text filename=".github/CODEOWNERS"
 # Framework core — affects every app; platform team reviews all changes
 packages/core/                     @your-org/platform-team
 
@@ -232,4 +236,12 @@ For a new workspace, after running `npx @agent-native/core@latest create`:
 - [ ] Configure the approval policy and approver emails
 - [ ] Set up SendGrid (`SENDGRID_API_KEY`, `SENDGRID_FROM_EMAIL`) for admin notifications
 - [ ] Connect Slack or Telegram for workspace messaging
-- [ ] Configure shared MCP servers — add `mcp-servers/<name>.json` workspace resources in Dispatch for All-app or selected-app grants; use `mcp.config.json` or [MCP hub mode](/docs/mcp-clients#hub) for lower-level deployments
+- [ ] Configure shared MCP servers — see [Multi-App Workspaces — Shared MCP servers](/docs/multi-app-workspace#shared-mcp)
+
+## What's next {#whats-next}
+
+- [**Workspace**](/docs/workspace) — the customization layer this page governs (skills, memory, agents, MCP servers)
+- [**Multi-App Workspaces**](/docs/multi-app-workspace) — the deployment shape: one monorepo, many apps
+- [**Dispatch**](/docs/dispatch) — the runtime control plane referenced throughout this page
+- [**Sharing**](/docs/sharing) — access control for individual resources, complementing repo-level CODEOWNERS
+- [**Audit Log**](/docs/audit-log) — the action-level audit trail that complements `git log`/`git blame`

package/docs/content/workspace.mdx

@@ -5,7 +5,11 @@ description: "Claude-Code-level customization per user — skills, memory, instr
 
 # Workspace
 
-> **Which workspace doc?** This page covers the **customization layer** — what a workspace _is_. For the deployment shape (one monorepo, many apps) see [Multi-App Workspaces](/docs/multi-app-workspace); for governance (who reviews, approves, and owns what) see [Workspace Governance](/docs/workspace-management).
+<Callout tone="info">
+
+**Which workspace doc?** This page covers the **customization layer** — what a workspace _is_. For the deployment shape (one monorepo, many apps) see [Multi-App Workspaces](/docs/multi-app-workspace); for governance (who reviews, approves, and owns what) see [Workspace Governance](/docs/workspace-management).
+
+</Callout>
 
 Every agent-native app ships with a **workspace**: the customization layer that makes the agent yours. It contains team instructions (`AGENTS.md`), shared learnings (`LEARNINGS.md`), personal structured memory (`memory/MEMORY.md`), skills the agent pulls in on demand, custom sub-agents, scheduled jobs, and connected MCP servers — everything you'd expect from a Claude Code / Codex setup.
 
@@ -82,7 +86,7 @@ The twist: **it's SQL rows, not filesystem files.** Each user gets their own wor
 | Per-project `CLAUDE.md` / skills | Per-app `AGENTS.md` + workspace memory resources   |
 | MCP config in a JSON file        | MCP config in JSON _or_ the settings UI, per scope |
 
-Same capabilities. Different economics. See [Templates](/docs/cloneable-saas) for why this matters for SaaS.
+Same capabilities. Different economics. See [Apps](/docs/cloneable-saas) for why this matters for SaaS.
 
 ## Overview {#overview}
 
@@ -219,11 +223,9 @@ workspace context/brand.md
 -> personal context/brand.md
 ```
 
-Keep `context/` files short and factual — a few bullets the agent can skim:
-
-```text
-<!-- context/brand.md -->
+For example:
 
+```text filename="context/brand.md"
 # Brand
 
 - Voice: direct, warm, concrete
@@ -386,15 +388,9 @@ There are two agent types in Workspace:
 
 Use custom agents for delegation within one app. Use connected agents when you need to call another app over A2A.
 
-## @ Tagging {#at-tagging}
-
-Type `@` in the chat input to reference workspace items. A dropdown appears at the cursor showing matching agents and files. Use arrow keys to navigate and Enter to select. The selected item appears as an inline chip in the input.
-
-When you send a message, **files/resources** are passed as references the agent can read, **custom agents** run locally with their profile instructions, and **connected agents** are called over A2A.
+## @ Tagging and / Slash Commands {#at-tagging}
 
-## / Slash Commands {#slash-commands}
-
-Type `/` at the start of a line to invoke a skill. A dropdown shows available skills with their names and descriptions; selecting one adds an inline chip and includes its content as context when the message is sent. If no skills are configured, the dropdown links to these docs.
+Type `@` in the chat input to reference an agent, file, or resource, or `/` to invoke a skill — both open a dropdown at the cursor and add an inline chip when you select an item. See [Agent Mentions](/docs/agent-mentions) for the full mechanics (routing, `MentionProvider`, sub-agent selection) and [Skills Guide](/docs/skills-guide) for how skills are authored and discovered.
 
 ## Code vs App Mode {#dev-vs-prod}
 
@@ -414,10 +410,6 @@ Workspace Connections let apps share the same provider account (Slack, GitHub, H
 
 See [Workspace Connections](/docs/workspace-connections) for the quickstart, connection/grant/credentialRef API, and concrete Slack, HubSpot, and GitHub examples.
 
----
-
-# Reference
-
 ## Resource API {#resource-api}
 
 Resources can be managed from server code, actions, or the REST API.
@@ -461,3 +453,12 @@ pnpm action resource-write --path "notes/meeting.md" --content "# Meeting Notes.
 # Delete a resource
 pnpm action resource-delete --path "notes/old.md"
 ```
+
+## What's next {#whats-next}
+
+- [**Skills Guide**](/docs/skills-guide) — author and scope the skill files referenced from `skills/`
+- [**Agent Mentions**](/docs/agent-mentions) — `@`-mention and `/`-command mechanics in full
+- [**Recurring Jobs**](/docs/recurring-jobs) — schedule the prompts created from Scheduled Tasks
+- [**Workspace Governance**](/docs/workspace-management) — who reviews, approves, and owns workspace changes
+- [**Multi-App Workspaces**](/docs/multi-app-workspace) — the deployment shape one workspace spans
+- [**Workspace Connections**](/docs/workspace-connections) — share provider credentials across apps

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.93.0",
+  "version": "0.94.0",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/src/templates/workspace-core/.agents/skills/voice-transcription/SKILL.md

@@ -13,17 +13,21 @@ metadata:
 
 # Voice Transcription
 
-Click-to-toggle microphone inside the sidebar composer turns speech into
-text. Users configure live transcription separately from AI cleanup in
-Settings → Voice Transcription. The feature is available in every template
-that renders `TiptapComposer`.
+The microphone inside the sidebar composer offers two distinct paths:
+editable dictation and an opt-in realtime speech-to-speech agent session.
+Users configure dictation separately from AI cleanup in Settings → Voice
+Transcription. Both paths are available in every template that renders the
+shared agent sidebar.
 
 ## UX rules
 
 - **Always show the mic alongside the send button.** Cursor replaces send
   with mic when the composer is empty; their users complain. We keep both
   visible — Lovable does the same.
-- **Click-to-toggle, not push-to-talk.** More forgiving in a sidebar, avoids
+- **Ask before switching modes.** The mic opens a shadcn popover offering
+  **Start voice mode** and **Keep dictating**; never silently replace the
+  established dictation behavior.
+- **Dictation is click-to-toggle, not push-to-talk.** More forgiving in a sidebar, avoids
   host-app hotkey clashes. Keyboard shortcut is `Cmd/Ctrl+Shift+M` and
   `Escape` cancels mid-recording.
 - **Transcript lands in the composer, editable, never auto-sent.** Insert at
@@ -34,6 +38,31 @@ that renders `TiptapComposer`.
   Never use a sparkle or robot icon.
 - **Errors via inline alert or toast, never `window.alert`.**
 
+## Realtime speech mode
+
+Realtime speech mode is a full-duplex OpenAI Realtime WebRTC session, separate
+from the dictation providers below. It requires the authenticated user's
+`OPENAI_API_KEY`, uses the server-owned `gpt-realtime-2.1` session
+configuration, and keeps the key out of browser code.
+
+- Starting voice mode collapses the chat into a persistent bottom-end speech
+  orb. Clicking the orb shows or hides chat without ending the session; ending
+  the session is a separate, explicit control.
+- Semantic VAD keeps listening, starts responses automatically, and supports
+  barge-in while the agent is speaking.
+- Function calls must cross the authenticated realtime tool bridge and enter
+  `executeAgentToolCall`. Never call `ActionEntry.run` directly: that bypasses
+  schema validation, approvals, audit/journal behavior, timeouts, redaction,
+  and mutation refreshes.
+- Preserve the active browser-tab id in request context so `set-url`,
+  `set-search-params`, `view-screen`, and tab-scoped application state affect
+  the app the user is actually speaking to.
+- Do not persist audio. Store only compact lifecycle and latest-transcript
+  context at `application_state["realtime-voice-session"]`; delete it when the
+  session ends.
+- Missing-key failures should open Settings focused on the user-scoped
+  `OPENAI_API_KEY` field. Never send, log, or echo the key to the browser.
+
 ## Source And Cleanup
 
 Settings must keep these as separate choices:
@@ -80,11 +109,14 @@ Default behavior:
 | --------------------------------------------------------------------- | --------------------------------------------------- |
 | `packages/core/src/client/composer/useVoiceDictation.ts`              | Provider-routing hook (MediaRecorder / Web Speech)  |
 | `packages/core/src/client/composer/VoiceButton.tsx`                   | Mic button + live amplitude + cancel overlay        |
+| `packages/core/src/client/composer/RealtimeVoiceMode.tsx`            | Opt-in popover + persistent speech orb              |
+| `packages/core/src/client/composer/useRealtimeVoiceMode.tsx`         | WebRTC lifecycle, provider events, and tool bridge  |
 | `packages/core/src/client/composer/TiptapComposer.tsx`                | Wires the hook, insertion, and keyboard shortcut    |
 | `packages/core/src/client/settings/VoiceTranscriptionSection.tsx`     | Live source + cleanup controls in sidebar settings  |
 | `packages/core/src/client/transcription/BuilderTranscriptionCta.tsx`  | CTA shown when Builder account isn't connected      |
 | `packages/core/src/client/transcription/use-live-transcription.ts`    | Web Speech live-transcription hook for recordings   |
 | `packages/core/src/server/transcribe-voice.ts`                        | Route handler (routes to Builder/Gemini/Groq/Whisper) |
+| `packages/core/src/server/realtime-voice.ts`                          | Authenticated OpenAI SDP and action-tool routes     |
 | `packages/core/src/transcription/builder-transcription.ts`            | Builder proxy transcription client                  |
 | `packages/core/src/voice/`                                            | Shared voice context pack, prompt, and replacement helpers |
 | `packages/core/src/secrets/register-framework-secrets.ts`             | Framework-level provider key registration           |
@@ -139,4 +171,6 @@ Templates can:
 - Don't call transcription providers from the client — go through `/_agent-native/transcribe-voice` so the user's secret stays server-side.
 - Don't remove the cancel affordance — mic permission abuse paranoia is real.
 - Don't auto-submit the transcript — users always edit before sending.
+- Don't route realtime tool calls around the central guarded agent executor.
+- Don't persist realtime audio or put provider keys in SDP/session payloads.
 - Don't copy Cursor's "hide send when empty" pattern — it confuses users.

package/corpus/core/docs/content/locales/ar-SA/migration-workbench.mdx

@@ -1,76 +0,0 @@
----
-title: "الترحيل إلى Agent-Native (/الترحيل)"
-description: "الترحيل هو هدف مضمن/ترحيل في مساحة عمل Agent-Native Code - وليس تطبيقًا منفصلاً. راجع رمز Agent-Native UI للحصول على الدليل الكامل."
----
-
-# الترحيل إلى Agent-Native (/الترحيل)
-
-الترحيل **ليس منتجًا أو قالبًا منفصلاً** — فهو مضمن
-هدف `/migrate` داخل مساحة عمل [Agent-Native Code](/docs/code-agents-ui).
-يتم تشغيله كجلسة تعليمات برمجية عادية يمكنك استئنافها والإرفاق بها وفحصها وإيقافها.
-
-<Diagram id="doc-block-4n71h8" title={"/migrate عبارة عن جلسة تعليمات برمجية، وليست تطبيقًا منفصلاً"} summary={"يتم إدخال المسار، URL، أو الوصف؛ يشترك التشغيل في نفس المخزن والنص وعناصر التحكم مثل أي جلسة تعليمات برمجية أخرى، ويمكن أن يصدر ملفًا محمولاً."}>
-
-```html
-<div class="diagram-migrate">
-  <div class="diagram-col">
-    <div class="diagram-pill">./local-app</div>
-    <div class="diagram-pill">https://example.com</div>
-    <div class="diagram-pill">--describe \"...\"</div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center" data-rough>
-    <span class="diagram-pill accent">/migrate goal</span
-    ><small class="diagram-muted"
-      >نفس المخزن · النص · عناصر تشغيل التنفيذ</small
-    >
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-col">
-    <div class="diagram-box" data-rough>تطبيق مرحل</div>
-    <div class="diagram-pill ok">--emit dossier</div>
-  </div>
-</div>
-```
-
-```css
-.diagram-migrate {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  flex-wrap: wrap;
-}
-.diagram-migrate .diagram-col {
-  display: flex;
-  flex-direction: column;
-  gap: 8px;
-}
-.diagram-migrate .diagram-arrow {
-  font-size: 22px;
-  line-height: 1;
-}
-.diagram-migrate .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
-```
-
-</Diagram>
-
-```bash
-npx @agent-native/core@latest code /migrate ./my-next-app --out ../migrated-app
-npx @agent-native/core@latest code /migrate https://example.com --describe "marketing site plus dashboard"
-npx @agent-native/core@latest migrate ./my-next-app --out ../migrated-app   # shortcut into the same goal
-```
-
-الدليل الكامل — أشكال الإدخال (المسار / URL / الوصف)، ملفات `--emit`،
-وضع التخطيط مقابل الوضع التلقائي، وعناصر التحكم في التشغيل، وبيانات الاعتماد، والروابط العميقة لسطح المكتب، و
-صادرات الحزمة `@agent-native/migrate` — موجودة في
-[Agent-Native Code UI → Migrating to Agent-Native](/docs/code-agents-ui#migrate).
-
-> [!NOTE]
-> تمت إزالة تطبيق تفاصيل `migration` القديم المخفي. استخدم الكود
-> ، أو علامة التبويب Desktop Code، أو الملف المنبعث كالملف المدعوم
-> الأسطح.

package/corpus/core/docs/content/locales/de-DE/migration-workbench.mdx

@@ -1,76 +0,0 @@
----
-title: "Migration nach Agent-Native (/migrate)"
-description: "Migration ist ein integriertes /migrate-Ziel im Agent-Native-Code-Arbeitsbereich – keine separate App. Die vollständige Anleitung finden Sie unter Agent-Native-Code UI."
----
-
-# Migration nach Agent-Native (/migrate)
-
-Migration ist **kein separates Produkt oder eine separate Vorlage** – sie ist integriert
-`/migrate`-Ziel im [Agent-Native Code](/docs/code-agents-ui)-Arbeitsbereich.
-Es wird als normale Code-Sitzung ausgeführt, die Sie fortsetzen, anhängen, überprüfen und beenden können.
-
-<Diagram id="doc-block-g1pprw" title="/migrate ist eine Code-Sitzung, keine separate App" summary={"Ein Pfad, URL oder eine Beschreibung wird eingegeben; Die Ausführung nutzt den gleichen Speicher, das gleiche Transkript und die gleichen Steuerelemente wie jede andere Code-Sitzung und kann ein tragbares Dossier ausgeben."}>
-
-```html
-<div class="diagram-migrate">
-  <div class="diagram-col">
-    <div class="diagram-pill">./local-app</div>
-    <div class="diagram-pill">https://example.com</div>
-    <div class="diagram-pill">--describe \"...\"</div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center" data-rough>
-    <span class="diagram-pill accent">/migrate goal</span
-    ><small class="diagram-muted"
-      >gleicher Store · Transkript · Laufsteuerung</small
-    >
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-col">
-    <div class="diagram-box" data-rough>Migrierte App</div>
-    <div class="diagram-pill ok">--emit dossier</div>
-  </div>
-</div>
-```
-
-```css
-.diagram-migrate {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  flex-wrap: wrap;
-}
-.diagram-migrate .diagram-col {
-  display: flex;
-  flex-direction: column;
-  gap: 8px;
-}
-.diagram-migrate .diagram-arrow {
-  font-size: 22px;
-  line-height: 1;
-}
-.diagram-migrate .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
-```
-
-</Diagram>
-
-```bash
-npx @agent-native/core@latest code /migrate ./my-next-app --out ../migrated-app
-npx @agent-native/core@latest code /migrate https://example.com --describe "marketing site plus dashboard"
-npx @agent-native/core@latest migrate ./my-next-app --out ../migrated-app   # shortcut into the same goal
-```
-
-Der vollständige Leitfaden – Eingabeformen (Pfad / URL / Beschreibung), `--emit`-Dossiers,
-Plan vs. Auto-Modus, Ausführungskontrollen, Anmeldeinformationen, Desktop-Deep-Links und
-`@agent-native/migrate`-Paketexporte – lebt in
-[Agent-Native Code UI → Migrating to Agent-Native](/docs/code-agents-ui#migrate).
-
-> [!NOTE]
-> Die alte versteckte `migration`-Detail-App wurde entfernt. Verwenden Sie den Code
-> -Arbeitsbereich, die Registerkarte „Desktop-Code“ oder ein ausgegebenes Dossier als unterstützt
-> Oberflächen.

package/corpus/core/docs/content/locales/es-ES/migration-workbench.mdx

@@ -1,76 +0,0 @@
----
-title: "Migrar a Agent-Native (/migrar)"
-description: "La migración es un objetivo de migración integrado en el espacio de trabajo del Código Agent-Native, no una aplicación separada. Consulte el código Agent-Native UI para obtener la guía completa."
----
-
-# Migrar a Agent-Native (/migrar)
-
-La migración **no es un producto o plantilla independiente**: es algo integrado
-Objetivo `/migrate` dentro del espacio de trabajo [Agent-Native Code](/docs/code-agents-ui).
-Se ejecuta como una sesión de Código normal que puede reanudar, adjuntar, inspeccionar y detener.
-
-<Diagram id="doc-block-qeqnep" title={"/migrate es una sesión de Código, no una aplicación separada"} summary={"Entra una ruta, URL, o descripción; la ejecución comparte el mismo almacén, transcripción y controles que cualquier otra sesión de Código y puede emitir un expediente portátil."}>
-
-```html
-<div class="diagram-migrate">
-  <div class="diagram-col">
-    <div class="diagram-pill">./local-app</div>
-    <div class="diagram-pill">https://example.com</div>
-    <div class="diagram-pill">--describe \"...\"</div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center" data-rough>
-    <span class="diagram-pill accent">/migrate goal</span
-    ><small class="diagram-muted"
-      >mismo almacén · transcripción · controles de ejecución</small
-    >
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-col">
-    <div class="diagram-box" data-rough>App migrada</div>
-    <div class="diagram-pill ok">--emit dossier</div>
-  </div>
-</div>
-```
-
-```css
-.diagram-migrate {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  flex-wrap: wrap;
-}
-.diagram-migrate .diagram-col {
-  display: flex;
-  flex-direction: column;
-  gap: 8px;
-}
-.diagram-migrate .diagram-arrow {
-  font-size: 22px;
-  line-height: 1;
-}
-.diagram-migrate .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
-```
-
-</Diagram>
-
-```bash
-npx @agent-native/core@latest code /migrate ./my-next-app --out ../migrated-app
-npx @agent-native/core@latest code /migrate https://example.com --describe "marketing site plus dashboard"
-npx @agent-native/core@latest migrate ./my-next-app --out ../migrated-app   # shortcut into the same goal
-```
-
-La guía completa: formas de entrada (ruta/URL/descripción), expedientes `--emit`,
-Modo plan versus automático, controles de ejecución, credenciales, enlaces profundos de escritorio y
-Exportaciones de paquetes `@agent-native/migrate`: vive en
-[Agent-Native Code UI → Migrating to Agent-Native](/docs/code-agents-ui#migrate).
-
-> [!NOTE]
-> Se ha eliminado la aplicación de detalles `migration` oculta heredada. Utilice el código
-> espacio de trabajo, la pestaña Código de escritorio o un dossier emitido como compatible
-> superficies.

package/corpus/core/docs/content/locales/fr-FR/migration-workbench.mdx

@@ -1,76 +0,0 @@
----
-title: "Migration vers Agent-Native (/migrate)"
-description: "La migration est un objectif /migrate intégré dans l'espace de travail Code Agent-Native, et non une application distincte. Voir le code Agent-Native UI pour le guide complet."
----
-
-# Migration vers Agent-Native (/migrate)
-
-La migration n'est **pas un produit ou un modèle distinct** : il s'agit du produit intégré
-Objectif `/migrate` dans l'espace de travail [Agent-Native Code](/docs/code-agents-ui).
-Il s'exécute comme une session de code normale que vous pouvez reprendre, attacher, inspecter et arrêter.
-
-<Diagram id="doc-block-pw3ptd" title="/migrate est une session de code, pas une application distincte" summary={"Un chemin, URL, ou une description entre ; l'exécution partage le même magasin, la même transcription et les mêmes contrôles que toutes les autres sessions de code et peut émettre un dossier portable."}>
-
-```html
-<div class="diagram-migrate">
-  <div class="diagram-col">
-    <div class="diagram-pill">./local-app</div>
-    <div class="diagram-pill">https://example.com</div>
-    <div class="diagram-pill">--describe \"...\"</div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center" data-rough>
-    <span class="diagram-pill accent">/migrate goal</span
-    ><small class="diagram-muted"
-      >même store · transcription · contrôles d’exécution</small
-    >
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-col">
-    <div class="diagram-box" data-rough>App migrée</div>
-    <div class="diagram-pill ok">--emit dossier</div>
-  </div>
-</div>
-```
-
-```css
-.diagram-migrate {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  flex-wrap: wrap;
-}
-.diagram-migrate .diagram-col {
-  display: flex;
-  flex-direction: column;
-  gap: 8px;
-}
-.diagram-migrate .diagram-arrow {
-  font-size: 22px;
-  line-height: 1;
-}
-.diagram-migrate .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
-```
-
-</Diagram>
-
-```bash
-npx @agent-native/core@latest code /migrate ./my-next-app --out ../migrated-app
-npx @agent-native/core@latest code /migrate https://example.com --describe "marketing site plus dashboard"
-npx @agent-native/core@latest migrate ./my-next-app --out ../migrated-app   # shortcut into the same goal
-```
-
-Le guide complet — formes d'entrée (chemin / URL / description), dossiers `--emit`,
-Mode Plan vs Auto, contrôles d'exécution, informations d'identification, liens profonds sur le bureau et
-Exportations de packages `@agent-native/migrate` – réside dans
-[Agent-Native Code UI → Migrating to Agent-Native](/docs/code-agents-ui#migrate).
-
-> [!NOTE]
-> L'ancienne application de détails cachée `migration` a été supprimée. Utilisez le code
-> espace de travail, l'onglet Desktop Code ou un dossier émis comme pris en charge
-> surfaces.