fix(billing): gate AI credit-cap at entry points instead of workflow executor

Restores the credit-cap enforcement that was lifted in #19904 (which had
correctly identified that gating per-workflow-step was too coarse), but
moves it to the AI entry points where the actual cost lives.

- agent-async-executor.service: gate executeAgent.
- ai-generate-text.controller: gate the REST handler.
- agent-title-generation.service: gate generateThreadTitle.
- workflow-executor.workspace-service: replace #19904's TODO with an
  absolute-behavior comment documenting why the gate is not here.

Chat resolver was already gated; no change there. Repair-tool-call util
is a sub-call inside an already-gated flow and is left ungated.

Net effect: a workspace that exhausts credits via chat or AI agent stops
making AI calls, but its non-AI workflows (DB CRUD, branching, action
steps) continue running normally.

Addresses the root cause of the 2026-04-26 token-usage incident.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.claude-pr/.mcp.json

@@ -0,0 +1,22 @@
+{
+  "mcpServers": {
+    "postgres": {
+      "type": "stdio",
+      "command": "bash",
+      "args": ["-c", "source packages/twenty-server/.env && npx -y @modelcontextprotocol/server-postgres \"$PG_DATABASE_URL\""],
+      "env": {}
+    },
+    "playwright": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["@playwright/mcp@latest", "--no-sandbox", "--headless"],
+      "env": {}
+    },
+    "context7": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@upstash/context7-mcp"],
+      "env": {}
+    }
+  }
+}

.claude-pr/CLAUDE.md

@@ -0,0 +1,223 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+Twenty is an open-source CRM built with modern technologies in a monorepo structure. The codebase is organized as an Nx workspace with multiple packages.
+
+## Key Commands
+
+### Development
+```bash
+# Start development environment (frontend + backend + worker)
+yarn start
+
+# Individual package development
+npx nx start twenty-front     # Start frontend dev server
+npx nx start twenty-server    # Start backend server
+npx nx run twenty-server:worker  # Start background worker
+```
+
+### Testing
+```bash
+# Preferred: run a single test file (fast)
+npx jest path/to/test.test.ts --config=packages/PROJECT/jest.config.mjs
+
+# Run all tests for a package
+npx nx test twenty-front      # Frontend unit tests
+npx nx test twenty-server     # Backend unit tests
+npx nx run twenty-server:test:integration:with-db-reset  # Integration tests with DB reset
+# To run an indivual test or a pattern of tests, use the following command:
+cd packages/{workspace} && npx jest "pattern or filename"
+
+# Storybook
+npx nx storybook:build twenty-front
+npx nx storybook:test twenty-front
+
+# When testing the UI end to end, click on "Continue with Email" and use the prefilled credentials.
+```
+
+### Code Quality
+```bash
+# Linting (diff with main - fastest, always prefer this)
+npx nx lint:diff-with-main twenty-front
+npx nx lint:diff-with-main twenty-server
+npx nx lint:diff-with-main twenty-front --configuration=fix  # Auto-fix
+
+# Linting (full project - slower, use only when needed)
+npx nx lint twenty-front
+npx nx lint twenty-server
+
+# Type checking
+npx nx typecheck twenty-front
+npx nx typecheck twenty-server
+
+# Format code
+npx nx fmt twenty-front
+npx nx fmt twenty-server
+```
+
+### Build
+```bash
+# Build packages (twenty-shared must be built first)
+npx nx build twenty-shared
+npx nx build twenty-front
+npx nx build twenty-server
+```
+
+### Database Operations
+```bash
+# Database management
+npx nx database:reset twenty-server         # Reset database
+npx nx run twenty-server:database:init:prod # Initialize database
+npx nx run twenty-server:database:migrate:prod # Run instance commands (fast only)
+
+# Generate an instance command (fast or slow)
+npx nx run twenty-server:database:migrate:generate --name <name> --type <fast|slow>
+```
+
+### 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 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)
+npx nx run twenty-front:graphql:generate
+npx nx run twenty-front:graphql:generate --configuration=metadata
+```
+
+## Architecture Overview
+
+### Tech Stack
+- **Frontend**: React 18, TypeScript, Jotai (state management), Linaria (styling), Vite
+- **Backend**: NestJS, TypeORM, PostgreSQL, Redis, GraphQL (with GraphQL Yoga)
+- **Monorepo**: Nx workspace managed with Yarn 4
+
+### Package Structure
+```
+packages/
+├── twenty-front/          # React frontend application
+├── twenty-server/         # NestJS backend API
+├── twenty-ui/             # Shared UI components library
+├── twenty-shared/         # Common types and utilities
+├── twenty-emails/         # Email templates with React Email
+├── twenty-website/        # Next.js documentation website
+├── twenty-zapier/         # Zapier integration
+└── twenty-e2e-testing/    # Playwright E2E tests
+```
+
+### Key Development Principles
+- **Functional components only** (no class components)
+- **Named exports only** (no default exports)
+- **Types over interfaces** (except when extending third-party interfaces)
+- **String literals over enums** (except for GraphQL enums)
+- **No 'any' type allowed** — strict TypeScript enforced
+- **Event handlers preferred over useEffect** for state updates
+- **Props down, events up** — unidirectional data flow
+- **Composition over inheritance**
+- **No abbreviations** in variable names (`user` not `u`, `fieldMetadata` not `fm`)
+
+### Naming Conventions
+- **Variables/functions**: camelCase
+- **Constants**: SCREAMING_SNAKE_CASE
+- **Types/Classes**: PascalCase (suffix component props with `Props`, e.g. `ButtonProps`)
+- **Files/directories**: kebab-case with descriptive suffixes (`.component.tsx`, `.service.ts`, `.entity.ts`, `.dto.ts`, `.module.ts`)
+- **TypeScript generics**: descriptive names (`TData` not `T`)
+
+### File Structure
+- Components under 300 lines, services under 500 lines
+- Components in their own directories with tests and stories
+- Use `index.ts` barrel exports for clean imports
+- Import order: external libraries first, then internal (`@/`), then relative
+
+### Comments
+- Use short-form comments (`//`), not JSDoc blocks
+- Explain WHY (business logic), not WHAT
+- Do not comment obvious code
+- Multi-line comments use multiple `//` lines, not `/** */`
+
+### State Management
+- **Jotai** for global state: atoms for primitive state, selectors for derived state, atom families for dynamic collections
+- Component-specific state with React hooks (`useState`, `useReducer` for complex logic)
+- GraphQL cache managed by Apollo Client
+- Use functional state updates: `setState(prev => prev + 1)`
+
+### Backend Architecture
+- **NestJS modules** for feature organization
+- **TypeORM** for database ORM with PostgreSQL
+- **GraphQL** API with code-first approach
+- **Redis** for caching and session management
+- **BullMQ** for background job processing
+
+### Database & Upgrade Commands
+- **PostgreSQL** as primary database
+- **Redis** for caching and sessions
+- **ClickHouse** for analytics (when enabled)
+- When changing entity files, generate an **instance command** (`database:migrate:generate --name <name> --type <fast|slow>`)
+- **Fast** instance commands handle schema changes; **slow** ones add a `runDataMigration` step for data backfills
+- **Workspace commands** iterate over all active/suspended workspaces for per-workspace upgrades
+- Commands use `@RegisteredInstanceCommand` and `@RegisteredWorkspaceCommand` decorators for automatic discovery
+- Include both `up` and `down` logic in instance commands
+- Never delete or rewrite committed instance command `up`/`down` logic
+- See `packages/twenty-server/docs/UPGRADE_COMMANDS.md` for full documentation
+
+### Utility Helpers
+Use existing helpers from `twenty-shared` instead of manual type guards:
+- `isDefined()`, `isNonEmptyString()`, `isNonEmptyArray()`
+
+## Development Workflow
+
+IMPORTANT: Use Context7 for code generation, setup or configuration steps, or library/API documentation. Automatically use the Context7 MCP tools to resolve library IDs and get library docs without waiting for explicit requests.
+
+### Before Making Changes
+1. Always run linting (`lint:diff-with-main`) and type checking after code changes
+2. Test changes with relevant test suites (prefer single-file test runs)
+3. Ensure instance commands are generated for entity changes (`database:migrate:generate`)
+4. Check that GraphQL schema changes are backward compatible
+5. Run `graphql:generate` after any GraphQL schema changes
+
+### Code Style Notes
+- Use **Linaria** for styling with zero-runtime CSS-in-JS (styled-components pattern)
+- Follow **Nx** workspace conventions for imports
+- Use **Lingui** for internationalization
+- Apply security first, then formatting (sanitize before format)
+
+### Testing Strategy
+- **Test behavior, not implementation** — focus on user perspective
+- **Test pyramid**: 70% unit, 20% integration, 10% E2E
+- Query by user-visible elements (text, roles, labels) over test IDs
+- Use `@testing-library/user-event` for realistic interactions
+- Descriptive test names: "should [behavior] when [condition]"
+- Clear mocks between tests with `jest.clearAllMocks()`
+
+## Dev Environment Setup
+
+All dev environments (Claude Code web, Cursor, local) use one script:
+
+```bash
+bash packages/twenty-utils/setup-dev-env.sh
+```
+
+This handles everything: starts Postgres + Redis (auto-detects local services vs Docker), creates databases, and copies `.env` files. Idempotent — safe to run multiple times.
+
+- `--docker` — force Docker mode (uses `packages/twenty-docker/docker-compose.dev.yml`)
+- `--down` — stop services
+- `--reset` — wipe data and restart fresh
+- **Skip the setup script** for tasks that only read code — architecture questions, code review, documentation, etc.
+
+**Note:** CI workflows (GitHub Actions) manage services via Actions service containers and run setup steps individually — they don't use this script.
+
+## Important Files
+- `nx.json` - Nx workspace configuration with task definitions
+- `tsconfig.base.json` - Base TypeScript configuration
+- `package.json` - Root package with workspace definitions
+- `.cursor/rules/` - Detailed development guidelines and best practices

.github/actions/yarn-install/action.yaml

@@ -7,17 +7,6 @@ inputs:
 runs:
   using: 'composite'
   steps:
-    - name: Free disk space for install
-      if: runner.os == 'Linux'
-      shell: bash
-      run: |
-        # Default GitHub images ship large SDKs this repo does not use; removing
-        # them avoids ENOSPC when restoring or linking a full Yarn node_modules.
-        sudo rm -rf /usr/share/dotnet
-        sudo rm -rf /usr/local/lib/android
-        sudo rm -rf /opt/ghc
-        sudo rm -rf /opt/hostedtoolcache/CodeQL
-        df -h
     - name: Cache primary key builder
       id: globals
       shell: bash

.github/workflows/ci-server.yaml

@@ -78,83 +78,6 @@ jobs:
           tag: scope:backend
           tasks: lint,typecheck
 
-  server-previous-version-upgrade-mutation-guard:
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    steps:
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 10
-      - name: Get changed upgrade-version-command files
-        id: changed-files
-        uses: tj-actions/changed-files@v45
-        with:
-          files: |
-            packages/twenty-server/src/database/commands/upgrade-version-command/**
-      - name: Check upgrade version commands are in current version only
-        if: >
-          steps.changed-files.outputs.any_changed == 'true' &&
-          !contains(github.event.pull_request.labels.*.name, 'ci:allow-previous-version-upgrade-mutation')
-        run: |
-          VERSION_CONSTANT_FILE="packages/twenty-server/src/engine/core-modules/upgrade/constants/twenty-current-version.constant.ts"
-
-          CURRENT_VERSION=$(sed -n "s/.*TWENTY_CURRENT_VERSION = '\([0-9.]*\)'.*/\1/p" "$VERSION_CONSTANT_FILE")
-
-          if [ -z "$CURRENT_VERSION" ]; then
-            echo "::error::Could not extract TWENTY_CURRENT_VERSION from $VERSION_CONSTANT_FILE"
-            exit 1
-          fi
-
-          CURRENT_DIR=$(echo "$CURRENT_VERSION" | sed -E 's/^([0-9]+)\.([0-9]+)\..*/\1-\2/')
-
-          echo "Current version: $CURRENT_VERSION (directory: $CURRENT_DIR)"
-
-          ADDED_OFFENDERS=""
-          MODIFIED_OFFENDERS=""
-
-          check_files() {
-            local category="$1"
-            shift
-            for file in "$@"; do
-              VERSION_DIR=$(echo "$file" | sed -n 's|.*upgrade-version-command/\([0-9]*-[0-9]*\)/.*|\1|p')
-
-              if [ -n "$VERSION_DIR" ] && [ "$VERSION_DIR" != "$CURRENT_DIR" ]; then
-                if [ "$category" = "added" ]; then
-                  ADDED_OFFENDERS="$ADDED_OFFENDERS\n  - $file (version directory: $VERSION_DIR)"
-                else
-                  MODIFIED_OFFENDERS="$MODIFIED_OFFENDERS\n  - $file (version directory: $VERSION_DIR)"
-                fi
-              fi
-            done
-          }
-
-          check_files "added" ${{ steps.changed-files.outputs.added_files }}
-          check_files "modified" ${{ steps.changed-files.outputs.modified_files }}
-
-          if [ -n "$ADDED_OFFENDERS" ] || [ -n "$MODIFIED_OFFENDERS" ]; then
-            echo "This PR touches upgrade command files outside the current version directory ($CURRENT_DIR / $CURRENT_VERSION)."
-
-            if [ -n "$ADDED_OFFENDERS" ]; then
-              echo ""
-              echo "New files added to non-current version directories:"
-              echo -e "$ADDED_OFFENDERS"
-            fi
-
-            if [ -n "$MODIFIED_OFFENDERS" ]; then
-              echo ""
-              echo "Existing files modified in non-current version directories:"
-              echo -e "$MODIFIED_OFFENDERS"
-            fi
-
-            echo ""
-            echo "If this is intentional, add the label 'ci:allow-previous-version-upgrade-mutation' to this PR and re-run CI."
-            echo "Otherwise, please move your changes to the current version directory ($CURRENT_DIR)."
-
-            echo "::error::Upgrade commands were added or modified in non-current version directories."
-            exit 1
-          fi
-
   server-validation:
     needs: server-build
     timeout-minutes: 30
@@ -388,7 +311,6 @@ jobs:
         changed-files-check,
         server-build,
         server-lint-typecheck,
-        server-previous-version-upgrade-mutation-guard,
         server-validation,
         server-test,
         server-integration-test,

.github/workflows/i18n-pull.yaml

@@ -58,7 +58,6 @@ jobs:
           npx nx run twenty-server:lingui:compile --strict
           npx nx run twenty-emails:lingui:compile --strict
           npx nx run twenty-front:lingui:compile --strict
-          npx nx run twenty-website-new:lingui:compile --strict
         continue-on-error: true
 
       - name: Stash any changes before pulling translations
@@ -116,7 +115,6 @@ jobs:
           npx nx run twenty-server:lingui:compile
           npx nx run twenty-emails:lingui:compile
           npx nx run twenty-front:lingui:compile
-          npx nx run twenty-website-new:lingui:compile
           git status
           git add .
           if ! git diff --staged --quiet --exit-code; then

.github/workflows/i18n-push.yaml

@@ -41,7 +41,6 @@ jobs:
           npx nx run twenty-server:lingui:extract
           npx nx run twenty-emails:lingui:extract
           npx nx run twenty-front:lingui:extract
-          npx nx run twenty-website-new:lingui:extract
 
       - name: Check and commit extracted files
         id: check_extract_changes
@@ -61,7 +60,6 @@ jobs:
           npx nx run twenty-server:lingui:compile
           npx nx run twenty-emails:lingui:compile
           npx nx run twenty-front:lingui:compile
-          npx nx run twenty-website-new:lingui:compile
 
       - name: Check and commit compiled files
         id: check_compile_changes

package.json

@@ -1,18 +1,172 @@
 {
   "private": true,
+  "dependencies": {
+    "@apollo/client": "^4.0.0",
+    "@floating-ui/react": "^0.24.3",
+    "@linaria/core": "^6.2.0",
+    "@linaria/react": "^6.2.1",
+    "@radix-ui/colors": "^3.0.0",
+    "@sniptt/guards": "^0.2.0",
+    "@tabler/icons-react": "^3.31.0",
+    "@wyw-in-js/babel-preset": "^1.0.6",
+    "@wyw-in-js/vite": "^0.7.0",
+    "archiver": "^7.0.1",
+    "danger-plugin-todos": "^1.3.1",
+    "date-fns": "^2.30.0",
+    "date-fns-tz": "^2.0.0",
+    "deep-equal": "^2.2.2",
+    "file-type": "16.5.4",
+    "framer-motion": "^11.18.0",
+    "fuse.js": "^7.1.0",
+    "googleapis": "105",
+    "hex-rgb": "^5.0.0",
+    "immer": "^10.1.1",
+    "jotai": "^2.17.1",
+    "libphonenumber-js": "^1.10.26",
+    "lodash.camelcase": "^4.3.0",
+    "lodash.chunk": "^4.2.0",
+    "lodash.compact": "^3.0.1",
+    "lodash.escaperegexp": "^4.1.2",
+    "lodash.groupby": "^4.6.0",
+    "lodash.identity": "^3.0.0",
+    "lodash.isempty": "^4.4.0",
+    "lodash.isequal": "^4.5.0",
+    "lodash.isobject": "^3.0.2",
+    "lodash.kebabcase": "^4.1.1",
+    "lodash.mapvalues": "^4.6.0",
+    "lodash.merge": "^4.6.2",
+    "lodash.omit": "^4.5.0",
+    "lodash.pickby": "^4.6.0",
+    "lodash.snakecase": "^4.1.1",
+    "lodash.upperfirst": "^4.3.1",
+    "microdiff": "^1.3.2",
+    "next-with-linaria": "^1.3.0",
+    "planer": "^1.2.0",
+    "pluralize": "^8.0.0",
+    "react": "^18.2.0",
+    "react-dom": "^18.2.0",
+    "react-responsive": "^9.0.2",
+    "react-router-dom": "^6.30.3",
+    "react-tooltip": "^5.13.1",
+    "remark-gfm": "^4.0.1",
+    "rxjs": "^7.2.0",
+    "semver": "^7.5.4",
+    "slash": "^5.1.0",
+    "temporal-polyfill": "^0.3.0",
+    "ts-key-enum": "^2.0.12",
+    "tslib": "^2.8.1",
+    "type-fest": "4.10.1",
+    "typescript": "5.9.2",
+    "uuid": "^9.0.0",
+    "vite-tsconfig-paths": "^4.2.1",
+    "xlsx-ugnis": "^0.19.3",
+    "zod": "^4.1.11"
+  },
   "devDependencies": {
+    "@babel/core": "^7.14.5",
+    "@babel/preset-react": "^7.14.5",
+    "@babel/preset-typescript": "^7.24.6",
+    "@chromatic-com/storybook": "^4.1.3",
+    "@graphql-codegen/cli": "^3.3.1",
+    "@graphql-codegen/client-preset": "^4.1.0",
+    "@graphql-codegen/typescript": "^3.0.4",
+    "@graphql-codegen/typescript-operations": "^3.0.4",
+    "@graphql-codegen/typescript-react-apollo": "^3.3.7",
     "@nx/jest": "22.5.4",
     "@nx/js": "22.5.4",
     "@nx/react": "22.5.4",
     "@nx/storybook": "22.5.4",
     "@nx/vite": "22.5.4",
     "@nx/web": "22.5.4",
+    "@oxlint/plugins": "^1.51.0",
+    "@sentry/types": "^8",
+    "@storybook-community/storybook-addon-cookie": "^5.0.0",
+    "@storybook/addon-coverage": "^3.0.0",
+    "@storybook/addon-docs": "^10.3.3",
+    "@storybook/addon-links": "^10.3.3",
+    "@storybook/addon-vitest": "^10.3.3",
+    "@storybook/icons": "^2.0.1",
+    "@storybook/react-vite": "^10.3.3",
+    "@storybook/test-runner": "^0.24.2",
+    "@swc-node/register": "^1.11.1",
+    "@swc/cli": "^0.7.10",
+    "@swc/core": "^1.15.11",
+    "@swc/helpers": "~0.5.19",
+    "@swc/jest": "^0.2.39",
+    "@testing-library/dom": "^10.4.0",
+    "@testing-library/jest-dom": "^6.6.3",
+    "@testing-library/react": "^16.3.0",
+    "@types/addressparser": "^1.0.3",
+    "@types/bcrypt": "^5.0.0",
+    "@types/bytes": "^3.1.1",
+    "@types/chrome": "^0.0.267",
+    "@types/deep-equal": "^1.0.1",
+    "@types/fs-extra": "^11.0.4",
+    "@types/graphql-fields": "^1.3.6",
+    "@types/inquirer": "^9.0.9",
+    "@types/jest": "^30.0.0",
+    "@types/lodash.camelcase": "^4.3.7",
+    "@types/lodash.compact": "^3.0.9",
+    "@types/lodash.escaperegexp": "^4.1.9",
+    "@types/lodash.groupby": "^4.6.9",
+    "@types/lodash.identity": "^3.0.9",
+    "@types/lodash.isempty": "^4.4.7",
+    "@types/lodash.isequal": "^4.5.7",
+    "@types/lodash.isobject": "^3.0.7",
+    "@types/lodash.kebabcase": "^4.1.7",
+    "@types/lodash.mapvalues": "^4.6.9",
+    "@types/lodash.omit": "^4.5.9",
+    "@types/lodash.pickby": "^4.6.9",
+    "@types/lodash.snakecase": "^4.1.7",
+    "@types/lodash.upperfirst": "^4.3.7",
+    "@types/ms": "^0.7.31",
+    "@types/node": "^24.0.0",
+    "@types/passport-google-oauth20": "^2.0.11",
+    "@types/passport-jwt": "^3.0.8",
+    "@types/passport-microsoft": "^2.1.0",
+    "@types/pluralize": "^0.0.33",
     "@types/react": "^18.2.39",
+    "@types/react-datepicker": "^6.2.0",
     "@types/react-dom": "^18.2.15",
+    "@types/supertest": "^2.0.11",
+    "@types/uuid": "^9.0.2",
+    "@typescript/native-preview": "^7.0.0-dev.20260116.1",
+    "@vitejs/plugin-react-swc": "4.2.3",
+    "@vitest/browser-playwright": "^4.0.18",
+    "@vitest/coverage-istanbul": "^4.0.18",
+    "@vitest/coverage-v8": "^4.0.18",
+    "@yarnpkg/types": "^4.0.0",
+    "chromatic": "^6.18.0",
     "concurrently": "^8.2.2",
+    "danger": "^13.0.4",
+    "dotenv-cli": "^7.4.4",
+    "esbuild": "^0.25.10",
     "http-server": "^14.1.1",
+    "jest": "29.7.0",
+    "jest-environment-jsdom": "30.0.0-beta.3",
+    "jest-environment-node": "^29.4.1",
+    "jest-fetch-mock": "^3.0.3",
+    "jsdom": "~22.1.0",
+    "msw": "^2.12.7",
+    "msw-storybook-addon": "^2.0.6",
     "nx": "22.5.4",
-    "verdaccio": "^6.3.1"
+    "prettier": "^3.1.1",
+    "raw-loader": "^4.0.2",
+    "rimraf": "^5.0.5",
+    "source-map-support": "^0.5.20",
+    "storybook": "^10.3.3",
+    "storybook-addon-mock-date": "2.0.0",
+    "storybook-addon-pseudo-states": "^10.3.3",
+    "supertest": "^6.1.3",
+    "ts-jest": "^29.1.1",
+    "ts-loader": "^9.2.3",
+    "ts-node": "10.9.1",
+    "tsc-alias": "^1.8.16",
+    "tsconfig-paths": "^4.2.0",
+    "tsx": "^4.17.0",
+    "verdaccio": "^6.3.1",
+    "vite": "^7.0.0",
+    "vitest": "^4.0.18"
   },
   "engines": {
     "node": "^24.5.0",

packages/create-twenty-app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-twenty-app",
-  "version": "2.2.0",
+  "version": "2.0.0",
   "description": "Command-line interface to create Twenty application",
   "main": "dist/cli.cjs",
   "bin": "dist/cli.cjs",
@@ -40,17 +40,12 @@
     "uuid": "^13.0.0"
   },
   "devDependencies": {
-    "@swc/core": "^1.15.11",
-    "@swc/jest": "^0.2.39",
     "@types/fs-extra": "^11.0.0",
     "@types/inquirer": "^9.0.0",
-    "@types/jest": "^30.0.0",
     "@types/lodash.camelcase": "^4.3.7",
     "@types/lodash.kebabcase": "^4.1.7",
     "@types/lodash.startcase": "^4",
     "@types/node": "^20.0.0",
-    "jest": "29.7.0",
-    "jest-environment-node": "^29.4.1",
     "twenty-shared": "workspace:*",
     "typescript": "^5.9.2",
     "vite": "^7.0.0",

packages/create-twenty-app/src/cli.ts

@@ -26,7 +26,6 @@ const program = new Command(packageJson.name)
     '--skip-local-instance',
     'Skip the local Twenty instance setup prompt',
   )
-  .option('-y, --yes', 'Auto-confirm prompts (e.g. start existing container)')
   .helpOption('-h, --help', 'Display this help message.')
   .action(
     async (
@@ -37,7 +36,6 @@ const program = new Command(packageJson.name)
         displayName?: string;
         description?: string;
         skipLocalInstance?: boolean;
-        yes?: boolean;
       },
     ) => {
       if (directory && !/^[a-z0-9-]+$/.test(directory)) {
@@ -61,7 +59,6 @@ const program = new Command(packageJson.name)
         displayName: options?.displayName,
         description: options?.description,
         skipLocalInstance: options?.skipLocalInstance,
-        yes: options?.yes,
       });
     },
   );

