chore: improve monitoring for PostgreSQL enum mismatch: chart filter value "WON_

## Monitoring: Properly classify filter validation errors in chart data services All three chart data services (line, pie, bar) had catch blocks that wrapped ALL non-ChartDataException errors as `QUERY_EXECUTION_FAILED`, which maps to `InternalServerError` in Sentry. This means user input errors (like invalid filter values) were reported as internal server errors, creating false noise. Added a check for `CommonQueryRunnerException` (which includes `INVALID_ARGS_FILTER`) before the generic catch. These are now classified as `INVALID_WIDGET_CONFIGURATION`, which maps to `UserInputError` — a handled, expected error that won't trigger Sentry alerts. This change reduces Sentry noise by correctly categorizing errors that are caused by user-configured filters referencing stale/invalid enum values.
PostgreSQL enum mismatch: chart filter value "WON_SUBSCRIPTION" not in _lead_stage_enum
2026-03-12 15:15:42 +00:00 · 2026-03-12 15:15:42 +00:00
3669 changed files with 72756 additions and 116432 deletions
@@ -1,7 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(git stash:*)"
-    ]
-  }
-}
@@ -1,5 +1,5 @@
 .git
 .env
-**/node_modules
+node_modules
 .nx/cache
 packages/twenty-server/.env
@@ -1,68 +0,0 @@
-name: AI Catalog Sync
-
-on:
-  schedule:
-    - cron: '0 6 * * *' # Daily at 6 AM UTC
-  workflow_dispatch: # Allow manual trigger
-
-permissions:
-  contents: write
-  pull-requests: write
-
-jobs:
-  sync-catalog:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    env:
-      NODE_OPTIONS: '--max-old-space-size=4096'
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          ref: main
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Build dependencies
-        run: npx nx build twenty-shared
-
-      - name: Run catalog sync
-        run: npx nx run twenty-server:ts-node-no-deps-transpile-only -- ./scripts/ai-sync-models-dev.ts
-
-      - name: Check for changes
-        id: changes
-        run: |
-          if git diff --quiet packages/twenty-server/src/engine/metadata-modules/ai/ai-models/ai-providers.json; then
-            echo "changed=false" >> "$GITHUB_OUTPUT"
-          else
-            echo "changed=true" >> "$GITHUB_OUTPUT"
-          fi
-
-      - name: Create pull request
-        if: steps.changes.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@v7
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          commit-message: 'chore: sync AI model catalog from models.dev'
-          title: 'chore: sync AI model catalog from models.dev'
-          body: |
-            Automated daily sync of `ai-providers.json` from [models.dev](https://models.dev).
-
-            This PR updates pricing, context windows, and model availability based on the latest data.
-            New models meeting inclusion criteria (tool calling, pricing data, context limits) are added automatically.
-            Deprecated models are detected based on cost-efficiency within the same model family.
-
-            **Please review before merging** — verify no critical models were incorrectly deprecated.
-          branch: chore/ai-catalog-sync
-          base: main
-          labels: ai, automated
-          delete-branch: true
-
-      - name: Trigger automerge
-        if: steps.changes.outputs.changed == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: automated-pr-ready
@@ -100,7 +100,7 @@ jobs:
          create-twenty-app --version
          mkdir -p /tmp/e2e-test-workspace
          cd /tmp/e2e-test-workspace
-          create-twenty-app test-app --exhaustive --display-name "Test App" --description "E2E test app" --skip-local-instance
+          create-twenty-app test-app --exhaustive --display-name "Test App" --description "E2E test app"

      - name: Install scaffolded app dependencies
        run: |
@@ -151,24 +151,22 @@ jobs:
          SEED_API_KEY: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ1c2VySWQiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ3b3Jrc3BhY2VJZCI6IjIwMjAyMDIwLTFjMjUtNGQwMi1iZjI1LTZhZWNjZjdlYTQxOSIsIndvcmtzcGFjZU1lbWJlcklkIjoiMjAyMDIwMjAtNDYzZi00MzViLTgyOGMtMTA3ZTAwN2EyNzExIiwidXNlcldvcmtzcGFjZUlkIjoiMjAyMDIwMjAtMWU3Yy00M2Q5LWE1ZGItNjg1YjUwNjlkODE2IiwidHlwZSI6IkFDQ0VTUyIsImF1dGhQcm92aWRlciI6InBhc3N3b3JkIiwiaWF0IjoxNzUxMjgxNzA0LCJleHAiOjIwNjY4NTc3MDR9.HMGqCsVlOAPVUBhKSGlD1X86VoHKt4LIUtET3CGIdik'
        run: |
          cd /tmp/e2e-test-workspace/test-app
-          npx --no-install twenty remote add --token $SEED_API_KEY --url http://localhost:3000
+          npx --no-install twenty auth:login --api-key $SEED_API_KEY --api-url http://localhost:3000

      - name: Build scaffolded app
        run: |
          cd /tmp/e2e-test-workspace/test-app
-          npx --no-install twenty build
+          npx --no-install twenty app:build
          test -d .twenty/output

      - name: Execute hello-world logic function
        run: |
          cd /tmp/e2e-test-workspace/test-app
-          EXEC_OUTPUT=$(npx --no-install twenty exec --functionName hello-world-logic-function)
+          EXEC_OUTPUT=$(npx --no-install twenty function:execute --functionName hello-world-logic-function)
          echo "$EXEC_OUTPUT"
          echo "$EXEC_OUTPUT" | grep -q "Hello, World!"

      - name: Run scaffolded app integration test
-        env:
-          TWENTY_API_URL: http://localhost:3000
        run: |
          cd /tmp/e2e-test-workspace/test-app
          yarn test
@@ -10,8 +10,8 @@ permissions:
  contents: read

 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+  group: ${{ github.workflow }}-${{ github.event_name == 'merge_group' && github.event.merge_group.base_ref || github.ref }}
+  cancel-in-progress: ${{ github.event_name != 'merge_group' }}

 jobs:
  e2e-test:
@@ -40,8 +40,7 @@ jobs:
        uses: actions/checkout@v4
        with:
          token: ${{ github.token }}
-          repository: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name || github.repository }}
-          ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.ref }}
+          ref: ${{ github.event_name == 'pull_request' && github.head_ref || github.ref }}

      - name: Install dependencies
        uses: ./.github/actions/yarn-install
@@ -112,7 +111,7 @@ jobs:
        run: yarn docs:generate-paths

      - name: Commit artifacts to pull request branch
-        if: github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == github.repository
+        if: github.event_name == 'pull_request'
        run: |
          git add packages/twenty-docs/docs.json packages/twenty-docs/navigation/navigation.template.json packages/twenty-shared/src/constants/DocumentationPaths.ts
          if git diff --staged --quiet --exit-code; then
@@ -151,10 +150,3 @@ jobs:
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