packages/create-twenty-app/src/create-app.command.ts

@@ -11,9 +11,7 @@ import * as path from 'path';
 import { basename } from 'path';
 import {
   authLoginOAuth,
-  checkDockerRunning,
   ConfigService,
-  containerExists,
   detectLocalServer,
   serverStart,
   type ServerStartResult,
@@ -29,7 +27,6 @@ type CreateAppOptions = {
   displayName?: string;
   description?: string;
   skipLocalInstance?: boolean;
-  yes?: boolean;
 };
 
 export class CreateAppCommand {
@@ -74,7 +71,7 @@ export class CreateAppCommand {
       let serverResult: ServerStartResult | undefined;
 
       if (!options.skipLocalInstance) {
-        const shouldStartServer = await this.shouldStartServer(options.yes);
+        const shouldStartServer = await this.shouldStartServer();
 
         if (shouldStartServer) {
           const startResult = await serverStart({
@@ -226,35 +223,13 @@ export class CreateAppCommand {
     );
   }
 
-  private async shouldStartServer(autoConfirm?: boolean): Promise<boolean> {
+  private async shouldStartServer(): Promise<boolean> {
     const existingServerUrl = await detectLocalServer();
 
     if (existingServerUrl) {
       return true;
     }
 
-    if (checkDockerRunning() && containerExists()) {
-      if (autoConfirm) {
-        return true;
-      }
-
-      const { startExisting } = await inquirer.prompt([
-        {
-          type: 'confirm',
-          name: 'startExisting',
-          message:
-            'An existing Twenty server container was found. Would you like to start it?',
-          default: true,
-        },
-      ]);
-
-      return startExisting;
-    }
-
-    if (autoConfirm) {
-      return true;
-    }
-
     const { startDocker } = await inquirer.prompt([
       {
         type: 'confirm',

packages/twenty-apps/community/github-connector/package.json

@@ -1,6 +1,6 @@
 {
   "name": "github-connector",
-  "version": "0.2.0",
+  "version": "0.1.0",
   "license": "MIT",
   "engines": {
     "node": "^24.5.0",

packages/twenty-apps/community/github-connector/src/__tests__/schema.integration-test.ts

@@ -77,7 +77,6 @@ describe('PullRequestReview object', () => {
     expect(names).toContain('firstSubmittedAt');
     expect(names).toContain('lastSubmittedAt');
     expect(names).toContain('eventCount');
-    expect(names).toContain('isSelfReview');
     expect(names).toContain('reviewer');
     expect(names).toContain('pullRequest');
     expect(names).toContain('reviewEvents');

packages/twenty-apps/community/github-connector/src/__tests__/webhook-signature.integration-test.ts

@@ -82,17 +82,7 @@ describe('verifyGitHubSignature', () => {
 });
 
 describe('getRawBodyForSignature', () => {
-  it('prefers event.rawBody when the runtime forwarded it', () => {
-    const original = '{ "action": "opened", "number": 42 }';
-    expect(
-      getRawBodyForSignature({
-        body: { action: 'opened', number: 42 },
-        rawBody: original,
-      }),
-    ).toBe(original);
-  });
-
-  it('falls back to string body when rawBody is not provided', () => {
+  it('returns the string as-is for string body', () => {
     expect(
       getRawBodyForSignature({ body: '{"a":1}', isBase64Encoded: false }),
     ).toBe('{"a":1}');
@@ -129,22 +119,3 @@ describe('verifyGitHubSignature with parsed body', () => {
     });
   });
 });
-
-describe('end-to-end: server forwards rawBody, signature verifies', () => {
-  it('verifies a signature when rawBody is present alongside parsed body', () => {
-    const original = '{ "action": "opened", "number": 42 }';
-    const event = {
-      body: { action: 'opened', number: 42 },
-      rawBody: original,
-      isBase64Encoded: false,
-    };
-
-    const rawBody = getRawBodyForSignature(event);
-    const result = verifyGitHubSignature({
-      rawBody,
-      signatureHeader: sign(original),
-      secret: SECRET,
-    });
-    expect(result.ok).toBe(true);
-  });
-});

packages/twenty-apps/community/github-connector/src/modules/github/connector/webhook-signature.ts

@@ -7,11 +7,7 @@ export type SignatureVerificationResult =
 export function getRawBodyForSignature(event: {
   body: unknown;
   isBase64Encoded?: boolean;
-  rawBody?: string;
 }): string | null {
-  if (typeof event.rawBody === 'string') {
-    return event.rawBody;
-  }
   const raw = event.body;
   if (raw == null) return '';
   if (typeof raw === 'string') {

packages/twenty-apps/community/github-connector/src/modules/github/contributor/logic-functions/contributor-stats.logic-function.ts

@@ -298,12 +298,7 @@ const handler = async (
       const res = await client.query({
         pullRequestReviews: {
           __args: {
-            filter: {
-              and: [
-                { reviewerId: { eq: contributorId } },
-                { isSelfReview: { eq: false } },
-              ],
-            },
+            filter: { reviewerId: { eq: contributorId } },
             orderBy: [{ firstSubmittedAt: 'DescNullsLast' }],
             first: PAGE_SIZE,
             after: cursor,

packages/twenty-apps/community/github-connector/src/modules/github/contributor/logic-functions/top-contributors.logic-function.ts

@@ -198,7 +198,6 @@ const handler = async (
             const res = await client.query({
               pullRequestReviews: {
                 __args: {
-                  filter: { isSelfReview: { eq: false } },
                   orderBy: [{ firstSubmittedAt: 'DescNullsLast' }],
                   first: PAGE_SIZE,
                   after: cursor,

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/graphql/mutations/batch-upsert.ts

@@ -15,6 +15,5 @@ export async function batchUpsertConsolidatedReviews(
     eventCount: true,
     reviewerId: true,
     pullRequestId: true,
-    isSelfReview: true,
   }) as Promise<PullRequestReviewRow[]>;
 }

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/logic-functions/recompute-pull-request-reviews.logic-function.ts

@@ -23,10 +23,7 @@ type ReviewEventNode = {
   reviewerId: string | null;
   pullRequestId: string | null;
   reviewer: { ghLogin: string | null } | null;
-  pullRequest: {
-    githubNumber: number | null;
-    authorId: string | null;
-  } | null;
+  pullRequest: { githubNumber: number | null } | null;
 };
 
 type GroupContext = {
@@ -34,7 +31,6 @@ type GroupContext = {
   reviewerId: string | null;
   prNumber: number | null;
   reviewerLogin: string | null;
-  prAuthorId: string | null;
   events: { state: ReviewEventState; submittedAt: string | null }[];
 };
 
@@ -72,7 +68,7 @@ const handler = async (_event: RoutePayload<unknown>) => {
               reviewerId: true,
               pullRequestId: true,
               reviewer: { ghLogin: true },
-              pullRequest: { githubNumber: true, authorId: true },
+              pullRequest: { githubNumber: true },
             },
           },
           pageInfo: { hasNextPage: true, endCursor: true },
@@ -99,7 +95,6 @@ const handler = async (_event: RoutePayload<unknown>) => {
             reviewerId: node.reviewerId,
             prNumber: node.pullRequest?.githubNumber ?? null,
             reviewerLogin: node.reviewer?.ghLogin ?? null,
-            prAuthorId: node.pullRequest?.authorId ?? null,
             events: [],
           };
           groups.set(key, group);
@@ -110,9 +105,6 @@ const handler = async (_event: RoutePayload<unknown>) => {
         if (group.prNumber === null && node.pullRequest?.githubNumber != null) {
           group.prNumber = node.pullRequest.githubNumber;
         }
-        if (group.prAuthorId === null && node.pullRequest?.authorId) {
-          group.prAuthorId = node.pullRequest.authorId;
-        }
         group.events.push({
           state: node.state,
           submittedAt: node.submittedAt,
@@ -131,7 +123,6 @@ const handler = async (_event: RoutePayload<unknown>) => {
         prNumber: group.prNumber,
         reviewerLogin: group.reviewerLogin,
         events: group.events,
-        prAuthorId: group.prAuthorId,
       }),
     );
   }

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/objects/pull-request-review.object.ts

@@ -24,9 +24,6 @@ export const REVIEW_EVENT_COUNT_FIELD_UNIVERSAL_IDENTIFIER =
 export const PULL_REQUEST_REVIEW_CREATED_AT_FIELD_UNIVERSAL_IDENTIFIER =
   'b4d61187-1b78-5d6e-9752-79f994ff6d55';
 
-export const REVIEW_IS_SELF_REVIEW_FIELD_UNIVERSAL_IDENTIFIER =
-  'c1f3e8a2-9b5d-4e7f-8a6c-2d4b6f8e1a93';
-
 enum ReviewState {
   APPROVED = 'APPROVED',
   CHANGES_REQUESTED = 'CHANGES_REQUESTED',
@@ -119,15 +116,5 @@ export default defineObject({
       icon: 'IconHash',
       defaultValue: 0,
     },
-    {
-      universalIdentifier: REVIEW_IS_SELF_REVIEW_FIELD_UNIVERSAL_IDENTIFIER,
-      name: 'isSelfReview',
-      type: FieldType.BOOLEAN,
-      label: 'Self review',
-      description:
-        'True when the reviewer is the same contributor as the PR author. Self reviews are excluded from review-count aggregations (top reviewers, contributor stats, etc.) so contributors are credited only for reviews on other people\u2019s PRs.',
-      icon: 'IconUserCheck',
-      defaultValue: false,
-    },
   ],
 });

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/types/pull-request-review-row.ts

@@ -8,5 +8,4 @@ export type PullRequestReviewRow = {
   eventCount?: number | null;
   reviewerId?: string | null;
   pullRequestId?: string | null;
-  isSelfReview?: boolean | null;
 };

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/utils/build-consolidated-row.ts

@@ -12,7 +12,6 @@ export type ConsolidatedReviewUpsertInput = {
   eventCount: number;
   reviewerId: string | null;
   pullRequestId: string;
-  isSelfReview: boolean;
 };
 
 export type BuildConsolidatedRowParams = {
@@ -21,23 +20,8 @@ export type BuildConsolidatedRowParams = {
   prNumber: number | null;
   reviewerLogin: string | null;
   events: ReviewEventForConsolidation[];
-  /**
-   * Author of the PR being reviewed. When non-null and equal to `reviewerId`
-   * the consolidated row is flagged as a self-review so downstream
-   * aggregations (top reviewers, contributor stats, etc.) can exclude it.
-   */
-  prAuthorId?: string | null;
 };
 
-export const isSelfReview = (
-  reviewerId: string | null,
-  prAuthorId: string | null | undefined,
-): boolean =>
-  reviewerId !== null &&
-  prAuthorId !== null &&
-  prAuthorId !== undefined &&
-  reviewerId === prAuthorId;
-
 export const buildReviewKey = (
   pullRequestId: string,
   reviewerId: string | null,
@@ -65,6 +49,5 @@ export const buildConsolidatedRow = (
     eventCount: verdict.eventCount,
     reviewerId: params.reviewerId,
     pullRequestId: params.pullRequestId,
-    isSelfReview: isSelfReview(params.reviewerId, params.prAuthorId ?? null),
   };
 };

packages/twenty-apps/community/github-connector/src/modules/github/pull-request-review/utils/consolidate-reviews.integration-test.ts

@@ -8,7 +8,6 @@ import {
   buildConsolidatedRow,
   buildReviewKey,
   buildConsolidatedTitle,
-  isSelfReview,
 } from 'src/modules/github/pull-request-review/utils/build-consolidated-row';
 
 const evt = (
@@ -141,71 +140,6 @@ describe('buildConsolidatedRow', () => {
       eventCount: 3,
       reviewerId: 'rev-2',
       pullRequestId: 'pr-1',
-      isSelfReview: false,
     });
   });
-
-  it('flags isSelfReview when prAuthorId equals reviewerId', () => {
-    const row = buildConsolidatedRow({
-      pullRequestId: 'pr-1',
-      reviewerId: 'alice',
-      prNumber: 7,
-      reviewerLogin: 'alice',
-      prAuthorId: 'alice',
-      events: [evt('COMMENTED', '2025-04-01T10:00:00Z')],
-    });
-    expect(row.isSelfReview).toBe(true);
-  });
-
-  it('does not flag isSelfReview when prAuthorId differs from reviewerId', () => {
-    const row = buildConsolidatedRow({
-      pullRequestId: 'pr-1',
-      reviewerId: 'alice',
-      prNumber: 7,
-      reviewerLogin: 'alice',
-      prAuthorId: 'bob',
-      events: [evt('APPROVED', '2025-04-01T10:00:00Z')],
-    });
-    expect(row.isSelfReview).toBe(false);
-  });
-
-  it('does not flag isSelfReview when prAuthorId is missing', () => {
-    const row = buildConsolidatedRow({
-      pullRequestId: 'pr-1',
-      reviewerId: 'alice',
-      prNumber: 7,
-      reviewerLogin: 'alice',
-      events: [evt('APPROVED', '2025-04-01T10:00:00Z')],
-    });
-    expect(row.isSelfReview).toBe(false);
-  });
-
-  it('does not flag isSelfReview when reviewerId is null (ghost reviewer)', () => {
-    const row = buildConsolidatedRow({
-      pullRequestId: 'pr-1',
-      reviewerId: null,
-      prNumber: 7,
-      reviewerLogin: null,
-      prAuthorId: null,
-      events: [evt('COMMENTED', '2025-04-01T10:00:00Z')],
-    });
-    expect(row.isSelfReview).toBe(false);
-  });
-});
-
-describe('isSelfReview', () => {
-  it('returns true only when both ids are present and equal', () => {
-    expect(isSelfReview('a', 'a')).toBe(true);
-  });
-
-  it('returns false when ids differ', () => {
-    expect(isSelfReview('a', 'b')).toBe(false);
-  });
-
-  it('returns false when either side is null/undefined', () => {
-    expect(isSelfReview(null, 'a')).toBe(false);
-    expect(isSelfReview('a', null)).toBe(false);
-    expect(isSelfReview('a', undefined)).toBe(false);
-    expect(isSelfReview(null, null)).toBe(false);
-  });
 });

packages/twenty-apps/community/github-connector/src/modules/github/pull-request/logic-functions/fetch-prs.logic-function.ts

@@ -110,16 +110,9 @@ const handler = async (event: RoutePayload<FetchPrsPayload>) => {
     reviewerId: string | null;
     prNumber: number;
     reviewerLogin: string | null;
-    prAuthorId: string | null;
     events: { state: ReviewEventState; submittedAt: string | null }[];
   };
 
-  const authorIdByPullRequestId = new Map<string, string | null>();
-  for (const pr of prData) {
-    const id = prIdByNumber.get(pr.githubNumber);
-    if (id) authorIdByPullRequestId.set(id, pr.authorId);
-  }
-
   let skippedReviews = 0;
   const reviewEventData: ReviewEventInput[] = [];
   const groups = new Map<GroupKey, GroupContext>();
@@ -148,7 +141,6 @@ const handler = async (event: RoutePayload<FetchPrsPayload>) => {
           reviewerId,
           prNumber: pr.number,
           reviewerLogin: review.author?.login ?? null,
-          prAuthorId: authorIdByPullRequestId.get(pullRequestId) ?? null,
           events: [],
         };
         groups.set(key, group);
@@ -185,7 +177,6 @@ const handler = async (event: RoutePayload<FetchPrsPayload>) => {
         prNumber: group.prNumber,
         reviewerLogin: group.reviewerLogin,
         events: group.events,
-        prAuthorId: group.prAuthorId,
       }),
     );
     const consolidatedRecords = await timed(

packages/twenty-apps/examples/postcard/src/application.config.ts

@@ -8,6 +8,7 @@ export default defineApplication({
   universalIdentifier: APPLICATION_UNIVERSAL_IDENTIFIER,
   displayName: 'Postcard App',
   description: 'Send postcards easily with Twenty',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-apps/fixtures/minimal-app/application.config.ts

@@ -4,5 +4,6 @@ export default defineApplication({
   universalIdentifier: 'e1e2e3e4-e5e6-4000-8000-000000000001',
   displayName: 'Root App',
   description: 'An app with all entities at root level',
+  icon: 'IconFolder',
   defaultRoleUniversalIdentifier: 'e1e2e3e4-e5e6-4000-8000-000000000002',
 });

packages/twenty-apps/fixtures/rich-app/application.config.ts

@@ -5,6 +5,7 @@ export default defineApplication({
   universalIdentifier: '4ec0391d-18d5-411c-b2f3-266ddc1c3ef7',
   displayName: 'Rich App',
   description: 'A simple rich app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-client-sdk/package.json

@@ -1,6 +1,6 @@
 {
   "name": "twenty-client-sdk",
-  "version": "2.2.0",
+  "version": "2.0.0",
   "sideEffects": false,
   "license": "AGPL-3.0",
   "scripts": {
@@ -46,8 +46,6 @@
     "graphql": "^16.8.1"
   },
   "devDependencies": {
-    "@typescript/native-preview": "^7.0.0-dev.20260116.1",
-    "tsc-alias": "^1.8.16",
     "twenty-shared": "workspace:*",
     "typescript": "^5.9.2",
     "vite": "^7.0.0",

packages/twenty-client-sdk/src/metadata/generated/schema.graphql

@@ -580,7 +580,6 @@ type Application {
   id: UUID!
   name: String!
   description: String
-  logo: String
   version: String
   universalIdentifier: String!
   packageJsonChecksum: String
@@ -2203,6 +2202,7 @@ type MarketplaceApp {
   id: String!
   name: String!
   description: String!
+  icon: String!
   author: String!
   category: String!
   logo: String
@@ -2609,6 +2609,19 @@ type Skill {
   updatedAt: DateTime!
 }
 
+type AgentChatThread {
+  id: UUID!
+  title: String
+  totalInputTokens: Int!
+  totalOutputTokens: Int!
+  contextWindowTokens: Int
+  conversationSize: Int!
+  totalInputCredits: Float!
+  totalOutputCredits: Float!
+  createdAt: DateTime!
+  updatedAt: DateTime!
+}
+
 type AgentMessage {
   id: UUID!
   threadId: UUID!
@@ -2621,21 +2634,6 @@ type AgentMessage {
   createdAt: DateTime!
 }
 
-type AgentChatThread {
-  id: ID!
-  title: String
-  totalInputTokens: Int!
-  totalOutputTokens: Int!
-  contextWindowTokens: Int
-  conversationSize: Int!
-  totalInputCredits: Float!
-  totalOutputCredits: Float!
-  createdAt: DateTime!
-  updatedAt: DateTime!
-  deletedAt: DateTime
-  lastMessageAt: DateTime
-}
-
 type AiSystemPromptSection {
   title: String!
   content: String!
@@ -2663,6 +2661,22 @@ type AgentChatEvent {
   event: JSON!
 }
 
+type AgentChatThreadEdge {
+  """The node containing the AgentChatThread"""
+  node: AgentChatThread!
+
+  """Cursor for this node."""
+  cursor: ConnectionCursor!
+}
+
+type AgentChatThreadConnection {
+  """Paging information"""
+  pageInfo: PageInfo!
+
+  """Array of edges."""
+  edges: [AgentChatThreadEdge!]!
+}
+
 type AgentTurnEvaluation {
   id: UUID!
   turnId: UUID!
@@ -2979,13 +2993,22 @@ type Query {
   webhooks: [Webhook!]!
   webhook(id: UUID!): Webhook
   minimalMetadata: MinimalMetadata!
-  chatThreads: [AgentChatThread!]!
   chatThread(id: UUID!): AgentChatThread!
   chatMessages(threadId: UUID!): [AgentMessage!]!
   chatStreamCatchupChunks(threadId: UUID!): ChatStreamCatchupChunks!
   getAiSystemPromptPreview: AiSystemPromptPreview!
   skills: [Skill!]!
   skill(id: UUID!): Skill
+  chatThreads(
+    """Limit or page results."""
+    paging: CursorPaging! = {first: 10}
+
+    """Specify to filter the records returned."""
+    filter: AgentChatThreadFilter! = {}
+
+    """Specify to sort results."""
+    sorting: [AgentChatThreadSort!]! = [{field: updatedAt, direction: DESC}]
+  ): AgentChatThreadConnection!
   agentTurns(agentId: UUID!): [AgentTurn!]!
   checkUserExists(email: String!, captchaToken: String): CheckUserExist!
   checkWorkspaceInviteHashIsValid(inviteHash: String!): WorkspaceInviteHashValid!
@@ -3034,6 +3057,56 @@ input AgentIdInput {
   id: UUID!
 }
 
+input AgentChatThreadFilter {
+  and: [AgentChatThreadFilter!]
+  or: [AgentChatThreadFilter!]
+  id: UUIDFilterComparison
+  updatedAt: DateFieldComparison
+}
+
+input DateFieldComparison {
+  is: Boolean
+  isNot: Boolean
+  eq: DateTime
+  neq: DateTime
+  gt: DateTime
+  gte: DateTime
+  lt: DateTime
+  lte: DateTime
+  in: [DateTime!]
+  notIn: [DateTime!]
+  between: DateFieldComparisonBetween
+  notBetween: DateFieldComparisonBetween
+}
+
+input DateFieldComparisonBetween {
+  lower: DateTime!
+  upper: DateTime!
+}
+
+input AgentChatThreadSort {
+  field: AgentChatThreadSortFields!
+  direction: SortDirection!
+  nulls: SortNulls
+}
+
+enum AgentChatThreadSortFields {
+  id
+  updatedAt
+}
+
+"""Sort Directions"""
+enum SortDirection {
+  ASC
+  DESC
+}
+
+"""Sort Nulls Options"""
+enum SortNulls {
+  NULLS_FIRST
+  NULLS_LAST
+}
+
 input EventLogQueryInput {
   table: EventLogTable!
   filters: EventLogFiltersInput
@@ -3120,7 +3193,6 @@ type Mutation {
   updateView(id: String!, input: UpdateViewInput!): View!
   deleteView(id: String!): Boolean!
   destroyView(id: String!): Boolean!
-  upsertViewWidget(input: UpsertViewWidgetInput!): View!
   createViewSort(input: CreateViewSortInput!): ViewSort!
   updateViewSort(input: UpdateViewSortInput!): ViewSort!
   deleteViewSort(input: DeleteViewSortInput!): Boolean!
@@ -3219,10 +3291,6 @@ type Mutation {
   createChatThread: AgentChatThread!
   sendChatMessage(threadId: UUID!, text: String!, messageId: UUID!, browsingContext: JSON, modelId: String, fileIds: [UUID!]): SendChatMessageResult!
   stopAgentChatStream(threadId: UUID!): Boolean!
-  renameChatThread(id: UUID!, title: String!): AgentChatThread!
-  archiveChatThread(id: UUID!): AgentChatThread!
-  unarchiveChatThread(id: UUID!): AgentChatThread!
-  deleteChatThread(id: UUID!): Boolean!
   deleteQueuedChatMessage(messageId: UUID!): Boolean!
   createSkill(input: CreateSkillInput!): Skill!
   updateSkill(input: UpdateSkillInput!): Skill!
@@ -3442,59 +3510,6 @@ input UpdateViewInput {
   shouldHideEmptyGroups: Boolean
 }
 
-input UpsertViewWidgetInput {
-  """The id of the view widget (page layout widget)."""
-  widgetId: UUID!
-
-  """The view fields to upsert."""
-  viewFields: [UpsertViewWidgetViewFieldInput!]
-
-  """The view filters to upsert."""
-  viewFilters: [UpsertViewWidgetViewFilterInput!]
-
-  """The view filter groups to upsert."""
-  viewFilterGroups: [UpsertViewWidgetViewFilterGroupInput!]
-
-  """The view sorts to upsert."""
-  viewSorts: [UpsertViewWidgetViewSortInput!]
-}
-
-input UpsertViewWidgetViewFieldInput {
-  """The id of an existing view field to update."""
-  viewFieldId: UUID
-
-  """
-  The field metadata id. Used to create a new view field when viewFieldId is not provided.
-  """
-  fieldMetadataId: UUID
-  isVisible: Boolean!
-  position: Float!
-  size: Float
-}
-
-input UpsertViewWidgetViewFilterInput {
-  id: UUID
-  fieldMetadataId: UUID!
-  operand: ViewFilterOperand = CONTAINS
-  value: JSON!
-  viewFilterGroupId: UUID
-  positionInViewFilterGroup: Float
-  subFieldName: String
-}
-
-input UpsertViewWidgetViewFilterGroupInput {
-  id: UUID
-  parentViewFilterGroupId: UUID
-  logicalOperator: ViewFilterGroupLogicalOperator = AND
-  positionInViewFilterGroup: Float
-}
-
-input UpsertViewWidgetViewSortInput {
-  id: UUID
-  fieldMetadataId: UUID!
-  direction: ViewSortDirection = ASC
-}
-
 input CreateViewSortInput {
   id: UUID
   fieldMetadataId: UUID!

packages/twenty-client-sdk/src/metadata/generated/schema.ts

@@ -414,7 +414,6 @@ export interface Application {
     id: Scalars['UUID']
     name: Scalars['String']
     description?: Scalars['String']
-    logo?: Scalars['String']
     version?: Scalars['String']
     universalIdentifier: Scalars['String']
     packageJsonChecksum?: Scalars['String']
@@ -1941,6 +1940,7 @@ export interface MarketplaceApp {
     id: Scalars['String']
     name: Scalars['String']
     description: Scalars['String']
+    icon: Scalars['String']
     author: Scalars['String']
     category: Scalars['String']
     logo?: Scalars['String']
@@ -2304,6 +2304,20 @@ export interface Skill {
     __typename: 'Skill'
 }
 
+export interface AgentChatThread {
+    id: Scalars['UUID']
+    title?: Scalars['String']
+    totalInputTokens: Scalars['Int']
+    totalOutputTokens: Scalars['Int']
+    contextWindowTokens?: Scalars['Int']
+    conversationSize: Scalars['Int']
+    totalInputCredits: Scalars['Float']
+    totalOutputCredits: Scalars['Float']
+    createdAt: Scalars['DateTime']
+    updatedAt: Scalars['DateTime']
+    __typename: 'AgentChatThread'
+}
+
 export interface AgentMessage {
     id: Scalars['UUID']
     threadId: Scalars['UUID']
@@ -2317,22 +2331,6 @@ export interface AgentMessage {
     __typename: 'AgentMessage'
 }
 
-export interface AgentChatThread {
-    id: Scalars['ID']
-    title?: Scalars['String']
-    totalInputTokens: Scalars['Int']
-    totalOutputTokens: Scalars['Int']
-    contextWindowTokens?: Scalars['Int']
-    conversationSize: Scalars['Int']
-    totalInputCredits: Scalars['Float']
-    totalOutputCredits: Scalars['Float']
-    createdAt: Scalars['DateTime']
-    updatedAt: Scalars['DateTime']
-    deletedAt?: Scalars['DateTime']
-    lastMessageAt?: Scalars['DateTime']
-    __typename: 'AgentChatThread'
-}
-
 export interface AiSystemPromptSection {
     title: Scalars['String']
     content: Scalars['String']
@@ -2365,6 +2363,22 @@ export interface AgentChatEvent {
     __typename: 'AgentChatEvent'
 }
 
+export interface AgentChatThreadEdge {
+    /** The node containing the AgentChatThread */
+    node: AgentChatThread
+    /** Cursor for this node. */
+    cursor: Scalars['ConnectionCursor']
+    __typename: 'AgentChatThreadEdge'
+}
+
+export interface AgentChatThreadConnection {
+    /** Paging information */
+    pageInfo: PageInfo
+    /** Array of edges. */
+    edges: AgentChatThreadEdge[]
+    __typename: 'AgentChatThreadConnection'
+}
+
 export interface AgentTurnEvaluation {
     id: Scalars['UUID']
     turnId: Scalars['UUID']
@@ -2577,13 +2591,13 @@ export interface Query {
     webhooks: Webhook[]
     webhook?: Webhook
     minimalMetadata: MinimalMetadata
-    chatThreads: AgentChatThread[]
     chatThread: AgentChatThread
     chatMessages: AgentMessage[]
     chatStreamCatchupChunks: ChatStreamCatchupChunks
     getAiSystemPromptPreview: AiSystemPromptPreview
     skills: Skill[]
     skill?: Skill
+    chatThreads: AgentChatThreadConnection
     agentTurns: AgentTurn[]
     checkUserExists: CheckUserExist
     checkWorkspaceInviteHashIsValid: WorkspaceInviteHashValid
@@ -2619,6 +2633,16 @@ export interface Query {
     __typename: 'Query'
 }
 
+export type AgentChatThreadSortFields = 'id' | 'updatedAt'
+
+
+/** Sort Directions */
+export type SortDirection = 'ASC' | 'DESC'
+
+
+/** Sort Nulls Options */
+export type SortNulls = 'NULLS_FIRST' | 'NULLS_LAST'
+
 export type EventLogTable = 'WORKSPACE_EVENT' | 'PAGEVIEW' | 'OBJECT_EVENT' | 'USAGE_EVENT' | 'APPLICATION_LOG'
 
 export type UsageOperationType = 'AI_CHAT_TOKEN' | 'AI_WORKFLOW_TOKEN' | 'WORKFLOW_EXECUTION' | 'CODE_EXECUTION' | 'WEB_SEARCH'
@@ -2651,7 +2675,6 @@ export interface Mutation {
     updateView: View
     deleteView: Scalars['Boolean']
     destroyView: Scalars['Boolean']
-    upsertViewWidget: View
     createViewSort: ViewSort
     updateViewSort: ViewSort
     deleteViewSort: Scalars['Boolean']
@@ -2750,10 +2773,6 @@ export interface Mutation {
     createChatThread: AgentChatThread
     sendChatMessage: SendChatMessageResult
     stopAgentChatStream: Scalars['Boolean']
-    renameChatThread: AgentChatThread
-    archiveChatThread: AgentChatThread
-    unarchiveChatThread: AgentChatThread
-    deleteChatThread: Scalars['Boolean']
     deleteQueuedChatMessage: Scalars['Boolean']
     createSkill: Skill
     updateSkill: Skill
@@ -3294,7 +3313,6 @@ export interface ApplicationGenqlSelection{
     id?: boolean | number
     name?: boolean | number
     description?: boolean | number
-    logo?: boolean | number
     version?: boolean | number
     universalIdentifier?: boolean | number
     packageJsonChecksum?: boolean | number
@@ -4904,6 +4922,7 @@ export interface MarketplaceAppGenqlSelection{
     id?: boolean | number
     name?: boolean | number
     description?: boolean | number
+    icon?: boolean | number
     author?: boolean | number
     category?: boolean | number
     logo?: boolean | number
@@ -5299,20 +5318,6 @@ export interface SkillGenqlSelection{
     __scalar?: boolean | number
 }
 
-export interface AgentMessageGenqlSelection{
-    id?: boolean | number
-    threadId?: boolean | number
-    turnId?: boolean | number
-    agentId?: boolean | number
-    role?: boolean | number
-    status?: boolean | number
-    parts?: AgentMessagePartGenqlSelection
-    processedAt?: boolean | number
-    createdAt?: boolean | number
-    __typename?: boolean | number
-    __scalar?: boolean | number
-}
-
 export interface AgentChatThreadGenqlSelection{
     id?: boolean | number
     title?: boolean | number
@@ -5324,8 +5329,20 @@ export interface AgentChatThreadGenqlSelection{
     totalOutputCredits?: boolean | number
     createdAt?: boolean | number
     updatedAt?: boolean | number
-    deletedAt?: boolean | number
-    lastMessageAt?: boolean | number
+    __typename?: boolean | number
+    __scalar?: boolean | number
+}
+
+export interface AgentMessageGenqlSelection{
+    id?: boolean | number
+    threadId?: boolean | number
+    turnId?: boolean | number
+    agentId?: boolean | number
+    role?: boolean | number
+    status?: boolean | number
+    parts?: AgentMessagePartGenqlSelection
+    processedAt?: boolean | number
+    createdAt?: boolean | number
     __typename?: boolean | number
     __scalar?: boolean | number
 }
@@ -5367,6 +5384,24 @@ export interface AgentChatEventGenqlSelection{
     __scalar?: boolean | number
 }
 
+export interface AgentChatThreadEdgeGenqlSelection{
+    /** The node containing the AgentChatThread */
+    node?: AgentChatThreadGenqlSelection
+    /** Cursor for this node. */
+    cursor?: boolean | number
+    __typename?: boolean | number
+    __scalar?: boolean | number
+}
+
+export interface AgentChatThreadConnectionGenqlSelection{
+    /** Paging information */
+    pageInfo?: PageInfoGenqlSelection
+    /** Array of edges. */
+    edges?: AgentChatThreadEdgeGenqlSelection
+    __typename?: boolean | number
+    __scalar?: boolean | number
+}
+
 export interface AgentTurnEvaluationGenqlSelection{
     id?: boolean | number
     turnId?: boolean | number
@@ -5581,13 +5616,19 @@ export interface QueryGenqlSelection{
     webhooks?: WebhookGenqlSelection
     webhook?: (WebhookGenqlSelection & { __args: {id: Scalars['UUID']} })
     minimalMetadata?: MinimalMetadataGenqlSelection
-    chatThreads?: AgentChatThreadGenqlSelection
     chatThread?: (AgentChatThreadGenqlSelection & { __args: {id: Scalars['UUID']} })
     chatMessages?: (AgentMessageGenqlSelection & { __args: {threadId: Scalars['UUID']} })
     chatStreamCatchupChunks?: (ChatStreamCatchupChunksGenqlSelection & { __args: {threadId: Scalars['UUID']} })
     getAiSystemPromptPreview?: AiSystemPromptPreviewGenqlSelection
     skills?: SkillGenqlSelection
     skill?: (SkillGenqlSelection & { __args: {id: Scalars['UUID']} })
+    chatThreads?: (AgentChatThreadConnectionGenqlSelection & { __args: {
+    /** Limit or page results. */
+    paging: CursorPaging, 
+    /** Specify to filter the records returned. */
+    filter: AgentChatThreadFilter, 
+    /** Specify to sort results. */
+    sorting: AgentChatThreadSort[]} })
     agentTurns?: (AgentTurnGenqlSelection & { __args: {agentId: Scalars['UUID']} })
     checkUserExists?: (CheckUserExistGenqlSelection & { __args: {email: Scalars['String'], captchaToken?: (Scalars['String'] | null)} })
     checkWorkspaceInviteHashIsValid?: (WorkspaceInviteHashValidGenqlSelection & { __args: {inviteHash: Scalars['String']} })
@@ -5634,6 +5675,14 @@ export interface AgentIdInput {
 /** The id of the agent. */
 id: Scalars['UUID']}
 
+export interface AgentChatThreadFilter {and?: (AgentChatThreadFilter[] | null),or?: (AgentChatThreadFilter[] | null),id?: (UUIDFilterComparison | null),updatedAt?: (DateFieldComparison | null)}
+
+export interface DateFieldComparison {is?: (Scalars['Boolean'] | null),isNot?: (Scalars['Boolean'] | null),eq?: (Scalars['DateTime'] | null),neq?: (Scalars['DateTime'] | null),gt?: (Scalars['DateTime'] | null),gte?: (Scalars['DateTime'] | null),lt?: (Scalars['DateTime'] | null),lte?: (Scalars['DateTime'] | null),in?: (Scalars['DateTime'][] | null),notIn?: (Scalars['DateTime'][] | null),between?: (DateFieldComparisonBetween | null),notBetween?: (DateFieldComparisonBetween | null)}
+
+export interface DateFieldComparisonBetween {lower: Scalars['DateTime'],upper: Scalars['DateTime']}
+
+export interface AgentChatThreadSort {field: AgentChatThreadSortFields,direction: SortDirection,nulls?: (SortNulls | null)}
+
 export interface EventLogQueryInput {table: EventLogTable,filters?: (EventLogFiltersInput | null),first?: (Scalars['Int'] | null),after?: (Scalars['String'] | null)}
 
 export interface EventLogFiltersInput {eventType?: (Scalars['String'] | null),userWorkspaceId?: (Scalars['String'] | null),dateRange?: (EventLogDateRangeInput | null),recordId?: (Scalars['String'] | null),objectMetadataId?: (Scalars['String'] | null)}
@@ -5676,7 +5725,6 @@ export interface MutationGenqlSelection{
     updateView?: (ViewGenqlSelection & { __args: {id: Scalars['String'], input: UpdateViewInput} })
     deleteView?: { __args: {id: Scalars['String']} }
     destroyView?: { __args: {id: Scalars['String']} }
-    upsertViewWidget?: (ViewGenqlSelection & { __args: {input: UpsertViewWidgetInput} })
     createViewSort?: (ViewSortGenqlSelection & { __args: {input: CreateViewSortInput} })
     updateViewSort?: (ViewSortGenqlSelection & { __args: {input: UpdateViewSortInput} })
     deleteViewSort?: { __args: {input: DeleteViewSortInput} }
@@ -5775,10 +5823,6 @@ export interface MutationGenqlSelection{
     createChatThread?: AgentChatThreadGenqlSelection
     sendChatMessage?: (SendChatMessageResultGenqlSelection & { __args: {threadId: Scalars['UUID'], text: Scalars['String'], messageId: Scalars['UUID'], browsingContext?: (Scalars['JSON'] | null), modelId?: (Scalars['String'] | null), fileIds?: (Scalars['UUID'][] | null)} })
     stopAgentChatStream?: { __args: {threadId: Scalars['UUID']} }
-    renameChatThread?: (AgentChatThreadGenqlSelection & { __args: {id: Scalars['UUID'], title: Scalars['String']} })
-    archiveChatThread?: (AgentChatThreadGenqlSelection & { __args: {id: Scalars['UUID']} })
-    unarchiveChatThread?: (AgentChatThreadGenqlSelection & { __args: {id: Scalars['UUID']} })
-    deleteChatThread?: { __args: {id: Scalars['UUID']} }
     deleteQueuedChatMessage?: { __args: {messageId: Scalars['UUID']} }
     createSkill?: (SkillGenqlSelection & { __args: {input: CreateSkillInput} })
     updateSkill?: (SkillGenqlSelection & { __args: {input: UpdateSkillInput} })
@@ -5900,30 +5944,6 @@ export interface CreateViewInput {id?: (Scalars['UUID'] | null),name: Scalars['S
 
 export interface UpdateViewInput {id?: (Scalars['UUID'] | null),name?: (Scalars['String'] | null),type?: (ViewType | null),icon?: (Scalars['String'] | null),position?: (Scalars['Float'] | null),isCompact?: (Scalars['Boolean'] | null),openRecordIn?: (ViewOpenRecordIn | null),kanbanAggregateOperation?: (AggregateOperations | null),kanbanAggregateOperationFieldMetadataId?: (Scalars['UUID'] | null),anyFieldFilterValue?: (Scalars['String'] | null),calendarLayout?: (ViewCalendarLayout | null),calendarFieldMetadataId?: (Scalars['UUID'] | null),visibility?: (ViewVisibility | null),mainGroupByFieldMetadataId?: (Scalars['UUID'] | null),shouldHideEmptyGroups?: (Scalars['Boolean'] | null)}
 
-export interface UpsertViewWidgetInput {
-/** The id of the view widget (page layout widget). */
-widgetId: Scalars['UUID'],
-/** The view fields to upsert. */
-viewFields?: (UpsertViewWidgetViewFieldInput[] | null),
-/** The view filters to upsert. */
-viewFilters?: (UpsertViewWidgetViewFilterInput[] | null),
-/** The view filter groups to upsert. */
-viewFilterGroups?: (UpsertViewWidgetViewFilterGroupInput[] | null),
-/** The view sorts to upsert. */
-viewSorts?: (UpsertViewWidgetViewSortInput[] | null)}
-
-export interface UpsertViewWidgetViewFieldInput {
-/** The id of an existing view field to update. */
-viewFieldId?: (Scalars['UUID'] | null),
-/** The field metadata id. Used to create a new view field when viewFieldId is not provided. */
-fieldMetadataId?: (Scalars['UUID'] | null),isVisible: Scalars['Boolean'],position: Scalars['Float'],size?: (Scalars['Float'] | null)}
-
-export interface UpsertViewWidgetViewFilterInput {id?: (Scalars['UUID'] | null),fieldMetadataId: Scalars['UUID'],operand?: (ViewFilterOperand | null),value: Scalars['JSON'],viewFilterGroupId?: (Scalars['UUID'] | null),positionInViewFilterGroup?: (Scalars['Float'] | null),subFieldName?: (Scalars['String'] | null)}
-
-export interface UpsertViewWidgetViewFilterGroupInput {id?: (Scalars['UUID'] | null),parentViewFilterGroupId?: (Scalars['UUID'] | null),logicalOperator?: (ViewFilterGroupLogicalOperator | null),positionInViewFilterGroup?: (Scalars['Float'] | null)}
-
-export interface UpsertViewWidgetViewSortInput {id?: (Scalars['UUID'] | null),fieldMetadataId: Scalars['UUID'],direction?: (ViewSortDirection | null)}
-
 export interface CreateViewSortInput {id?: (Scalars['UUID'] | null),fieldMetadataId: Scalars['UUID'],direction?: (ViewSortDirection | null),viewId: Scalars['UUID']}
 
 export interface UpdateViewSortInput {
@@ -7999,14 +8019,6 @@ export interface LogicFunctionLogsInput {applicationId?: (Scalars['UUID'] | null
     
 
 
-    const AgentMessage_possibleTypes: string[] = ['AgentMessage']
-    export const isAgentMessage = (obj?: { __typename?: any } | null): obj is AgentMessage => {
-      if (!obj?.__typename) throw new Error('__typename is missing in "isAgentMessage"')
-      return AgentMessage_possibleTypes.includes(obj.__typename)
-    }
-    
-
-
     const AgentChatThread_possibleTypes: string[] = ['AgentChatThread']
     export const isAgentChatThread = (obj?: { __typename?: any } | null): obj is AgentChatThread => {
       if (!obj?.__typename) throw new Error('__typename is missing in "isAgentChatThread"')
@@ -8015,6 +8027,14 @@ export interface LogicFunctionLogsInput {applicationId?: (Scalars['UUID'] | null
     
 
 
+    const AgentMessage_possibleTypes: string[] = ['AgentMessage']
+    export const isAgentMessage = (obj?: { __typename?: any } | null): obj is AgentMessage => {
+      if (!obj?.__typename) throw new Error('__typename is missing in "isAgentMessage"')
+      return AgentMessage_possibleTypes.includes(obj.__typename)
+    }
+    
+
+
     const AiSystemPromptSection_possibleTypes: string[] = ['AiSystemPromptSection']
     export const isAiSystemPromptSection = (obj?: { __typename?: any } | null): obj is AiSystemPromptSection => {
       if (!obj?.__typename) throw new Error('__typename is missing in "isAiSystemPromptSection"')
@@ -8055,6 +8075,22 @@ export interface LogicFunctionLogsInput {applicationId?: (Scalars['UUID'] | null
     
 
 
+    const AgentChatThreadEdge_possibleTypes: string[] = ['AgentChatThreadEdge']
+    export const isAgentChatThreadEdge = (obj?: { __typename?: any } | null): obj is AgentChatThreadEdge => {
+      if (!obj?.__typename) throw new Error('__typename is missing in "isAgentChatThreadEdge"')
+      return AgentChatThreadEdge_possibleTypes.includes(obj.__typename)
+    }
+    
+
+
+    const AgentChatThreadConnection_possibleTypes: string[] = ['AgentChatThreadConnection']
+    export const isAgentChatThreadConnection = (obj?: { __typename?: any } | null): obj is AgentChatThreadConnection => {
+      if (!obj?.__typename) throw new Error('__typename is missing in "isAgentChatThreadConnection"')
+      return AgentChatThreadConnection_possibleTypes.includes(obj.__typename)
+    }
+    
+
+
     const AgentTurnEvaluation_possibleTypes: string[] = ['AgentTurnEvaluation']
     export const isAgentTurnEvaluation = (obj?: { __typename?: any } | null): obj is AgentTurnEvaluation => {
       if (!obj?.__typename) throw new Error('__typename is missing in "isAgentTurnEvaluation"')
@@ -8786,6 +8822,21 @@ export const enumAllMetadataName = {
    webhook: 'webhook' as const
 }
 
+export const enumAgentChatThreadSortFields = {
+   id: 'id' as const,
+   updatedAt: 'updatedAt' as const
+}
+
+export const enumSortDirection = {
+   ASC: 'ASC' as const,
+   DESC: 'DESC' as const
+}
+
+export const enumSortNulls = {
+   NULLS_FIRST: 'NULLS_FIRST' as const,
+   NULLS_LAST: 'NULLS_LAST' as const
+}
+
 export const enumEventLogTable = {
    WORKSPACE_EVENT: 'WORKSPACE_EVENT' as const,
    PAGEVIEW: 'PAGEVIEW' as const,

packages/twenty-docker/twenty-app-dev/rootfs/etc/s6-overlay/scripts/register-crons.sh

@@ -4,6 +4,6 @@ set -e
 echo "==> START Registering cron jobs"
 
 cd /app/packages/twenty-server
-yarn command:prod cron:register:all
+yarn command:prod cron:register:all --dev-mode
 
 echo "==> DONE"

packages/twenty-docker/twenty-website-new/Dockerfile

@@ -11,12 +11,10 @@ COPY ./nx.json .
 COPY ./.yarn/releases /app/.yarn/releases
 COPY ./.yarn/patches /app/.yarn/patches
 COPY ./packages/twenty-oxlint-rules /app/packages/twenty-oxlint-rules
-COPY ./packages/twenty-shared/package.json /app/packages/twenty-shared/package.json
 COPY ./packages/twenty-website-new/package.json /app/packages/twenty-website-new/package.json
 
 RUN yarn
 
-COPY ./packages/twenty-shared /app/packages/twenty-shared
 COPY ./packages/twenty-website-new /app/packages/twenty-website-new
 RUN npx nx build twenty-website-new
 

packages/twenty-docker/twenty/Dockerfile

@@ -49,6 +49,8 @@ RUN yarn workspaces focus --production twenty-emails twenty-shared twenty-sdk tw
 
 FROM common-deps AS twenty-front-build
 
+ARG REACT_APP_SERVER_BASE_URL
+
 COPY ./packages/twenty-front /app/packages/twenty-front
 COPY ./packages/twenty-front-component-renderer /app/packages/twenty-front-component-renderer
 COPY ./packages/twenty-ui /app/packages/twenty-ui
@@ -136,6 +138,9 @@ USER 1000
 
 FROM twenty-server AS twenty
 
+ARG REACT_APP_SERVER_BASE_URL
+ENV REACT_APP_SERVER_BASE_URL=$REACT_APP_SERVER_BASE_URL
+
 COPY --chown=1000 --from=twenty-front-build /app/packages/twenty-front/build /app/packages/twenty-server/dist/front
 
 LABEL org.opencontainers.image.description="Twenty image with backend and frontend."
@@ -227,6 +232,7 @@ RUN mkdir -p /data/postgres /data/redis /app/packages/twenty-server/.local-stora
  && chown -R postgres:postgres /data/postgres \
  && chown 1000:1000 /data/redis /app/packages/twenty-server/.local-storage
 
+ARG REACT_APP_SERVER_BASE_URL
 ARG APP_VERSION=0.0.0
 
 ENV S6_KEEP_ENV=1
@@ -235,6 +241,7 @@ ENV PG_DATABASE_URL=postgres://twenty:twenty@localhost:5432/default \
     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=2020 \

packages/twenty-docs/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ Dev mode is only available on Twenty instances running in development (`NODE_ENV
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="Dev mode terminal output" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="Dev mode terminal output" />
 </div>
 
 #### One-shot sync with `yarn twenty dev --once`
@@ -127,7 +127,13 @@ Click on **My twenty app** to open its **application registration**. A registrat
 Click **View installed app** to see the installed app. The **About** tab shows the current version and management options:
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Installed app" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Installed app — About tab" />
+</div>
+
+Switch to the **Content** tab to see everything your app provides — objects, fields, logic functions, and agents:
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="Installed app — Content tab" />
 </div>
 
 You are all set! Edit any file in `src/` and the changes will be picked up automatically.
@@ -213,31 +219,13 @@ The scaffolder already started a local Twenty server for you. To manage it later
 | `yarn twenty server start --port 3030` | Start on a custom port |
 | `yarn twenty server start --test` | Start a separate test instance on port 2021 |
 | `yarn twenty server stop` | Stop the server (preserves data) |
-| `yarn twenty server status` | Show server status, URL, version, and credentials |
+| `yarn twenty server status` | Show server status, URL, and credentials |
 | `yarn twenty server logs` | Stream server logs |
 | `yarn twenty server logs --lines 100` | Show the last 100 log lines |
 | `yarn twenty server reset` | Delete all data and start fresh |
-| `yarn twenty server upgrade` | Pull the latest `twenty-app-dev` image and recreate the container |
-| `yarn twenty server upgrade 2.2.0` | Upgrade to a specific version |
 
 Data is persisted across restarts in two Docker volumes (`twenty-app-dev-data` for PostgreSQL, `twenty-app-dev-storage` for files). Use `reset` to wipe everything and start fresh.
 
-### Upgrading the server image
-
-Use `yarn twenty server upgrade` to check for a newer `twenty-app-dev` Docker image and update the container. The command pulls the image, compares it against the one the container was created from, and only recreates the container if the image actually changed. Your data volumes are preserved — only the container is replaced.
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-If a newer image is available and the container was running, the upgrade command automatically starts a new container with the updated image. Run `yarn twenty server start` afterward to wait for it to become healthy. If the image hasn't changed, the container is left untouched.
-
-You can verify the running version with `yarn twenty server status`, which displays the `APP_VERSION` from the container.
-
 ### Running a test instance
 
 Pass `--test` to any `server` command to manage a second, fully isolated instance — useful for running integration tests or experimenting without touching your main dev data.
@@ -246,10 +234,9 @@ Pass `--test` to any `server` command to manage a second, fully isolated instanc
 |---------|-------------|
 | `yarn twenty server start --test` | Start the test instance (defaults to port 2021) |
 | `yarn twenty server stop --test` | Stop the test instance |
-| `yarn twenty server status --test` | Show test instance status, URL, version, and credentials |
+| `yarn twenty server status --test` | Show test instance status, URL, and credentials |
 | `yarn twenty server logs --test` | Stream test instance logs |
 | `yarn twenty server reset --test` | Wipe test data and start fresh |
-| `yarn twenty server upgrade --test` | Upgrade the test instance image |
 
 The test instance runs in its own Docker container (`twenty-app-dev-test`) with dedicated volumes (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) and config, so it can run in parallel with your main instance without conflicts. Combine `--test` with `--port` to override the default 2021.
 

packages/twenty-docs/developers/extend/apps/logic-functions.mdx

@@ -101,7 +101,6 @@ The `RoutePayload` type has the following structure:
   | `queryStringParameters` | `Record<string, string \| undefined>` | Query string parameters (multiple values joined with commas)  | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }`|
   | `pathParameters` | `Record<string, string \| undefined>` | Path parameters extracted from the route pattern | `/users/:id`, `/users/123` -> `{ id: '123' }` |
   | `body` | `object \| null` | Parsed request body (JSON) | `{ id: 1 }` -> `{ id: 1 }` |
-  | `rawBody` | `string \| undefined` | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. | |
   | `isBase64Encoded` | `boolean` | Whether the body is base64 encoded | |
   | `requestContext.http.method` | `string` | HTTP method (GET, POST, PUT, PATCH, DELETE) | |
   | `requestContext.http.path` | `string` | Raw request path | |

packages/twenty-docs/l/ar/developers/extend/apps/logic-functions.mdx

@@ -94,16 +94,15 @@ const handler = async (event: RoutePayload) => {
 
 يحتوي نوع `RoutePayload` على البنية التالية:
 
-  | الخاصية                      | النوع                                                   | الوصف                                                                                                                                                                                                 | مثال                                                                       |
-  | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | رؤوس HTTP (فقط تلك المدرجة في `forwardedRequestHeaders`)                                                                                                                                              | انظر القسم أدناه                                                           |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | معلمات سلسلة الاستعلام (تُضمّ القيم المتعددة باستخدام فواصل)                                                                                                                                          | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | معلمات المسار المستخرجة من نمط المسار                                                                                                                                                                 | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | جسم الطلب المُحلَّل (JSON)                                                                                                                                                                            | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | ما إذا كان جسم الطلب مُرمَّزًا بترميز base64                                                                                                                                                          |                                                                            |
-  | `requestContext.http.method` | `string`                                                | طريقة HTTP (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                            |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | المسار الخام للطلب                                                                                                                                                                                    |                                                                            |
+  | الخاصية                      | النوع                                                   | الوصف                                                        | مثال                                                                       |
+  | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | رؤوس HTTP (فقط تلك المدرجة في `forwardedRequestHeaders`)     | انظر القسم أدناه                                                           |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | معلمات سلسلة الاستعلام (تُضمّ القيم المتعددة باستخدام فواصل) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | معلمات المسار المستخرجة من نمط المسار                        | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | جسم الطلب المُحلَّل (JSON)                                   | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | ما إذا كان جسم الطلب مُرمَّزًا بترميز base64                 |                                                                            |
+  | `requestContext.http.method` | `string`                                                | طريقة HTTP (GET, POST, PUT, PATCH, DELETE)                   |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | المسار الخام للطلب                                           |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/ar/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ description: تعرّف على خطط تسعير Twenty وكيفية التبد
 * دعم قياسي
 
 <Note>
-Premium features (SSO, row-level permissions and AI usage data) are not included in the Pro plan.
+الميزات المتميزة (SSO وأذونات على مستوى الصف) غير مشمولة في خطة Pro.
 </Note>
 
 ### المؤسسة (سحابي)
@@ -27,7 +27,7 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 للفرق الأكبر ذات الاحتياجات المتقدّمة:
 
 * كل ما في Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **ميزات متميزة**: تكامل SSO وأذونات على مستوى الصف
 * دعم متميز
 
 ## خطط الاستضافة الذاتية
@@ -45,7 +45,7 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 للفرق التي تحتاج إلى ميزات متميزة أثناء الاستضافة الذاتية:
 
 * جميع ميزات Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **ميزات متميزة**: تكامل SSO وأذونات على مستوى الصف
 * دعم فريق Twenty
 * لا يُشترط نشر الشيفرة المخصّصة كمفتوح المصدر قبل التوزيع
 
@@ -55,7 +55,6 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 
 * **تكامل SSO**: تسجيل دخول أحادي مع موفّر الهوية لديك
 * **أذونات على مستوى الصف**: تحكّم دقيق في الوصول على مستوى السجل
-* **AI usage data**: Track AI consumption across the workspace
 
 ## التبديل بين الخطط
 
@@ -78,15 +77,3 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 ### التبديل إلى الفوترة الشهرية
 
 تواصل مع الدعم للعودة إلى الفوترة الشهرية.
-
-## Obtain an Enterprise Key for Organization (Self-Hosted)
-
-To use the Organization (Self-Hosted) plan, you need to obtain an Enterprise key:
-
-1. Go to **Settings → Admin Panel → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Enterprise key" />
-
-2. Click **Get Enterprise Key**
-3. When you are redirected to Stripe, enter your payment details and confirm
-4. When your Enterprise key is displayed, paste it into the Enterprise settings page and activate the Organization license

packages/twenty-docs/l/ar/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ description: الأسئلة الشائعة حول تسعير Twenty والفوت
 لا تتوفر الميزات المتميزة إلا في خطط Organization (السحابة أو الاستضافة الذاتية):
 * **تكامل SSO**: تسجيل الدخول الأحادي مع موفر الهوية لديك
 * **أذونات على مستوى السجل**: تحكم دقيق في الوصول على مستوى السجل
-* **بيانات استخدام الذكاء الاصطناعي**: تتبع استهلاك الذكاء الاصطناعي عبر مساحة العمل
-</Accordion>
-
-<Accordion title="هل خطة Organization على السحابة وخطة Organization ذاتية الاستضافة متماثلتان؟">
-كلتاهما تقدمان الميزات المتميزة نفسها. ومع ذلك، لا يمكن استخدام اشتراك السحابة لعمليات النشر ذاتية الاستضافة. يتطلب النشر ذاتي الاستضافة مفتاح Enterprise.
 </Accordion>
 
 <Accordion title="هل تقدمون مقاعد مجانية للمستخدمين العارضين فقط؟">

packages/twenty-docs/l/ar/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ People ←→ Project Assignments ←→ Projects
 1. اذهب إلى **الإعدادات → نموذج البيانات**
 2. انقر **+ كائن جديد**
 3. سمِّه تسمية وصفية (مثلًا: "تعيين مشروع"، "عضو فريق"، "طلب منتج")
-4. فعِّل خيار "تخطي إنشاء حقل الاسم"
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="كائن ربط جديد" />
-
-5. انقر على **حفظ**
+4. انقر على **حفظ**
 
 <Tip>
 **اتفاقية التسمية**: استخدم اسمًا يصف العلاقة، مثل "تعيين مشروع" أو "عضوية الفريق". هذا يجعل نموذج البيانات أسهل في الفهم.
 </Tip>
 
-## الخطوة 2: إنشاء علاقات بين الكائنات وكائن الربط
+## الخطوة 2: إنشاء علاقات من كائن الربط
 
-أضف حقول العلاقة من كلٍ من الكائنين لديك إلى كائن الربط.
+أضِف حقول علاقة من كائن الربط إلى كلا الكائنين اللذين تريد ربطهما.
 
-### العلاقة الأولى (الكائن A → كائن الربط)
-
-1. حدِّد الكائن الأول لديك في **الإعدادات → نموذج البيانات**
-2. انقر **+ إضافة علاقة**
-3. اختر كائن الربط (مثلًا، "تعيينات المشروع")
-4. عيِّن نوع العلاقة إلى **واحد-إلى-متعدد** (يمكن لشخص واحد الارتباط بالعديد من التعيينات)
-5. قم بتسمية الحقول:
-   * الحقل على الأشخاص: مثلًا، "تعيينات المشروع"
-   * الحقل على كائن الربط: مثلًا، "شخص"
-6. انقر على **حفظ**
-
-### العلاقة الثانية (الكائن B → كائن الربط)
-
-1. حدِّد الكائن الثاني لديك في **الإعدادات → نموذج البيانات**
-2. انقر **+ إضافة علاقة**
-3. اختر كائن الربط (مثلًا، "تعيينات المشروع")
-4. عيِّن نوع العلاقة إلى **واحد-إلى-متعدد** (يمكن لمشروع واحد الارتباط بالعديد من التعيينات)
-5. فعّل **"هذه علاقة بكائن ربط"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### العلاقة الأولى (كائن الربط → الكائن A)
 
+1. حدِّد كائن الربط في **الإعدادات → نموذج البيانات**
+2. انقر **+ إضافة حقل**
+3. اختر **العلاقة** كنوع الحقل
+4. اختر الكائن الأول (مثلًا، "الأشخاص")
+5. عيِّن نوع العلاقة إلى **متعدد-إلى-واحد** (يمكن لعديد من التعيينات الارتباط بشخص واحد)
 6. قم بتسمية الحقول:
+   * الحقل على كائن الربط: مثلًا، "شخص"
+   * الحقل على الأشخاص: مثلًا، "تعيينات المشروع"
+7. انقر على **حفظ**
+
+### العلاقة الثانية (كائن الربط → الكائن B)
+
+1. وأنت ما زلت في كائن الربط، انقر **+ إضافة حقل**
+2. اختر **العلاقة** كنوع الحقل
+3. اختر الكائن الثاني (مثلًا، "المشاريع")
+4. عيِّن نوع العلاقة إلى **متعدد-إلى-واحد**
+5. قم بتسمية الحقول:
    * الحقل على كائن الربط: مثلًا، "مشروع"
    * الحقل على المشاريع: مثلًا، "أعضاء الفريق"
-7. انقر على **حفظ**
+6. انقر على **حفظ**
 
 ## الخطوة 3: ضبط عرض علاقة الربط
 
@@ -105,6 +98,18 @@ People ←→ Project Assignments ←→ Projects
 6. حدِّد **العلاقة الهدف** (مثلًا، "مشروع" — الحقل على كائن الربط الذي يشير إلى الجانب الآخر)
 7. انقر على **حفظ**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+كرِّر على الكائن الآخر:
+
+1. اختر "المشاريع" في نموذج البيانات
+2. حرِّر حقل العلاقة "أعضاء الفريق"
+3. فعّل مفتاح الربط
+4. حدِّد "شخص" كالعلاقة الهدف
+5. حفظ
+
 ## النتيجة
 
 بعد التكوين:
@@ -125,15 +130,15 @@ People ←→ Project Assignments ←→ Projects
 
 ### إضافة علاقات
 
-1. **الأشخاص → تعيين مشروع**
-   * النوع: واحد-إلى-متعدد
-   * الحقل على الأشخاص: "تعيينات المشروع"
+1. **تعيين مشروع → الأشخاص**
+   * النوع: متعدد-إلى-واحد
    * الحقل على التعيين: "شخص"
+   * الحقل على الأشخاص: "تعيينات المشروع"
 
-2. **المشاريع → تعيين مشروع**
-   * النوع: واحد-إلى-متعدد
-   * الحقل على المشاريع: "أعضاء الفريق"
+2. **تعيين مشروع → المشاريع**
+   * النوع: متعدد-إلى-واحد
    * الحقل على التعيين: "مشروع"
+   * الحقل على المشاريع: "أعضاء الفريق"
 
 ### ضبط عرض علاقة الربط
 

packages/twenty-docs/l/ar/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ description: خصص الشريط الجانبي الأيسر ليتوافق مع
 ## قائمة الأوامر
 
 اضغط `Cmd+K` (أو `Ctrl+K`) لفتح قائمة الأوامر — شريط بحث للوصول السريع يتيح لك الانتقال إلى أي سجل أو طريقة عرض أو إجراء دون التنقل عبر الشريط الجانبي.
-
-## تخصيص الشريط الجانبي
-
-لتخصيص الشريط الجانبي، مرّر المؤشر فوق قسم "مساحة العمل" في الشريط الجانبي وانقر على أيقونة مفتاح الربط.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="أيقونة تحرير التنقّل" />

packages/twenty-docs/l/ar/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: صفحات السجل
 description: خصص تخطيط صفحات تفاصيل السجلات باستخدام علامات تبويب وأدوات.
 ---
 
-## نظرة عامة
-
 عند فتح سجل في Twenty، تتكون صفحة التفاصيل من **علامات تبويب** و**أدوات**. كلاهما قابل للتخصيص بالكامل حسب نوع الكائن.
 
 ## علامات التبويب
@@ -40,20 +38,12 @@ description: خصص تخطيط صفحات تفاصيل السجلات باستخ
 
 1. افتح أي سجل
 2. اضغط على `Cmd+K` وابحث عن "تحرير تخطيط صفحة السجل"
-
-أو
-
-1. انتقل إلى الإعدادات > نموذج البيانات > الكائن الذي تختاره > التخطيط
-
-2. انقر على الزر "تخصيص صفحة السجل" لذلك الكائن
-
 3. أنت الآن في وضع التخصيص:
    * **أضف أدوات** من منتقي الأدوات
    * **اسحب الأدوات** لإعادة وضعها على الشبكة
    * **غيّر حجم الأدوات** بسحب حوافها
    * **اضبط الحقول** المعروضة داخل كل أداة
    * **أدِر علامات التبويب** — أضف، أزل، أعد التسمية، وأعد الترتيب
-
 4. احفظ تغييراتك — سيتم تطبيقها على جميع السجلات لذلك النوع من الكائنات
 
 ## ظهور الحقول

packages/twenty-docs/l/cs/developers/extend/apps/logic-functions.mdx

@@ -95,16 +95,15 @@ const handler = async (event: RoutePayload) => {
 
 Typ `RoutePayload` má následující strukturu:
 
-  | Vlastnost                    | Typ                                                     | Popis                                                                                                                                                                                                 | Příklad                                                                    |
-  | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | Záhlaví HTTP (pouze ta uvedená v `forwardedRequestHeaders`)                                                                                                                                           | viz sekci níže                                                             |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parametry query stringu (více hodnot spojených čárkami)                                                                                                                                               | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Parametry cesty extrahované ze vzoru trasy                                                                                                                                                            | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Parsované tělo požadavku (JSON)                                                                                                                                                                       | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Zda je tělo kódováno base64                                                                                                                                                                           |                                                                            |
-  | `requestContext.http.method` | `string`                                                | Metoda HTTP (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                           |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | Nezpracovaná cesta požadavku                                                                                                                                                                          |                                                                            |
+  | Vlastnost                    | Typ                                                     | Popis                                                       | Příklad                                                                    |
+  | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | Záhlaví HTTP (pouze ta uvedená v `forwardedRequestHeaders`) | viz sekci níže                                                             |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parametry query stringu (více hodnot spojených čárkami)     | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Parametry cesty extrahované ze vzoru trasy                  | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Parsované tělo požadavku (JSON)                             | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Zda je tělo kódováno base64                                 |                                                                            |
+  | `requestContext.http.method` | `string`                                                | Metoda HTTP (GET, POST, PUT, PATCH, DELETE)                 |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | Nezpracovaná cesta požadavku                                |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/cs/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Pro týmy připravené škálovat:
 * Standardní podpora
 
 <Note>
-Premium features (SSO, row-level permissions and AI usage data) are not included in the Pro plan.
+Prémiové funkce (SSO a oprávnění na úrovni řádků) nejsou součástí plánu Pro.
 </Note>
 
 ### Organizace (Cloud)
@@ -27,7 +27,7 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 Pro větší týmy s pokročilými potřebami:
 
 * Vše z plánu Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **Prémiové funkce**: integrace SSO a oprávnění na úrovni řádků
 * Prioritní podpora
 
 ## Plány pro self‑hosting
@@ -45,7 +45,7 @@ Hostujte Twenty na vlastní infrastruktuře bez poplatků:
 Pro týmy, které při self‑hostingu potřebují prémiové funkce:
 
 * Všechny funkce plánu Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **Prémiové funkce**: integrace SSO a oprávnění na úrovni řádků
 * Podpora týmu Twenty
 * Není vyžadováno zveřejnit vlastní kód jako open‑source před distribucí
 
@@ -55,7 +55,6 @@ Prémiové funkce jsou dostupné pouze v plánech Organizace (Cloud nebo self‑
 
 * **Integrace SSO**: jednotné přihlášení s vaším poskytovatelem identity
 * **Oprávnění na úrovni řádků**: jemně odstupňované řízení přístupu na úrovni záznamu
-* **AI usage data**: Track AI consumption across the workspace
 
 ## Přepínání plánů
 
@@ -78,15 +77,3 @@ Chcete-li přejít na nižší plán, kontaktujte podporu.
 ### Přepnout na měsíční fakturaci
 
 Chcete-li přepnout zpět na měsíční fakturaci, kontaktujte podporu.
-
-## Obtain an Enterprise Key for Organization (Self-Hosted)
-
-To use the Organization (Self-Hosted) plan, you need to obtain an Enterprise key:
-
-1. Go to **Settings → Admin Panel → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Enterprise key" />
-
-2. Click **Get Enterprise Key**
-3. When you are redirected to Stripe, enter your payment details and confirm
-4. When your Enterprise key is displayed, paste it into the Enterprise settings page and activate the Organization license

packages/twenty-docs/l/cs/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ Pokud chcete hostovat sami a potřebujete prémiové funkce (SSO a oprávnění
 Prémiové funkce jsou dostupné pouze v plánech Organization (Cloud nebo Self-Hosted):
 * **Integrace SSO**: Jednotné přihlášení s vaším poskytovatelem identity
 * **Oprávnění na úrovni řádků**: Jemně granulované řízení přístupu na úrovni záznamu
-* **AI usage data**: Track AI consumption across the workspace
-</Accordion>
-
-<Accordion title="Is Organization plan on cloud and Organization plan on self-hosted the same?">
-They offer the same premium features. However, a cloud subscription cannot be used for self-hosted deployments. Self-hosted requires an Enterprise key.
 </Accordion>
 
 <Accordion title="Nabízíte volná místa pro uživatele pouze s přístupem ke čtení?">

packages/twenty-docs/l/cs/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ Nejprve vytvořte mezilehlý objekt, který bude uchovávat propojení.
 1. Přejděte do **Nastavení → Datový model**
 2. Klikněte na **+ New object**
 3. Pojmenujte jej výstižně (např. "Project Assignment", "Team Member", "Product Order")
-4. Přepněte "Přeskočit vytvoření pole Název" na zapnuto
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Nový spojovací objekt" />
-
-5. Klikněte na **Uložit**
+4. Klikněte na **Uložit**
 
 <Tip>
 **Konvence pojmenování**: Použijte název, který popisuje vztah, například "Project Assignment" nebo "Team Membership". Tím bude datový model srozumitelnější.
 </Tip>
 
-## Krok 2: Vytvořte vztahy mezi objekty a spojovacím objektem
+## Krok 2: Vytvořte vztahy ze spojovacího objektu
 
-Přidejte vztahová pole z obou objektů do spojovacího objektu.
+Přidejte relační pole ze spojovacího objektu do obou objektů, které chcete propojit.
 
-### První vztah (Objekt A → Junction)
-
-1. Vyberte svůj první objekt v **Settings → Data Model**
-2. Klikněte na **+ Přidat vztah**
-3. Vyberte spojovací objekt (např. "Project Assignments")
-4. Nastavte typ vztahu na **One-To-Many** (jedna osoba může být propojena s mnoha přiřazeními)
-5. Pojmenujte pole:
-   * Pole na People: např. "Project Assignments"
-   * Pole na spojovacím objektu: např. "Person"
-6. Klikněte na **Uložit**
-
-### Druhý vztah (Objekt B → Junction)
-
-1. Vyberte svůj druhý objekt v **Settings → Data Model**
-2. Klikněte na **+ Přidat vztah**
-3. Vyberte spojovací objekt (např. "Project Assignments")
-4. Nastavte typ vztahu na **One-To-Many** (jeden projekt může být propojen s mnoha přiřazeními)
-5. Povolte **"This is a relation to a Junction Object"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### První vztah (Junction → Objekt A)
 
+1. Vyberte svůj spojovací objekt v **Settings → Data Model**
+2. Klikněte na **+ Add Field**
+3. Zvolte **Relation** jako typ pole
+4. Vyberte první objekt (např. "People")
+5. Nastavte typ vztahu na **Many-to-One** (mnoho přiřazení může odkazovat na jednu osobu)
 6. Pojmenujte pole:
+   * Pole na spojovacím objektu: např. "Person"
+   * Pole na People: např. "Project Assignments"
+7. Klikněte na **Uložit**
+
+### Druhý vztah (Junction → Objekt B)
+
+1. Stále na spojovacím objektu klikněte na **+ Add Field**
+2. Zvolte **Relation** jako typ pole
+3. Vyberte druhý objekt (např. "Projects")
+4. Nastavte typ vztahu na **Many-to-One**
+5. Pojmenujte pole:
    * Pole na spojovacím objektu: např. "Project"
    * Pole na Projects: např. "Team Members"
-7. Klikněte na **Uložit**
+6. Klikněte na **Uložit**
 
 ## Krok 3: Nakonfigurujte zobrazení vztahu přes spojovací objekt
 
@@ -105,6 +98,18 @@ Nyní nakonfigurujte zdrojové objekty tak, aby zobrazovaly propojené záznamy
 6. Vyberte **Target relation** (např. "Project" — pole na spojovacím objektu, které ukazuje na druhou stranu)
 7. Klikněte na **Uložit**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Opakujte pro druhý objekt:
+
+1. Vyberte "Projects" v Data Model
+2. Upravte relační pole "Team Members"
+3. Povolte přepínač pro vztah přes spojovací objekt
+4. Vyberte "Person" jako cílový vztah
+5. Uložit
+
 ## Výsledek
 
 Po konfiguraci:
@@ -125,15 +130,15 @@ Zde je kompletní postup:
 
 ### Přidejte vztahy
 
-1. **People → Project Assignment**
-   * Typ: One-to-Many
-   * Pole na People: "Project Assignments"
+1. **Project Assignment → People**
+   * Typ: Many-to-One
    * Pole na Assignment: "Person"
+   * Pole na People: "Project Assignments"
 
-2. **Projects → Project Assignment**
-   * Typ: One-to-Many
-   * Pole na Projects: "Team Members"
+2. **Project Assignment → Projects**
+   * Typ: Many-to-One
    * Pole na Assignment: "Project"
+   * Pole na Projects: "Team Members"
 
 ### Nakonfigurujte zobrazení spojovacího objektu
 

packages/twenty-docs/l/cs/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ Přidejte odkazy na externí nástroje přímo do postranního panelu. Užitečn
 ## Nabídka příkazů
 
 Stiskněte `Cmd+K` (nebo `Ctrl+K`) pro otevření nabídky příkazů — rychlá vyhledávací lišta pro přechod na libovolný záznam, zobrazení nebo akci bez procházení postranního panelu.
-
-## Přizpůsobení postranního panelu
-
-Chcete-li přizpůsobit postranní panel, najeďte myší na sekci "Pracovní prostor" v postranním panelu a klikněte na ikonu klíče.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Ikona pro úpravu navigace" />

packages/twenty-docs/l/cs/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Stránky záznamů
 description: Přizpůsobte rozvržení jednotlivých stránek detailu záznamu pomocí karet a widgetů.
 ---
 
-## Přehled
-
 Když v Twenty otevřete záznam, stránka detailu se skládá z **karet** a **widgetů**. Obojí lze pro každý typ objektu plně přizpůsobit.
 
 ## Karty
@@ -40,20 +38,12 @@ Widgety jsou stavební prvky uvnitř každé karty. Mezi dostupné typy widgetů
 
 1. Otevřete libovolný záznam
 2. Stiskněte `Cmd+K` a vyhledejte "Upravit rozložení stránky záznamu"
-
-nebo
-
-1. Přejděte do Nastavení > Datový model > objekt dle vašeho výběru > Rozložení
-
-2. Klikněte na tlačítko "Přizpůsobit stránku záznamu" pro daný objekt
-
 3. Nyní jste v režimu přizpůsobení:
    * **Přidávejte widgety** z výběru widgetů
    * **Přetahujte widgety** pro jejich přemístění v mřížce
    * **Změňte velikost widgetů** tažením jejich okrajů
    * **Nakonfigurujte pole** zobrazovaná v jednotlivých widgetech
    * **Spravujte karty** — přidávejte, odebírejte, přejmenovávejte, měňte pořadí
-
 4. Uložte změny — budou platit pro všechny záznamy daného typu objektu
 
 ## Viditelnost polí

packages/twenty-docs/l/de/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ Der Dev-Modus ist nur auf Twenty-Instanzen verfügbar, die im Entwicklungsmodus
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="Terminalausgabe im Dev-Modus" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="Terminalausgabe im Dev-Modus" />
 </div>
 
 #### Einmalige Synchronisierung mit `yarn twenty dev --once`
@@ -127,7 +127,13 @@ Klicken Sie auf **My twenty app**, um die **Anwendungsregistrierung** zu öffnen
 Klicken Sie auf **View installed app**, um die installierte App anzuzeigen. Die Registerkarte **About** zeigt die aktuelle Version und Verwaltungsoptionen:
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Installierte App" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Installierte App — Registerkarte About" />
+</div>
+
+Wechseln Sie zur Registerkarte **Content**, um alles zu sehen, was Ihre App bereitstellt — Objekte, Felder, Logikfunktionen und Agenten:
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="Installierte App — Registerkarte Content" />
 </div>
 
 Alles erledigt! Bearbeiten Sie eine beliebige Datei in `src/`, und die Änderungen werden automatisch übernommen.
@@ -207,49 +213,30 @@ Die Beispiele stammen aus dem Verzeichnis [twenty-apps/examples](https://github.
 
 Der Scaffolder hat bereits einen lokalen Twenty-Server für Sie gestartet. Um ihn später zu verwalten, verwenden Sie `yarn twenty server`:
 
-| Befehl                                 | Beschreibung                                                                     |
-| -------------------------------------- | -------------------------------------------------------------------------------- |
-| `yarn twenty server start`             | Lokalen Server starten (lädt das Image bei Bedarf herunter)                      |
-| `yarn twenty server start --port 3030` | Auf einem benutzerdefinierten Port starten                                       |
-| `yarn twenty server start --test`      | Starten Sie eine separate Testinstanz auf Port 2021                              |
-| `yarn twenty server stop`              | Server stoppen (Daten bleiben erhalten)                                          |
-| `yarn twenty server status`            | Serverstatus, URL, Version und Anmeldedaten anzeigen                             |
-| `yarn twenty server logs`              | Serverprotokolle streamen                                                        |
-| `yarn twenty server logs --lines 100`  | Die letzten 100 Protokollzeilen anzeigen                                         |
-| `yarn twenty server reset`             | Alle Daten löschen und neu starten                                               |
-| `yarn twenty server upgrade`           | Das neueste `twenty-app-dev`-Image herunterladen und den Container neu erstellen |
-| `yarn twenty server upgrade 2.2.0`     | Auf eine bestimmte Version aktualisieren                                         |
+| Befehl                                 | Beschreibung                                                |
+| -------------------------------------- | ----------------------------------------------------------- |
+| `yarn twenty server start`             | Lokalen Server starten (lädt das Image bei Bedarf herunter) |
+| `yarn twenty server start --port 3030` | Auf einem benutzerdefinierten Port starten                  |
+| `yarn twenty server start --test`      | Starten Sie eine separate Testinstanz auf Port 2021         |
+| `yarn twenty server stop`              | Server stoppen (Daten bleiben erhalten)                     |
+| `yarn twenty server status`            | Serverstatus, URL und Anmeldedaten anzeigen                 |
+| `yarn twenty server logs`              | Serverprotokolle streamen                                   |
+| `yarn twenty server logs --lines 100`  | Die letzten 100 Protokollzeilen anzeigen                    |
+| `yarn twenty server reset`             | Alle Daten löschen und neu starten                          |
 
 Daten bleiben über Neustarts hinweg in zwei Docker-Volumes bestehen (`twenty-app-dev-data` für PostgreSQL, `twenty-app-dev-storage` für Dateien). Verwenden Sie `reset`, um alles zu löschen und neu zu beginnen.
 
-### Aktualisieren des Server-Images
-
-Verwenden Sie `yarn twenty server upgrade`, um nach einem neueren `twenty-app-dev`-Docker-Image zu suchen und den Container zu aktualisieren. Der Befehl lädt das Image herunter, vergleicht es mit dem, aus dem der Container erstellt wurde, und erstellt den Container nur neu, wenn sich das Image tatsächlich geändert hat. Ihre Daten-Volumes bleiben erhalten — nur der Container wird ersetzt.
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-Wenn ein neueres Image verfügbar ist und der Container lief, startet der Upgrade-Befehl automatisch einen neuen Container mit dem aktualisierten Image. Führen Sie anschließend `yarn twenty server start` aus, um zu warten, bis er betriebsbereit ist. Wenn sich das Image nicht geändert hat, bleibt der Container unverändert.
-
-Sie können die laufende Version mit `yarn twenty server status` überprüfen; dieser Befehl zeigt die `APP_VERSION` des Containers an.
-
 ### Eine Testinstanz ausführen
 
 Übergeben Sie `--test` an jeden `server`-Befehl, um eine zweite, vollständig isolierte Instanz zu verwalten — nützlich, um Integrationstests auszuführen oder zu experimentieren, ohne Ihre Hauptentwicklungsdaten anzutasten.
 
-| Befehl                              | Beschreibung                                                   |
-| ----------------------------------- | -------------------------------------------------------------- |
-| `yarn twenty server start --test`   | Die Testinstanz starten (standardmäßig Port 2021)              |
-| `yarn twenty server stop --test`    | Die Testinstanz stoppen                                        |
-| `yarn twenty server status --test`  | Status, URL, Version und Anmeldedaten der Testinstanz anzeigen |
-| `yarn twenty server logs --test`    | Protokolle der Testinstanz streamen                            |
-| `yarn twenty server reset --test`   | Alle Testdaten löschen und neu starten                         |
-| `yarn twenty server upgrade --test` | Das Image der Testinstanz aktualisieren                        |
+| Befehl                             | Beschreibung                                          |
+| ---------------------------------- | ----------------------------------------------------- |
+| `yarn twenty server start --test`  | Die Testinstanz starten (standardmäßig Port 2021)     |
+| `yarn twenty server stop --test`   | Die Testinstanz stoppen                               |
+| `yarn twenty server status --test` | Status, URL und Anmeldedaten der Testinstanz anzeigen |
+| `yarn twenty server logs --test`   | Protokolle der Testinstanz streamen                   |
+| `yarn twenty server reset --test`  | Alle Testdaten löschen und neu starten                |
 
 Die Testinstanz läuft in einem eigenen Docker-Container (`twenty-app-dev-test`) mit dedizierten Volumes (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) und eigener Konfiguration, sodass sie parallel zu Ihrer Hauptinstanz ohne Konflikte ausgeführt werden kann. Kombinieren Sie `--test` mit `--port`, um den Standardport 2021 zu überschreiben.
 

packages/twenty-docs/l/de/developers/extend/apps/logic-functions.mdx

@@ -94,16 +94,15 @@ const handler = async (event: RoutePayload) => {
 
 Der Typ `RoutePayload` hat die folgende Struktur:
 
-  | Eigenschaft                  | Typ                                                     | Beschreibung                                                                                                                                                                                                                           | Beispiel                                                                   |
-  | ---------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | HTTP-Header (nur die in `forwardedRequestHeaders` aufgelisteten)                                                                                                                                                                       | siehe Abschnitt unten                                                      |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Query-String-Parameter (mehrere Werte mit Kommas verbunden)                                                                                                                                                                            | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Aus dem Routenmuster extrahierte Pfadparameter                                                                                                                                                                                         | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Geparster Request-Body (JSON)                                                                                                                                                                                                          | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Ursprünglicher UTF-8-Request-Body vor dem JSON-Parsing. Nützlich zur Verifizierung von Webhook-Signaturen im HMAC-Stil (z. B. GitHubs `X-Hub-Signature-256`, Stripe). `undefined`, wenn die Laufzeitumgebung es nicht beibehalten hat. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Gibt an, ob der Body Base64-codiert ist                                                                                                                                                                                                |                                                                            |
-  | `requestContext.http.method` | `Zeichenkette`                                          | HTTP-Methode (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                                                           |                                                                            |
-  | `requestContext.http.path`   | `Zeichenkette`                                          | Rohpfad der Anfrage                                                                                                                                                                                                                    |                                                                            |
+  | Eigenschaft                  | Typ                                                     | Beschreibung                                                     | Beispiel                                                                   |
+  | ---------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | HTTP-Header (nur die in `forwardedRequestHeaders` aufgelisteten) | siehe Abschnitt unten                                                      |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Query-String-Parameter (mehrere Werte mit Kommas verbunden)      | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Aus dem Routenmuster extrahierte Pfadparameter                   | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Geparster Request-Body (JSON)                                    | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Gibt an, ob der Body Base64-codiert ist                          |                                                                            |
+  | `requestContext.http.method` | `Zeichenkette`                                          | HTTP-Methode (GET, POST, PUT, PATCH, DELETE)                     |                                                                            |
+  | `requestContext.http.path`   | `Zeichenkette`                                          | Rohpfad der Anfrage                                              |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/de/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Für Teams, die bereit sind zu skalieren:
 * Standard-Support
 
 <Note>
-Premiumfunktionen (SSO, Berechtigungen auf Zeilenebene und KI-Nutzungsdaten) sind im Pro-Tarif nicht enthalten.
+Premiumfunktionen (SSO und Berechtigungen auf Zeilenebene) sind im Pro-Plan nicht enthalten.
 </Note>
 
 ### Organisation (Cloud)
@@ -27,7 +27,7 @@ Premiumfunktionen (SSO, Berechtigungen auf Zeilenebene und KI-Nutzungsdaten) sin
 Für größere Teams mit erweiterten Anforderungen:
 
 * Alles aus Pro
-* **Premiumfunktionen**: SSO-Integration, Berechtigungen auf Zeilenebene und KI-Nutzungsdaten
+* **Premiumfunktionen**: SSO-Integration und Berechtigungen auf Zeilenebene
 * Vorrangiger Support
 
 ## Selbstgehostete Pläne
@@ -45,7 +45,7 @@ Hosten Sie Twenty auf Ihrer eigenen Infrastruktur kostenlos:
 Für Teams, die beim Selbsthosting Premiumfunktionen benötigen:
 
 * Alle Pro-Funktionen
-* **Premiumfunktionen**: SSO-Integration, Berechtigungen auf Zeilenebene und KI-Nutzungsdaten
+* **Premiumfunktionen**: SSO-Integration und Berechtigungen auf Zeilenebene
 * Support durch das Twenty-Team
 * Keine Verpflichtung, benutzerdefinierten Code vor der Weitergabe als Open Source zu veröffentlichen
 
@@ -55,7 +55,6 @@ Premiumfunktionen sind nur in den Organisation-Plänen (Cloud oder Selbstgehoste
 
 * **SSO-Integration**: Single Sign-On mit Ihrem Identitätsanbieter
 * **Berechtigungen auf Zeilenebene**: Feingranulare Zugriffskontrolle auf Datensatzebene
-* **KI-Nutzungsdaten**: Verfolgen Sie den KI-Verbrauch in Ihrem Arbeitsbereich
 
 ## Pläne wechseln
 
@@ -78,15 +77,3 @@ Wenden Sie sich an den Support, um Ihren Plan herabzustufen.
 ### Zur monatlichen Abrechnung wechseln
 
 Wenden Sie sich an den Support, um wieder zur monatlichen Abrechnung zu wechseln.
-
-## Enterprise-Schlüssel für Organization (Self-Hosted) abrufen
-
-Um den Tarif Organization (Self-Hosted) zu verwenden, müssen Sie einen Enterprise-Schlüssel abrufen:
-
-1. Gehen Sie zu **Einstellungen → Admin-Panel → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Enterprise-Schlüssel" />
-
-2. Klicken Sie auf **Enterprise-Schlüssel abrufen**
-3. Wenn Sie zu Stripe weitergeleitet werden, geben Sie Ihre Zahlungsdaten ein und bestätigen Sie
-4. Wenn Ihr Enterprise-Schlüssel angezeigt wird, fügen Sie ihn auf der Seite Enterprise-Einstellungen ein und aktivieren Sie die Organization-Lizenz

packages/twenty-docs/l/de/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ Wenn Sie selbst hosten möchten und die Premium-Funktionen (SSO und Berechtigung
 Premium-Funktionen sind nur in den Organization-Tarifen (Cloud oder Self-Hosted) verfügbar:
 * **SSO-Integration**: Single Sign-On mit Ihrem Identitätsanbieter
 * **Berechtigungen auf Zeilenebene**: feingranulare Zugriffskontrolle auf Datensatzebene
-* **KI-Nutzungsdaten**: Verfolgen Sie den KI-Verbrauch in Ihrem Arbeitsbereich
-</Accordion>
-
-<Accordion title="Sind der Organisationsplan in der Cloud und der Organisationsplan bei selbst gehosteter Bereitstellung gleich?">
-Sie bieten dieselben Premium-Funktionen. Ein Cloud-Abonnement kann jedoch nicht für selbst gehostete Bereitstellungen verwendet werden. Für selbst gehostete Bereitstellungen ist ein Enterprise-Schlüssel erforderlich.
 </Accordion>
 
 <Accordion title="Bieten Sie kostenlose Plätze für Nur-Ansicht-Benutzer an?">

packages/twenty-docs/l/de/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ Erstellen Sie zunächst das Zwischenobjekt, das die Verknüpfungen speichert.
 1. Gehen Sie zu **Einstellungen → Datenmodell**
 2. Klicken Sie auf **+ Neues Objekt**
 3. Benennen Sie es aussagekräftig (z. B. "Projektzuweisung", "Teammitglied", "Produktbestellung")
-4. Schalten Sie "Erstellen eines Namensfelds überspringen" ein
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Neues Verknüpfungsobjekt" />
-
-5. Klicken Sie auf **Speichern**
+4. Klicken Sie auf **Speichern**
 
 <Tip>
 **Namenskonvention**: Verwenden Sie einen Namen, der die Beziehung beschreibt, z. B. "Projektzuweisung" oder "Teammitgliedschaft". Das macht das Datenmodell leichter verständlich.
 </Tip>
 
-## Schritt 2: Beziehungen zwischen Objekten und dem Verknüpfungsobjekt erstellen
+## Schritt 2: Beziehungen vom Verknüpfungsobjekt erstellen
 
-Fügen Sie für jedes Ihrer beiden Objekte Beziehungsfelder zum Verknüpfungsobjekt hinzu.
+Fügen Sie vom Verknüpfungsobjekt aus Beziehungsfelder zu beiden Objekten hinzu, die Sie verbinden möchten.
 
-### Erste Beziehung (Objekt A → Verknüpfung)
-
-1. Wählen Sie Ihr erstes Objekt unter **Einstellungen → Datenmodell** aus
-2. Klicken Sie auf **+ Beziehung hinzufügen**
-3. Wählen Sie das Verknüpfungsobjekt aus (z. B. "Projektzuweisungen")
-4. Legen Sie den Beziehungstyp auf **Eins-zu-Viele** fest (eine Person kann mit vielen Zuweisungen verknüpft werden)
-5. Benennen Sie die Felder:
-   * Feld bei Personen: z. B. "Projektzuweisungen"
-   * Feld auf der Verknüpfung: z. B. "Person"
-6. Klicken Sie auf **Speichern**
-
-### Zweite Beziehung (Objekt B → Verknüpfung)
-
-1. Wählen Sie Ihr zweites Objekt unter **Einstellungen → Datenmodell** aus
-2. Klicken Sie auf **+ Beziehung hinzufügen**
-3. Wählen Sie das Verknüpfungsobjekt aus (z. B. "Projektzuweisungen")
-4. Legen Sie den Beziehungstyp auf **Eins-zu-Viele** fest (ein Projekt kann mit vielen Zuweisungen verknüpft werden)
-5. Aktivieren Sie **"Dies ist eine Beziehung zu einem Verknüpfungsobjekt"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### Erste Beziehung (Verknüpfung → Objekt A)
 
+1. Wählen Sie Ihr Verknüpfungsobjekt unter **Einstellungen → Datenmodell** aus
+2. Klicken Sie auf **+ Feld hinzufügen**
+3. Wählen Sie **Relation** als Feldtyp
+4. Wählen Sie das erste Objekt aus (z. B. "Personen")
+5. Legen Sie den Beziehungstyp auf **Viele-zu-Eins** fest (viele Zuweisungen können mit einer Person verknüpft werden)
 6. Benennen Sie die Felder:
+   * Feld auf der Verknüpfung: z. B. "Person"
+   * Feld bei Personen: z. B. "Projektzuweisungen"
+7. Klicken Sie auf **Speichern**
+
+### Zweite Beziehung (Verknüpfung → Objekt B)
+
+1. Bleiben Sie im Verknüpfungsobjekt und klicken Sie auf **+ Feld hinzufügen**
+2. Wählen Sie **Relation** als Feldtyp
+3. Wählen Sie das zweite Objekt aus (z. B. "Projekte")
+4. Legen Sie den Beziehungstyp auf **Viele-zu-Eins** fest
+5. Benennen Sie die Felder:
    * Feld auf der Verknüpfung: z. B. "Projekt"
    * Feld bei Projekten: z. B. "Teammitglieder"
-7. Klicken Sie auf **Speichern**
+6. Klicken Sie auf **Speichern**
 
 ## Schritt 3: Anzeige der Verknüpfungsbeziehung konfigurieren
 
@@ -105,6 +98,18 @@ Konfigurieren Sie nun die Quellobjekte so, dass verknüpfte Datensätze direkt a
 6. Wählen Sie die **Zielbeziehung** aus (z. B. "Projekt" — das Feld an der Verknüpfung, das auf die andere Seite zeigt)
 7. Klicken Sie auf **Speichern**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Wiederholen Sie dies für das andere Objekt:
+
+1. Wählen Sie "Projekte" im Datenmodell aus
+2. Bearbeiten Sie das Beziehungsfeld "Teammitglieder"
+3. Aktivieren Sie den Verknüpfungsschalter
+4. Wählen Sie "Person" als Zielbeziehung aus
+5. Speichern
+
 ## Ergebnis
 
 Nach der Konfiguration:
@@ -125,15 +130,15 @@ Hier ist eine vollständige Schritt-für-Schritt-Anleitung:
 
 ### Beziehungen hinzufügen
 
-1. **Personen → Projektzuweisung**
-   * Typ: Eins-zu-Viele
-   * Feld bei Personen: "Projektzuweisungen"
+1. **Projektzuweisung → Personen**
+   * Typ: Viele-zu-Eins
    * Feld bei Zuweisung: "Person"
+   * Feld bei Personen: "Projektzuweisungen"
 
-2. **Projekte → Projektzuweisung**
-   * Typ: Eins-zu-Viele
-   * Feld bei Projekten: "Teammitglieder"
+2. **Projektzuweisung → Projekte**
+   * Typ: Viele-zu-Eins
    * Feld bei Zuweisung: "Projekt"
+   * Feld bei Projekten: "Teammitglieder"
 
 ### Verknüpfungsanzeige konfigurieren
 

packages/twenty-docs/l/de/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ Fügen Sie Links zu externen Tools direkt in der Seitenleiste hinzu. Nützlich,
 ## Befehlsmenü
 
 Drücken Sie `Cmd+K` (oder `Ctrl+K`), um das Befehlsmenü zu öffnen — eine Suchleiste für den Schnellzugriff, mit der Sie zu jedem Datensatz, jeder Ansicht oder Aktion springen können, ohne durch die Seitenleiste zu navigieren.
-
-## Anpassung der Seitenleiste
-
-Um die Seitenleiste anzupassen, bewegen Sie den Mauszeiger über den Abschnitt "Arbeitsbereich" in der Seitenleiste und klicken Sie auf das Schraubenschlüssel-Symbol.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Symbol zum Bearbeiten der Navigation" />

packages/twenty-docs/l/de/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Datensatzseiten
 description: Passen Sie das Layout einzelner Datensatz-Detailseiten mit Tabs und Widgets an.
 ---
 
-## Übersicht
-
 Wenn Sie in Twenty einen Datensatz öffnen, besteht die Detailseite aus **Tabs** und **Widgets**. Beide lassen sich je Objekttyp vollständig anpassen.
 
 ## Registerkarten
@@ -40,20 +38,12 @@ Widgets sind die Bausteine in jedem Tab. Zu den verfügbaren Widget-Typen gehör
 
 1. Öffnen Sie einen beliebigen Datensatz
 2. Drücken Sie `Cmd+K` und suchen Sie nach "Layout der Datensatzseite bearbeiten"
-
-oder
-
-1. Gehen Sie zu Einstellungen > Datenmodell > Objekt Ihrer Wahl > Layout
-
-2. Klicken Sie für dieses Objekt auf die Schaltfläche "Datensatzseite anpassen"
-
 3. Sie befinden sich jetzt im Anpassungsmodus:
    * **Widgets hinzufügen** aus der Widget-Auswahl
    * **Widgets ziehen**, um sie im Raster neu zu positionieren
    * **Widgets in der Größe ändern**, indem Sie ihre Ränder ziehen
    * **Felder konfigurieren**, die in jedem Widget angezeigt werden
    * **Tabs verwalten** — hinzufügen, entfernen, umbenennen, neu anordnen
-
 4. Speichern Sie Ihre Änderungen — sie gelten für alle Datensätze dieses Objekttyps
 
 ## Feldsichtbarkeit

packages/twenty-docs/l/it/developers/extend/apps/logic-functions.mdx

@@ -94,16 +94,15 @@ const handler = async (event: RoutePayload) => {
 
 Il tipo `RoutePayload` ha la seguente struttura:
 
-  | Proprietà                    | Tipo                                                    | Descrizione                                                                                                                                                                                           | Esempio                                                                    |
-  | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | Intestazioni HTTP (solo quelle elencate in `forwardedRequestHeaders`)                                                                                                                                 | vedi la sezione sotto                                                      |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parametri della query string (valori multipli uniti da virgole)                                                                                                                                       | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Parametri di percorso estratti dal pattern della route                                                                                                                                                | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Corpo della richiesta analizzato (JSON)                                                                                                                                                               | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Indica se il corpo è codificato in base64                                                                                                                                                             |                                                                            |
-  | `requestContext.http.method` | `string`                                                | Metodo HTTP (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                           |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | Percorso della richiesta non elaborato                                                                                                                                                                |                                                                            |
+  | Proprietà                    | Tipo                                                    | Descrizione                                                           | Esempio                                                                    |
+  | ---------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | Intestazioni HTTP (solo quelle elencate in `forwardedRequestHeaders`) | vedi la sezione sotto                                                      |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parametri della query string (valori multipli uniti da virgole)       | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Parametri di percorso estratti dal pattern della route                | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Corpo della richiesta analizzato (JSON)                               | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Indica se il corpo è codificato in base64                             |                                                                            |
+  | `requestContext.http.method` | `string`                                                | Metodo HTTP (GET, POST, PUT, PATCH, DELETE)                           |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | Percorso della richiesta non elaborato                                |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/it/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Per i team pronti a scalare:
 * Supporto standard
 
 <Note>
-Premium features (SSO, row-level permissions and AI usage data) are not included in the Pro plan.
+Le funzionalità premium (SSO e autorizzazioni a livello di riga) non sono incluse nel piano Pro.
 </Note>
 
 ### Organizzazione (Cloud)
@@ -27,7 +27,7 @@ Premium features (SSO, row-level permissions and AI usage data) are not included
 Per i team più numerosi con esigenze avanzate:
 
 * Tutto ciò che è incluso in Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **Funzionalità premium**: integrazione SSO e autorizzazioni a livello di riga
 * Supporto prioritario
 
 ## Piani self‑hosted
@@ -45,7 +45,7 @@ Esegui Twenty sulla tua infrastruttura senza costi:
 Per i team che necessitano di funzionalità premium con il self‑hosting:
 
 * Tutte le funzionalità di Pro
-* **Premium features**: SSO integration, row-level permissions and AI usage data
+* **Funzionalità premium**: integrazione SSO e autorizzazioni a livello di riga
 * Supporto del team di Twenty
 * Nessun requisito di pubblicare il codice personalizzato come open source prima della distribuzione
 
@@ -55,7 +55,6 @@ Le funzionalità premium sono disponibili solo nei piani Organizzazione (Cloud o
 
 * **Integrazione SSO**: Single Sign‑On con il tuo provider di identità
 * **Autorizzazioni a livello di riga**: controllo degli accessi granulare a livello di record
-* **AI usage data**: Track AI consumption across the workspace
 
 ## Cambio piano
 
@@ -78,15 +77,3 @@ Contatta il supporto per eseguire il downgrade del tuo piano.
 ### Passa alla fatturazione mensile
 
 Contatta il supporto per tornare alla fatturazione mensile.
-
-## Obtain an Enterprise Key for Organization (Self-Hosted)
-
-To use the Organization (Self-Hosted) plan, you need to obtain an Enterprise key:
-
-1. Go to **Settings → Admin Panel → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Enterprise key" />
-
-2. Click **Get Enterprise Key**
-3. When you are redirected to Stripe, enter your payment details and confirm
-4. When your Enterprise key is displayed, paste it into the Enterprise settings page and activate the Organization license

packages/twenty-docs/l/it/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ Se vuoi effettuare il self-hosting e hai bisogno delle funzionalità Premium (SS
 Le funzionalità Premium sono disponibili solo nei piani Organization (Cloud o Self-Hosted):
 * **Integrazione SSO**: Single Sign-On con il tuo provider di identità
 * **Autorizzazioni a livello di riga**: controllo degli accessi granulare a livello di record
-* **Dati di utilizzo dell'IA**: Tieni traccia del consumo dell'IA nel tuo spazio di lavoro
-</Accordion>
-
-<Accordion title="Il piano Organization su cloud e il piano Organization in modalità self-hosted sono la stessa cosa?">
-Offrono le stesse funzionalità Premium. Tuttavia, un abbonamento cloud non può essere utilizzato per distribuzioni self-hosted. La modalità self-hosted richiede una chiave Enterprise.
 </Accordion>
 
 <Accordion title="Offrite posti gratuiti per utenti solo visualizzazione?">

packages/twenty-docs/l/it/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ Per prima cosa, crea l'oggetto intermedio che conterrà i collegamenti.
 1. Vai a **Impostazioni → Modello dati**
 2. Fai clic su **+ Nuovo oggetto**
 3. Assegnagli un nome descrittivo (ad es., "Assegnazione al progetto", "Membro del team", "Ordine del prodotto")
-4. Attiva l'opzione "Salta la creazione di un campo Nome"
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Nuovo oggetto pivot" />
-
-5. Clicca su **Salva**
+4. Clicca su **Salva**
 
 <Tip>
 **Convenzione di denominazione**: Usa un nome che descriva la relazione, come "Assegnazione al progetto" o "Appartenenza al team". Questo rende il modello di dati più facile da comprendere.
 </Tip>
 
-## Passaggio 2: Crea relazioni tra gli oggetti e l'oggetto di giunzione
+## Passaggio 2: Crea le relazioni dall'oggetto di giunzione
 
-Aggiungi campi di relazione da ciascuno dei due oggetti all'oggetto di giunzione.
+Aggiungi campi di relazione dall'oggetto di giunzione a entrambi gli oggetti che desideri collegare.
 
-### Prima relazione (Oggetto A → Oggetto di giunzione)
-
-1. Seleziona il tuo primo oggetto in **Impostazioni → Modello dati**
-2. Fai clic su **+ Aggiungi relazione**
-3. Seleziona l'oggetto di giunzione (ad es., "Assegnazioni al progetto")
-4. Imposta il tipo di relazione su **Uno-a-molti** (una persona può collegarsi a molte assegnazioni)
-5. Assegna un nome ai campi:
-   * Campo su Persone: ad es., "Assegnazioni ai progetti"
-   * Campo sull'oggetto di giunzione: ad es., "Persona"
-6. Clicca su **Salva**
-
-### Seconda relazione (Oggetto B → Oggetto di giunzione)
-
-1. Seleziona il tuo secondo oggetto in **Impostazioni → Modello dati**
-2. Fai clic su **+ Aggiungi relazione**
-3. Seleziona l'oggetto di giunzione (ad es., "Assegnazioni al progetto")
-4. Imposta il tipo di relazione su **Uno-a-molti** (un progetto può collegarsi a molte assegnazioni)
-5. Abilita **"Questa è una relazione con un oggetto di giunzione"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### Prima relazione (Giunzione → Oggetto A)
 
+1. Seleziona il tuo oggetto di giunzione in **Impostazioni → Modello dati**
+2. Fai clic su **+ Aggiungi campo**
+3. Scegli **Relazione** come tipo di campo
+4. Seleziona il primo oggetto (ad es., "Persone")
+5. Imposta il tipo di relazione su **Molti-a-uno** (molte assegnazioni possono collegarsi a una persona)
 6. Assegna un nome ai campi:
+   * Campo sull'oggetto di giunzione: ad es., "Persona"
+   * Campo su Persone: ad es., "Assegnazioni ai progetti"
+7. Clicca su **Salva**
+
+### Seconda relazione (Giunzione → Oggetto B)
+
+1. Sempre sull'oggetto di giunzione, fai clic su **+ Aggiungi campo**
+2. Scegli **Relazione** come tipo di campo
+3. Seleziona il secondo oggetto (ad es., "Progetti")
+4. Imposta il tipo di relazione su **Molti-a-uno**
+5. Assegna un nome ai campi:
    * Campo sull'oggetto di giunzione: ad es., "Progetto"
    * Campo su Progetti: ad es., "Membri del team"
-7. Clicca su **Salva**
+6. Clicca su **Salva**
 
 ## Passaggio 3: Configura la visualizzazione della relazione di giunzione
 
@@ -105,6 +98,18 @@ Ora configura gli oggetti sorgente per visualizzare direttamente i record colleg
 6. Seleziona la **Relazione di destinazione** (ad es., "Progetto" — il campo sull'oggetto di giunzione che punta all'altro lato)
 7. Clicca su **Salva**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Ripeti per l'altro oggetto:
+
+1. Seleziona "Progetti" in Modello dati
+2. Modifica il campo di relazione "Membri del team"
+3. Abilita l'interruttore di giunzione
+4. Seleziona "Persona" come relazione di destinazione
+5. Salva
+
 ## Risultato
 
 Dopo la configurazione:
@@ -125,15 +130,15 @@ Ecco una procedura completa:
 
 ### Aggiungi relazioni
 
-1. **Persone → Assegnazione al progetto**
-   * Tipo: Uno-a-molti
-   * Campo su Persone: "Assegnazioni ai progetti"
+1. **Assegnazione al progetto → Persone**
+   * Tipo: Molti-a-uno
    * Campo su Assegnazione: "Persona"
+   * Campo su Persone: "Assegnazioni ai progetti"
 
-2. **Progetti → Assegnazione al progetto**
-   * Tipo: Uno-a-molti
-   * Campo su Progetti: "Membri del team"
+2. **Assegnazione al progetto → Progetti**
+   * Tipo: Molti-a-uno
    * Campo su Assegnazione: "Progetto"
+   * Campo su Progetti: "Membri del team"
 
 ### Configura la visualizzazione della giunzione
 

packages/twenty-docs/l/it/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ Aggiungi collegamenti a strumenti esterni direttamente nella barra laterale. Uti
 ## Menu Comandi
 
 Premi `Cmd+K` (o `Ctrl+K`) per aprire il menu comandi — una barra di ricerca ad accesso rapido per passare a qualsiasi record, vista o azione senza usare la barra laterale.
-
-## Personalizzare la barra laterale
-
-Per personalizzare la barra laterale, passa il mouse sulla sezione "Workspace" nella barra laterale e fai clic sull'icona a forma di chiave inglese.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Icona di modifica della navigazione" />

packages/twenty-docs/l/it/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Pagine dei record
 description: Personalizza il layout delle singole pagine di dettaglio dei record con schede e widget.
 ---
 
-## Panoramica
-
 Quando apri un record in Twenty, la pagina di dettaglio è composta da **schede** e **widget**. Entrambi sono completamente personalizzabili per ciascun tipo di oggetto.
 
 ## Schede
@@ -40,20 +38,12 @@ I widget sono gli elementi costitutivi all'interno di ogni scheda. Tipi di widge
 
 1. Apri un record qualsiasi
 2. Premi `Cmd+K` e cerca "Modifica il layout della pagina del record"
-
-o
-
-1. Vai a Impostazioni > Modello dati > oggetto di tua scelta > Layout
-
-2. Fai clic sul pulsante "Personalizza pagina del record" per quell'oggetto
-
 3. Ora sei in modalità di personalizzazione:
    * **Aggiungi widget** dal selettore di widget
    * **Trascina i widget** per riposizionarli sulla griglia
    * **Ridimensiona i widget** trascinando i bordi
    * **Configura i campi** mostrati all'interno di ciascun widget
    * **Gestisci le schede** — aggiungi, rimuovi, rinomina, riordina
-
 4. Salva le modifiche — si applicano a tutti i record di quel tipo di oggetto
 
 ## Visibilità dei campi

packages/twenty-docs/l/pt/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ O modo de desenvolvimento só está disponível em instâncias do Twenty em modo
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="Saída do terminal no modo de desenvolvimento" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="Saída do terminal no modo de desenvolvimento" />
 </div>
 
 #### Sincronização única com `yarn twenty dev --once`
@@ -127,7 +127,13 @@ Clique em **My twenty app** para abrir o seu **registro do aplicativo**. Um regi
 Clique em **View installed app** para ver o aplicativo instalado. A aba **About** mostra a versão atual e as opções de gerenciamento:
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Aplicação instalada" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Aplicativo instalado — aba About" />
+</div>
+
+Altere para a aba **Content** para ver tudo o que seu aplicativo oferece — objetos, campos, funções de lógica e agentes:
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="Aplicativo instalado — aba Content" />
 </div>
 
 Tudo pronto! Edite qualquer arquivo em `src/` e as alterações serão detectadas automaticamente.
@@ -207,49 +213,30 @@ Os exemplos são obtidos do diretório [twenty-apps/examples](https://github.com
 
 A ferramenta de scaffolding já iniciou um servidor local do Twenty para você. Para gerenciá-lo depois, use `yarn twenty server`:
 
-| Comando                                | Descrição                                                         |
-| -------------------------------------- | ----------------------------------------------------------------- |
-| `yarn twenty server start`             | Inicia o servidor local (baixa a imagem se necessário)            |
-| `yarn twenty server start --port 3030` | Iniciar em uma porta personalizada                                |
-| `yarn twenty server start --test`      | Inicie uma instância de teste separada na porta 2021              |
-| `yarn twenty server stop`              | Interrompe o servidor (preserva os dados)                         |
-| `yarn twenty server status`            | Mostra o status do servidor, a URL, a versão e as credenciais     |
-| `yarn twenty server logs`              | Transmite os logs do servidor                                     |
-| `yarn twenty server logs --lines 100`  | Mostra as últimas 100 linhas de log                               |
-| `yarn twenty server reset`             | Exclui todos os dados e inicia do zero                            |
-| `yarn twenty server upgrade`           | Baixe a imagem mais recente `twenty-app-dev` e recrie o contêiner |
-| `yarn twenty server upgrade 2.2.0`     | Atualizar para uma versão específica                              |
+| Comando                                | Descrição                                              |
+| -------------------------------------- | ------------------------------------------------------ |
+| `yarn twenty server start`             | Inicia o servidor local (baixa a imagem se necessário) |
+| `yarn twenty server start --port 3030` | Iniciar em uma porta personalizada                     |
+| `yarn twenty server start --test`      | Inicie uma instância de teste separada na porta 2021   |
+| `yarn twenty server stop`              | Interrompe o servidor (preserva os dados)              |
+| `yarn twenty server status`            | Mostra o status do servidor, a URL e as credenciais    |
+| `yarn twenty server logs`              | Transmite os logs do servidor                          |
+| `yarn twenty server logs --lines 100`  | Mostra as últimas 100 linhas de log                    |
+| `yarn twenty server reset`             | Exclui todos os dados e inicia do zero                 |
 
 Os dados são persistidos entre reinicializações em dois volumes do Docker (`twenty-app-dev-data` para PostgreSQL, `twenty-app-dev-storage` para arquivos). Use `reset` para apagar tudo e começar do zero.
 
-### Atualizando a imagem do servidor
-
-Use `yarn twenty server upgrade` para verificar se há uma imagem do Docker `twenty-app-dev` mais recente e atualizar o container. O comando baixa a imagem, a compara com aquela a partir da qual o container foi criado e só recria o container se a imagem realmente tiver sido alterada. Seus volumes de dados são preservados — apenas o container é substituído.
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-Se uma imagem mais recente estiver disponível e o container estiver em execução, o comando de atualização iniciará automaticamente um novo container com a imagem atualizada. Em seguida, execute `yarn twenty server start` para aguardar até que ele fique saudável. Se a imagem não tiver mudado, o container permanece inalterado.
-
-Você pode verificar a versão em execução com `yarn twenty server status`, que exibe o `APP_VERSION` do container.
-
 ### Executando uma instância de teste
 
 Passe `--test` para qualquer comando de `server` para gerenciar uma segunda instância totalmente isolada — útil para executar testes de integração ou experimentar sem tocar nos seus dados principais de desenvolvimento.
 
-| Comando                             | Descrição                                                               |
-| ----------------------------------- | ----------------------------------------------------------------------- |
-| `yarn twenty server start --test`   | Inicia a instância de teste (padrão: porta 2021)                        |
-| `yarn twenty server stop --test`    | Interrompe a instância de teste                                         |
-| `yarn twenty server status --test`  | Mostra o status da instância de teste, a URL, a versão e as credenciais |
-| `yarn twenty server logs --test`    | Transmite os logs da instância de teste                                 |
-| `yarn twenty server reset --test`   | Exclui os dados de teste e inicia do zero                               |
-| `yarn twenty server upgrade --test` | Atualiza a imagem da instância de teste                                 |
+| Comando                            | Descrição                                                     |
+| ---------------------------------- | ------------------------------------------------------------- |
+| `yarn twenty server start --test`  | Inicia a instância de teste (padrão: porta 2021)              |
+| `yarn twenty server stop --test`   | Interrompe a instância de teste                               |
+| `yarn twenty server status --test` | Mostra o status da instância de teste, a URL e as credenciais |
+| `yarn twenty server logs --test`   | Transmite os logs da instância de teste                       |
+| `yarn twenty server reset --test`  | Exclui os dados de teste e inicia do zero                     |
 
 A instância de teste é executada em seu próprio contêiner Docker (`twenty-app-dev-test`) com volumes dedicados (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) e configuração própria, para que possa ser executada em paralelo com sua instância principal sem conflitos. Combine `--test` com `--port` para substituir a porta padrão 2021.
 

packages/twenty-docs/l/pt/developers/extend/apps/logic-functions.mdx

@@ -94,16 +94,15 @@ const handler = async (event: RoutePayload) => {
 
 O tipo `RoutePayload` tem a seguinte estrutura:
 
-  | Propriedade                  | Tipo                                                    | Descrição                                                                                                                                                                                                                                   | Exemplo                                                                    |
-  | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | Cabeçalhos HTTP (apenas aqueles listados em `forwardedRequestHeaders`)                                                                                                                                                                      | veja a seção abaixo                                                        |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parâmetros de query string (valores múltiplos unidos por vírgulas)                                                                                                                                                                          | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Parâmetros de caminho extraídos do padrão de rota                                                                                                                                                                                           | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Corpo da requisição analisado (JSON)                                                                                                                                                                                                        | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Corpo da solicitação UTF-8 original, antes da análise de JSON. Útil para verificar assinaturas de webhook no estilo HMAC (por exemplo, `X-Hub-Signature-256` do GitHub, Stripe). `undefined` quando o ambiente de execução não o preservou. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Se o corpo está codificado em base64                                                                                                                                                                                                        |                                                                            |
-  | `requestContext.http.method` | `string`                                                | Método HTTP (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                                                                 |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | Caminho bruto da requisição                                                                                                                                                                                                                 |                                                                            |
+  | Propriedade                  | Tipo                                                    | Descrição                                                              | Exemplo                                                                    |
+  | ---------------------------- | ------------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | Cabeçalhos HTTP (apenas aqueles listados em `forwardedRequestHeaders`) | veja a seção abaixo                                                        |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Parâmetros de query string (valores múltiplos unidos por vírgulas)     | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Parâmetros de caminho extraídos do padrão de rota                      | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Corpo da requisição analisado (JSON)                                   | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Se o corpo está codificado em base64                                   |                                                                            |
+  | `requestContext.http.method` | `string`                                                | Método HTTP (GET, POST, PUT, PATCH, DELETE)                            |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | Caminho bruto da requisição                                            |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/pt/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Para equipes prontas para escalar:
 * Suporte padrão
 
 <Note>
-Os recursos Premium (SSO, permissões em nível de linha e dados de uso de IA) não estão incluídos no plano Pro.
+Recursos premium (SSO e permissões em nível de linha) não estão incluídos no plano Pro.
 </Note>
 
 ### Organização (Nuvem)
@@ -27,7 +27,7 @@ Os recursos Premium (SSO, permissões em nível de linha e dados de uso de IA) n
 Para equipes maiores com necessidades avançadas:
 
 * Tudo do Pro
-* **Recursos Premium**: integração com SSO, permissões em nível de linha e dados de uso de IA
+* **Recursos premium**: integração SSO e permissões em nível de linha
 * Suporte prioritário
 
 ## Planos auto-hospedados
@@ -45,7 +45,7 @@ Hospede o Twenty na sua própria infraestrutura sem custo:
 Para equipes que precisam de recursos premium enquanto se auto-hospedam:
 
 * Todos os recursos do Pro
-* **Recursos Premium**: integração com SSO, permissões em nível de linha e dados de uso de IA
+* **Recursos premium**: integração SSO e permissões em nível de linha
 * Suporte da equipe Twenty
 * Sem necessidade de publicar código personalizado como código aberto antes de distribuir
 
@@ -55,7 +55,6 @@ Os recursos premium estão disponíveis apenas nos planos Organização (Nuvem o
 
 * **Integração SSO**: Single Sign-On com seu provedor de identidade
 * **Permissões em nível de linha**: controle de acesso granular no nível de registro
-* **Dados de uso de IA**: Acompanhe o consumo de IA em todo o espaço de trabalho
 
 ## Mudança de planos
 
@@ -78,15 +77,3 @@ Entre em contato com o suporte para fazer downgrade do seu plano.
 ### Mudar para faturamento mensal
 
 Entre em contato com o suporte para voltar ao faturamento mensal.
-
-## Obtenha uma chave Enterprise para Organization (Self-Hosted)
-
-Para usar o plano Organization (Self-Hosted), você precisa obter uma chave Enterprise:
-
-1. Vá para **Configurações → Painel de Administração → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Chave Enterprise" />
-
-2. Clique em **Obter chave Enterprise**
-3. Quando você for redirecionado ao Stripe, insira seus dados de pagamento e confirme
-4. Quando sua chave Enterprise for exibida, cole-a na página de configurações do Enterprise e ative a licença do Organization

packages/twenty-docs/l/pt/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ Se você quiser hospedar por conta própria e precisar dos recursos Premium (SSO
 Os recursos Premium estão disponíveis apenas nos planos Organization (Cloud ou Self-Hosted):
 * **Integração de SSO**: Single Sign-On com seu provedor de identidade
 * **Permissões em nível de linha**: Controle de acesso granular no nível de registro
-* **Dados de uso de IA**: Acompanhe o consumo de IA em todo o espaço de trabalho
-</Accordion>
-
-<Accordion title="O plano Organization na nuvem e o plano Organization em ambiente autohospedado são iguais?">
-Ambos oferecem os mesmos recursos Premium. No entanto, uma assinatura na nuvem não pode ser usada para implantações autohospedadas. O ambiente autohospedado requer uma chave Enterprise.
 </Accordion>
 
 <Accordion title="Você oferece assentos gratuitos para usuários apenas visualizadores?">

packages/twenty-docs/l/pt/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ Primeiro, crie o objeto intermediário que manterá as conexões.
 1. Vá a **Definições → Modelo de Dados**
 2. Clique em **+ Novo objeto**
 3. Dê um nome descritivo (por exemplo, "Atribuição de Projeto", "Membro da Equipe", "Pedido de Produto")
-4. Ative a opção "Ignorar a criação de um campo Nome"
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Novo objeto pivô" />
-
-5. Clique em **Salvar**
+4. Clique em **Salvar**
 
 <Tip>
 **Convenção de nomenclatura**: Use um nome que descreva a relação, como "Atribuição de Projeto" ou "Participação na Equipe". Isso torna o modelo de dados mais fácil de entender.
 </Tip>
 
-## Etapa 2: Crie relações entre os objetos e o objeto de junção
+## Etapa 2: Criar Relações a partir do Objeto de Junção
 
-Adicione campos de relação de cada um dos seus dois objetos ao objeto de junção.
+Adicione campos de relação do objeto de junção para ambos os objetos que deseja conectar.
 
-### Primeira Relação (Objeto A → Junção)
-
-1. Selecione seu primeiro objeto em **Settings → Data Model**
-2. Clique em **+ Adicionar relação**
-3. Selecione o objeto de junção (por exemplo, "Atribuições de Projeto")
-4. Defina o tipo de relação como **Um-para-muitos** (uma pessoa pode se vincular a muitas atribuições)
-5. Nomeie os campos:
-   * Campo em Pessoas: por exemplo, "Atribuições de Projeto"
-   * Campo na junção: por exemplo, "Pessoa"
-6. Clique em **Salvar**
-
-### Segunda Relação (Objeto B → Junção)
-
-1. Selecione seu segundo objeto em **Settings → Data Model**
-2. Clique em **+ Adicionar relação**
-3. Selecione o objeto de junção (por exemplo, "Atribuições de Projeto")
-4. Defina o tipo de relação como **Um-para-muitos** (um projeto pode se vincular a muitas atribuições)
-5. Ative **"Esta é uma relação com um objeto de junção"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### Primeira Relação (Junção → Objeto A)
 
+1. Selecione seu objeto de junção em **Settings → Data Model**
+2. Clique em **+ Adicionar campo**
+3. Escolha **Relação** como o tipo de campo
+4. Selecione o primeiro objeto (por exemplo, "Pessoas")
+5. Defina o tipo de relação como **Muitos-para-um** (muitas atribuições podem se vincular a uma pessoa)
 6. Nomeie os campos:
+   * Campo na junção: por exemplo, "Pessoa"
+   * Campo em Pessoas: por exemplo, "Atribuições de Projeto"
+7. Clique em **Salvar**
+
+### Segunda Relação (Junção → Objeto B)
+
+1. Ainda no objeto de junção, clique em **+ Add Field**
+2. Escolha **Relação** como o tipo de campo
+3. Selecione o segundo objeto (por exemplo, "Projetos")
+4. Defina o tipo de relação como **Muitos-para-um**
+5. Nomeie os campos:
    * Campo na junção: por exemplo, "Projeto"
    * Campo em Projetos: por exemplo, "Membros da Equipe"
-7. Clique em **Salvar**
+6. Clique em **Salvar**
 
 ## Etapa 3: Configurar a Exibição da Relação de Junção
 
@@ -105,6 +98,18 @@ Agora configure os objetos de origem para exibir diretamente os registros vincul
 6. Selecione a **Relação de destino** (por exemplo, "Projeto" — o campo na junção que aponta para o outro lado)
 7. Clique em **Salvar**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Repita para o outro objeto:
+
+1. Selecione "Projetos" em Data Model
+2. Edite o campo de relação "Membros da Equipe"
+3. Ative o alternador de junção
+4. Selecione "Pessoa" como a relação de destino
+5. Salvar
+
 ## Resultado
 
 Após a configuração:
@@ -125,15 +130,15 @@ Aqui está um passo a passo completo:
 
 ### Adicionar Relações
 
-1. **Pessoas → Atribuição de Projeto**
-   * Tipo: Um-para-muitos
-   * Campo em Pessoas: "Atribuições de Projeto"
+1. **Atribuição de Projeto → Pessoas**
+   * Tipo: Muitos-para-um
    * Campo em Atribuição: "Pessoa"
+   * Campo em Pessoas: "Atribuições de Projeto"
 
-2. **Projetos → Atribuição de Projeto**
-   * Tipo: Um-para-muitos
-   * Campo em Projetos: "Membros da Equipe"
+2. **Atribuição de Projeto → Projetos**
+   * Tipo: Muitos-para-um
    * Campo em Atribuição: "Projeto"
+   * Campo em Projetos: "Membros da Equipe"
 
 ### Configurar Exibição de Junção
 

packages/twenty-docs/l/pt/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ Adicione links para ferramentas externas diretamente na barra lateral. Útil par
 ## Menu de Comandos
 
 Pressione `Cmd+K` (ou `Ctrl+K`) para abrir o menu de comandos — uma barra de pesquisa de acesso rápido para ir a qualquer registro, visualização ou ação sem navegar pela barra lateral.
-
-## Personalizando a barra lateral
-
-Para personalizar a barra lateral, passe o cursor sobre a seção "Workspace" na barra lateral e clique no ícone de chave inglesa.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Ícone de edição da navegação" />

packages/twenty-docs/l/pt/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Páginas de Registos
 description: Personalize o layout das páginas de detalhe de registos individuais com abas e widgets.
 ---
 
-## Visão Geral
-
 Ao abrir um registo no Twenty, a página de detalhe é composta por **abas** e **widgets**. Ambos são totalmente personalizáveis por tipo de objeto.
 
 ## Abas
@@ -40,20 +38,12 @@ Os widgets são os componentes básicos dentro de cada aba. Tipos de widget disp
 
 1. Abra qualquer registro
 2. Pressione `Cmd+K` e pesquise por "Edit record page layout"
-
-ou
-
-1. Vá para Configurações > Modelo de dados > objeto de sua escolha > Layout
-
-2. Clique no botão "Personalizar página de registro" para esse objeto
-
 3. Agora você está no modo de personalização:
    * **Adicionar widgets** no seletor de widgets
    * **Arraste widgets** para reposicioná-los na grade
    * **Redimensione os widgets** arrastando suas bordas
    * **Configure campos** exibidos em cada widget
    * **Gerencie abas** — adicione, remova, renomeie, reordene
-
 4. Salve suas alterações — elas se aplicam a todos os registros desse tipo de objeto
 
 ## Visibilidade de campos

packages/twenty-docs/l/ru/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ yarn twenty dev --verbose
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="Вывод терминала в режиме разработки" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="Вывод терминала в режиме разработки" />
 </div>
 
 #### Разовая синхронизация с `yarn twenty dev --once`
@@ -127,7 +127,13 @@ yarn twenty dev --once
 Нажмите **View installed app**, чтобы посмотреть установленное приложение. Вкладка **About** показывает текущую версию и параметры управления:
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Установленное приложение" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Установленное приложение — вкладка About" />
+</div>
+
+Переключитесь на вкладку **Content**, чтобы увидеть всё, что предоставляет ваше приложение: объекты, поля, логические функции и агенты:
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="Установленное приложение — вкладка Content" />
 </div>
 
 Готово! Отредактируйте любой файл в `src/`, и изменения будут подхвачены автоматически.
@@ -207,49 +213,30 @@ npx create-twenty-app@latest my-twenty-app --example postcard
 
 Генератор каркаса уже запустил для вас локальный сервер Twenty. Чтобы управлять им позже, используйте `yarn twenty server`:
 
-| Команда                                | Описание                                                           |
-| -------------------------------------- | ------------------------------------------------------------------ |
-| `yarn twenty server start`             | Запустить локальный сервер (при необходимости скачивает образ)     |
-| `yarn twenty server start --port 3030` | Запустить на пользовательском порту                                |
-| `yarn twenty server start --test`      | Запускает отдельный тестовый экземпляр на порту 2021               |
-| `yarn twenty server stop`              | Остановить сервер (данные сохраняются)                             |
-| `yarn twenty server status`            | Показать состояние сервера, URL, версию и учётные данные           |
-| `yarn twenty server logs`              | Потоковый вывод журналов сервера                                   |
-| `yarn twenty server logs --lines 100`  | Показать последние 100 строк журнала                               |
-| `yarn twenty server reset`             | Удалить все данные и начать с чистого листа                        |
-| `yarn twenty server upgrade`           | Загрузить последний образ `twenty-app-dev` и пересоздать контейнер |
-| `yarn twenty server upgrade 2.2.0`     | Обновить до конкретной версии                                      |
+| Команда                                | Описание                                                       |
+| -------------------------------------- | -------------------------------------------------------------- |
+| `yarn twenty server start`             | Запустить локальный сервер (при необходимости скачивает образ) |
+| `yarn twenty server start --port 3030` | Запустить на пользовательском порту                            |
+| `yarn twenty server start --test`      | Запускает отдельный тестовый экземпляр на порту 2021           |
+| `yarn twenty server stop`              | Остановить сервер (данные сохраняются)                         |
+| `yarn twenty server status`            | Показать состояние сервера, URL и учётные данные               |
+| `yarn twenty server logs`              | Потоковый вывод журналов сервера                               |
+| `yarn twenty server logs --lines 100`  | Показать последние 100 строк журнала                           |
+| `yarn twenty server reset`             | Удалить все данные и начать с чистого листа                    |
 
 Данные сохраняются между перезапусками в двух томах Docker (`twenty-app-dev-data` для PostgreSQL, `twenty-app-dev-storage` для файлов). Используйте `reset`, чтобы стереть всё и начать заново.
 
-### Обновление образа сервера
-
-Используйте `yarn twenty server upgrade`, чтобы проверить наличие более нового Docker-образа `twenty-app-dev` и обновить контейнер. Команда скачивает образ, сравнивает его с тем, из которого был создан контейнер, и пересоздаёт контейнер только если образ действительно изменился. Ваши тома данных сохраняются — заменяется только контейнер.
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-Если доступен более новый образ и контейнер был запущен, команда обновления автоматически запускает новый контейнер с обновлённым образом. Затем выполните `yarn twenty server start`, чтобы дождаться перехода контейнера в состояние healthy. Если образ не изменился, контейнер остаётся без изменений.
-
-Вы можете проверить запущенную версию с помощью `yarn twenty server status` — эта команда показывает `APP_VERSION` из контейнера.
-
 ### Запуск тестового экземпляра
 
 Передайте `--test` любой команде `server`, чтобы управлять вторым, полностью изолированным экземпляром — это полезно для запуска интеграционных тестов или экспериментов, не затрагивая ваши основные данные разработки.
 
-| Команда                             | Описание                                                              |
-| ----------------------------------- | --------------------------------------------------------------------- |
-| `yarn twenty server start --test`   | Запустить тестовый экземпляр (по умолчанию — порт 2021)               |
-| `yarn twenty server stop --test`    | Остановить тестовый экземпляр                                         |
-| `yarn twenty server status --test`  | Показать состояние тестового экземпляра, URL, версию и учётные данные |
-| `yarn twenty server logs --test`    | Выводить журналы тестового экземпляра в потоковом режиме              |
-| `yarn twenty server reset --test`   | Удалить тестовые данные и начать с чистого листа                      |
-| `yarn twenty server upgrade --test` | Обновить образ тестового экземпляра                                   |
+| Команда                            | Описание                                                      |
+| ---------------------------------- | ------------------------------------------------------------- |
+| `yarn twenty server start --test`  | Запустить тестовый экземпляр (по умолчанию — порт 2021)       |
+| `yarn twenty server stop --test`   | Остановить тестовый экземпляр                                 |
+| `yarn twenty server status --test` | Показать состояние тестового экземпляра, URL и учётные данные |
+| `yarn twenty server logs --test`   | Выводить журналы тестового экземпляра в потоковом режиме      |
+| `yarn twenty server reset --test`  | Удалить тестовые данные и начать с чистого листа              |
 
 Тестовый экземпляр запускается в собственном контейнере Docker (`twenty-app-dev-test`) с выделенными томами (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) и собственной конфигурацией, поэтому он может работать параллельно с вашим основным экземпляром без конфликтов. Совместите `--test` с `--port`, чтобы переопределить значение по умолчанию (2021).
 

packages/twenty-docs/l/ru/developers/extend/apps/logic-functions.mdx

@@ -94,16 +94,15 @@ const handler = async (event: RoutePayload) => {
 
 Тип `RoutePayload` имеет следующую структуру:
 
-  | Свойство                     | Тип                                                     | Описание                                                                                                                                                                                                                | Пример                                                                     |
-  | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | HTTP-заголовки (только перечисленные в `forwardedRequestHeaders`)                                                                                                                                                       | см. раздел ниже                                                            |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Параметры строки запроса (несколько значений объединяются запятыми)                                                                                                                                                     | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Параметры пути, извлечённые из шаблона маршрута                                                                                                                                                                         | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Разобранное тело запроса (JSON)                                                                                                                                                                                         | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | Исходное тело запроса в кодировке UTF-8, до разбора JSON. Полезно для проверки подписей вебхуков в стиле HMAC (например, `X-Hub-Signature-256` от GitHub, Stripe). `undefined`, если среда выполнения не сохранила его. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Является ли тело закодированным в base64                                                                                                                                                                                |                                                                            |
-  | `requestContext.http.method` | `string`                                                | Метод HTTP (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                                              |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | Необработанный путь запроса                                                                                                                                                                                             |                                                                            |
+  | Свойство                     | Тип                                                     | Описание                                                            | Пример                                                                     |
+  | ---------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | HTTP-заголовки (только перечисленные в `forwardedRequestHeaders`)   | см. раздел ниже                                                            |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Параметры строки запроса (несколько значений объединяются запятыми) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Параметры пути, извлечённые из шаблона маршрута                     | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Разобранное тело запроса (JSON)                                     | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Является ли тело закодированным в base64                            |                                                                            |
+  | `requestContext.http.method` | `string`                                                | Метод HTTP (GET, POST, PUT, PATCH, DELETE)                          |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | Необработанный путь запроса                                         |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/ru/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Twenty предлагает гибкие тарифы для команд люб
 * Стандартная поддержка
 
 <Note>
-Премиальные функции (SSO, разрешения на уровне строк и данные об использовании ИИ) не включены в тариф Pro.
+Премиальные функции (SSO и разрешения на уровне записей) не входят в план Pro.
 </Note>
 
 ### Организация (облако)
@@ -27,7 +27,7 @@ Twenty предлагает гибкие тарифы для команд люб
 Для крупных команд с расширенными потребностями:
 
 * Все, что есть в Pro
-* **Премиальные функции**: интеграция SSO, разрешения на уровне строк и данные об использовании ИИ
+* **Премиальные функции**: интеграция с SSO и разрешения на уровне записей
 * Приоритетная поддержка
 
 ## Планы для самостоятельного размещения
@@ -45,7 +45,7 @@ Twenty предлагает гибкие тарифы для команд люб
 Для команд, которым нужны премиальные функции при самостоятельном размещении:
 
 * Все возможности Pro
-* **Премиальные функции**: интеграция SSO, разрешения на уровне строк и данные об использовании ИИ
+* **Премиальные функции**: интеграция с SSO и разрешения на уровне записей
 * Поддержка от команды Twenty
 * Не требуется публиковать пользовательский код с открытым исходным кодом перед распространением
 
@@ -55,7 +55,6 @@ Twenty предлагает гибкие тарифы для команд люб
 
 * **Интеграция с SSO**: единый вход через вашего поставщика идентификации
 * **Разрешения на уровне записей**: тонкая настройка управления доступом на уровне записей
-* **Данные об использовании ИИ**: Отслеживайте потребление ИИ в рабочем пространстве
 
 ## Переключение планов
 
@@ -78,15 +77,3 @@ Twenty предлагает гибкие тарифы для команд люб
 ### Переход на ежемесячную оплату
 
 Свяжитесь со службой поддержки, чтобы вернуться на ежемесячную оплату.
-
-## Получите ключ Enterprise для организации (самостоятельный хостинг)
-
-Чтобы использовать тариф Organization (Self-Hosted), необходимо получить ключ Enterprise:
-
-1. Перейдите в **Настройки → Панель администратора → Enterprise**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Ключ Enterprise" />
-
-2. Нажмите **Получить ключ Enterprise**
-3. Когда вы будете перенаправлены на Stripe, введите платёжные данные и подтвердите
-4. Когда ваш ключ Enterprise будет отображён, вставьте его на странице настроек Enterprise и активируйте лицензию Organization

packages/twenty-docs/l/ru/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ description: Часто задаваемые вопросы о тарифах и
 Премиум-функции доступны только в планах Organization (облако или Self-Hosted):
 * **Интеграция с SSO**: единый вход с вашим провайдером идентификации
 * **Разрешения на уровне записей**: детализированное управление доступом на уровне записей
-* **Данные об использовании ИИ**: Отслеживайте потребление ИИ в рабочем пространстве
-</Accordion>
-
-<Accordion title="Одинаков ли тариф Organization в облаке и в самостоятельно размещаемой версии?">
-Они предлагают одинаковые премиум-функции. Однако облачную подписку нельзя использовать для развертываний на собственном хостинге. Для самостоятельно размещаемой версии требуется ключ Enterprise.
 </Accordion>
 
 <Accordion title="Предлагаете ли вы бесплатные места для пользователей с правами только просмотра?">
@@ -32,7 +27,7 @@ description: Часто задаваемые вопросы о тарифах и
 </Accordion>
 
 <Accordion title="Где я могу переключить свою подписку на план Pro?">
-Пожалуйста, свяжитесь с нашей командой напрямую через раздел «Поддержка», в данный момент нет простого способа сделать это через пользовательский интерфейс.
+Пожалуйста, свяжитесь с нашей командой напрямую через Поддержку, в данный момент нет простого способа сделать это через пользовательский интерфейс.
 </Accordion>
 
 <Accordion title="Где я могу переключить свою подписку на годовой период?">

packages/twenty-docs/l/ru/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ People ←→ Project Assignments ←→ Projects
 1. Перейдите в **Настройки → Модель данных**
 2. Нажмите **+ Новый объект**
 3. Дайте ему понятное имя (например, "Project Assignment", "Team Member", "Product Order")
-4. Включите переключатель «Пропустить создание поля „Имя“»
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Новый объект-связка" />
-
-5. Нажмите **Сохранить**
+4. Нажмите **Сохранить**
 
 <Tip>
 **Рекомендации по именованию**: Используйте название, описывающее связь, например "Project Assignment" или "Team Membership". Так модель данных становится более понятной.
 </Tip>
 
-## Шаг 2: Создайте связи между объектами и объектом-связкой
+## Шаг 2: Создайте связи из объекта-связки
 
-Добавьте поля связи из каждого из двух объектов в объект-связку.
+Добавьте поля связи из объекта-связки к обоим объектам, которые вы хотите соединить.
 
-### Первая связь (Объект A → Объект-связка)
-
-1. Выберите ваш первый объект в **Настройках → Модель данных**
-2. Нажмите **+ Добавить связь**
-3. Выберите объект-связку (например, "Назначения по проектам")
-4. Установите тип связи **Один-ко-многим** (один человек может быть связан со многими назначениями)
-5. Назовите поля:
-   * Поле в объекте Люди: например, "Project Assignments"
-   * Поле на объекте-связке: например, "Person"
-6. Нажмите **Сохранить**
-
-### Вторая связь (Объект B → Объект-связка)
-
-1. Выберите ваш второй объект в **Настройках → Модель данных**
-2. Нажмите **+ Добавить связь**
-3. Выберите объект-связку (например, "Назначения по проектам")
-4. Установите тип связи **Один-ко-многим** (один проект может быть связан со многими назначениями)
-5. Включите **"Это связь с объектом-связкой"**
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### Первая связь (Объект-связка → Объект A)
 
+1. Выберите ваш объект-связку в **Настройки → Модель данных**
+2. Нажмите **+ Добавить поле**
+3. Выберите тип поля **Связь**
+4. Выберите первый объект (например, "Люди")
+5. Установите тип связи **Многие-к-одному** (много назначений могут ссылаться на одного человека)
 6. Назовите поля:
+   * Поле на объекте-связке: например, "Person"
+   * Поле в объекте Люди: например, "Project Assignments"
+7. Нажмите **Сохранить**
+
+### Вторая связь (Объект-связка → Объект B)
+
+1. Оставаясь на объекте-связке, нажмите **+ Добавить поле**
+2. Выберите тип поля **Связь**
+3. Выберите второй объект (например, "Проекты")
+4. Установите тип связи **Многие-к-одному**
+5. Назовите поля:
    * Поле на объекте-связке: например, "Project"
    * Поле в объекте Проекты: например, "Team Members"
-7. Нажмите **Сохранить**
+6. Нажмите **Сохранить**
 
 ## Шаг 3: Настройте отображение связи через объект-связку
 
@@ -105,6 +98,18 @@ People ←→ Project Assignments ←→ Projects
 6. Выберите **Целевую связь** (например, "Project" — поле на объекте-связке, указывающее на другую сторону)
 7. Нажмите **Сохранить**
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Повторите для другого объекта:
+
+1. Выберите "Проекты" в Модели данных
+2. Отредактируйте поле связи "Team Members"
+3. Включите переключатель объекта-связки
+4. Выберите "Person" как целевую связь
+5. Сохранить
+
 ## Результат
 
 После настройки:
@@ -125,15 +130,15 @@ People ←→ Project Assignments ←→ Projects
 
 ### Добавьте связи
 
-1. **Люди → Назначение на проект**
-   * Тип: Один-ко-многим
-   * Поле в объекте Люди: "Project Assignments"
+1. **Project Assignment → Люди**
+   * Тип: Многие-к-одному
    * Поле в объекте Assignment: "Person"
+   * Поле в объекте Люди: "Project Assignments"
 
-2. **Проекты → Назначение на проект**
-   * Тип: Один-ко-многим
-   * Поле в объекте Проекты: "Team Members"
+2. **Project Assignment → Проекты**
+   * Тип: Многие-к-одному
    * Поле в объекте Assignment: "Project"
+   * Поле в объекте Проекты: "Team Members"
 
 ### Настройте отображение объекта-связки
 

packages/twenty-docs/l/ru/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ description: Настройте левую боковую панель под т
 ## Меню команд
 
 Нажмите `Cmd+K` (или `Ctrl+K`), чтобы открыть меню команд — строку быстрого поиска для перехода к любой записи, представлению или действию, не используя боковую панель.
-
-## Настройка боковой панели
-
-Чтобы настроить боковую панель, наведите курсор на раздел "Workspace" на боковой панели и нажмите значок гаечного ключа.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Значок редактирования навигации" />

packages/twenty-docs/l/ru/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Страницы записей
 description: Настройте макет отдельных страниц сведений о записях с вкладками и виджетами.
 ---
 
-## Обзор
-
 Когда вы открываете запись в Twenty, страница сведений состоит из **вкладок** и **виджетов**. Оба полностью настраиваются для каждого типа объекта.
 
 ## Вкладки
@@ -40,20 +38,12 @@ description: Настройте макет отдельных страниц с
 
 1. Откройте любую запись
 2. Нажмите `Cmd+K` и найдите "Изменить макет страницы записи"
-
-или
-
-1. Перейдите в Настройки > Модель данных > объект по вашему выбору > Макет
-
-2. Нажмите кнопку "Настроить страницу записи" для этого объекта
-
 3. Теперь вы в режиме настройки:
    * **Добавляйте виджеты** из списка виджетов
    * **Перетаскивайте виджеты**, чтобы изменить их положение на сетке
    * **Изменяйте размер виджетов**, перетаскивая их границы
    * **Настраивайте поля**, отображаемые в каждом виджете
    * **Управляйте вкладками** — добавляйте, удаляйте, переименовывайте, меняйте порядок
-
 4. Сохраните изменения — они применятся ко всем записям этого типа объекта
 
 ## Видимость полей

packages/twenty-docs/l/tr/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ Geliştirme modu yalnızca geliştirme ortamında (`NODE_ENV=development`) çal
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="Geliştirme modu terminal çıktısı" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="Geliştirme modu terminal çıktısı" />
 </div>
 
 #### Tek seferlik eşitleme `yarn twenty dev --once` ile
@@ -127,7 +127,13 @@ Tarayıcınızda [http://localhost:2020/settings/applications#developer](http://
 Yüklü uygulamayı görmek için **View installed app**'e tıklayın. **About** sekmesi, geçerli sürümü ve yönetim seçeneklerini gösterir:
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Yüklü uygulama" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="Yüklü uygulama — About sekmesi" />
+</div>
+
+Uygulamanızın sağladığı her şeyi — nesneler, alanlar, mantık işlevleri ve ajanlar — görmek için **Content** sekmesine geçin:
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="Yüklü uygulama — Content sekmesi" />
 </div>
 
 Her şey hazır! `src/` içindeki herhangi bir dosyayı düzenleyin; değişiklikler otomatik olarak alınacaktır.
@@ -207,49 +213,30 @@ npx create-twenty-app@latest my-twenty-app --example postcard
 
 İskelet oluşturucu sizin için zaten yerel bir Twenty sunucusu başlattı. Daha sonra yönetmek için `yarn twenty server` komutunu kullanın:
 
-| Komut                                  | Açıklama                                                              |
-| -------------------------------------- | --------------------------------------------------------------------- |
-| `yarn twenty server start`             | Yerel sunucuyu başlatır (gerekirse imajı çeker)                       |
-| `yarn twenty server start --port 3030` | Özel bir portta başlatır                                              |
-| `yarn twenty server start --test`      | 2021 numaralı bağlantı noktasında ayrı bir test örneği başlatın       |
-| `yarn twenty server stop`              | Sunucuyu durdurur (verileri korur)                                    |
-| `yarn twenty server status`            | Sunucu durumunu, URL'yi, sürümü ve kimlik bilgilerini gösterir        |
-| `yarn twenty server logs`              | Sunucu günlüklerini akış olarak iletir                                |
-| `yarn twenty server logs --lines 100`  | Son 100 günlük satırını gösterir                                      |
-| `yarn twenty server reset`             | Tüm verileri siler ve sıfırdan başlatır                               |
-| `yarn twenty server upgrade`           | En son `twenty-app-dev` imajını çeker ve konteyneri yeniden oluşturur |
-| `yarn twenty server upgrade 2.2.0`     | Belirli bir sürüme yükseltin                                          |
+| Komut                                  | Açıklama                                                        |
+| -------------------------------------- | --------------------------------------------------------------- |
+| `yarn twenty server start`             | Yerel sunucuyu başlatır (gerekirse imajı çeker)                 |
+| `yarn twenty server start --port 3030` | Özel bir portta başlatır                                        |
+| `yarn twenty server start --test`      | 2021 numaralı bağlantı noktasında ayrı bir test örneği başlatın |
+| `yarn twenty server stop`              | Sunucuyu durdurur (verileri korur)                              |
+| `yarn twenty server status`            | Sunucu durumunu, URL'yi ve kimlik bilgilerini gösterir          |
+| `yarn twenty server logs`              | Sunucu günlüklerini akış olarak iletir                          |
+| `yarn twenty server logs --lines 100`  | Son 100 günlük satırını gösterir                                |
+| `yarn twenty server reset`             | Tüm verileri siler ve sıfırdan başlatır                         |
 
 Veriler, yeniden başlatmalar arasında iki Docker biriminde kalıcıdır (PostgreSQL için `twenty-app-dev-data`, dosyalar için `twenty-app-dev-storage`). Her şeyi silip baştan başlamak için `reset` kullanın.
 
-### Sunucu imajını yükseltme
-
-Daha yeni bir `twenty-app-dev` Docker imajı olup olmadığını kontrol etmek ve konteyneri güncellemek için `yarn twenty server upgrade` komutunu kullanın. Komut imajı çeker, konteynerin oluşturulduğu imajla karşılaştırır ve imaj gerçekten değiştiyse yalnızca konteyneri yeniden oluşturur. Veri birimleriniz korunur — yalnızca konteyner değiştirilir.
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-Daha yeni bir imaj mevcutsa ve konteyner çalışıyorsa, yükseltme komutu güncellenmiş imajla yeni bir konteyneri otomatik olarak başlatır. Ardından sağlıklı hale gelmesini beklemek için `yarn twenty server start` komutunu çalıştırın. İmaj değişmediyse, konteyner olduğu gibi bırakılır.
-
-`yarn twenty server status` ile çalışan sürümü doğrulayabilirsiniz; bu komut, konteynerden `APP_VERSION` değerini görüntüler.
-
 ### Test örneği çalıştırma
 
 `server` komutlarının herhangi birine `--test` parametresini vererek ikinci, tamamen yalıtılmış bir örneği yönetin — entegrasyon testlerini çalıştırmak veya ana geliştirme verilerinize dokunmadan denemeler yapmak için kullanışlıdır.
 
-| Komut                               | Açıklama                                                               |
-| ----------------------------------- | ---------------------------------------------------------------------- |
-| `yarn twenty server start --test`   | Test örneğini başlatır (varsayılan bağlantı noktası 2021'dir)          |
-| `yarn twenty server stop --test`    | Test örneğini durdurur                                                 |
-| `yarn twenty server status --test`  | Test örneğinin durumunu, URL'yi, sürümü ve kimlik bilgilerini gösterir |
-| `yarn twenty server logs --test`    | Test örneği günlüklerini akış olarak iletir                            |
-| `yarn twenty server reset --test`   | Test verilerini siler ve sıfırdan başlatır                             |
-| `yarn twenty server upgrade --test` | Test örneğinin imajını yükseltin                                       |
+| Komut                              | Açıklama                                                       |
+| ---------------------------------- | -------------------------------------------------------------- |
+| `yarn twenty server start --test`  | Test örneğini başlatır (varsayılan bağlantı noktası 2021'dir)  |
+| `yarn twenty server stop --test`   | Test örneğini durdurur                                         |
+| `yarn twenty server status --test` | Test örneğinin durumunu, URL'yi ve kimlik bilgilerini gösterir |
+| `yarn twenty server logs --test`   | Test örneği günlüklerini akış olarak iletir                    |
+| `yarn twenty server reset --test`  | Test verilerini siler ve sıfırdan başlatır                     |
 
 Test örneği, kendine ait bir Docker konteynerinde (`twenty-app-dev-test`), ayrılmış birimlerle (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) ve yapılandırmayla çalışır; böylece ana örneğinizle çakışma olmadan paralel olarak çalışabilir. Varsayılan 2021'i geçersiz kılmak için `--test` ile `--port`'u birlikte kullanın.
 

packages/twenty-docs/l/tr/developers/extend/apps/logic-functions.mdx

@@ -95,16 +95,15 @@ const handler = async (event: RoutePayload) => {
 
 `RoutePayload` türünün yapısı şu şekildedir:
 
-  | Özellik                      | Tür                                                     | Açıklama                                                                                                                                                                                                             | Örnek                                                                      |
-  | ---------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | HTTP başlıkları (`forwardedRequestHeaders` içinde listelenenlerle sınırlı)                                                                                                                                           | aşağıdaki bölüme bakın                                                     |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Sorgu dizesi parametreleri (birden çok değer virgülle birleştirilir)                                                                                                                                                 | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | Rota deseninden çıkarılan yol parametreleri                                                                                                                                                                          | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
-  | `body`                       | `object \| null`                                        | Ayrıştırılmış istek gövdesi (JSON)                                                                                                                                                                                   | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | JSON ayrıştırılmadan önceki özgün UTF-8 istek gövdesi. HMAC tarzı webhook imzalarını doğrulamak için kullanışlıdır (ör. GitHub'ın `X-Hub-Signature-256`, Stripe). Çalışma zamanı onu korumadığında `undefined` olur. |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | Gövdenin base64 ile kodlanıp kodlanmadığı                                                                                                                                                                            |                                                                            |
-  | `requestContext.http.method` | `string`                                                | HTTP yöntemi (GET, POST, PUT, PATCH, DELETE)                                                                                                                                                                         |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | Ham istek yolu                                                                                                                                                                                                       |                                                                            |
+  | Özellik                      | Tür                                                     | Açıklama                                                                   | Örnek                                                                      |
+  | ---------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | HTTP başlıkları (`forwardedRequestHeaders` içinde listelenenlerle sınırlı) | aşağıdaki bölüme bakın                                                     |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | Sorgu dizesi parametreleri (birden çok değer virgülle birleştirilir)       | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | Rota deseninden çıkarılan yol parametreleri                                | `/users/:id`, `/users/123` -> `{ id: '123' }`                              |
+  | `body`                       | `object \| null`                                        | Ayrıştırılmış istek gövdesi (JSON)                                         | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | Gövdenin base64 ile kodlanıp kodlanmadığı                                  |                                                                            |
+  | `requestContext.http.method` | `string`                                                | HTTP yöntemi (GET, POST, PUT, PATCH, DELETE)                               |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | Ham istek yolu                                                             |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/tr/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ Büyümeye hazır ekipler için:
 * Standart destek
 
 <Note>
-Premium özellikler (SSO, satır düzeyi izinler ve Yapay Zeka kullanım verileri) Pro plana dahil değildir.
+Premium özellikler (SSO ve satır düzeyi izinler) Pro planına dahil değildir.
 </Note>
 
 ### Kuruluş (Bulut)
@@ -27,7 +27,7 @@ Premium özellikler (SSO, satır düzeyi izinler ve Yapay Zeka kullanım veriler
 Gelişmiş ihtiyaçları olan daha büyük ekipler için:
 
 * Pro'daki her şey
-* **Premium özellikler**: SSO entegrasyonu, satır düzeyi izinler ve Yapay Zeka kullanım verileri
+* **Premium özellikler**: SSO entegrasyonu ve satır düzeyi izinler
 * Öncelikli destek
 
 ## Kendi Kendine Barındırılan Planlar
@@ -45,7 +45,7 @@ Twenty'yi kendi altyapınızda hiçbir ücret ödemeden barındırın:
 Kendi kendine barındırma yaparken premium özelliklere ihtiyaç duyan ekipler için:
 
 * Tüm Pro özellikleri
-* **Premium özellikler**: SSO entegrasyonu, satır düzeyi izinler ve Yapay Zeka kullanım verileri
+* **Premium özellikler**: SSO entegrasyonu ve satır düzeyi izinler
 * Twenty ekibinden destek
 * Dağıtmadan önce özel kodu açık kaynak olarak yayınlama zorunluluğu yoktur.
 
@@ -55,7 +55,6 @@ Premium özellikler yalnızca Kuruluş planlarında (Bulut veya Kendi Kendine Ba
 
 * **SSO entegrasyonu**: Kimlik sağlayıcınızla Tek Oturum Açma
 * **Satır düzeyi izinler**: Kayıt düzeyinde ayrıntılı erişim denetimi
-* **Yapay Zeka kullanım verileri**: Çalışma alanı genelinde Yapay Zeka tüketimini takip edin
 
 ## Planlar Arasında Geçiş
 
@@ -78,15 +77,3 @@ Planınızı düşürmek için destek ekibiyle iletişime geçin.
 ### Aylığa Geçiş Yap
 
 Aylık faturalamaya geri dönmek için destek ekibiyle iletişime geçin.
-
-## Organizasyon (Kendi Sunucunuzda Barındırılan) için Kurumsal Anahtar edinin
-
-Organizasyon (Kendi Sunucunuzda Barındırılan) planını kullanmak için bir Kurumsal Anahtar edinmeniz gerekir:
-
-1. **Ayarlar → Yönetici Paneli → Kurumsal** bölümüne gidin
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="Kurumsal Anahtar" />
-
-2. **Kurumsal Anahtar Alın**'ı tıklayın
-3. Stripe'a yönlendirildiğinizde ödeme bilgilerinizi girin ve onaylayın
-4. Kurumsal anahtarınız görüntülendiğinde, bunu Kurumsal ayarlar sayfasına yapıştırın ve Organizasyon lisansını etkinleştirin

packages/twenty-docs/l/tr/user-guide/billing/how-tos/billing-faq.mdx

@@ -16,11 +16,6 @@ Kendiniz barındırmak istiyor ve Premium özelliklere (SSO ve satır düzeyi iz
 Premium özellikler yalnızca Kuruluş planlarında (Bulut veya Kendi Barındırmalı) kullanılabilir:
 * **SSO entegrasyonu**: Kimlik sağlayıcınızla Tek Oturum Açma
 * **Satır düzeyi izinler**: Kayıt düzeyinde ayrıntılı erişim denetimi
-* **Yapay Zeka kullanım verileri**: Çalışma alanı genelinde Yapay Zeka tüketimini takip edin
-</Accordion>
-
-<Accordion title="Buluttaki Organization planı ile kendi barındırmalı ortamdaki Organization planı aynı mı?">
-İkisi de aynı Premium özellikleri sunar. Ancak bulut aboneliği, kendi barındırmalı dağıtımlarda kullanılamaz. Kendi barındırmalı kurulumlar için bir Enterprise anahtarı gerekir.
 </Accordion>
 
 <Accordion title="Salt görüntüleme kullanıcıları için ücretsiz koltuklar sunuyor musunuz?">

packages/twenty-docs/l/tr/user-guide/data-model/how-tos/create-many-to-many-relations.mdx

@@ -53,45 +53,38 @@ Bağlantı ilişkisi anahtarını etkinleştirdiğinizde, Twenty aradaki bağlan
 1. **Ayarlar → Veri Modeli** bölümüne gidin
 2. **+ Yeni nesne**'ye tıklayın
 3. Açıklayıcı bir ad verin (örn. "Project Assignment", "Team Member", "Product Order")
-4. "Ad alanı oluşturmayı atla" seçeneğini açın
-
-<img src="/images/user-guide/fields/new-pivot-object.png" alt="Yeni pivot nesnesi" />
-
-5. **Kaydet**'e tıklayın
+4. **Kaydet**'e tıklayın
 
 <Tip>
 **Adlandırma kuralı**: "Project Assignment" veya "Team Membership" gibi ilişkiyi tanımlayan bir ad kullanın. Bu, veri modelinin anlaşılmasını kolaylaştırır.
 </Tip>
 
-## Adım 2: Nesneler ile Bağlantı nesnesi arasında ilişkiler oluşturun
+## Adım 2: Bağlantı Nesnesinden İlişkiler Oluşturun
 
-İki nesnenizin her birinden bağlantı nesnesine ilişki alanları ekleyin.
+Bağlamak istediğiniz her iki nesneye de bağlantı nesnesinden ilişki alanları ekleyin.
 
-### İlk İlişki (Nesne A → Bağlantı)
-
-1. İlk nesnenizi **Ayarlar → Veri Modeli**'nde seçin
-2. **+ İlişki Ekle**'ye tıklayın
-3. Bağlantı nesnesini seçin (örn. "Project Assignments")
-4. İlişki türünü **Birden-Çoğa** olarak ayarlayın (bir kişi birçok atamaya bağlanabilir)
-5. Alanları adlandırın:
-   * People üzerindeki alan: örn. "Project Assignments"
-   * Bağlantı üzerindeki alan: örn. "Person"
-6. **Kaydet**'e tıklayın
-
-### İkinci İlişki (Nesne B → Bağlantı)
-
-1. İkinci nesnenizi **Ayarlar → Veri Modeli**'nde seçin
-2. **+ İlişki Ekle**'ye tıklayın
-3. Bağlantı nesnesini seçin (örn. "Project Assignments")
-4. İlişki türünü **Birden-Çoğa** olarak ayarlayın (bir proje birçok atamaya bağlanabilir)
-5. **"Bu, bir bağlantı nesnesine kurulan bir ilişkidir"** seçeneğini etkinleştirin
-
-<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />
+### İlk İlişki (Bağlantı → Nesne A)
 
+1. **Ayarlar → Veri Modeli**'nde bağlantı nesnenizi seçin
+2. **+ Alan Ekle**'ye tıklayın
+3. Alan türü olarak **İlişki**'yi seçin
+4. İlk nesneyi seçin (örn. "People")
+5. İlişki türünü **Çoktan-Bire** olarak ayarlayın (birçok atama bir kişiye bağlanabilir)
 6. Alanları adlandırın:
+   * Bağlantı üzerindeki alan: örn. "Person"
+   * People üzerindeki alan: örn. "Project Assignments"
+7. **Kaydet**'e tıklayın
+
+### İkinci İlişki (Bağlantı → Nesne B)
+
+1. Hâlâ bağlantı nesnesindeyken, **+ Add Field**'e tıklayın
+2. Alan türü olarak **İlişki**'yi seçin
+3. İkinci nesneyi seçin (örn. "Projects")
+4. İlişki türünü **Çoktan-Bire** olarak ayarlayın
+5. Alanları adlandırın:
    * Bağlantı üzerindeki alan: örn. "Project"
    * Projects üzerindeki alan: örn. "Team Members"
-7. **Kaydet**'e tıklayın
+6. **Kaydet**'e tıklayın
 
 ## Adım 3: Bağlantı İlişkisi Görüntüsünü Yapılandırın
 
@@ -105,6 +98,18 @@ Bağlantı ilişkisi anahtarını etkinleştirdiğinizde, Twenty aradaki bağlan
 6. **Hedef ilişki**yi seçin (örn. "Project" — bağlantı üzerindeki, diğer tarafı işaret eden alan)
 7. **Kaydet**'e tıklayın
 
+{/* TODO: Add image
+<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}}/>
+*/}
+
+Diğer nesne için tekrarlayın:
+
+1. Veri Modeli'nde "Projects"i seçin
+2. "Team Members" ilişki alanını düzenleyin
+3. Bağlantı anahtarını etkinleştirin
+4. Hedef ilişki olarak "Person"ı seçin
+5. Kaydet
+
 ## Sonuç
 
 Yapılandırmadan sonra:
@@ -125,15 +130,15 @@ Bağlantı nesnesi hâlâ mevcuttur ve bağlantıları saklar, ancak kullanıcı
 
 ### İlişkiler Ekleyin
 
-1. **People → Project Assignment**
-   * Tür: Birden-Çoğa
-   * People üzerindeki alan: "Project Assignments"
+1. **Project Assignment → People**
+   * Tür: Çoktan-Bire
    * Assignment üzerindeki alan: "Person"
+   * People üzerindeki alan: "Project Assignments"
 
-2. **Projects → Project Assignment**
-   * Tür: Birden-Çoğa
-   * Projects üzerindeki alan: "Team Members"
+2. **Project Assignment → Projects**
+   * Tür: Çoktan-Bire
    * Assignment üzerindeki alan: "Project"
+   * Projects üzerindeki alan: "Team Members"
 
 ### Bağlantı Görüntüsünü Yapılandırın
 

packages/twenty-docs/l/tr/user-guide/layout/capabilities/navigation.mdx

@@ -30,9 +30,3 @@ Harici araçlara yönelik bağlantıları doğrudan kenar çubuğuna ekleyin. Wi
 ## Komut Menüsü
 
 Komut menüsünü açmak için `Cmd+K` (veya `Ctrl+K`) tuşlarına basın — kenar çubuğunda gezinmeden herhangi bir kayda, görünüme veya eyleme atlamak için hızlı erişim sunan bir arama çubuğu.
-
-## Kenar Çubuğunu Özelleştirme
-
-Kenar çubuğunu özelleştirmek için kenar çubuğundaki "Workspace" bölümünün üzerine gelin ve anahtar simgesine tıklayın.
-
-<img src="/images/user-guide/layout/navigation-edit-icon.png" alt="Gezinti düzenleme simgesi" />

packages/twenty-docs/l/tr/user-guide/layout/capabilities/record-pages.mdx

@@ -3,8 +3,6 @@ title: Kayıt Sayfaları
 description: Her bir kayıt ayrıntı sayfasının düzenini sekmeler ve widget'larla özelleştirin.
 ---
 
-## Genel Bakış
-
 Twenty'de bir kaydı açtığınızda, ayrıntı sayfası **sekmeler** ve **widget'lar** içerir. Her ikisi de her nesne türü bazında tamamen özelleştirilebilir.
 
 ## Sekmeler
@@ -40,20 +38,12 @@ Widget'lar, her sekmenin içindeki yapı taşlarıdır. Kullanılabilir widget t
 
 1. Herhangi bir kaydı açın
 2. `Cmd+K` tuşlarına basın ve "Kayıt sayfası yerleşimini düzenle" ifadesini arayın
-
-veya
-
-1. Ayarlar > Veri modeli > seçtiğiniz nesne > Düzen'e gidin
-
-2. O nesne için "Kayıt sayfasını özelleştir" düğmesine tıklayın
-
 3. Artık özelleştirme modundasınız:
    * **Widget ekleyin** widget seçicisinden
    * **Widget'ları sürükleyin** ve ızgara üzerinde yeniden konumlandırın
    * **Widget'ları yeniden boyutlandırın** kenarlarını sürükleyerek
    * **Alanları yapılandırın** — her bir widget içinde gösterilen
    * **Sekmeleri yönetin** — ekleyin, kaldırın, yeniden adlandırın, yeniden sıralayın
-
 4. Değişikliklerinizi kaydedin — bu değişiklikler o nesne türündeki tüm kayıtlara uygulanır
 
 ## Alan görünürlüğü

packages/twenty-docs/l/zh/developers/extend/apps/data-model.mdx

@@ -77,6 +77,7 @@ export default defineApplication({
   universalIdentifier: '39783023-bcac-41e3-b0d2-ff1944d8465d',
   displayName: 'My Twenty App',
   description: 'My first Twenty app',
+  icon: 'IconWorld',
   applicationVariables: {
     DEFAULT_RECIPIENT_NAME: {
       universalIdentifier: '19e94e59-d4fe-4251-8981-b96d0a9f74de',

packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx

@@ -92,7 +92,7 @@ yarn twenty dev --verbose
 </Warning>
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/dev.png" alt="开发模式终端输出" />
+  <img src="/images/docs/developers/extends/apps/dev.jpg" alt="开发模式终端输出" />
 </div>
 
 #### 使用 `yarn twenty dev --once` 进行一次性同步
@@ -127,7 +127,13 @@ yarn twenty dev --once
 点击 **查看已安装的应用** 以查看已安装的应用。 **关于** 选项卡显示当前版本和管理选项：
 
 <div style={{textAlign: 'center'}}>
-  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="已安装的应用" />
+  <img src="/images/docs/developers/extends/apps/app-in-ui-3.png" alt="已安装的应用 — “关于”选项卡" />
+</div>
+
+切换到 **内容** 选项卡，以查看你的应用提供的全部内容——对象、字段、逻辑函数和智能体：
+
+<div style={{textAlign: 'center'}}>
+  <img src="/images/docs/developers/extends/apps/app-in-ui-4.png" alt="已安装的应用 — “内容”选项卡" />
 </div>
 
 一切就绪！ 编辑 `src/` 中的任意文件，更改会被自动检测到。
@@ -207,49 +213,30 @@ npx create-twenty-app@latest my-twenty-app --example postcard
 
 脚手架工具已经为你启动了一个本地 Twenty 服务器。 稍后要进行管理，请使用 `yarn twenty server`：
 
-| 命令                                     | 描述                               |
-| -------------------------------------- | -------------------------------- |
-| `yarn twenty server start`             | 启动本地服务器（按需拉取镜像）                  |
-| `yarn twenty server start --port 3030` | 在自定义端口启动                         |
-| `yarn twenty server start --test`      | 在 2021 端口启动一个独立的测试实例             |
-| `yarn twenty server stop`              | 停止服务器（保留数据）                      |
-| `yarn twenty server status`            | 显示服务器状态、URL、版本和凭据                |
-| `yarn twenty server logs`              | 流式输出服务器日志                        |
-| `yarn twenty server logs --lines 100`  | 显示最近 100 行日志                     |
-| `yarn twenty server reset`             | 删除所有数据并全新开始                      |
-| `yarn twenty server upgrade`           | 拉取最新的 `twenty-app-dev` 镜像并重新创建容器 |
-| `yarn twenty server upgrade 2.2.0`     | 升级到指定版本                          |
+| 命令                                     | 描述                   |
+| -------------------------------------- | -------------------- |
+| `yarn twenty server start`             | 启动本地服务器（按需拉取镜像）      |
+| `yarn twenty server start --port 3030` | 在自定义端口启动             |
+| `yarn twenty server start --test`      | 在 2021 端口启动一个独立的测试实例 |
+| `yarn twenty server stop`              | 停止服务器（保留数据）          |
+| `yarn twenty server status`            | 显示服务器状态、URL 和凭据      |
+| `yarn twenty server logs`              | 流式输出服务器日志            |
+| `yarn twenty server logs --lines 100`  | 显示最近 100 行日志         |
+| `yarn twenty server reset`             | 删除所有数据并全新开始          |
 
 数据在重启后会保留，存储于两个 Docker 卷中（`twenty-app-dev-data` 用于 PostgreSQL，`twenty-app-dev-storage` 用于文件）。 使用 `reset` 清空所有内容并重新开始。
 
-### 升级服务器镜像
-
-使用 `yarn twenty server upgrade` 来检查是否有更新的 `twenty-app-dev` Docker 镜像并更新容器。 该命令会拉取镜像，与容器创建时所用的镜像进行比较，仅当镜像确实发生变化时才会重新创建容器。 您的数据卷将被保留——只会替换容器。
-
-```bash filename="Terminal"
-# Upgrade to the latest version (skips recreation if already up to date)
-yarn twenty server upgrade
-
-# Upgrade to a specific version
-yarn twenty server upgrade 2.2.0
-```
-
-如果有可用的新镜像且容器正在运行，升级命令会使用更新后的镜像自动启动一个新容器。 随后运行 `yarn twenty server start`，等待其变为健康状态。 如果镜像没有变化，容器将保持不变。
-
-您可以使用 `yarn twenty server status` 验证正在运行的版本，该命令会显示容器中的 `APP_VERSION`。
-
 ### 运行测试实例
 
 向任何 `server` 命令传递 `--test` 以管理第二个、完全隔离的实例——这对于运行集成测试或在不影响主开发数据的情况下进行试验非常有用。
 
-| 命令                                  | 描述                  |
-| ----------------------------------- | ------------------- |
-| `yarn twenty server start --test`   | 启动测试实例 (默认端口为 2021) |
-| `yarn twenty server stop --test`    | 停止测试实例              |
-| `yarn twenty server status --test`  | 显示测试实例状态、URL、版本和凭据  |
-| `yarn twenty server logs --test`    | 流式输出测试实例日志          |
-| `yarn twenty server reset --test`   | 清除测试数据并全新开始         |
-| `yarn twenty server upgrade --test` | 升级测试实例镜像            |
+| 命令                                 | 描述                  |
+| ---------------------------------- | ------------------- |
+| `yarn twenty server start --test`  | 启动测试实例 (默认端口为 2021) |
+| `yarn twenty server stop --test`   | 停止测试实例              |
+| `yarn twenty server status --test` | 显示测试实例状态、URL 和凭据    |
+| `yarn twenty server logs --test`   | 流式输出测试实例日志          |
+| `yarn twenty server reset --test`  | 清除测试数据并全新开始         |
 
 测试实例在其独立的 Docker 容器 (`twenty-app-dev-test`) 中运行，配有专用的卷 (`twenty-app-dev-test-data`, `twenty-app-dev-test-storage`) 和配置，因此可以与主实例并行运行且不会发生冲突。 将 `--test` 与 `--port` 一起使用以覆盖默认的 2021 端口。
 

packages/twenty-docs/l/zh/developers/extend/apps/logic-functions.mdx

@@ -95,16 +95,15 @@ const handler = async (event: RoutePayload) => {
 
 `RoutePayload` 类型具有以下结构：
 
-  | 属性                           | 类型                                                      | 描述                                                                                                                    | 示例                                                                         |
-  | ---------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
-  | `headers`                    | `Record\<string, string \| undefined>` | HTTP 请求头（仅限 `forwardedRequestHeaders` 中列出的那些）                                                                         | 见下文                                                                        |
-  | `queryStringParameters`      | `Record\<string, string \| undefined>` | 查询字符串参数（多个值以逗号连接）                                                                                                     | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
-  | `pathParameters`             | `Record\<string, string \| undefined>` | 从路由模式中提取的路径参数                                                                                                         | `/users/:id`，`/users/123` -> `{ id: '123' }`                               |
-  | `body`                       | `object \| null`                                        | 已解析的请求体（JSON）                                                                                                         | `{ id: 1 }` -> `{ id: 1 }`                                                 |
-  | `rawBody`                    | `string \| undefined`                                   | 在 JSON 解析之前的原始 UTF-8 请求体。 用于验证 HMAC 风格的 Webhook 签名（例如 GitHub 的 `X-Hub-Signature-256`、Stripe）。 当运行时未保留它时为 `undefined`。 |                                                                            |
-  | `isBase64Encoded`            | `boolean`                                               | 请求体是否为 base64 编码                                                                                                      |                                                                            |
-  | `requestContext.http.method` | `string`                                                | HTTP 方法（GET、POST、PUT、PATCH、DELETE）                                                                                    |                                                                            |
-  | `requestContext.http.path`   | `string`                                                | 原始请求路径                                                                                                                |                                                                            |
+  | 属性                           | 类型                                                      | 描述                                            | 示例                                                                         |
+  | ---------------------------- | ------------------------------------------------------- | --------------------------------------------- | -------------------------------------------------------------------------- |
+  | `headers`                    | `Record\<string, string \| undefined>` | HTTP 请求头（仅限 `forwardedRequestHeaders` 中列出的那些） | 见下文                                                                        |
+  | `queryStringParameters`      | `Record\<string, string \| undefined>` | 查询字符串参数（多个值以逗号连接）                             | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |
+  | `pathParameters`             | `Record\<string, string \| undefined>` | 从路由模式中提取的路径参数                                 | `/users/:id`，`/users/123` -> `{ id: '123' }`                               |
+  | `body`                       | `object \| null`                                        | 已解析的请求体（JSON）                                 | `{ id: 1 }` -> `{ id: 1 }`                                                 |
+  | `isBase64Encoded`            | `boolean`                                               | 请求体是否为 base64 编码                              |                                                                            |
+  | `requestContext.http.method` | `string`                                                | HTTP 方法（GET、POST、PUT、PATCH、DELETE）            |                                                                            |
+  | `requestContext.http.path`   | `string`                                                | 原始请求路径                                        |                                                                            |
 
 
 #### forwardedRequestHeaders

packages/twenty-docs/l/zh/user-guide/billing/capabilities/pricing-plans.mdx

@@ -19,7 +19,7 @@ description: 了解 Twenty 的定价方案以及如何在它们之间切换。
 * 标准支持
 
 <Note>
-Pro 方案不包含高级功能（SSO、行级权限和 AI 使用数据）。
+Pro 计划不包含高级功能（SSO 和行级权限）。
 </Note>
 
 ### 组织计划（云端）
@@ -27,7 +27,7 @@ Pro 方案不包含高级功能（SSO、行级权限和 AI 使用数据）。
 适用于具有高级需求的大型团队：
 
 * 包含 Pro 的全部内容
-* **高级功能**：SSO 集成、行级权限和 AI 使用数据
+* **高级功能**：SSO 集成和行级权限
 * 优先支持
 
 ## 自托管方案
@@ -45,7 +45,7 @@ Pro 方案不包含高级功能（SSO、行级权限和 AI 使用数据）。
 适用于在自托管同时需要高级功能的团队：
 
 * 所有 Pro 功能
-* **高级功能**：SSO 集成、行级权限和 AI 使用数据
+* **高级功能**：SSO 集成和行级权限
 * Twenty 团队支持
 * 分发前无需将自定义代码开源
 
@@ -55,7 +55,6 @@ Pro 方案不包含高级功能（SSO、行级权限和 AI 使用数据）。
 
 * **SSO 集成**：与您的身份提供商进行单点登录
 * **行级权限**：在记录级别进行细粒度访问控制
-* **AI 使用数据**：在整个工作区跟踪 AI 消耗
 
 ## 切换计划
 
@@ -78,15 +77,3 @@ Pro 方案不包含高级功能（SSO、行级权限和 AI 使用数据）。
 ### 切换为按月计费
 
 联系支持以切换回按月计费。
-
-## 为 Organization (Self-Hosted) 获取企业密钥
-
-要使用 Organization (Self-Hosted) 方案，您需要获取企业密钥：
-
-1. 转到 **设置 → 管理员面板 → 企业版**
-
-<img src="/images/user-guide/billing/enterprise-key.png" alt="企业密钥" />
-
-2. 单击 **获取企业密钥**
-3. 当您被重定向到 Stripe 时，输入您的付款信息并确认
-4. 当显示出您的企业密钥时，将其粘贴到企业版设置页面并激活 Organization 许可证