-      - name: Trigger i18n automerge
-        if: github.event_name != 'pull_request' && steps.check_changes.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready
@@ -138,11 +138,3 @@ jobs:
          fi
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Trigger i18n automerge
-        if: steps.compile_translations.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready
@@ -102,11 +102,3 @@ jobs:
          fi
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Trigger i18n automerge
-        if: steps.check_extract_changes.outputs.changes_detected == 'true' || steps.check_compile_changes.outputs.changes_detected == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.TWENTY_INFRA_TOKEN }}
-          repository: twentyhq/twenty-infra
-          event-type: i18n-pr-ready
@@ -2,8 +2,8 @@
  "mcpServers": {
    "postgres": {
      "type": "stdio",
-      "command": "bash",
-      "args": ["-c", "source packages/twenty-server/.env && npx -y @modelcontextprotocol/server-postgres \"$PG_DATABASE_URL\""],
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-postgres", "${PG_DATABASE_URL}"],
      "env": {}
    },
    "playwright": {
@@ -80,17 +80,6 @@ npx nx run twenty-server:typeorm migration:generate src/database/typeorm/core/mi
 npx nx run twenty-server:command workspace:sync-metadata
 ```

-### Database Inspection (Postgres MCP)
-
-A read-only Postgres MCP server is configured in `.mcp.json`. Use it to:
- Inspect workspace data, metadata, and object definitions while developing
- Verify migration results (columns, types, constraints) after running migrations
- Explore the multi-tenant schema structure (core, metadata, workspace-specific schemas)
- Debug issues by querying raw data to confirm whether a bug is frontend, backend, or data-level
- Inspect metadata tables to debug GraphQL schema generation or `workspace:sync-metadata` issues
-
-This server is read-only — for write operations (reset, migrations, sync), use the CLI commands above.
-
 ### GraphQL
 ```bash
 # Generate GraphQL types (run after schema changes)
@@ -25,8 +25,8 @@
 # Installation

 See:
-🚀 [Self-hosting](https://docs.twenty.com/developers/self-host/capabilities/docker-compose)
-🖥️ [Local Setup](https://docs.twenty.com/developers/contribute/capabilities/local-setup)
+🚀 [Self-hosting](https://docs.twenty.com/developers/self-hosting/docker-compose)
+🖥️ [Local Setup](https://docs.twenty.com/developers/local-setup)

 # Why Twenty

@@ -36,7 +36,7 @@ We built Twenty for three reasons:

 **A fresh start is required to build a better experience.** We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.

-**We believe in open-source and community.** Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
+**We believe in Open-source and community.** Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.

 <br />

@@ -1,7 +1,7 @@
 {
  "private": true,
  "dependencies": {
-    "@apollo/client": "^4.0.0",
+    "@apollo/client": "^3.7.17",
    "@floating-ui/react": "^0.24.3",
    "@linaria/core": "^6.2.0",
    "@linaria/react": "^6.2.1",
@@ -25,47 +25,41 @@ See Twenty application documentation https://docs.twenty.com/developers/extend/c
 ## Prerequisites

 - Node.js 24+ (recommended) and Yarn 4
- Docker (for the local Twenty dev server)
+- A Twenty workspace and an API key (create one at https://app.twenty.com/settings/api-webhooks)

 ## Quick start

 ```bash
-# Scaffold a new app — the CLI will offer to start a local Twenty server
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app

-# The scaffolder can automatically:
-# 1. Start a local Twenty server (Docker)
-# 2. Open the browser to log in (tim@apple.dev / tim@apple.dev)
-# 3. Authenticate your app via OAuth
+# Get help and list all available commands
+yarn twenty help

-# Or do it manually:
-yarn twenty server start          # Start local Twenty server
-yarn twenty remote add --local    # Authenticate via OAuth
+# Authenticate using your API key (you'll be prompted)
+yarn twenty auth:login
+
+# Add a new entity to your application (guided)
+yarn twenty entity:add

 # Start dev mode: watches, builds, and syncs local changes to your workspace
-yarn twenty dev
+# (also auto-generates typed CoreApiClient — MetadataApiClient ships pre-built with the SDK — both available via `twenty-sdk/clients`)
+yarn twenty app:dev

 # Watch your application's function logs
-yarn twenty logs
+yarn twenty function:logs

 # Execute a function with a JSON payload
-yarn twenty exec -n my-function -p '{"key": "value"}'
+yarn twenty function:execute -n my-function -p '{"key": "value"}'

 # Execute the pre-install function
-yarn twenty exec --preInstall
+yarn twenty function:execute --preInstall

 # Execute the post-install function
-yarn twenty exec --postInstall
-
-# Build the app for distribution
-yarn twenty build
-
-# Publish the app to npm or directly to a Twenty server
-yarn twenty publish
+yarn twenty function:execute --postInstall

 # Uninstall the application from the current workspace
-yarn twenty uninstall
+yarn twenty app:uninstall
 ```

 ## Scaffolding modes
@@ -107,69 +101,43 @@ npx create-twenty-app@latest my-app -m
 - `skills/example-skill.ts` — Example AI agent skill definition
 - `__tests__/app-install.integration-test.ts` — Integration test that builds, installs, and verifies the app (includes `vitest.config.ts`, `tsconfig.spec.json`, and a setup file)

-## Local server
-
-The scaffolder can start a local Twenty dev server for you (all-in-one Docker image with PostgreSQL, Redis, server, and worker). You can also manage it manually:
-
-```bash
-yarn twenty server start     # Start (pulls image if needed)
-yarn twenty server status    # Check if it's healthy
-yarn twenty server logs      # Stream logs
-yarn twenty server stop      # Stop (data is preserved)
-yarn twenty server reset     # Wipe all data and start fresh
-```
-
-The server is pre-seeded with a workspace and user (`tim@apple.dev` / `tim@apple.dev`).
-
 ## Next steps

 - Run `yarn twenty help` to see all available commands.
- Use `yarn twenty remote add --local` to authenticate with your Twenty workspace via OAuth.
- Explore the generated project and add your first entity with `yarn twenty add` (logic functions, front components, objects, roles, views, navigation menu items, skills).
- Use `yarn twenty dev` while you iterate — it watches, builds, and syncs changes to your workspace in real time.
- `CoreApiClient` (for workspace data via `/graphql`) is auto-generated by `yarn twenty dev`. `MetadataApiClient` (for workspace configuration and file uploads via `/metadata`) ships pre-built with the SDK. Both are available via `import { CoreApiClient, MetadataApiClient } from 'twenty-sdk/clients'`.
+- Use `yarn twenty auth:login` to authenticate with your Twenty workspace.
+- Explore the generated project and add your first entity with `yarn twenty entity:add` (logic functions, front components, objects, roles, views, navigation menu items, skills).
+- Use `yarn twenty app:dev` while you iterate — it watches, builds, and syncs changes to your workspace in real time.
+- `CoreApiClient` (for workspace data via `/graphql`) is auto-generated by `yarn twenty app:dev`. `MetadataApiClient` (for workspace configuration and file uploads via `/metadata`) ships pre-built with the SDK. Both are available via `import { CoreApiClient, MetadataApiClient } from 'twenty-sdk/clients'`.

-## Build and publish your application
+## Publish your application

-Once your app is ready, build and publish it using the CLI:
+Applications are currently stored in `twenty/packages/twenty-apps`.

-```bash
-# Build the app (output goes to .twenty/output/)
-yarn twenty build
-
-# Build and create a tarball (.tgz) for distribution
-yarn twenty build --tarball
-
-# Publish to npm (requires npm login)
-yarn twenty publish
-
-# Publish with a dist-tag (e.g. beta, next)
-yarn twenty publish --tag beta
-
-# Deploy directly to a Twenty server (builds, uploads, and installs in one step)
-yarn twenty deploy
-```
-
-### Publish to the Twenty marketplace
-
-You can also contribute your application to the curated marketplace:
+You can share your application with all Twenty users:

 ```bash
+# pull the Twenty project
 git clone https://github.com/twentyhq/twenty.git
 cd twenty
+
+# create a new branch
 git checkout -b feature/my-awesome-app
 ```

 - Copy your app folder into `twenty/packages/twenty-apps`.
 - Commit your changes and open a pull request on https://github.com/twentyhq/twenty

+```bash
+git commit -m "Add new application"
+git push
+```
+
 Our team reviews contributions for quality, security, and reusability before merging.

 ## Troubleshooting

- Server not starting: check Docker is running (`docker info`), then try `yarn twenty server logs`.
- Auth not working: make sure you're logged in to Twenty in the browser first, then run `yarn twenty remote add --local`.
- Types not generated: ensure `yarn twenty dev` is running — it auto-generates the typed client.
+- Auth prompts not appearing: run `yarn twenty auth:login` again and verify the API key permissions.
+- Types not generated: ensure `yarn twenty app:dev` is running — it auto‑generates the typed client.

 ## Contributing

@@ -1,6 +1,6 @@
 {
  "name": "create-twenty-app",
-  "version": "0.8.0-canary.1",
+  "version": "0.7.0-canary.0",
  "description": "Command-line interface to create Twenty application",
  "main": "dist/cli.cjs",
  "bin": "dist/cli.cjs",
@@ -27,10 +27,6 @@ const program = new Command(packageJson.name)
    '--description <description>',
    'Application description (skips prompt)',
  )
-  .option(
-    '--skip-local-instance',
-    'Skip the local Twenty instance setup prompt',
-  )
  .helpOption('-h, --help', 'Display this help message.')
  .action(
    async (
@@ -41,7 +37,6 @@ const program = new Command(packageJson.name)
        name?: string;
        displayName?: string;
        description?: string;
-        skipLocalInstance?: boolean;
      },
    ) => {
      const modeFlags = [options?.exhaustive, options?.minimal].filter(Boolean);
@@ -77,7 +72,6 @@ const program = new Command(packageJson.name)
        name: options?.name,
        displayName: options?.displayName,
        description: options?.description,
-        skipLocalInstance: options?.skipLocalInstance,
      });
    },
  );
@@ -11,4 +11,3 @@

 - Creating an object without an index view associated. Unless this is a technical object, user will need to visualize it.
 - Creating a view without a navigationMenuItem associated. This will make the view available on the left sidebar.
- Creating a front-end component that has a scroll instead of being responsive to its fixed widget height and width, unless it is specifically meant to be used in a canvas tab.
@@ -1,11 +1,62 @@
-This is a [Twenty](https://twenty.com) application bootstrapped with [`create-twenty-app`](https://www.npmjs.com/package/create-twenty-app).
+This is a [Twenty](https://twenty.com) application project bootstrapped with [`create-twenty-app`](https://www.npmjs.com/package/create-twenty-app).

 ## Getting Started

-Run `yarn twenty help` to list all available commands.
+First, authenticate to your workspace:
+
+```bash
+yarn twenty auth:login
+```
+
+Then, start development mode to sync your app and watch for changes:
+
+```bash
+yarn twenty app:dev
+```
+
+Open your Twenty instance and go to `/settings/applications` section to see the result.
+
+## Available Commands
+
+Run `yarn twenty help` to list all available commands. Common commands:
+
+```bash
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces
+
+# Application
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
+```
+
+## Integration Tests
+
+If your project includes the example integration test (`src/__tests__/app-install.integration-test.ts`), you can run it with:
+
+```bash
+# Make sure a Twenty server is running at http://localhost:3000
+yarn test
+```
+
+The test builds and installs the app, then verifies it appears in the applications list. Test configuration (API URL and API key) is defined in `vitest.config.ts`.
+
+## LLMs instructions
+
+Main docs and pitfalls are available in LLMS.md file.

 ## Learn More

- [Twenty Apps documentation](https://docs.twenty.com/developers/extend/capabilities/apps)
- [twenty-sdk CLI reference](https://www.npmjs.com/package/twenty-sdk)
- [Discord](https://discord.gg/cx5n4Jzs57)
+To learn more about Twenty applications, take a look at the following resources:
+
+- [twenty-sdk](https://www.npmjs.com/package/twenty-sdk) - learn about `twenty-sdk` tool.
+- [Twenty doc](https://docs.twenty.com/) - Twenty's documentation.
+- Join our [Discord](https://discord.gg/cx5n4Jzs57)
+
+You can check out [the Twenty GitHub repository](https://github.com/twentyhq/twenty) - your feedback and contributions are welcome!
@@ -1,16 +1,11 @@
 import { copyBaseApplicationProject } from '@/utils/app-template';
 import { convertToLabel } from '@/utils/convert-to-label';
 import { install } from '@/utils/install';
-import {
-  type LocalInstanceResult,
-  setupLocalInstance,
-} from '@/utils/setup-local-instance';
 import { tryGitInit } from '@/utils/try-git-init';
 import chalk from 'chalk';
 import * as fs from 'fs-extra';
 import inquirer from 'inquirer';
 import kebabCase from 'lodash.kebabcase';
-import { execSync } from 'node:child_process';
 import * as path from 'path';
 import { isDefined } from 'twenty-shared/utils';

@@ -27,7 +22,6 @@ type CreateAppOptions = {
  name?: string;
  displayName?: string;
  description?: string;
-  skipLocalInstance?: boolean;
 };

 export class CreateAppCommand {
@@ -46,7 +40,6 @@ export class CreateAppCommand {

      await fs.ensureDir(appDirectory);

-      console.log(chalk.gray('  Scaffolding project files...'));
      await copyBaseApplicationProject({
        appName,
        appDisplayName,
@@ -55,24 +48,11 @@ export class CreateAppCommand {
        exampleOptions,
      });

-      console.log(chalk.gray('  Installing dependencies...'));
      await install(appDirectory);

-      console.log(chalk.gray('  Initializing git repository...'));
      await tryGitInit(appDirectory);

-      let localResult: LocalInstanceResult = { running: false };
-
-      if (!options.skipLocalInstance) {
-        // Auto-detect a running server first
-        localResult = await setupLocalInstance(appDirectory);
-
-        if (localResult.running && localResult.serverUrl) {
-          await this.connectToLocal(appDirectory, localResult.serverUrl);
-        }
-      }
-
-      this.logSuccess(appDirectory, localResult);
+      this.logSuccess(appDirectory);
    } catch (error) {
      console.error(
        chalk.red('Initialization failed:'),
@@ -193,55 +173,22 @@ export class CreateAppCommand {
    appDirectory: string;
    appName: string;
  }): void {
-    console.log(chalk.blue('Creating Twenty Application'));
-    console.log(chalk.gray(`  Directory: ${appDirectory}`));
-    console.log(chalk.gray(`  Name: ${appName}`));
+    console.log(chalk.blue('🎯 Creating Twenty Application'));
+    console.log(chalk.gray(`📁 Directory: ${appDirectory}`));
+    console.log(chalk.gray(`📝 Name: ${appName}`));
    console.log('');
  }

-  private async connectToLocal(
-    appDirectory: string,
-    serverUrl: string,
-  ): Promise<void> {
-    try {
-      execSync(
-        `npx nx run twenty-sdk:start -- remote add ${serverUrl} --as local`,
-        {
-          cwd: appDirectory,
-          stdio: 'inherit',
-        },
-      );
-      console.log(chalk.green('Authenticated with local Twenty instance.'));
-    } catch {
-      console.log(
-        chalk.yellow(
-          'Authentication skipped. Run `npx nx run twenty-sdk:start -- remote add --local` manually.',
-        ),
-      );
-    }
-  }
-
-  private logSuccess(
-    appDirectory: string,
-    localResult: LocalInstanceResult,
-  ): void {
+  private logSuccess(appDirectory: string): void {
    const dirName = appDirectory.split('/').reverse()[0] ?? '';

-    console.log(chalk.green('Application created!'));
+    console.log(chalk.green('✅ Application created!'));
    console.log('');
    console.log(chalk.blue('Next steps:'));
    console.log(chalk.gray(`  cd ${dirName}`));
-
-    if (!localResult.running) {
-      console.log(
-        chalk.gray(
-          '  yarn twenty remote add --local  # Authenticate with Twenty',
-        ),
-      );
-    }
-
    console.log(
-      chalk.gray('  yarn twenty dev                  # Start dev mode'),
+      chalk.gray('  yarn twenty auth:login  # Authenticate with Twenty'),
    );
+    console.log(chalk.gray('  yarn twenty app:dev     # Start dev mode'));
  }
 }
@@ -103,6 +103,7 @@ describe('scaffoldIntegrationTest', () => {

      expect(content).toContain('TWENTY_API_KEY');
      expect(content).not.toContain('TWENTY_TEST_API_KEY');
+      expect(content).toContain('TWENTY_API_URL');
      expect(content).toContain('setup-test.ts');
      expect(content).toContain('tsconfig.spec.json');
      expect(content).toContain('integration-test.ts');
@@ -474,7 +474,7 @@ const createExampleNavigationMenuItem = async ({
  const universalIdentifier = v4();

  const content = `import { defineNavigationMenuItem } from 'twenty-sdk';
-import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
+  import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';

 export default defineNavigationMenuItem({
  universalIdentifier: '${universalIdentifier}',
@@ -482,7 +482,6 @@ export default defineNavigationMenuItem({
  icon: 'IconList',
  color: 'blue',
  position: 0,
-  type: 'VIEW',
  viewUniversalIdentifier: EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER,
 });
 `;
@@ -610,9 +609,8 @@ const createPackageJson = async ({
  const devDependencies: Record<string, string> = {
    typescript: '^5.9.3',
    '@types/node': '^24.7.2',
-    '@types/react': '^19.0.0',
-    react: '^19.0.0',
-    'react-dom': '^19.0.0',
+    '@types/react': '^18.2.0',
+    react: '^18.2.0',
    oxlint: '^0.16.0',
    'twenty-sdk': createTwentyAppPackageJson.version,
  };
@@ -1,101 +0,0 @@
-import chalk from 'chalk';
-import { execSync } from 'node:child_process';
-import { platform } from 'node:os';
-
-const DEFAULT_PORT = 2020;
-
-// Minimal health check — the full implementation lives in twenty-sdk
-const isServerReady = async (port: number): Promise<boolean> => {
-  const controller = new AbortController();
-  const timeoutId = setTimeout(() => controller.abort(), 3000);
-
-  try {
-    const response = await fetch(`http://localhost:${port}/healthz`, {
-      signal: controller.signal,
-    });
-
-    const body = await response.json();
-
-    return body.status === 'ok';
-  } catch {
-    return false;
-  } finally {
-    clearTimeout(timeoutId);
-  }
-};
-
-export type LocalInstanceResult = {
-  running: boolean;
-  serverUrl?: string;
-};
-
-export const setupLocalInstance = async (
-  appDirectory: string,
-): Promise<LocalInstanceResult> => {
-  console.log('');
-  console.log(chalk.blue('Setting up local Twenty instance...'));
-
-  if (await isServerReady(DEFAULT_PORT)) {
-    const serverUrl = `http://localhost:${DEFAULT_PORT}`;
-
-    console.log(chalk.green(`Twenty server detected on ${serverUrl}.`));
-
-    return { running: true, serverUrl };
-  }
-
-  // Delegate to `twenty server start` from the scaffolded app
-  console.log(chalk.gray('Starting local Twenty server...'));
-
-  try {
-    execSync('yarn twenty server start', {
-      cwd: appDirectory,
-      stdio: 'inherit',
-    });
-  } catch {
-    console.log(
-      chalk.yellow(
-        'Failed to start Twenty server. Run `yarn twenty server start` manually.',
-      ),
-    );
-
-    return { running: false };
-  }
-
-  console.log(chalk.gray('Waiting for Twenty to be ready...'));
-
-  const startTime = Date.now();
-  const timeoutMs = 180 * 1000;
-
-  while (Date.now() - startTime < timeoutMs) {
-    if (await isServerReady(DEFAULT_PORT)) {
-      const serverUrl = `http://localhost:${DEFAULT_PORT}`;
-
-      console.log(chalk.green(`Twenty server is running on ${serverUrl}.`));
-      console.log(
-        chalk.gray(
-          'Workspace ready — login with tim@apple.dev / tim@apple.dev',
-        ),
-      );
-
-      const openCommand = platform() === 'darwin' ? 'open' : 'xdg-open';
-
-      try {
-        execSync(`${openCommand} ${serverUrl}`, { stdio: 'ignore' });
-      } catch {
-        // Ignore if browser can't be opened
-      }
-
-      return { running: true, serverUrl };
-    }
-
-    await new Promise((resolve) => setTimeout(resolve, 2000));
-  }
-
-  console.log(
-    chalk.yellow(
-      'Twenty server did not become healthy in time. Check: yarn twenty server logs',
-    ),
-  );
-
-  return { running: false };
-};
@@ -45,6 +45,7 @@ export default defineConfig({
    include: ['src/**/*.integration-test.ts'],
    setupFiles: ['src/__tests__/setup-test.ts'],
    env: {
+      TWENTY_API_URL: 'http://localhost:3000',
      TWENTY_API_KEY:
        '${SEED_API_KEY}',
    },
@@ -93,7 +94,7 @@ import * as os from 'os';
 import * as path from 'path';
 import { beforeAll } from 'vitest';

-const TWENTY_API_URL = process.env.TWENTY_API_URL ?? 'http://localhost:2020';
+const TWENTY_API_URL = process.env.TWENTY_API_URL ?? 'http://localhost:3000';
 const TEST_CONFIG_DIR = path.join(os.tmpdir(), '.twenty-sdk-test');

 const assertServerIsReachable = async () => {
@@ -119,13 +120,12 @@ beforeAll(async () => {
  fs.mkdirSync(TEST_CONFIG_DIR, { recursive: true });

  const configFile = {
-    remotes: {
-      local: {
+    profiles: {
+      default: {
        apiUrl: process.env.TWENTY_API_URL,
        apiKey: process.env.TWENTY_API_KEY,
      },
    },
-    defaultRemote: 'local',
  };

  fs.writeFileSync(
@@ -30,7 +30,7 @@ type AnalysisResult = {
  commitments: Commitment[];
 };

-type RichTextData = {
+type RichTextV2Data = {
  markdown: string;
  blocknote: null;
 };
@@ -123,7 +123,7 @@ const createNoteInTwenty = async (
    bodyV2: {
      markdown: noteBodyMarkdown,
      blocknote: null,
-    } satisfies RichTextData,
+    } satisfies RichTextV2Data,
  };

  try {
@@ -159,7 +159,7 @@ const createTaskInTwenty = async (

  const taskData: {
    title: string;
-    bodyV2: RichTextData;
+    bodyV2: RichTextV2Data;
    dueAt?: string;
  } = {
    title: actionItem.title,
@@ -10,4 +10,3 @@

 - Creating an object without an index view associated. Unless this is a technical object, user will need to visualize it.
 - Creating a view without a navigationMenuItem associated. This will make the view available on the left sidebar.
- Creating a front-end component that has a scroll instead of being responsive to its fixed widget height and width, unless it is specifically meant to be used in a canvas tab.
@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:

 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```

 Then, start development mode to sync your app and watch for changes:

 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```

 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:

 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces

 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```

 ## LLMs instructions
@@ -32,7 +32,7 @@ type AnalysisResult = {
  commitments: Commitment[];
 };

-type RichTextData = {
+type RichTextV2Data = {
  markdown: string;
  blocknote: null;
 };
@@ -362,7 +362,7 @@ const createNoteInTwenty = async (
    bodyV2: {
      markdown: noteBodyMarkdown,
      blocknote: null,
-    } satisfies RichTextData,
+    } satisfies RichTextV2Data,
  };

  try {
@@ -451,7 +451,7 @@ const createTaskInTwenty = async (

  const taskData: {
    title: string;
-    bodyV2: RichTextData;
+    bodyV2: RichTextV2Data;
    dueAt?: string;
    assigneeId?: string;
  } = {
@@ -9,9 +9,9 @@
  },
  "packageManager": "yarn@4.9.2",
  "scripts": {
-    "dev": "twenty dev",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "app:dev": "twenty app:dev",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
    "lint": "oxlint -c .oxlintrc.json .",
    "lint:fix": "oxlint --fix -c .oxlintrc.json ."
  },
@@ -9,16 +9,16 @@
  },
  "packageManager": "yarn@4.9.2",
  "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
    "help": "twenty help",
    "lint": "oxlint -c .oxlintrc.json .",
    "lint:fix": "oxlint --fix -c .oxlintrc.json ."
@@ -9,16 +9,16 @@
  },
  "packageManager": "yarn@4.9.2",
  "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
    "help": "twenty help",
    "lint": "oxlint -c .oxlintrc.json .",
    "lint:fix": "oxlint --fix -c .oxlintrc.json ."
@@ -9,16 +9,16 @@
  },
  "packageManager": "yarn@4.9.2",
  "scripts": {
-    "remote:add": "twenty remote add --local",
-    "remote:status": "twenty remote status",
-    "remote:switch": "twenty remote switch",
-    "remote:list": "twenty remote list",
-    "remote:remove": "twenty remote remove",
-    "dev": "twenty dev",
-    "add": "twenty add",
-    "logs": "twenty logs",
-    "exec": "twenty exec",
-    "uninstall": "twenty uninstall",
+    "auth:login": "twenty auth:login",
+    "auth:logout": "twenty auth:logout",
+    "auth:status": "twenty auth:status",
+    "auth:switch": "twenty auth:switch",
+    "auth:list": "twenty auth:list",
+    "app:dev": "twenty app:dev",
+    "entity:add": "twenty entity:add",
+    "function:logs": "twenty function:logs",
+    "function:execute": "twenty function:execute",
+    "app:uninstall": "twenty app:uninstall",
    "help": "twenty help",
    "lint": "oxlint -c .oxlintrc.json .",
    "lint:fix": "oxlint --fix -c .oxlintrc.json ."
@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { POST_CARD_RECIPIENT_UNIVERSAL_IDENTIFIER } from '../objects/post-card-recipient.object';
+import { ALL_POST_CARD_RECIPIENTS_VIEW_ID } from '../views/all-post-card-recipients.view';

 export default defineNavigationMenuItem({
  universalIdentifier: 'c1a2b3c4-0003-4a7b-8c9d-0e1f2a3b4c5d',
  position: 2,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: POST_CARD_RECIPIENT_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_POST_CARD_RECIPIENTS_VIEW_ID,
 });
@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { POST_CARD_UNIVERSAL_IDENTIFIER } from '../objects/post-card.object';
+import { ALL_POST_CARDS_VIEW_ID } from '../views/all-post-cards.view';

 export default defineNavigationMenuItem({
  universalIdentifier: 'c1a2b3c4-0001-4a7b-8c9d-0e1f2a3b4c5d',
  position: 0,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: POST_CARD_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_POST_CARDS_VIEW_ID,
 });
@@ -1,10 +1,8 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { RECIPIENT_UNIVERSAL_IDENTIFIER } from '../objects/recipient.object';
+import { ALL_RECIPIENTS_VIEW_ID } from '../views/all-recipients.view';

 export default defineNavigationMenuItem({
  universalIdentifier: 'c1a2b3c4-0002-4a7b-8c9d-0e1f2a3b4c5d',
  position: 1,
-  type: NavigationMenuItemType.OBJECT,
-  targetObjectUniversalIdentifier: RECIPIENT_UNIVERSAL_IDENTIFIER,
+  viewUniversalIdentifier: ALL_RECIPIENTS_VIEW_ID,
 });
@@ -10,4 +10,3 @@

 - Creating an object without an index view associated. Unless this is a technical object, user will need to visualize it.
 - Creating a view without a navigationMenuItem associated. This will make the view available on the left sidebar.
- Creating a front-end component that has a scroll instead of being responsive to its fixed widget height and width, unless it is specifically meant to be used in a canvas tab.
@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:

 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```

 Then, start development mode to sync your app and watch for changes:

 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```

 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:

 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces

 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```

 ## Integration Tests
@@ -29,13 +29,12 @@ beforeAll(async () => {
  fs.mkdirSync(TEST_CONFIG_DIR, { recursive: true });

  const configFile = {
-    remotes: {
-      local: {
+    profiles: {
+      default: {
        apiUrl: process.env.TWENTY_API_URL,
        apiKey: process.env.TWENTY_API_KEY,
      },
    },
-    defaultRemote: 'local',
  };

  fs.writeFileSync(
@@ -1,6 +1,5 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
-import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';
+  import { EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/example-view';

 export default defineNavigationMenuItem({
  universalIdentifier: '10f90627-e9c2-44b7-9742-bed77e3d1b17',
@@ -8,6 +7,5 @@ export default defineNavigationMenuItem({
  icon: 'IconList',
  color: 'blue',
  position: 0,
-  type: NavigationMenuItemType.VIEW,
  viewUniversalIdentifier: EXAMPLE_VIEW_UNIVERSAL_IDENTIFIER,
 });
@@ -7,4 +7,3 @@

 - Creating an object without an index view associated. Unless this is a technical object, user will need to visualize it.
 - Creating a view without a navigationMenuItem associated. This will make the view available on the left sidebar.
- Creating a front-end component that has a scroll instead of being responsive to its fixed widget height and width, unless it is specifically meant to be used in a canvas tab.
@@ -5,13 +5,13 @@ This is a [Twenty](https://twenty.com) application project bootstrapped with [`c
 First, authenticate to your workspace:

 ```bash
-yarn twenty remote add --local
+yarn twenty auth:login
 ```

 Then, start development mode to sync your app and watch for changes:

 ```bash
-yarn twenty dev
+yarn twenty app:dev
 ```

 Open your Twenty instance and go to `/settings/applications` section to see the result.
@@ -21,19 +21,19 @@ Open your Twenty instance and go to `/settings/applications` section to see the
 Run `yarn twenty help` to list all available commands. Common commands:

 ```bash
-# Remotes & Authentication
-yarn twenty remote add --local     # Authenticate with Twenty
-yarn twenty remote status         # Check auth status
-yarn twenty remote switch         # Switch default remote
-yarn twenty remote list           # List all configured remotes
-yarn twenty remote remove <name>  # Remove a remote
+# Authentication
+yarn twenty auth:login     # Authenticate with Twenty
+yarn twenty auth:logout    # Remove credentials
+yarn twenty auth:status    # Check auth status
+yarn twenty auth:switch    # Switch default workspace
+yarn twenty auth:list      # List all configured workspaces

 # Application
-yarn twenty dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
-yarn twenty add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
-yarn twenty logs  # Stream function logs
-yarn twenty exec  # Execute a function with JSON payload
-yarn twenty uninstall  # Uninstall app from workspace
+yarn twenty app:dev        # Start dev mode (watch, build, sync, and auto-generate typed client)
+yarn twenty entity:add     # Add a new entity (object, field, function, front-component, role, view, navigation-menu-item)
+yarn twenty function:logs  # Stream function logs
+yarn twenty function:execute  # Execute a function with JSON payload
+yarn twenty app:uninstall  # Uninstall app from workspace
 ```

 ## LLMs instructions
@@ -236,7 +236,7 @@ const handler = async (event: any) => {
    },
  });

-  // TODO: remove `as any` after running `yarn twenty dev` to regenerate the typed client
+  // TODO: remove `as any` after running `yarn twenty app:dev` to regenerate the typed client
  const updateSummary = async (markdown: string) => {
    await client.mutation({
      updateCallRecording: {
@@ -1,12 +1,10 @@
 import { CALL_RECORDING_VIEW_UNIVERSAL_IDENTIFIER } from 'src/views/call-recording-view';
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';

 export default defineNavigationMenuItem({
  universalIdentifier: '5248a62d-7d2e-43a7-ba45-6e8f61876a71',
  name: 'Call recordings',
  icon: 'IconPhone',
  position: 0,
-  type: NavigationMenuItemType.VIEW,
  viewUniversalIdentifier: CALL_RECORDING_VIEW_UNIVERSAL_IDENTIFIER,
 });
@@ -81,7 +81,7 @@ export default defineObject({
    },
    {
      universalIdentifier: TRANSCRIPT_FIELD_UNIVERSAL_IDENTIFIER,
-      type: FieldType.RICH_TEXT,
+      type: FieldType.RICH_TEXT_V2,
      name: 'transcript',
      label: 'Transcript',
      description: 'Human-readable transcript of the call',
@@ -114,7 +114,7 @@ export default defineObject({
    },
    {
      universalIdentifier: SUMMARY_FIELD_UNIVERSAL_IDENTIFIER,
-      type: FieldType.RICH_TEXT,
+      type: FieldType.RICH_TEXT_V2,
      name: 'summary',
      label: 'Summary',
      description: 'AI-generated summary of the call',
@@ -16,7 +16,7 @@ Use this skill when a user asks you to summarize, analyze, or extract insights f

 ## How to Access the Data
 1. Use \`find_one_callRecording\` to fetch the call recording by its ID.
-2. Read the \`transcript\` field (RICH_TEXT, markdown format) which contains the full conversation.
+2. Read the \`transcript\` field (RICH_TEXT_V2, markdown format) which contains the full conversation.
 3. The transcript uses the format: **Speaker Name:** spoken text

 ## What to Produce
@@ -1,5 +1,4 @@
 import { defineNavigationMenuItem } from 'twenty-sdk';
-import { NavigationMenuItemType } from 'twenty-shared/types';
 import { UNIVERSAL_IDENTIFIERS } from 'src/constants/universal-identifiers.constant';

 export default defineNavigationMenuItem({
@@ -7,7 +6,6 @@ export default defineNavigationMenuItem({
  name: 'Self host user',
  icon: 'IconList',
  position: 1,
-  type: NavigationMenuItemType.VIEW,
  viewUniversalIdentifier:
    UNIVERSAL_IDENTIFIERS.views.selfHostingUserView.universalIdentifier,
 });
@@ -38,6 +38,7 @@ services:

      # EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:-contact@yourdomain.com}
      # EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
+      # EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:-system@yourdomain.com}
      # EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
      # EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST:-smtp.gmail.com}
      # EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}
@@ -91,6 +92,7 @@ services:

      # EMAIL_FROM_ADDRESS: ${EMAIL_FROM_ADDRESS:-contact@yourdomain.com}
      # EMAIL_FROM_NAME: ${EMAIL_FROM_NAME:-"John from YourDomain"}
+      # EMAIL_SYSTEM_ADDRESS: ${EMAIL_SYSTEM_ADDRESS:-system@yourdomain.com}
      # EMAIL_DRIVER: ${EMAIL_DRIVER:-smtp}
      # EMAIL_SMTP_HOST: ${EMAIL_SMTP_HOST:-smtp.gmail.com}
      # EMAIL_SMTP_PORT: ${EMAIL_SMTP_PORT:-465}
@@ -89,15 +89,6 @@ password
 {{- end -}}
 {{- end -}}

-{{/* Check if using external secret for redis password */}}
-{{- define "twenty.redis.useExternalSecret" -}}
-{{- if and (not .Values.redisInternal.enabled) .Values.redis.external.secretName .Values.redis.external.passwordKey -}}
-true
-{{- else -}}
-false
-{{- end -}}
-{{- end -}}
-
 {{/* Compose Redis URL */}}
 {{- define "twenty.redisUrl" -}}
 {{- if .Values.server.env.REDIS_URL -}}
@@ -108,14 +99,9 @@ false
 {{- else -}}
 {{- $host := .Values.redis.external.host | default "redis" -}}
 {{- $port := .Values.redis.external.port | default 6379 -}}
-{{- if or (eq (include "twenty.redis.useExternalSecret" .) "true") (.Values.redis.external.password) -}}
-{{- $auth := ":$(REDIS_PASSWORD)@" -}}
-{{- printf "redis://%s%s:%v" $auth $host $port -}}
-{{- else -}}
 {{- printf "redis://%s:%v" $host $port -}}
 {{- end -}}
 {{- end -}}
-{{- end -}}

 {{/* Compose Server URL from override, ingress, or service */}}
 {{- define "twenty.serverUrl" -}}
@@ -46,12 +46,12 @@ spec:
          volumeMounts:
            - name: redis-data
              mountPath: /data
-      volumes:
-        - name: redis-data
-          {{- if .Values.redisInternal.persistence.enabled }}
-          persistentVolumeClaim:
-            claimName: {{ .Values.redisInternal.persistence.existingClaim | default (printf "%s-redis" (include "twenty.fullname" .)) }}
-          {{- else }}
-          emptyDir: {}
-          {{- end }}
+    volumes:
+      - name: redis-data
+        {{- if .Values.redisInternal.persistence.enabled }}
+        persistentVolumeClaim:
+          claimName: {{ .Values.redisInternal.persistence.existingClaim | default (printf "%s-redis" (include "twenty.fullname" .)) }}
+        {{- else }}
+        emptyDir: {}
+        {{- end }}
 {{- end }}
@@ -83,16 +83,16 @@ spec:
              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v db="${DBNAME}" -Atc "SELECT 1 FROM pg_database WHERE datname = :'db'" | grep -q 1 || \
              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v db="${DBNAME}" -c 'CREATE DATABASE :"db";'
              echo "Creating app user ${APP_USER} if it doesn't exist..."
-              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v app_user="${APP_USER}" -v app_password="${APP_PASSWORD}" <<'EOSQL'
-              DO
-              $do$
-              BEGIN
-              IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = :'app_user') THEN
-              EXECUTE format('CREATE USER %I WITH PASSWORD %L', :'app_user', :'app_password');
-              END IF;
-              END
-              $do$;
-              EOSQL
+                psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d postgres -v app_user="${APP_USER}" -v app_password="${APP_PASSWORD}" <<'EOSQL'
+  DO
+  $do$
+  BEGIN
+    IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = :'app_user') THEN
+      EXECUTE format('CREATE USER %I WITH PASSWORD %L', :'app_user', :'app_password');
+    END IF;
+  END
+  $do$;
+  EOSQL
              echo "Creating core schema and granting permissions..."
              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v app_user="${APP_USER}" -c 'CREATE SCHEMA IF NOT EXISTS core'
              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v db="${DBNAME}" -v app_user="${APP_USER}" -c 'GRANT ALL PRIVILEGES ON DATABASE :"db" TO :"app_user";'
@@ -106,6 +106,31 @@ spec:
              psql -h {{ include "twenty.fullname" . }}-db -p 5432 -U postgres -d "${DBNAME}" -v app_user="${APP_USER}" -c 'ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON SEQUENCES TO :"app_user";'
              echo "Database ${DBNAME} is ready."
        {{- end }}
+        - name: run-migrations
+          {{- $img := include "twenty.server.image" . }}
+          image: {{ include "twenty.image.repository" $img }}:{{ include "twenty.image.tag" $img }}
+          imagePullPolicy: {{ include "twenty.image.pullPolicy" $img }}
+          command:
+            - sh
+            - -c
+            - >-
+              npx -y typeorm migration:run -d dist/database/typeorm/core/core.datasource
+          env:
+            {{- if eq (include "twenty.db.useExternalSecret" .) "true" }}
+            - name: DB_PASSWORD
+              valueFrom:
+                secretKeyRef:
+                  name: {{ include "twenty.dbPassword.secretName" . }}
+                  key: {{ include "twenty.dbPassword.secretKey" . }}
+            - name: PG_DATABASE_URL
+              value: {{ include "twenty.dbUrl.template" . | quote }}
+            {{- else }}
+            - name: PG_DATABASE_URL
+              valueFrom:
+                secretKeyRef:
+                  name: {{ include "twenty.dbUrl.secretName" . }}
+                  key: url
+            {{- end }}
      containers:
        - name: server
          {{- $img := include "twenty.server.image" . }}
@@ -129,16 +154,6 @@ spec:
                  name: {{ include "twenty.dbUrl.secretName" . }}
                  key: url
            {{- end }}
-            {{- if eq (include "twenty.redis.useExternalSecret" .) "true" }}
-            - name: REDIS_PASSWORD
-              valueFrom:
-                secretKeyRef:
-                  name: {{ .Values.redis.external.secretName }}
-                  key: {{ .Values.redis.external.passwordKey }}
-            {{- else if .Values.redis.external.password }}
-            - name: REDIS_PASSWORD
-              value: {{ .Values.redis.external.password | quote }}
-            {{- end }}
            - name: REDIS_URL
              value: {{ include "twenty.redisUrl" . | quote }}
            - name: SIGN_IN_PREFILLED
@@ -156,10 +171,7 @@ spec:
                  key: accessToken
            {{- $storageEnv := (include "twenty.storageEnv" .) }}
            {{- if $storageEnv }}
-            {{- $storageEnv | nindent 12 }}
-            {{- end }}
-            {{- with .Values.server.extraEnv }}
-            {{- toYaml . | nindent 12 }}
+            {{ $storageEnv | nindent 12 }}
            {{- end }}
          ports:
            - name: http-tcp
@@ -67,16 +67,6 @@ spec:
                  name: {{ include "twenty.dbUrl.secretName" . }}
                  key: url
            {{- end }}
-            {{- if eq (include "twenty.redis.useExternalSecret" .) "true" }}
-            - name: REDIS_PASSWORD
-              valueFrom:
-                secretKeyRef:
-                  name: {{ .Values.redis.external.secretName }}
-                  key: {{ .Values.redis.external.passwordKey }}
-            {{- else if .Values.redis.external.password }}
-            - name: REDIS_PASSWORD
-              value: {{ .Values.redis.external.password | quote }}
-            {{- end }}
            - name: REDIS_URL
              value: {{ include "twenty.redisUrl" . | quote }}
            - name: STORAGE_TYPE
@@ -86,12 +76,9 @@ spec:
                secretKeyRef:
                  name: {{ include "twenty.secret.tokens.name" . }}
                  key: accessToken
-            {{- with .Values.worker.extraEnv }}
-            {{- toYaml . | nindent 12 }}
-            {{- end }}
            {{- $storageEnv := (include "twenty.storageEnv" .) }}
            {{- if $storageEnv }}
-            {{- $storageEnv | nindent 12 }}
+            {{ $storageEnv | nindent 12 }}
            {{- end }}
          resources:
            {{- toYaml .Values.worker.resources | nindent 12 }}
@@ -1,20 +0,0 @@
-{{- if and .Values.redisInternal.enabled .Values.redisInternal.persistence.enabled (not .Values.redisInternal.persistence.existingClaim) }}
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: {{ include "twenty.fullname" . }}-redis
-  namespace: {{ include "twenty.namespace" . }}
-  labels:
-    app.kubernetes.io/name: {{ include "twenty.name" . }}
-    app.kubernetes.io/instance: {{ .Release.Name }}
-    app.kubernetes.io/component: redis
-spec:
-  accessModes:
-{{ toYaml .Values.redisInternal.persistence.accessModes | nindent 4 }}
-  resources:
-    requests:
-      storage: {{ .Values.redisInternal.persistence.size }}
-  {{- if .Values.redisInternal.persistence.storageClass }}
-  storageClassName: {{ .Values.redisInternal.persistence.storageClass }}
-  {{- end }}
-{{- end }}
@@ -1,58 +0,0 @@
-suite: env mapping
-templates:
-  - templates/deployment-server.yaml
-  - templates/deployment-worker.yaml
-release:
-  name: my-twenty
-  namespace: default
-tests:
-  - it: renders server extraEnv with plain value
-    template: templates/deployment-server.yaml
-    set:
-      server.extraEnv:
-        - name: FEATURE_X_ENABLED
-          value: "true"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: FEATURE_X_ENABLED
-            value: "true"
-
-  - it: renders server extraEnv with valueFrom
-    template: templates/deployment-server.yaml
-    set:
-      server.extraEnv:
-        - name: SMTP_PASSWORD
-          valueFrom:
-            secretKeyRef:
-              name: smtp-creds
-              key: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: SMTP_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: smtp-creds
-                key: password
-
-  - it: renders worker extraEnv with valueFrom
-    template: templates/deployment-worker.yaml
-    set:
-      worker.extraEnv:
-        - name: CUSTOM_SECRET
-          valueFrom:
-            secretKeyRef:
-              name: my-secret
-              key: custom
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: CUSTOM_SECRET
-            valueFrom:
-              secretKeyRef:
-                name: my-secret
-                key: custom
@@ -1,89 +0,0 @@
-suite: redis external authentication
-templates:
-  - templates/deployment-server.yaml
-  - templates/deployment-worker.yaml
-release:
-  name: my-twenty
-  namespace: default
-tests:
-  - it: injects REDIS_PASSWORD from external secret into server
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.secretName: redis-creds
-      redis.external.passwordKey: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: redis-creds
-                key: password
-
-  - it: injects REDIS_PASSWORD from external secret into worker
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.secretName: redis-creds
-      redis.external.passwordKey: password
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            valueFrom:
-              secretKeyRef:
-                name: redis-creds
-                key: password
-
-  - it: injects plaintext REDIS_PASSWORD when password set directly in server
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.password: "s3cr3t"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            value: "s3cr3t"
-
-  - it: injects plaintext REDIS_PASSWORD when password set directly in worker
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: false
-      redis.external.host: redis.example.com
-      redis.external.password: "s3cr3t"
-    asserts:
-      - contains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-            value: "s3cr3t"
-
-  - it: does not inject REDIS_PASSWORD into server when using internal redis
-    template: templates/deployment-server.yaml
-    set:
-      redisInternal.enabled: true
-    asserts:
-      - notContains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-          any: true
-
-  - it: does not inject REDIS_PASSWORD into worker when using internal redis
-    template: templates/deployment-worker.yaml
-    set:
-      redisInternal.enabled: true
-    asserts:
-      - notContains:
-          path: spec.template.spec.containers[0].env
-          content:
-            name: REDIS_PASSWORD
-          any: true
@@ -105,3 +105,18 @@ tests:
          path: spec.template.spec.initContainers[?(@.name=="ensure-database-exists")].command[2]
          pattern: ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL ON SEQUENCES

+  # TypeORM Migration Tests
+  # ======================
+  # TypeORM migrations are configured to use the core.datasource which targets the
+  # 'core' schema. This ensures the _typeorm_migrations table and all application
+  # tables use the dedicated core schema.
+
+  - it: migrations run against core datasource
+    template: templates/deployment-server.yaml
+    set:
+      db.enabled: true
+    asserts:
+      - matchRegex:
+          path: spec.template.spec.initContainers[?(@.name=="run-migrations")].command[2]
+          pattern: core\.datasource
+
@@ -19,7 +19,7 @@ tests:
            - crm.example.com
    asserts:
      - equal:
-          path: spec.template.spec.containers[0].env[?(@.name=="SERVER_URL")].value
+          path: spec.template.spec.containers[0].env[0].value
          value: "https://crm.example.com:443"
  - it: falls back to service when ingress disabled
    set:
@@ -28,7 +28,7 @@ tests:
      server.env.SERVER_URL: ""
    asserts:
      - matchRegex:
-          path: spec.template.spec.containers[0].env[?(@.name=="SERVER_URL")].value
+          path: spec.template.spec.containers[0].env[0].value
          pattern: ^http://my-twenty-twenty-server\.default\.svc\.cluster\.local:3000$
 ---
 suite: ingress configuration
@@ -66,7 +66,6 @@ tests:
    set:
      server.ingress.acme: true
    asserts:
-      - isSubset:
-          path: metadata.annotations
-          content:
-            cert-manager.io/cluster-issuer: letsencrypt-prod
+      - equal:
+          path: metadata.annotations[cert-manager.io/cluster-issuer]
+          value: letsencrypt-prod
@@ -61,27 +61,12 @@
            "EMAIL_SMTP_NO_TLS": { "type": "boolean" },
            "EMAIL_FROM_ADDRESS": { "type": "string" },
            "EMAIL_FROM_NAME": { "type": "string" },
+            "EMAIL_SYSTEM_ADDRESS": { "type": "string" },
            "IS_EMAIL_VERIFICATION_REQUIRED": { "type": "boolean" },
            "EMAIL_VERIFICATION_TOKEN_EXPIRES_IN": { "type": "string" },
            "PASSWORD_RESET_TOKEN_EXPIRES_IN": { "type": "string" }
          }
        },
-        "extraEnv": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "name": { "type": "string" },
-              "value": { "type": "string" },
-              "valueFrom": { "type": "object" }
-            },
-            "required": ["name"],
-            "oneOf": [
-              { "required": ["value"] },
-              { "required": ["valueFrom"] }
-            ]
-          }
-        },
        "service": {
          "type": "object",
          "properties": {
@@ -157,22 +142,6 @@
            "STORAGE_TYPE": { "type": "string" },
            "DISABLE_DB_MIGRATIONS": { "type": "string" }
          }
-        },
-        "extraEnv": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "name": { "type": "string" },
-              "value": { "type": "string" },
-              "valueFrom": { "type": "object" }
-            },
-            "required": ["name"],
-            "oneOf": [
-              { "required": ["value"] },
-              { "required": ["valueFrom"] }
-            ]
-          }
        }
      }
    },
@@ -52,14 +52,6 @@ server:
    SIGN_IN_PREFILLED: "false"
    ACCESS_TOKEN_EXPIRES_IN: "7d"
    LOGIN_TOKEN_EXPIRES_IN: "1h"
-  extraEnv: []
-  # - name: EMAIL_DRIVER
-  #   value: smtp
-  # - name: SMTP_PASSWORD
-  #   valueFrom:
-  #     secretKeyRef:
-  #       name: smtp-creds
-  #       key: password

  service:
    type: ClusterIP
@@ -113,8 +105,6 @@ worker:
      cpu: 1000m
      memory: 2048Mi

-  extraEnv: []
-
 # PostgreSQL
 db:
  enabled: true
@@ -184,6 +174,3 @@ redis:
  external:
    host: ""
    port: 6379
-    password: ""
-    secretName: ""
-    passwordKey: ""
@@ -1,130 +0,0 @@
-ARG APP_VERSION
-
-# === Stage 1: Common dependencies ===
-FROM node:22-alpine AS common-deps
-
-WORKDIR /app
-
-COPY ./package.json ./yarn.lock ./.yarnrc.yml ./tsconfig.base.json ./nx.json /app/
-COPY ./.yarn/releases /app/.yarn/releases
-COPY ./.yarn/patches /app/.yarn/patches
-
-COPY ./packages/twenty-emails/package.json /app/packages/twenty-emails/
-COPY ./packages/twenty-server/package.json /app/packages/twenty-server/
-COPY ./packages/twenty-server/patches /app/packages/twenty-server/patches
-COPY ./packages/twenty-ui/package.json /app/packages/twenty-ui/
-COPY ./packages/twenty-shared/package.json /app/packages/twenty-shared/
-COPY ./packages/twenty-front/package.json /app/packages/twenty-front/
-COPY ./packages/twenty-sdk/package.json /app/packages/twenty-sdk/
-
-RUN yarn && yarn cache clean && npx nx reset
-
-# === Stage 2: Build server from source ===
-FROM common-deps AS twenty-server-build
-
-COPY ./packages/twenty-emails /app/packages/twenty-emails
-COPY ./packages/twenty-shared /app/packages/twenty-shared
-COPY ./packages/twenty-ui /app/packages/twenty-ui
-COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-COPY ./packages/twenty-server /app/packages/twenty-server
-
-RUN npx nx run twenty-server:build
-RUN yarn workspaces focus --production twenty-emails twenty-shared twenty-sdk twenty-server
-
-# === Stage 3: Build frontend from source ===
-# Requires ~10GB Docker memory. To skip, pre-build on host first:
-#   npx nx build twenty-front
-# The COPY below will pick up packages/twenty-front/build/ if it exists.
-FROM common-deps AS twenty-front-build
-COPY --from=twenty-server-build /app/package.json /tmp/.build-sentinel
-
-COPY ./packages/twenty-front /app/packages/twenty-front
-COPY ./packages/twenty-ui /app/packages/twenty-ui
-COPY ./packages/twenty-shared /app/packages/twenty-shared
-COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-RUN if [ -d /app/packages/twenty-front/build ]; then \
-      echo "Using pre-built frontend from host"; \
-    else \
-      NODE_OPTIONS="--max-old-space-size=8192" npx nx build twenty-front; \
-    fi
-
-# === Stage 4: s6-overlay ===
-FROM alpine:3.20 AS s6-fetch
-ARG S6_OVERLAY_VERSION=3.2.0.2
-ARG TARGETARCH
-RUN if [ "$TARGETARCH" = "arm64" ]; then echo "aarch64" > /tmp/s6arch; \
-    else echo "x86_64" > /tmp/s6arch; fi
-RUN S6_ARCH=$(cat /tmp/s6arch) && \
-    wget -O /tmp/s6-overlay-noarch.tar.xz \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz" && \
-    wget -O /tmp/s6-overlay-noarch.tar.xz.sha256 \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-noarch.tar.xz.sha256" && \
-    wget -O /tmp/s6-overlay-arch.tar.xz \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-${S6_ARCH}.tar.xz" && \
-    wget -O /tmp/s6-overlay-arch.tar.xz.sha256 \
-      "https://github.com/just-containers/s6-overlay/releases/download/v${S6_OVERLAY_VERSION}/s6-overlay-${S6_ARCH}.tar.xz.sha256" && \
-    cd /tmp && \
-    NOARCH_SUM=$(awk '{print $1}' s6-overlay-noarch.tar.xz.sha256) && \
-    ARCH_SUM=$(awk '{print $1}' s6-overlay-arch.tar.xz.sha256) && \
-    echo "$NOARCH_SUM  s6-overlay-noarch.tar.xz" | sha256sum -c - && \
-    echo "$ARCH_SUM  s6-overlay-arch.tar.xz" | sha256sum -c -
-
-# === Stage 5: Final all-in-one image ===
-FROM node:22-alpine
-
-# s6-overlay
-COPY --from=s6-fetch /tmp/s6-overlay-noarch.tar.xz /tmp/
-COPY --from=s6-fetch /tmp/s6-overlay-arch.tar.xz /tmp/
-RUN tar -C / -Jxpf /tmp/s6-overlay-noarch.tar.xz \
- && tar -C / -Jxpf /tmp/s6-overlay-arch.tar.xz \
- && rm /tmp/s6-overlay-*.tar.xz
-
-# Infrastructure: Postgres, Redis, and utilities
-RUN apk add --no-cache \
-    postgresql16 postgresql16-contrib \
-    redis \
-    curl jq su-exec
-
-# tsx for database setup scripts
-RUN npm install -g tsx
-
-# Twenty application (both server and frontend built from source)
-COPY --from=twenty-server-build /app /app
-COPY --from=twenty-front-build /app/packages/twenty-front/build /app/packages/twenty-server/dist/front
-
-# s6 service definitions
-COPY packages/twenty-docker/twenty-app-dev/rootfs/ /
-
-# Data directories
-RUN mkdir -p /data/postgres /data/redis /app/.local-storage \
- && chown -R postgres:postgres /data/postgres \
- && chown 1000:1000 /data/redis /app/.local-storage
-
-ARG REACT_APP_SERVER_BASE_URL
-ARG APP_VERSION=0.0.0
-
-# Tell s6-overlay to preserve container environment variables
-ENV S6_KEEP_ENV=1
-
-# Environment defaults
-ENV PG_DATABASE_URL=postgres://twenty:twenty@localhost:5432/default \
-    SERVER_URL=http://localhost:2020 \
-    REDIS_URL=redis://localhost:6379 \
-    STORAGE_TYPE=local \
-    APP_SECRET=twenty-app-dev-secret-not-for-production \
-    REACT_APP_SERVER_BASE_URL=$REACT_APP_SERVER_BASE_URL \
-    APP_VERSION=$APP_VERSION \
-    NODE_ENV=development \
-    NODE_PORT=3000 \
-    DISABLE_DB_MIGRATIONS=true \
-    DISABLE_CRON_JOBS_REGISTRATION=true \
-    IS_BILLING_ENABLED=false \
-    SIGN_IN_PREFILLED=true
-
-EXPOSE 3000
-VOLUME ["/data/postgres", "/app/.local-storage"]
-
-LABEL org.opencontainers.image.source=https://github.com/twentyhq/twenty
-LABEL org.opencontainers.image.description="All-in-one Twenty image for local development and SDK usage. Includes PostgreSQL, Redis, server, and worker."
-
-ENTRYPOINT ["/init"]
@@ -1 +0,0 @@
-oneshot
@@ -1 +0,0 @@
-/bin/sh /etc/s6-overlay/scripts/init-db.sh
@@ -1,13 +0,0 @@
-#!/bin/sh
-# Initialize PostgreSQL data directory if empty
-if [ ! -f /data/postgres/PG_VERSION ]; then
-  echo "Initializing PostgreSQL data directory..."
-  su-exec postgres initdb -D /data/postgres --auth=trust --encoding=UTF8
-  # Allow local connections without password
-  echo "host all all 127.0.0.1/32 trust" >> /data/postgres/pg_hba.conf
-  echo "host all all ::1/128 trust" >> /data/postgres/pg_hba.conf
-fi
-
-exec su-exec postgres postgres -D /data/postgres \
-  -c listen_addresses=localhost \
-  -c unix_socket_directories=/tmp
@@ -1 +0,0 @@
-longrun
@@ -1,6 +0,0 @@
-#!/bin/sh
-exec redis-server \
-  --dir /data/redis \
-  --maxmemory-policy noeviction \
-  --bind 127.0.0.1 \
-  --protected-mode yes
@@ -1 +0,0 @@
-longrun
@@ -1,3 +0,0 @@
-#!/bin/sh
-cd /app/packages/twenty-server
-exec yarn start:prod
@@ -1 +0,0 @@
-longrun
@@ -1,3 +0,0 @@
-#!/bin/sh
-cd /app/packages/twenty-server
-exec yarn worker:prod
@@ -1 +0,0 @@
-longrun
@@ -1,56 +0,0 @@
-#!/bin/sh
-set -e
-
-# Wait for PostgreSQL to be ready (timeout after 60s)
-echo "Waiting for PostgreSQL..."
-TRIES=0
-until su-exec postgres pg_isready -h localhost; do
-  TRIES=$((TRIES + 1))
-  if [ "$TRIES" -ge 120 ]; then
-    echo "ERROR: PostgreSQL did not become ready within 60s"
-    exit 1
-  fi
-  sleep 0.5
-done
-echo "PostgreSQL is ready."
-
-# Create role if it doesn't exist
-su-exec postgres psql -h localhost -tc \
-  "SELECT 1 FROM pg_roles WHERE rolname='twenty'" | grep -q 1 \
-  || su-exec postgres psql -h localhost -c "CREATE ROLE twenty WITH LOGIN PASSWORD 'twenty' SUPERUSER"
-
-# Create database if it doesn't exist
-su-exec postgres psql -h localhost -tc \
-  "SELECT 1 FROM pg_database WHERE datname='default'" | grep -q 1 \
-  || su-exec postgres createdb -h localhost -O twenty default
-
-# Run Twenty database setup and migrations
-cd /app/packages/twenty-server
-
-has_schema=$(PGPASSWORD=twenty psql -h localhost -U twenty -d default -tAc \
-  "SELECT EXISTS (SELECT 1 FROM information_schema.schemata WHERE schema_name = 'core')")
-
-if [ "$has_schema" = "f" ]; then
-  echo "Database appears to be empty, running initial setup..."
-  NODE_OPTIONS="--max-old-space-size=1500" tsx ./scripts/setup-db.ts
-fi
-
-# Always run migrations (idempotent — skips already-applied ones)
-yarn database:migrate:prod
-
-yarn command:prod cache:flush
-yarn command:prod upgrade
-yarn command:prod cache:flush
-
-# Only seed on first boot — check if the dev workspace already exists
-has_workspace=$(PGPASSWORD=twenty psql -h localhost -U twenty -d default -tAc \
-  "SELECT EXISTS (SELECT 1 FROM core.workspace WHERE id = '20202020-1c25-4d02-bf25-6aeccf7ea419')")
-
-if [ "$has_workspace" = "f" ]; then
-  echo "Seeding app dev data..."
-  yarn command:prod workspace:seed:dev --light || true
-else
-  echo "Dev workspace already seeded, skipping."
-fi
-
-echo "Database initialization complete."
@@ -30,11 +30,6 @@ COPY ./packages/twenty-ui /app/packages/twenty-ui
 COPY ./packages/twenty-sdk /app/packages/twenty-sdk
 COPY ./packages/twenty-server /app/packages/twenty-server

-RUN npx nx run twenty-server:lingui:extract && \
-    npx nx run twenty-server:lingui:compile && \
-    npx nx run twenty-emails:lingui:extract && \
-    npx nx run twenty-emails:lingui:compile
-
 RUN npx nx run twenty-server:build

 RUN yarn workspaces focus --production twenty-emails twenty-shared twenty-sdk twenty-server
@@ -48,8 +43,6 @@ COPY ./packages/twenty-front /app/packages/twenty-front
 COPY ./packages/twenty-ui /app/packages/twenty-ui
 COPY ./packages/twenty-shared /app/packages/twenty-shared
 COPY ./packages/twenty-sdk /app/packages/twenty-sdk
-RUN npx nx run twenty-front:lingui:extract && \
-    npx nx run twenty-front:lingui:compile
 RUN npx nx build twenty-front


@@ -9,7 +9,7 @@ The goal here is to have a consistent codebase, which is easy to read and easy t

 For this, it's better to be a bit more verbose than to be too concise.

-Always keep in mind that people read code more often than they write it, especially on an open source project, where anyone can contribute.
+Always keep in mind that people read code more often than they write it, specially on an open source project, where anyone can contribute.

 There are a lot of rules that are not defined here, but that are automatically checked by linters.

@@ -150,7 +150,7 @@ type MyType = {

 ### Use string literals instead of enums

-[String literals](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#literal-types) are the go-to way to handle enum-like values in TypeScript. They are easier to extend with Pick and Omit, and offer a better developer experience, especially with code completion.
+[String literals](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#literal-types) are the go-to way to handle enum-like values in TypeScript. They are easier to extend with Pick and Omit, and offer a better developer experience, specially with code completion.

 You can see why TypeScript recommends avoiding enums [here](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#enums).

@@ -288,3 +288,4 @@ An Oxlint rule, `typescript/consistent-type-imports`, enforces the no-type impor
 Please note that this rule specifically addresses rare edge cases where unintentional type imports occur. TypeScript itself discourages this practice, as mentioned in the [TypeScript 3.8 release notes](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html). In most situations, you should not need to use type-only imports.

 To ensure your code complies with this rule, make sure to run Oxlint as part of your development workflow.
+
@@ -7,7 +7,7 @@ description: "The guide for contributors (or curious developers) who want to run
 ## Prerequisites

 <Tabs>
-<Tab title="Linux and macOS">
+<Tab title="Linux and MacOS">

 Before you can install and use Twenty, make sure you install the following on your computer:
 - [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
@@ -31,7 +31,7 @@ wsl --install
 ```
 You should now see a prompt to restart your computer. If not, restart it manually.

-Upon restart, a PowerShell window will open and install Ubuntu. This may take up some time.
+Upon restart, a powershell window will open and install Ubuntu. This may take up some time.
 You'll see a prompt to create a username and password for your Ubuntu installation.

 2. Install and configure git
@@ -104,7 +104,7 @@ You should run all commands in the following steps from the root of the project.
 <Tabs>
  <Tab title="Linux">
    **Option 1 (preferred):** To provision your database locally:
-    Use the following link to install PostgreSQL on your Linux machine: [PostgreSQL Installation](https://www.postgresql.org/download/linux/)
+    Use the following link to install Postgresql on your Linux machine: [Postgresql Installation](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -131,7 +131,7 @@ You should run all commands in the following steps from the root of the project.
    ```

    The installer might not create the `postgres` user by default when installing
-    via Homebrew on macOS. Instead, it creates a PostgreSQL role that matches your macOS
+    via Homebrew on MacOS. Instead, it creates a PostgreSQL role that matches your macOS
    username (e.g., "john").
    To check and create the `postgres` user if necessary, follow these steps:
    ```bash
@@ -174,8 +174,8 @@ You should run all commands in the following steps from the root of the project.
  <Tab title="Windows (WSL)">
    All the following steps are to be run in the WSL terminal (within your virtual machine)

-    **Option 1:** To provision your PostgreSQL locally:
-    Use the following link to install PostgreSQL on your Linux virtual machine: [PostgreSQL Installation](https://www.postgresql.org/download/linux/)
+    **Option 1:** To provision your Postgresql locally:
+    Use the following link to install Postgresql on your Linux virtual machine: [Postgresql Installation](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -190,12 +190,10 @@ You should run all commands in the following steps from the root of the project.
  </Tab>
 </Tabs>

-You can now access the database at `localhost:5432`.
-
-If you used the Docker option above, the default credentials are user `postgres` and password `postgres`. For native PostgreSQL installations, use the credentials and roles configured on your machine.
+You can now access the database at [localhost:5432](localhost:5432), with user `postgres` and password `postgres` .

 ## Step 4: Set up a Redis Database (cache)
-Twenty requires a Redis cache to provide the best performance.
+Twenty requires a redis cache to provide the best performance

 <Tabs>
  <Tab title="Linux">
@@ -212,10 +210,8 @@ Twenty requires a Redis cache to provide the best performance.
    ```bash
    brew install redis
    ```
-    Start your Redis server:
-    ```bash
-    brew services start redis
-    ```
+    Start your redis server:
+    ```brew services start redis```

    **Option 2:** If you have docker installed:
    ```bash
@@ -233,11 +229,11 @@ Twenty requires a Redis cache to provide the best performance.
  </Tab>
 </Tabs>

-If you need a client GUI, we recommend [Redis Insight](https://redis.io/insight/) (free version available).
+If you need a Client GUI, we recommend [redis insight](https://redis.io/insight/) (free version available)

-## Step 5: Set up environment variables
+## Step 5: Setup environment variables

-Use environment variables or `.env` files to configure your project. More info [here](/developers/self-host/capabilities/setup).
+Use environment variables or `.env` files to configure your project. More info [here](/developers/self-host/capabilities/setup)

 Copy the `.env.example` files in `/front` and `/server`:
 ```bash
@@ -20,51 +20,19 @@ Apps let you build and manage Twenty customizations **as code**. Instead of conf
 ## Prerequisites

 - Node.js 24+ and Yarn 4
- Docker (for the local Twenty dev server)
+- A Twenty workspace and an API key (create one at https://app.twenty.com/settings/api-webhooks)

 ## Getting Started

-Create a new app using the official scaffolder. It can automatically start a local Twenty instance for you:
+Create a new app using the official scaffolder, then authenticate and start developing:

 ```bash filename="Terminal"
-# Scaffold a new app — the CLI will offer to start a local Twenty server
+# Scaffold a new app (includes all examples by default)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app

 # Start dev mode: automatically syncs local changes to your workspace
-yarn twenty dev
-```
-
-### Local Server Management
-
-The SDK includes commands to manage a local Twenty dev server (all-in-one Docker image with PostgreSQL, Redis, server, and worker):
-
-```bash filename="Terminal"
-# Start the local server (pulls the image if needed)
-yarn twenty server start
-
-# Check server status
-yarn twenty server status
-
-# Stream server logs
-yarn twenty server logs
-
-# Stop the server
-yarn twenty server stop
-
-# Reset all data and start fresh
-yarn twenty server reset
-```
-
-The local server comes pre-seeded with a workspace and user (`tim@apple.dev` / `tim@apple.dev`), so you can start developing immediately without any manual setup.
-
-### Authentication
-
-Connect your app to the local server using OAuth:
-
-```bash filename="Terminal"
-# Authenticate via OAuth (opens browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```

 The scaffolder supports two modes for controlling which example files are included:
@@ -95,12 +63,6 @@ yarn twenty function:execute --preInstall
 # Execute the post-install function
 yarn twenty function:execute --postInstall

-# Build the app for distribution
-yarn twenty app:build
-
-# Publish the app to npm or a Twenty server
-yarn twenty app:publish
-
 # Uninstall the application from the current workspace
 yarn twenty app:uninstall

@@ -1262,113 +1224,6 @@ Key points:

 Explore a minimal, end-to-end example that demonstrates objects, logic functions, front components, and multiple triggers [here](https://github.com/twentyhq/twenty/tree/main/packages/twenty-apps/hello-world):

-## Building your app
-
-Once you've developed your app with `app:dev`, use `app:build` to compile it into a distributable package.
-
-```bash filename="Terminal"
-# Build the app (output goes to .twenty/output/)
-yarn twenty app:build
-
-# Build and create a tarball (.tgz) for distribution
-yarn twenty app:build --tarball
-```
-
-The build process:
-
-1. **Parses and validates the manifest** — reads all `defineX()` entities from your source files and validates the manifest structure.
-2. **Compiles logic functions and front components** — bundles TypeScript sources into ESM `.mjs` files using esbuild.
-3. **Generates checksums** — computes MD5 hashes for each built file, stored in the manifest as `builtHandlerChecksum` / `builtComponentChecksum`.
-4. **Generates the typed API client** — introspects the GraphQL schema and generates typed `CoreApiClient` and `MetadataApiClient` clients.
-5. **Runs a TypeScript type check** — runs `tsc --noEmit` to catch type errors before publishing.
-6. **Rebuilds with the generated client** — performs a second compilation pass so the generated client types are included.
-7. **Optionally creates a tarball** — if `--tarball` is passed, runs `npm pack` to create a `.tgz` file ready for distribution.
-
-The build output in `.twenty/output/` contains:
-
-```text
-.twenty/output/
-├── manifest.json              # Manifest with checksums for all built files
-├── package.json               # Copied from app root
-├── yarn.lock                  # Copied from app root
-├── src/
-│   ├── logic-functions/       # Compiled .mjs logic function files
-│   └── front-components/      # Compiled .mjs front component files
-├── public/                    # Static assets (if any)
-└── my-app-1.0.0.tgz          # Only with --tarball flag
-```
-
-| Option | Description |
-|--------|-------------|
-| `[appPath]` | Path to the app directory (defaults to current directory) |
-| `--tarball` | Also pack the output into a `.tgz` tarball |
-
-## Publishing your app
-
-Use `app:publish` to distribute your app — either to the npm registry or directly to a Twenty server.
-
-### Publish to npm (default)
-
-```bash filename="Terminal"
-# Publish to npm (requires npm login)
-yarn twenty app:publish
-
-# Publish with a dist-tag (e.g. beta, next)
-yarn twenty app:publish --tag beta
-```
-
-This builds the app and runs `npm publish` from the `.twenty/output/` directory. The published package can then be installed from the Twenty marketplace by any workspace.
-
-### Publish to a Twenty server
-
-```bash filename="Terminal"
-# Publish directly to a Twenty server
-yarn twenty app:publish --server https://app.twenty.com
-```
-
-This builds the app with a tarball, uploads it to the server via the `uploadAppTarball` GraphQL mutation, and triggers installation in one step. This is useful for private deployments or testing against a specific server.
-
-| Option | Description |
-|--------|-------------|
-| `[appPath]` | Path to the app directory (defaults to current directory) |
-| `--server <url>` | Publish to a Twenty server instead of npm |
-| `--token <token>` | Authentication token for the target server |
-| `--tag <tag>` | npm dist-tag (e.g. `beta`, `next`) — only for npm publish |
-
-## Application registration
-
-Before an app can be installed in a workspace, it must be **registered**. A registration is a metadata record that describes where the app comes from and how to authenticate it. This is handled automatically by the CLI in most cases.
-
-### Source types
-
-Each registration has a **source type** that determines how the app's files are resolved during installation:
-
-| Source type | How files are resolved | Typical use case |
-|-------------|----------------------|------------------|
-| `LOCAL` | Files are synced in real-time by the CLI watcher — installation is skipped | Development with `app:dev` |
-| `NPM` | Fetched from the npm registry via the `sourcePackage` field | Published apps on npm |
-| `TARBALL` | Extracted from an uploaded `.tgz` file stored on the server | Private apps published with `--server` |
-
-### How registration happens
-
- **`app:dev`** — automatically creates a `LOCAL` registration the first time you run dev mode against a workspace.
- **`app:publish --server`** — uploads a tarball and creates (or updates) a `TARBALL` registration, then installs the app.
- **npm marketplace** — `NPM` registrations are created when apps are synced from the npm registry into the Twenty marketplace catalog.
- **GraphQL API** — you can also create registrations programmatically via the `createApplicationRegistration` mutation.
-
-### Registration vs installation
-
-**Registration** and **installation** are separate concepts:
-
- A **registration** (`ApplicationRegistration`) is a global metadata record describing the app: its name, source type, OAuth credentials, and marketplace listing status. It exists independently of any workspace.
- An **installation** (`Application`) is a per-workspace instance. When a user installs an app, Twenty resolves the package from the registration's source, writes the built files to storage, and synchronizes the manifest (creating objects, fields, logic functions, etc.) in that workspace.
-
-One registration can be installed in many workspaces. Each workspace gets its own copy of the app's files and data model.
-
-### OAuth credentials
-
-Each registration includes OAuth credentials (`oAuthClientId` and `oAuthClientSecret`) generated at creation time. These are used by the app to authenticate API requests on behalf of users. The client secret is returned **once** at creation — store it securely. You can rotate it later via the `rotateApplicationRegistrationClientSecret` mutation.
-
 ## Manual setup (without the scaffolder)

 While we recommend using `create-twenty-app` for the best getting-started experience, you can also set up a project manually. Do not install the CLI globally. Instead, add `twenty-sdk` as a local dependency and wire a single script in your package.json:
@@ -4,7 +4,7 @@ title: 1-Click w/ Docker Compose


 <Warning>
-Docker containers are for production hosting or self-hosting. For contributing, please check the [Local Setup](/developers/contribute/capabilities/local-setup).
+Docker containers are for production hosting or self-hosting, for the contribution please check the [Local Setup](/developers/contribute/capabilities/local-setup).
 </Warning>

 ## Overview
@@ -13,7 +13,7 @@ This guide provides step-by-step instructions to install and configure the Twent

 **Important:** Only modify settings explicitly mentioned in this guide. Altering other configurations may lead to issues.

-See [Setup Environment Variables](/developers/self-host/capabilities/setup) for advanced configuration. All environment variables must be declared in the `docker-compose.yml` file at the server and/or worker level, depending on the variable.
+See docs [Setup Environment Variables](/developers/self-host/capabilities/setup) for advanced configuration. All environment variables must be declared in the docker-compose.yml file at the server and / or worker level depending on the variable.

 ## System Requirements

@@ -237,3 +237,4 @@ docker compose up -d

 If you encounter any problem, check [Troubleshooting](/developers/self-host/capabilities/troubleshooting) for solutions.

+
@@ -157,9 +157,7 @@ plugins: [

 Run `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = 'you@yourdomain.com';` in database container to get access to admin panel.

-#### When running workflow, workflow run fails with "Logic function execution is disabled. Set LOGIC_FUNCTION_TYPE to LOCAL or LAMBDA to enable."

-In production, logic functions are disabled by default. Set the `LOGIC_FUNCTION_TYPE` environment variable to `LOCAL` or `LAMBDA` to enable them. This can be configured via environment variables or through the admin panel database variables. See the [Logic Functions setup guide](/developers/self-host/capabilities/setup#logic-functions-available-drivers) for details.

 ### 1-click Docker compose

@@ -175,8 +175,7 @@
                          "user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -622,8 +621,7 @@
                          "l/fr/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/fr/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/fr/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/fr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/fr/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/fr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -1069,8 +1067,7 @@
                          "l/ar/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/ar/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/ar/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ar/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ar/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ar/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -1516,8 +1513,7 @@
                          "l/cs/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/cs/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/cs/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/cs/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/cs/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/cs/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -1963,8 +1959,7 @@
                          "l/de/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/de/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/de/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/de/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/de/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/de/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -2410,8 +2405,7 @@
                          "l/es/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/es/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/es/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/es/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/es/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/es/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -2857,8 +2851,7 @@
                          "l/it/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/it/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/it/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/it/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/it/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/it/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -3304,8 +3297,7 @@
                          "l/ja/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/ja/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/ja/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ja/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ja/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ja/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -3751,8 +3743,7 @@
                          "l/ko/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/ko/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/ko/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ko/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ko/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ko/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -4198,8 +4189,7 @@
                          "l/pt/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/pt/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/pt/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/pt/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/pt/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/pt/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -4645,8 +4635,7 @@
                          "l/ro/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/ro/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/ro/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ro/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ro/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -5092,8 +5081,7 @@
                          "l/ru/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/ru/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/ru/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/ru/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/ru/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -5539,8 +5527,7 @@
                          "l/tr/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/tr/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/tr/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/tr/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/tr/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -5986,8 +5973,7 @@
                          "l/zh/user-guide/workflows/how-tos/crm-automations/formula-fields",
                          "l/zh/user-guide/workflows/how-tos/crm-automations/display-related-record-data",
                          "l/zh/user-guide/workflows/how-tos/crm-automations/closed-won-automations",
-                          "l/zh/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities",
-                          "l/zh/user-guide/workflows/how-tos/crm-automations/auto-reply-to-inbound-emails"
+                          "l/zh/user-guide/workflows/how-tos/crm-automations/detect-stale-opportunities"
                        ]
                      },
                      {
@@ -6316,10 +6302,6 @@
      "source": "/developers/extend/capabilities/apps",
      "destination": "/developers/extend/apps/getting-started"
    },
-    {
-      "source": "/developers/extend/mcp",
-      "destination": "/user-guide/ai/capabilities/mcp"
-    },
    {
      "source": "/developers/local-setup",
      "destination": "/developers/contribute/capabilities/local-setup"
@@ -8,7 +8,7 @@ title: دليل الأسلوب

 لهذا، من الأفضل أن تكون تفصيلًا أكثر قليلاً بدلاً من أن تكون موجزًا للغاية.

-دائمًا ضع في اعتبارك أن الناس يقرؤون التعليمات البرمجية أكثر مما يكتبونها، وخاصة في مشروع مفتوح المصدر، حيث يمكن لأي شخص المساهمة.
+دائمًا ضع في اعتبارك أن الناس يقرؤون التعليمات البرمجية أكثر مما يكتبونها، وخاصة في المشاريع مفتوحة المصدر، حيث يمكن لأي شخص المساهمة.

 هناك العديد من القواعد التي لم يتم تعريفها هنا، ولكن يتم التحقق منها تلقائيًا بواسطة أدوات الفحص.

@@ -6,7 +6,7 @@ description: الدليل للمساهمين (أو المطورين الفضول
 ## المتطلبات الأساسية

 <Tabs>
-<Tab title="Linux و macOS">
+<Tab title="Linux و MacOS">

 قبل أن تتمكن من تثبيت واستخدام Twenty، تأكد من تثبيت الأمور التالية على جهاز الكمبيوتر الخاص بك:
 * [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
@@ -103,7 +103,7 @@ cd twenty
 <Tabs>
  <Tab title="Linux">
    **الخيار 1 (المفضل):** لتوفير قاعدة بياناتك محليًا:
-    استخدم الرابط التالي لتثبيت PostgreSQL على جهاز Linux الخاص بك: [تثبيت PostgreSQL](https://www.postgresql.org/download/linux/)
+    استخدم الرابط التالي لتثبيت Postgresql على جهاز Linux الخاص بك: [تثبيت Postgresql](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -129,8 +129,8 @@ cd twenty
    brew services list
    ```

-    قد لا يقوم المُثبِّت بإنشاء المستخدم `postgres` افتراضيًا عند التثبيت
-    عبر Homebrew على macOS. بدلاً من ذلك، فإنه ينشئ دور PostgreSQL يطابق
+    المثبت قد لا ينشئ المستخدم `postgres` افتراضيًا عند التثبيت
+    عبر Homebrew على MacOS. بدلاً من ذلك، فإنه ينشئ دور PostgreSQL يطابق
    اسم المستخدم الخاص بك في MacOS (مثل "john").
    للتحقق وإنشاء المستخدم `postgres` إذا لزم الأمر، اتبع هذه الخطوات:
    ```bash
@@ -173,8 +173,8 @@ cd twenty
  <Tab title="ويندوز (WSL)">
    يجب أن تُنفذ جميع الخطوات التالية في تيرمينال WSL (داخل جهازك الافتراضي)

-    **الخيار 1:** لتوفير قاعدة بيانات PostgreSQL الخاصة بك محليًا:
-    استخدم الرابط التالي لتثبيت PostgreSQL على جهاز Linux الافتراضي الخاص بك: [تثبيت PostgreSQL](https://www.postgresql.org/download/linux/)
+    **الخيار 1:** لتوفير قاعدة بيانات Postgresql الخاصة بك محليًا:
+    استخدم الرابط التالي لتثبيت Postgresql على جهاز Linux الافتراضي الخاص بك: [تثبيت Postgresql](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -189,13 +189,11 @@ cd twenty
  </Tab>
 </Tabs>

-يمكنك الآن الوصول إلى قاعدة البيانات على `localhost:5432`.
-
-إذا استخدمت خيار Docker أعلاه، فإن بيانات الاعتماد الافتراضية هي اسم المستخدم `postgres` وكلمة المرور `postgres`. بالنسبة لتثبيتات PostgreSQL الأصلية، استخدم بيانات الاعتماد والأدوار المُكوَّنة على جهازك.
+يمكنك الآن الوصول إلى قاعدة البيانات على [localhost:5432](localhost:5432)، مع المستخدم `postgres` وكلمة المرور `postgres`.

 ## الخطوة 4: إعداد قاعدة بيانات Redis (للتخزين المؤقت)

-يتطلب Twenty مخزن بيانات Redis لتقديم أفضل أداء.
+يتطلب Twenty مخزن بيانات Redis لتقديم أفضل أداء

 <Tabs>
  <Tab title="Linux">
@@ -212,10 +210,8 @@ cd twenty
    ```bash
    brew install redis
    ```
-    ابدأ تشغيل خادم Redis:
-    ```bash
-    brew services start redis
-    ```
+    ابدأ خادم redis الخاص بك:
+    `brew services start redis`

    **الخيار 2:** إذا كنت قد قمت بتثبيت docker:
    ```bash
@@ -233,11 +229,11 @@ cd twenty
  </Tab>
 </Tabs>

-إذا كنت بحاجة إلى واجهة رسومية للعميل، نوصي بـ [Redis Insight](https://redis.io/insight/) (يتوفر إصدار مجاني).
+إذا كنت بحاجة إلى واجهة رسومية للعميل، نوصي بـ [redis insight](https://redis.io/insight/) (يتوفر إصدار مجاني)

 ## الخطوة 5: إعداد متغيرات البيئة

-استخدم متغيرات البيئة أو ملفات `.env` لتكوين مشروعك. المزيد من المعلومات [هنا](/l/ar/developers/self-host/capabilities/setup).
+استخدم متغيرات البيئة أو ملفات `.env` لتكوين مشروعك. المزيد من المعلومات [هنا](/l/ar/developers/self-host/capabilities/setup)

 انسخ ملفات `.env.example` الموجودة في `/front` و`/server`:

@@ -21,51 +21,19 @@ description: أنشئ وأدِر تخصيصات Twenty على هيئة كود.
 ## المتطلبات الأساسية

 * Node.js 24+ وYarn 4
-* Docker (لخادم تطوير Twenty المحلي)
+* مساحة عمل Twenty ومفتاح واجهة برمجة التطبيقات (أنشئ واحدًا على https://app.twenty.com/settings/api-webhooks)

 ## البدء

-أنشئ تطبيقًا جديدًا باستخدام المولّد الرسمي. يمكنه بدء مثيل محلي من Twenty تلقائيًا لك:
+أنشئ تطبيقًا جديدًا باستخدام المُهيئ الرسمي، ثم قم بالمصادقة وابدأ التطوير:

 ```bash filename="Terminal"
-# إنشاء تطبيق جديد — ستعرض واجهة سطر الأوامر خيار بدء خادم Twenty محلي
+# إنشاء تطبيق جديد (يتضمن جميع الأمثلة افتراضيًا)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app

 # ابدأ وضع التطوير: يُزامن التغييرات المحلية تلقائيًا مع مساحة العمل الخاصة بك
-yarn twenty dev
-```
-
-### إدارة الخادم المحلي
-
-يتضمن SDK أوامر لإدارة خادم تطوير Twenty محلي (صورة Docker متكاملة تتضمن PostgreSQL وRedis والخادم والعامل):
-
-```bash filename="Terminal"
-# ابدأ الخادم المحلي (يسحب الصورة إذا لزم الأمر)
-yarn twenty server start
-
-# تحقّق من حالة الخادم
-yarn twenty server status
-
-# بثّ سجلات الخادم
-yarn twenty server logs
-
-# أوقف الخادم
-yarn twenty server stop
-
-# أعد ضبط جميع البيانات وابدأ من جديد
-yarn twenty server reset
-```
-
-يأتي الخادم المحلي مهيأً مسبقًا بمساحة عمل ومستخدم (`tim@apple.dev` / `tim@apple.dev`)، بحيث يمكنك البدء في التطوير فورًا دون أي إعداد يدوي.
-
-### المصادقة
-
-وصّل تطبيقك بالخادم المحلي باستخدام OAuth:
-
-```bash filename="Terminal"
-# المصادقة عبر OAuth (يفتح المتصفح)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```

 يدعم المُنشئ وضعين للتحكم في ملفات الأمثلة التي سيتم تضمينها:
@@ -96,12 +64,6 @@ yarn twenty function:execute --preInstall
 # نفّذ دالة ما بعد التثبيت
 yarn twenty function:execute --postInstall

-# ابنِ التطبيق للتوزيع
-yarn twenty app:build
-
-# انشر التطبيق إلى npm أو إلى خادم Twenty
-yarn twenty app:publish
-
 # أزل تثبيت التطبيق من مساحة العمل الحالية
 yarn twenty app:uninstall

@@ -1278,113 +1240,6 @@ uploadFile(

 استكشف مثالًا بسيطًا شاملًا من البداية إلى النهاية يوضح الكائنات والوظائف المنطقية والمكوّنات الأمامية ومشغّلات متعددة [هنا](https://github.com/twentyhq/twenty/tree/main/packages/twenty-apps/hello-world):

-## بناء تطبيقك
-
-بمجرد أن تطوّر تطبيقك باستخدام `app:dev`، استخدم `app:build` لإنشاء حزمة قابلة للتوزيع منه.
-
-```bash filename="Terminal"
-# ابنِ التطبيق (الإخراج يذهب إلى .twenty/output/)
-yarn twenty app:build
-
-# ابنِ وأنشئ ملف tarball (.tgz) للتوزيع
-yarn twenty app:build --tarball
-```
-
-عملية البناء:
-
-1. **يقوم بتحليل ملف البيان والتحقق من صحته** — يقرأ جميع الكيانات `defineX()` من ملفات المصدر لديك ويُتحقّق من بنية ملف البيان.
-2. **يُصرِّف دوال المنطق ومكوّنات الواجهة** — يُجمّع مصادر TypeScript إلى ملفات ESM `.mjs` باستخدام esbuild.
-3. **يولّد قيم التحقّق** — يحسب تجزئات MD5 لكل ملف مُبنًى، وتُخزَّن في ملف البيان كـ `builtHandlerChecksum` / `builtComponentChecksum`.
-4. **ينشئ عميل API مضبوط الأنواع** — يفحص مخطط GraphQL ويُنشئ عميلَي `CoreApiClient` و`MetadataApiClient` مضبوطي الأنواع.
-5. **يشغّل فحص الأنواع لـ TypeScript** — يشغّل `tsc --noEmit` لاكتشاف أخطاء الأنواع قبل النشر.
-6. **يعيد البناء باستخدام العميل المُولَّد** — يُجري مرحلة ترجمة ثانية بحيث تُدرَج أنواع العميل المُولَّد.
-7. **ينشئ أرشيف tar اختياريًا** — إذا تم تمرير `--tarball`، يشغّل `npm pack` لإنشاء ملف `.tgz` جاهز للتوزيع.
-
-مخرجات البناء في `.twenty/output/` تتضمّن:
-
-```text
-.twenty/output/
-├── manifest.json              # Manifest with checksums for all built files
-├── package.json               # Copied from app root
-├── yarn.lock                  # Copied from app root
-├── src/
-│   ├── logic-functions/       # Compiled .mjs logic function files
-│   └── front-components/      # Compiled .mjs front component files
-├── public/                    # Static assets (if any)
-└── my-app-1.0.0.tgz          # Only with --tarball flag
-```
-
-| الخيار      | الوصف                                              |
-| ----------- | -------------------------------------------------- |
-| `[appPath]` | المسار إلى دليل التطبيق (افتراضيًا: الدليل الحالي) |
-| `--tarball` | قم أيضًا بحزم المخرجات في أرشيف `.tgz`             |
-
-## نشر تطبيقك
-
-استخدم `app:publish` لتوزيع تطبيقك — إما إلى سجل npm أو مباشرةً إلى خادم Twenty.
-
-### النشر إلى npm (الإعداد الافتراضي)
-
-```bash filename="Terminal"
-# Publish to npm (requires npm login)
-yarn twenty app:publish
-
-# Publish with a dist-tag (e.g. beta, next)
-yarn twenty app:publish --tag beta
-```
-
-يقوم هذا ببناء التطبيق وتشغيل `npm publish` من دليل `.twenty/output/`. بعد ذلك يمكن تثبيت الحزمة المنشورة من سوق Twenty بواسطة أي مساحة عمل.
-
-### النشر إلى خادم Twenty
-
-```bash filename="Terminal"
-# Publish directly to a Twenty server
-yarn twenty app:publish --server https://app.twenty.com
-```
-
-يقوم هذا ببناء التطبيق مع أرشيف tar، ويرفعه إلى الخادم عبر العملية `uploadAppTarball` في GraphQL، ويبدأ التثبيت في خطوة واحدة. يكون هذا مفيدًا لعمليات النشر الخاصة أو للاختبار مقابل خادم محدّد.
-
-| الخيار            | الوصف                                                    |
-| ----------------- | -------------------------------------------------------- |
-| `[appPath]`       | المسار إلى دليل التطبيق (افتراضيًا: الدليل الحالي)       |
-| `--server <url>`  | انشر إلى خادم Twenty بدلًا من npm                        |
-| `--token <token>` | رمز المصادقة للخادم المستهدف                             |
-| `--tag <tag>`     | علامة توزيع npm (مثل `beta`، `next`) — للنشر عبر npm فقط |
-
-## تسجيل التطبيق
-
-قبل أن يمكن تثبيت تطبيق في مساحة عمل، يجب أن يكون **مسجّلًا**. التسجيل هو سجل بيانات وصفية يوضّح مصدر التطبيق وكيفية مصادقته. يُعالَج هذا تلقائيًا بواسطة CLI في معظم الحالات.
-
-### أنواع المصادر
-
-لكل تسجيل **نوع مصدر** يحدّد كيفية تحديد ملفات التطبيق أثناء التثبيت:
-
-| نوع المصدر | كيفية تحديد الملفات                                                       | حالة الاستخدام النموذجية                |
-| ---------- | ------------------------------------------------------------------------- | --------------------------------------- |
-| `LOCAL`    | تتم مزامنة الملفات في الوقت الفعلي بواسطة مُراقِب CLI — يتم تخطّي التثبيت | التطوير باستخدام `app:dev`              |
-| `NPM`      | تُجلب من سجل npm عبر الحقل `sourcePackage`                                | تطبيقات منشورة على npm                  |
-| `TARBALL`  | تُستخرَج من ملف `.tgz` مرفوع ومخزَّن على الخادم                           | تطبيقات خاصة منشورة باستخدام `--server` |
-
-### كيفية إجراء التسجيل
-
-* **`app:dev`** — ينشئ تلقائيًا تسجيلًا من نوع `LOCAL` في المرة الأولى التي تشغّل فيها وضع التطوير لمساحة عمل.
-* **`app:publish --server`** — يرفع أرشيف tar وينشئ (أو يحدّث) تسجيلًا من نوع `TARBALL`، ثم يثبّت التطبيق.
-* **سوق npm** — يتم إنشاء تسجيلات `NPM` عند مزامنة التطبيقات من سجل npm إلى كتالوج سوق Twenty.
-* **واجهة برمجة تطبيقات GraphQL** — يمكنك أيضًا إنشاء التسجيلات برمجيًا عبر العملية `createApplicationRegistration`.
-
-### التسجيل مقابل التثبيت
-
-**التسجيل** و**التثبيت** مفهومان منفصلان:
-
-* **التسجيل** (`ApplicationRegistration`) هو سجل بيانات وصفية عام يصف التطبيق: اسمه، نوع المصدر، بيانات اعتماد OAuth، وحالة إدراجه في السوق. وهو موجود بشكل مستقل عن أي مساحة عمل.
-* **التثبيت** (`Application`) هو مثيل لكل مساحة عمل. عند قيام مستخدم بتثبيت تطبيق، تقوم Twenty بحلّ الحزمة من مصدر التسجيل، وتكتب الملفات المُبنَاة إلى التخزين، وتزامن البيان التعريفي (إنشاء الكائنات والحقول ودوال المنطق، إلخ) في مساحة العمل تلك.
-
-يمكن تثبيت تسجيل واحد في العديد من مساحات العمل. تحصل كل مساحة عمل على نسختها الخاصة من ملفات التطبيق ونموذج البيانات.
-
-### بيانات اعتماد OAuth
-
-يتضمن كل تسجيل بيانات اعتماد OAuth (`oAuthClientId` و`oAuthClientSecret`) يتم إنشاؤها وقت الإنشاء. يستخدمها التطبيق لمصادقة طلبات واجهة برمجة التطبيقات بالنيابة عن المستخدمين. يُعرَض سر العميل مرةً **واحدة** عند الإنشاء — خزّنه بأمان. يمكنك تدويره لاحقًا عبر العملية `rotateApplicationRegistrationClientSecret`.
-
 ## إعداد يدوي (بدون المهيئ)

 بينما نوصي باستخدام `create-twenty-app` للحصول على أفضل تجربة للبدء، يمكنك أيضًا إعداد مشروع يدويًا. لا تثبّت CLI عالميًا. بدل ذلك، أضف `twenty-sdk` كاعتماد محلي واربط سكربتًا واحدًا في ملف package.json لديك:
@@ -3,7 +3,7 @@ title: بنقرة واحدة مع Docker Compose
 ---

 <Warning>
-حاويات Docker مخصصة للاستضافة في بيئة الإنتاج أو للاستضافة الذاتية. للمساهمة، يُرجى الاطلاع على [الإعداد المحلي](/l/ar/developers/contribute/capabilities/local-setup).
+الحاويات الخاصة بدوكر مخصصة للاستضافة الإنتاجية أو الاستضافة الذاتية، للتحقيق يرجى التحقق من [الإعداد المحلي](/l/ar/developers/contribute/capabilities/local-setup).
 </Warning>

 ## نظرة عامة
@@ -12,7 +12,7 @@ title: بنقرة واحدة مع Docker Compose

 **مهم:** عدّل الإعدادات المذكورة صراحة في هذا الدليل فقط. قد يؤدي تعديل التكوينات الأخرى إلى مشاكل.

-راجع [إعداد متغيرات البيئة](/l/ar/developers/self-host/capabilities/setup) لإعداد متقدم. يجب إعلان جميع متغيرات البيئة في ملف `docker-compose.yml` على مستوى الخادم و/أو العامل، اعتمادًا على المتغير.
+راجع المستندات الخاصة بـ [إعداد متغيرات البيئة](/l/ar/developers/self-host/capabilities/setup) لإعداد متقدم. يجب إعلان جميع متغيرات البيئة في الملف docker-compose.yml على مستوى الخادم و/أو العامل بناءً على المتغير.

 ## متطلبات النظام

@@ -166,10 +166,6 @@ plugins: [

 قم بتشغيل `UPDATE core."user" SET "canAccessFullAdminPanel" = TRUE WHERE email = 'you@yourdomain.com';` في حاوية قاعدة البيانات للحصول على الوصول إلى لوحة الإدارة.

-#### عند تشغيل سير العمل، يفشل تشغيل سير العمل مع الرسالة "تم تعطيل تنفيذ دوال المنطق. عيّن LOGIC_FUNCTION_TYPE إلى LOCAL أو LAMBDA لتمكين ذلك."
-
-في بيئة الإنتاج، يتم تعطيل دوال المنطق افتراضيًا. قم بتعيين متغير البيئة `LOGIC_FUNCTION_TYPE` إلى `LOCAL` أو `LAMBDA` لتمكينها. يمكن تكوين ذلك عبر متغيرات البيئة أو من خلال متغيرات قاعدة البيانات في لوحة الإدارة. راجع [دليل إعداد دوال المنطق](/l/ar/developers/self-host/capabilities/setup#logic-functions-available-drivers) للحصول على التفاصيل.
-
 ### Docker compose بنقرة واحدة

 #### غير قادر على تسجيل الدخول
@@ -1,142 +0,0 @@
---
-title: خادم MCP
-description: اربط مساعدي الذكاء الاصطناعي بمساحة عمل Twenty الخاصة بك باستخدام بروتوكول سياق النموذج.
---
-
-<Warning>
-MCP حاليًا في مرحلة **ألفا** وهو متاح فقط في بعض مساحات العمل. قد لا يكون مفعّلًا لمساحة عملك بعد.
-</Warning>
-
-تعرض Twenty خادم [MCP](https://modelcontextprotocol.io/) بحيث تتمكّن مساعدات الذكاء الاصطناعي — Claude Desktop وClaude Code وCursor وChatGPT وغيرها — من قراءة وكتابة بيانات نظام إدارة علاقات العملاء (CRM) لديك باستخدام اللغة الطبيعية.
-
-استخدم **عنوان URL لمساحة العمل** (عنوان URL الذي تستخدمه للوصول إلى Twenty) كنقطة نهاية MCP. على Twenty Cloud، قد يكون عنوان URL لمساحة العمل هو `https://{mycompany}.twenty.com` أو نطاق مخصص. الخادم متاح على:
-
-| البيئة                | نقطة نهاية MCP                                                                           |
-| --------------------- | ---------------------------------------------------------------------------------------- |
-| **السحابة**           | `https://{your-workspace-url}/mcp` (على سبيل المثال: `https://mycompany.twenty.com/mcp`) |
-| **الاستضافة الذاتية** | `https://{your-domain}/mcp`                                                              |
-
-## طرق المصادقة
-
-لديك طريقتان لمصادقة عميل MCP: **OAuth** (مُوصى بها) أو **مفتاح API**.
-
-### الخيار أ — OAuth (مُوصى به)
-
-باستخدام OAuth، يفتح عميل MCP لديك نافذة متصفح لتسجيل الدخول. لا يتم تخزين أي أسرار في ملفات الإعداد، ويتم تحديث الرموز المميِّزة تلقائيًا.
-
-<Note>
-يتطلب OAuth عميل MCP يدعم [مواصفة تفويض MCP](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization). تدعمه Claude Desktop وClaude Code وCursor وChatGPT.
-</Note>
-
-أضِف ما يلي إلى تهيئة عميل MCP لديك، واستبدِل `{your-workspace-url}` بمضيف مساحة العمل لديك (على سبيل المثال: `mycompany.twenty.com`):
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp"
-    }
-  }
-}
-```
-
-هذا كل شيء — لا حاجة إلى مفتاح API. عند اتصال العميل للمرة الأولى، سيفعل ما يلي:
-
-1. اكتشاف بيانات التعريف الخاصة بـ OAuth لدى Twenty عبر `/.well-known/oauth-protected-resource` و`/.well-known/oauth-authorization-server`
-2. تسجيل نفسه كعميل OAuth عبر التسجيل الديناميكي للعميل (RFC 7591)
-3. فتح متصفحك لتفويض الوصول
-4. استلام الرموز المميِّزة والاتصال بخادم MCP
-
-تعيد الاتصالات اللاحقة استخدام الرموز المميِّزة المخزنة وتحدِّثها تلقائيًا.
-
-### الخيار ب — مفتاح API
-
-إذا كان عميل MCP لديك لا يدعم OAuth، أو كنت تفضّل بيانات اعتماد ثابتة، فمرِّر مفتاح API في ترويسة `Authorization`:
-
-```json
-{
-  "mcpServers": {
-    "twenty": {
-      "type": "streamable-http",
-      "url": "https://{your-workspace-url}/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_API_KEY"
-      }
-    }
-  }
-}
-```
-
-<Warning>
-يمنح مفتاح API الخاص بك حق الوصول إلى بيانات مساحة العمل. أبعِده عن أنظمة التحكم في الإصدارات وملفات dotfiles المشتركة.
-</Warning>
-
-لإنشاء مفتاح API، انتقل إلى **Settings > APIs & Webhooks > + Create key**. راجع [واجهات برمجة التطبيقات](/l/ar/developers/extend/api#create-an-api-key) للتفاصيل.
-
-## البدء السريع
-
-### 1. انسخ الإعداد
-
-انتقل إلى **Settings > AI > More > MCP Server** في Twenty. اختر طريقة المصادقة (OAuth أو مفتاح API)، وانسخ مقطع JSON (سيستخدم بالفعل عنوان URL لمساحة العمل لديك)، ثم الصقه في ملف إعدادات عميل MCP لديك.
-
-| العميل             | موقع ملف الإعداد                                                                                                                                    |
-| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Claude Desktop** | `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) أو `%APPDATA%\Claude\claude_desktop_config.json` (Windows)                |
-| **Claude Code**    | `~/.claude.json` (المستخدم) أو `.mcp.json` (المشروع)                                                                                                |
-| **Cursor**         | `.cursor/mcp.json` ضمن مشروعك، أو `~/.cursor/mcp.json` عالميًا                                                                                      |
-| **ChatGPT**        | فعِّل وضع المطوّر في **Settings > Apps & Connectors > Advanced settings**، ثم استخدم **Create** في **Settings > Apps & Connectors** لإضافة خادم MCP |
-
-### 2. الاتصال
-
-أعِد تشغيل عميل MCP لديك (أو أعد تحميل ملف الإعداد). إذا كنت تستخدم OAuth فسيتم توجيهك إلى Twenty لتفويض الوصول. إذا كنت تستخدم مفتاح API فسيكون الاتصال فوريًا.
-
-### 3. ابدأ باستخدامه
-
-اطلب من مساعد الذكاء الاصطناعي التفاعل مع نظام إدارة علاقات العملاء (CRM) لديك:
-
-* *"أرني أحدث 5 شركات تم إنشاؤها"*
-* *"أنشئ شخصًا جديدًا باسم Jane Doe في Acme Corp"*
-* *"اعثر على جميع الفرص المفتوحة التي تزيد قيمتها عن 10 آلاف دولار"*
-
-## الأدوات المتاحة
-
-بعد الاتصال، يوفّر خادم MCP أدوات تعكس واجهة برمجة تطبيقات Twenty (API). سير العمل الموصى به هو:
-
-1. **`get_tool_catalog`** — اكتشف جميع الأدوات المتاحة
-2. **`learn_tools`** — احصل على مخطط الإدخال لأدوات محددة
-3. **`execute_tool`** — شغّل أداة
-
-لا تحتاج إلى تذكّر أسماء الأدوات. اسأل مساعد الذكاء الاصطناعي عمّا يمكنه فعله وسيستدعي `get_tool_catalog` تلقائيًا.
-
-## الصلاحيات
-
-ترث اتصالات MCP أذونات المستخدم المُصادَق عليه (OAuth) أو الدور المُعيَّن لمفتاح API. لتقييد ما يمكن لخادم MCP القيام به:
-
-* **OAuth**: ينطبق دور المستخدم في مساحة العمل.
-* **API Key**: عيِّن دورًا لمفتاح API ضمن **Settings > Roles**. راجع [الأذونات](/l/ar/user-guide/permissions-access/capabilities/permissions).
-
-## التكوين ذاتي الاستضافة
-
-في حالات الاستضافة الذاتية، استبدِل `{your-workspace-url}` بعنوان URL الخاص بالخادم لديك. تأكّد من أن قيمة `SERVER_URL` في بيئتك تطابق عنوان URL العام لمثيل Twenty لديك — إذ يُستخدَم ذلك لإنشاء بيانات تعريف اكتشاف OAuth.
-
-```bash
-SERVER_URL=https://twenty.yourcompany.com
-```
-
-تُشتق نقطة نهاية MCP ونقاط نهاية OAuth وبيانات تعريف الاكتشاف جميعها من هذه القيمة.
-
-## استكشاف الأخطاء وإصلاحها
-
-**أخطاء "Unauthorized" أو 401**
-
-* OAuth: أعد التفويض عبر مسح الرموز المميِّزة المخزنة في عميل MCP لديك ثم أعد الاتصال.
-* API Key: تحقّق من أن المفتاح صالح ولم تنتهِ صلاحيته. أعِد توليده إذا لزم الأمر.
-
-**عملية OAuth لا تفتح متصفحًا**
-
-* تأكّد من أن عميل MCP لديك يدعم تفويض MCP. ارجع إلى طريقة مفتاح API إذا لم يكن كذلك.
-
-**انتهاء مهلة الاتصال**
-
-* تحقّق من إمكانية الوصول إلى عنوان URL لنقطة نهاية MCP من جهازك. بالنسبة لحالات الاستضافة الذاتية، تحقّق من أن الخادم يعمل وأن `SERVER_URL` مُعيَّن بشكل صحيح.
@@ -1,121 +0,0 @@
---
-title: الرد التلقائي على رسائل البريد الإلكتروني الواردة
-description: أنشئ سير عمل يستخدم الذكاء الاصطناعي لفرز رسائل البريد الإلكتروني الواردة وإرسال ردود ضمن سلسلة المحادثة تلقائيًا.
---
-
-استجب لرسائل البريد الإلكتروني الواردة خلال ثوانٍ — وليس ساعات. يستخدم سير العمل هذا وكيلاً للذكاء الاصطناعي لتصفية الضوضاء (النشرات الإخبارية، الرسائل غير المرغوب فيها، الردود التلقائية) وصياغة رد مخصص للرسائل الحقيقية، ثم يرسله كرد مُسلسل داخل المحادثة الأصلية.
-
-## كيف يعمل تسلسل رسائل البريد الإلكتروني
-
-تحمل كل رسالة بريد إلكتروني ترويسة `Message-ID` مخفية — بصمة فريدة يعيّنها خادم بريد المرسل. عند الرد على بريد إلكتروني، يقوم عميل البريد لديك بتعيين ترويسة `In-Reply-To` التي تُشير إلى تلك البصمة. بهذه الطريقة يقوم Gmail وOutlook وكل عميل آخر بتجميع الرسائل في سلاسل المحادثات.
-
-في Twenty، تُخزَّن تلك البصمة كـ `headerMessageId` على كائن Message. يلتقطه سير العمل لديك ويمرّره إلى حقل In-Reply-To لإجراء Send Email.
-
-## بناء سير العمل
-
-### الخطوة 1: إنشاء سير عمل جديد
-
-توجّه إلى **Settings -> Workflows** وانقر **+ New Workflow**.
-
-### الخطوة 2: التشغيل عند الرسائل الواردة
-
-اختر **When a Record is Created** ثم **Messages**.
-
-في كل مرة يصل فيها بريد إلكتروني إلى Twenty، يُشغَّل هذا.
-
-<img src="/images/user-guide/workflows/auto-reply/workflow-overview.png" style={{width:'100%'}} />
-
-### الخطوة 3: البحث عن المُرسِل
-
-أضِف إجراء **Search Records**.
-
-عنوان المُرسِل ليس في الرسالة نفسها — بل في سجل Message Participant المرتبط.
-
-| الحقل      | القيمة                             |
-| ---------- | ---------------------------------- |
-| **الكائن** | المشاركون في الرسالة               |
-| **تصفية**  | Message **يساوي** `{{trigger.id}}` |
-| **تصفية**  | Role **يساوي** From                |
-| **الحد**   | 1                                  |
-
-سيمنحك هذا بريد المُرسِل الإلكتروني في `handle` واسمه في `displayName`.
-
-<img src="/images/user-guide/workflows/auto-reply/find-sender.png" style={{width:'100%'}} />
-
-### الخطوة 4: الفرز بالذكاء الاصطناعي وصياغة الرد
-
-أضِف إجراء **AI Agent**. تقوم هذه الخطوة الواحدة بأمرين: تقرر ما إذا كان البريد الإلكتروني يستحق الرد، وإن كان كذلك، تصوغ ردًا.
-
-استخدم موجهًا مثل:
-
-```
-You are an email triage assistant for a sales team. Read the following
-inbound email and decide if it deserves a reply.
-
-Subject: {{trigger.subject}}
-Body: {{trigger.text}}
-From: {{Find Sender.first.displayName}} ({{Find Sender.first.handle}})
-
-If this email is spam, a newsletter, an automated notification, or
-otherwise does not need a human reply, respond with exactly: SKIP
-
-Otherwise, write a short, professional reply (3-4 sentences max) that:
- Acknowledges their specific message
- Lets them know someone from the team will follow up shortly
- Is warm but not overly casual
-
-Respond with only the reply text, no subject line or greeting prefix.
-```
-
-يُنتِج AI Agent استجابته في الحقل `response` الذي يمكن للخطوات التالية الرجوع إليه.
-
-<img src="/images/user-guide/workflows/auto-reply/ai-triage.png" style={{width:'100%'}} />
-
-### الخطوة 5: التفريع بناءً على قرار الذكاء الاصطناعي
-
-أضِف إجراء **If/Else** للتحقق مما إذا كان الذكاء الاصطناعي قرر الرد أم التخطي.
-
-| الحقل              | القيمة                                      |
-| ------------------ | ------------------------------------------- |
-| **الشرط**          | AI Agent `response` **لا يحتوي على** `SKIP` |
-| **إذا كان صحيحًا** | المتابعة إلى Send Email                     |
-| **وإلا**           | لا تفعل شيئًا (ينتهي سير العمل)             |
-
-يتم تجاهل الرسائل غير المرغوب فيها والنشرات البريدية والرسائل المُنشأة تلقائيًا. كل ما عدا ذلك ينتقل إلى الخطوة التالية.
-
-<img src="/images/user-guide/workflows/auto-reply/should-reply.png" style={{width:'100%'}} />
-
-### الخطوة 6: إرسال رد ضمن سلسلة المحادثة
-
-أضِف إجراء **Send Email** على فرع "if true". انقر **Advanced options** ثم **Add In-Reply-To**.
-
-| الحقل           | القيمة                                 |
-| --------------- | -------------------------------------- |
-| **إلى**         | `{{Find Sender.first.handle}}`         |
-| **الموضوع**     | `Re: {{trigger.subject}}`              |
-| **المحتوى**     | `{{AI Triage & Draft Reply.response}}` |
-| **In-Reply-To** | `{{trigger.headerMessageId}}`          |
-
-حقل In-Reply-To هو ما يجعل هذا ردًا بدلًا من محادثة جديدة. سيراه المستلِم ضمن سلسلة تحت البريد الأصلي في Gmail أو Outlook أو أي عميل آخر.
-
-<img src="/images/user-guide/workflows/auto-reply/send-email.png" style={{width:'100%'}} />
-
-<Tip>
-**In-Reply-To** يتوقّع `message.headerMessageId` من المشغّل — إنها البصمة الفريدة للبريد الإلكتروني، وليست عنوان المستلم. إذا تركته فارغًا، فسيُرسَل البريد الإلكتروني على أي حال، ولكن كرسالة مستقلة.
-</Tip>
-
-<Warning>
-يستخدم Gmail سطر الموضوع لتجميع الرسائل في سلاسل المحادثات. يجب أن يبدأ الموضوع بـ `Re:` (بما في ذلك النقطتان والمسافة) ليعرض Gmail الرد داخل سلسلة المحادثة الأصلية. بدون ذلك، سيظهر الرد كمحادثة منفصلة — حتى إذا تم تعيين ترويسة In-Reply-To بشكل صحيح.
-</Warning>
-
-### الخطوة 7: الاختبار والتفعيل
-
-اضغط **Test**، ثم تحقّق من عميل البريد لديك. يجب أن يظهر الرد متداخلًا تحت الرسالة الأصلية.
-
-فعِّل عندما تكون راضيًا عنه.
-
-## أفكار للبناء عليها
-
-* **الرد على كبار الشخصيات فقط** — أضِف فرعًا يتحقق من مجال المُرسِل أو مما إذا كان موجودًا كجهة اتصال في Twenty
-* **التوجيه حسب النية** — استخدم موجهات AI Agent منفصلة للتعامل مع استفسارات المبيعات بشكل مختلف عن طلبات الدعم
-* **الإثراء قبل الرد** — أضِف خطوة Search Records لجلب شركة المُرسِل أو سجل الصفقات إلى الموجه الخاص بالذكاء الاصطناعي للحصول على ردود أكثر تخصيصًا
@@ -6,7 +6,7 @@ description: Der Leitfaden für Mitwirkende (oder neugierige Entwickler), die Tw
 ## Voraussetzungen

 <Tabs>
-<Tab title="Linux und macOS">
+<Tab title="Linux und MacOS">

 Bevor Sie Twenty installieren und verwenden können, stellen Sie sicher, dass Sie Folgendes auf Ihrem Computer installiert haben:
 * [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
@@ -103,7 +103,7 @@ Alle folgenden Befehle innerhalb des Projekts sind vom Stammverzeichnis aus ausz
 <Tabs>
  <Tab title="Linux">
    **Option 1 (bevorzugt):** Um Ihre Datenbank lokal bereitzustellen:
-    Verwenden Sie den folgenden Link, um PostgreSQL auf Ihrem Linux-Rechner zu installieren: [PostgreSQL-Installation](https://www.postgresql.org/download/linux/)
+    Verwenden Sie den folgenden Link, um PostgreSQL auf Ihrem Linux-Rechner zu installieren: [Postgresql-Installation](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -129,8 +129,8 @@ Alle folgenden Befehle innerhalb des Projekts sind vom Stammverzeichnis aus ausz
     brew services list
    ```

-    Das Installationsprogramm erstellt den Benutzer `postgres` möglicherweise nicht standardmäßig bei der Installation
-    über Homebrew auf macOS. Stattdessen wird eine PostgreSQL-Rolle erstellt, die Ihrem macOS
+    Der Installer erstellt möglicherweise nicht standardmäßig den Benutzer `postgres`, wenn er
+    über Homebrew auf MacOS installiert wird. Stattdessen wird eine PostgreSQL-Rolle erstellt, die Ihrem macOS
    Benutzernamen (z. B. "john") entspricht.
    Um zu überprüfen und, falls erforderlich, den Benutzer `postgres` zu erstellen, führen Sie folgende Schritte aus:
    ```bash
@@ -174,7 +174,7 @@ Alle folgenden Befehle innerhalb des Projekts sind vom Stammverzeichnis aus ausz
    Alle folgenden Schritte sind im WSL-Terminal auszuführen (innerhalb Ihrer virtuellen Maschine)

    **Option 1:** Um Ihr PostgreSQL lokal bereitzustellen:
-    Verwenden Sie den folgenden Link, um PostgreSQL auf Ihrer Linux-VM zu installieren: [PostgreSQL-Installation](https://www.postgresql.org/download/linux/)
+    Verwenden Sie den folgenden Link, um PostgreSQL auf Ihrer Linux-VM zu installieren: [Postgresql-Installation](https://www.postgresql.org/download/linux/)
    ```bash
      psql postgres -c "CREATE DATABASE \"default\";" -c "CREATE DATABASE test;"
    ```
@@ -189,13 +189,11 @@ Alle folgenden Befehle innerhalb des Projekts sind vom Stammverzeichnis aus ausz
  </Tab>
 </Tabs>

-Sie können nun über `localhost:5432` auf die Datenbank zugreifen.
-
-Wenn Sie die oben genannte Docker-Option verwendet haben, lauten die Standardanmeldedaten Benutzer `postgres` und Passwort `postgres`. Für native PostgreSQL-Installationen verwenden Sie die auf Ihrem Rechner konfigurierten Anmeldedaten und Rollen.
+Sie können jetzt über [localhost:5432](localhost:5432) auf die Datenbank zugreifen, mit dem Benutzer `postgres` und dem Passwort `postgres`.

 ## Schritt 4: Einrichten einer Redis-Datenbank (Cache)

-Twenty benötigt einen Redis-Cache, um die beste Leistung zu bieten.
+Twenty benötigt einen Redis-Cache, um die beste Leistung zu bieten

 <Tabs>
  <Tab title="Linux">
@@ -213,9 +211,7 @@ Twenty benötigt einen Redis-Cache, um die beste Leistung zu bieten.
    brew install redis
    ```
    Starten Sie Ihren Redis-Server:
-    ```bash
-    brew services start redis
-    ```
+    `brew services start redis`

    **Option 2:** Wenn Sie Docker installiert haben:
    ```bash
@@ -233,11 +229,11 @@ Twenty benötigt einen Redis-Cache, um die beste Leistung zu bieten.
  </Tab>
 </Tabs>

-Wenn Sie eine Client-GUI benötigen, empfehlen wir [Redis Insight](https://redis.io/insight/) (kostenlose Version verfügbar).
+Wenn Sie eine Client-GUI benötigen, empfehlen wir [redis insight](https://redis.io/insight/) (kostenlose Version verfügbar)

 ## Schritt 5: Einrichten von Umgebungsvariablen

-Verwenden Sie Umgebungsvariablen oder `.env`-Dateien, um Ihr Projekt zu konfigurieren. Weitere Informationen [hier](/l/de/developers/self-host/capabilities/setup).
+Verwenden Sie Umgebungsvariablen oder `.env`-Dateien, um Ihr Projekt zu konfigurieren. Weitere Informationen [hier](/l/de/developers/self-host/capabilities/setup)

 Kopieren Sie die `.env.example`-Dateien in `/front` und `/server`:

@@ -21,51 +21,19 @@ Mit Apps können Sie Twenty-Anpassungen **als Code** erstellen und verwalten. An
 ## Voraussetzungen

 * Node.js 24+ und Yarn 4
-* Docker (für den lokalen Twenty-Dev-Server)
+* Ein Twenty-Workspace und ein API-Schlüssel (unter https://app.twenty.com/settings/api-webhooks erstellen)

 ## Erste Schritte

-Erstelle eine neue App mit dem offiziellen Scaffolder. Der Scaffolder kann für dich automatisch eine lokale Twenty-Instanz starten:
+Erstellen Sie mit dem offiziellen Scaffolder eine neue App, authentifizieren Sie sich und beginnen Sie mit der Entwicklung:

 ```bash filename="Terminal"
-# Eine neue App erstellen — die CLI bietet an, einen lokalen Twenty-Server zu starten
+# Eine neue App erstellen (enthält standardmäßig alle Beispiele)
 npx create-twenty-app@latest my-twenty-app
 cd my-twenty-app

 # Dev-Modus starten: synchronisiert lokale Änderungen automatisch mit deinem Arbeitsbereich
-yarn twenty dev
-```
-
-### Lokale Serververwaltung
-
-Das SDK enthält Befehle zur Verwaltung eines lokalen Twenty-Dev-Servers (All-in-One-Docker-Image mit PostgreSQL, Redis, Server und Worker):
-
-```bash filename="Terminal"
-# Den lokalen Server starten (lädt das Image bei Bedarf herunter)
-yarn twenty server start
-
-# Serverstatus prüfen
-yarn twenty server status
-
-# Serverprotokolle streamen
-yarn twenty server logs
-
-# Server stoppen
-yarn twenty server stop
-
-# Alle Daten zurücksetzen und neu starten
-yarn twenty server reset
-```
-
-Der lokale Server ist bereits mit einem Arbeitsbereich und einem Benutzer (`tim@apple.dev` / `tim@apple.dev`) vorbefüllt, sodass Sie ohne manuelle Einrichtung sofort mit der Entwicklung beginnen können.
-
-### Authentifizierung
-
-Verbinden Sie Ihre App mithilfe von OAuth mit dem lokalen Server:
-
-```bash filename="Terminal"
-# Authenticate via OAuth (opens browser)
-yarn twenty remote add --local
+yarn twenty app:dev
 ```

 Das Scaffolding-Tool unterstützt zwei Modi, um zu steuern, welche Beispieldateien enthalten sind:
@@ -96,17 +64,11 @@ yarn twenty function:execute --preInstall
 # Die Post-Installationsfunktion ausführen
 yarn twenty function:execute --postInstall

-# Die Anwendung für die Verteilung erstellen
-yarn twenty app:build
-
-# Die Anwendung auf npm oder einen Twenty-Server veröffentlichen
-yarn twenty app:publish
-
 # Die Anwendung aus dem aktuellen Arbeitsbereich deinstallieren
 yarn twenty app:uninstall

 # Hilfe zu Befehlen anzeigen
-yarn twenty help
+yarn twenty help},{
 ```

 Siehe auch: die CLI-Referenzseiten für [create-twenty-app](https://www.npmjs.com/package/create-twenty-app) und [twenty-sdk CLI](https://www.npmjs.com/package/twenty-sdk).
@@ -1278,113 +1240,6 @@ Hauptpunkte:

 Ein minimales End-to-End-Beispiel, das Objekte, Logikfunktionen, Frontend-Komponenten und mehrere Trigger demonstriert, finden Sie [hier](https://github.com/twentyhq/twenty/tree/main/packages/twenty-apps/hello-world):

-## Erstellen Ihrer App
-
-Sobald Sie Ihre App mit `app:dev` entwickelt haben, verwenden Sie `app:build`, um sie in ein verteilbares Paket zu kompilieren.
-
-```bash filename="Terminal"
-# Die App erstellen (Ausgabe nach .twenty/output/)
-yarn twenty app:build
-
-# Build ausführen und ein Tarball (.tgz) für die Verteilung erstellen
-yarn twenty app:build --tarball
-```
-
-Der Build-Prozess:
-
-1. **Parst und validiert das Manifest** — liest alle `defineX()`-Entitäten aus Ihren Quelldateien und validiert die Manifeststruktur.
-2. **Kompiliert Logikfunktionen und Front-Komponenten** — bündelt TypeScript-Quellcode in ESM `.mjs`-Dateien mit esbuild.
-3. **Erzeugt Checksummen** — berechnet MD5-Hashes für jede erstellte Datei, die im Manifest als `builtHandlerChecksum` / `builtComponentChecksum` gespeichert werden.
-4. **Generiert den typisierten API-Client** — führt eine Introspektion des GraphQL-Schemas durch und generiert die typisierten Clients `CoreApiClient` und `MetadataApiClient`.
-5. **Führt eine TypeScript-Typprüfung aus** — führt `tsc --noEmit` aus, um Typfehler vor der Veröffentlichung zu erkennen.
-6. **Baut mit dem generierten Client neu** — führt einen zweiten Kompiliervorgang durch, damit die generierten Client-Typen enthalten sind.
-7. **Erstellt optional einen Tarball** — wenn `--tarball` übergeben wird, wird `npm pack` ausgeführt, um eine `.tgz`-Datei zu erstellen, die für die Verteilung bereit ist.
-
-Der Build-Output in `.twenty/output/` enthält:
-
-```text
-.twenty/output/
-├── manifest.json              # Manifest with checksums for all built files
-├── package.json               # Copied from app root
-├── yarn.lock                  # Copied from app root
-├── src/
-│   ├── logic-functions/       # Compiled .mjs logic function files
-│   └── front-components/      # Compiled .mjs front component files
-├── public/                    # Static assets (if any)
-└── my-app-1.0.0.tgz          # Only with --tarball flag
-```
-
-| Option      | Beschreibung                                                   |
-| ----------- | -------------------------------------------------------------- |
-| `[appPath]` | Pfad zum App-Verzeichnis (standardmäßig aktuelles Verzeichnis) |
-| `--tarball` | Den Output zusätzlich in einen `.tgz`-Tarball packen           |
-
-## Veröffentlichen Ihrer App
-
-Verwenden Sie `app:publish`, um Ihre App zu verteilen — entweder zur npm-Registry oder direkt zu einem Twenty-Server.
-
-### Bei npm veröffentlichen (Standard)
-
-```bash filename="Terminal"
-# Publish to npm (requires npm login)
-yarn twenty app:publish
-
-# Publish with a dist-tag (e.g. beta, next)
-yarn twenty app:publish --tag beta
-```
-
-Dies baut die App und führt `npm publish` aus dem Verzeichnis `.twenty/output/` aus. Das veröffentlichte Paket kann dann von jedem Arbeitsbereich über den Twenty-Marktplatz installiert werden.
-
-### Auf einem Twenty-Server veröffentlichen
-
-```bash filename="Terminal"
-# Publish directly to a Twenty server
-yarn twenty app:publish --server https://app.twenty.com
-```
-
-Dies erstellt beim Build einen Tarball, lädt ihn über die GraphQL-Mutation `uploadAppTarball` auf den Server hoch und stößt die Installation in einem Schritt an. Dies ist nützlich für private Bereitstellungen oder Tests gegen einen bestimmten Server.
-
-| Option            | Beschreibung                                                       |
-| ----------------- | ------------------------------------------------------------------ |
-| `[appPath]`       | Pfad zum App-Verzeichnis (standardmäßig aktuelles Verzeichnis)     |
-| `--server <url>`  | Auf einen Twenty-Server anstelle von npm veröffentlichen           |
-| `--token <token>` | Authentifizierungstoken für den Zielserver                         |
-| `--tag <tag>`     | npm dist-tag (z. B. `beta`, `next`) — nur für npm-Veröffentlichung |
-
-## Anwendungsregistrierung
-
-Bevor eine App in einem Arbeitsbereich installiert werden kann, muss sie **registriert** werden. Eine Registrierung ist ein Metadatensatz, der beschreibt, woher die App stammt und wie sie authentifiziert wird. Dies wird in den meisten Fällen automatisch durch die CLI erledigt.
-
-### Quelltypen
-
-Jede Registrierung hat einen **Quelltyp**, der bestimmt, wie die Dateien der App während der Installation aufgelöst werden:
-
-| Quelltyp  | Wie Dateien aufgelöst werden                                                                   | Typischer Anwendungsfall                               |
-| --------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------ |
-| `LOCAL`   | Dateien werden in Echtzeit vom CLI-Watcher synchronisiert — die Installation wird übersprungen | Entwicklung mit `app:dev`                              |
-| `NPM`     | Über das Feld `sourcePackage` aus der npm-Registry abgerufen                                   | Veröffentlichte Apps auf npm                           |
-| `TARBALL` | Aus einer hochgeladenen, auf dem Server gespeicherten `.tgz`-Datei extrahiert                  | Private Apps, die mit `--server` veröffentlicht wurden |
-
-### Wie die Registrierung erfolgt
-
-* **`app:dev`** — erstellt beim ersten Ausführen des Dev-Modus für einen Arbeitsbereich automatisch eine `LOCAL`-Registrierung.
-* **`app:publish --server`** — lädt einen Tarball hoch und erstellt (oder aktualisiert) eine `TARBALL`-Registrierung und installiert anschließend die App.
-* **npm-Marktplatz** — `NPM`-Registrierungen werden erstellt, wenn Apps aus der npm-Registry in den Twenty-Marktplatzkatalog synchronisiert werden.
-* **GraphQL-API** — Sie können Registrierungen auch programmgesteuert über die Mutation `createApplicationRegistration` erstellen.
-
-### Registrierung vs. Installation
-
-**Registrierung** und **Installation** sind unterschiedliche Konzepte:
-
-* Eine **Registrierung** (`ApplicationRegistration`) ist ein globaler Metadatensatz, der die App beschreibt: ihren Namen, den Quelltyp, die OAuth-Anmeldedaten und den Status der Marktplatzlistung. Sie existiert unabhängig von jedem Arbeitsbereich.
-* Eine **Installation** (`Application`) ist eine Instanz pro Arbeitsbereich. Wenn ein Benutzer eine App installiert, ermittelt Twenty das Paket aus der Quelle der Registrierung, schreibt die erstellten Dateien in den Speicher und synchronisiert das Manifest (wobei Objekte, Felder, Logikfunktionen usw. erstellt werden) in diesem Arbeitsbereich.
-
-Eine Registrierung kann in vielen Arbeitsbereichen installiert werden. Jeder Arbeitsbereich erhält seine eigene Kopie der Dateien und des Datenmodells der App.
-
-### OAuth-Anmeldedaten
-
-Jede Registrierung enthält OAuth-Anmeldedaten (`oAuthClientId` und `oAuthClientSecret`), die bei der Erstellung generiert werden. Diese werden von der App verwendet, um API-Anfragen im Namen der Benutzer zu authentifizieren. Das Client-Secret wird bei der Erstellung **einmalig** zurückgegeben — bewahren Sie es sicher auf. Sie können es später über die Mutation `rotateApplicationRegistrationClientSecret` rotieren.
-
 ## Manuelle Einrichtung (ohne Scaffolder)

 Wir empfehlen zwar `create-twenty-app` für das beste Einstiegserlebnis, Sie können ein Projekt aber auch manuell einrichten. Installieren Sie die CLI nicht global. Fügen Sie stattdessen `twenty-sdk` als lokale Abhängigkeit hinzu und binden Sie ein einzelnes Skript in Ihrer package.json ein:
--- a/Show More
+++ b/Show More