fix

.cursor/Dockerfile

@@ -1,34 +0,0 @@
-FROM ubuntu:22.04
-
-ENV DEBIAN_FRONTEND=noninteractive
-
-RUN apt-get update && apt-get install -y \
-    curl \
-    git \
-    make \
-    build-essential \
-    postgresql-client \
-    docker.io \
-    && rm -rf /var/lib/apt/lists/*
-
-# Install nvm (project recommends nvm + .nvmrc for consistent Node versions)
-ENV NVM_DIR=/usr/local/nvm
-RUN mkdir -p $NVM_DIR \
-    && curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash
-
-SHELL ["/bin/bash", "-c"]
-
-# Copy .nvmrc so nvm install picks up the right version
-COPY .nvmrc /tmp/.nvmrc
-
-# Install Node.js from .nvmrc, enable Corepack, and symlink binaries
-# so they're available on PATH without hardcoding a version
-RUN . $NVM_DIR/nvm.sh \
-    && nvm install $(cat /tmp/.nvmrc) \
-    && nvm alias default $(cat /tmp/.nvmrc) \
-    && corepack enable \
-    && BIN_DIR=$(dirname $(nvm which default)) \
-    && ln -sf $BIN_DIR/node /usr/local/bin/node \
-    && ln -sf $BIN_DIR/npm /usr/local/bin/npm \
-    && ln -sf $BIN_DIR/npx /usr/local/bin/npx \
-    && ln -sf $BIN_DIR/corepack /usr/local/bin/corepack

.cursor/environment.json

@@ -1,10 +1,18 @@
 {
-  "install": "yarn install",
-  "start": "sudo service docker start && sleep 2 && (docker start twenty_pg 2>/dev/null || make -C packages/twenty-docker postgres-on-docker) && (docker start twenty_redis 2>/dev/null || make -C packages/twenty-docker redis-on-docker) && until docker exec twenty_pg pg_isready -U postgres -h localhost 2>/dev/null; do sleep 1; done && echo 'PostgreSQL ready' && until docker exec twenty_redis redis-cli ping 2>/dev/null | grep -q PONG; do sleep 1; done && echo 'Redis ready' && bash packages/twenty-utils/setup-dev-env.sh && npx nx database:reset twenty-server",
+  "install": "curl -fsSL https://deb.nodesource.com/setup_24.x | sudo -E bash - && sudo apt-get install -y nodejs && node --version && yarn install && echo 'Installing dependencies complete'",
+  "start": "sudo service docker start && echo 'Docker service started' && sleep 3 && echo 'Starting PostgreSQL and Redis containers...' && make postgres-on-docker && make redis-on-docker && echo 'Waiting for containers to initialize...' && sleep 20 && echo 'Checking container status...' && docker ps --filter name=twenty_ && echo 'Waiting for PostgreSQL to be ready...' && until docker exec twenty_pg pg_isready -U postgres -h localhost; do echo 'PostgreSQL not ready yet, waiting...'; sleep 3; done && echo 'PostgreSQL is ready!' && echo 'Setting up database...' && cd packages/twenty-server && npx nx database:reset twenty-server || echo 'Database already initialized' && echo 'Environment setup complete!'",
   "terminals": [
     {
       "name": "Development Server",
-      "command": "yarn start"
+      "command": "echo 'Waiting for database to be fully ready...' && sleep 30 && until docker exec twenty_pg pg_isready -U postgres -h localhost; do echo 'Waiting for PostgreSQL...'; sleep 2; done && echo 'Starting Twenty development server...' && export SERVER_URL=http://localhost:3000 && export PG_DATABASE_URL=postgres://postgres:postgres@localhost:5432/postgres && yarn start"
+    },
+    {
+      "name": "Database Management",
+      "command": "sleep 25 && echo 'Database management terminal ready' && echo 'Waiting for PostgreSQL to be available...' && until docker exec twenty_pg pg_isready -U postgres -h localhost; do echo 'Waiting for PostgreSQL...'; sleep 2; done && echo 'PostgreSQL is ready for database operations!' && echo 'You can now run database commands like:' && echo '  npx nx database:reset twenty-server' && echo '  npx nx database:migrate twenty-server' && bash"
+    },
+    {
+      "name": "Container Logs & Status",
+      "command": "sleep 10 && echo '=== Container Status Monitor ===' && while true; do echo '\\n=== Container Status at $(date) ===' && docker ps --filter name=twenty_ --format 'table {{.Names}}\\t{{.Status}}\\t{{.Ports}}' && echo '\\n=== PostgreSQL Status ===' && (docker exec twenty_pg pg_isready -U postgres -h localhost && echo 'PostgreSQL: ✅ Ready') || echo 'PostgreSQL: ❌ Not Ready' && echo '\\n=== Redis Status ===' && (docker exec twenty_redis redis-cli ping && echo 'Redis: ✅ Ready') || echo 'Redis: ❌ Not Ready' && sleep 30; done"
     }
   ]
-}
+} 

.cursor/rules/README.mdc

@@ -12,8 +12,6 @@ This directory contains Twenty's development guidelines and best practices in th
 ### Core Guidelines
 - **architecture.mdc** - Project overview, technology stack, and infrastructure setup (Always Applied)
 - **nx-rules.mdc** - Nx workspace guidelines and best practices (Auto-attached to Nx files)
-- **server-migrations.mdc** - Backend migration and TypeORM guidelines for `twenty-server` (Auto-attached to server entities and migration files)
-- **creating-syncable-entity.mdc** - Comprehensive guide for creating new syncable entities (with universalIdentifier and applicationId) in the workspace migration system (Agent-requested for metadata-modules and workspace-migration files)
 
 ### Code Quality
 - **typescript-guidelines.mdc** - TypeScript best practices and conventions (Auto-attached to .ts/.tsx files)
@@ -22,7 +20,7 @@ This directory contains Twenty's development guidelines and best practices in th
 
 ### React Development
 - **react-general-guidelines.mdc** - Core React development principles (Auto-attached to React files)
-- **react-state-management.mdc** - State management approaches with Jotai (Auto-attached to state files)
+- **react-state-management.mdc** - State management approaches with Recoil (Auto-attached to state files)
 
 ### Testing & Quality
 - **testing-guidelines.mdc** - Testing strategies and best practices (Auto-attached to test files)
@@ -40,10 +38,9 @@ You can manually reference any rule using the `@ruleName` syntax:
 - `@nx-rules` - Include Nx-specific guidance
 - `@react-general-guidelines` - Load React best practices
 - `@testing-guidelines` - Get testing recommendations
-- `@creating-syncable-entity` - Guide for creating new syncable entities
 
 ### Rule Types Used
-- **Always Applied** - Loaded in every context (architecture.mdc, README.mdc)
+- **Always Applied** - Loaded in every context (architecture.mdc, README.mdc)  
 - **Auto Attached** - Loaded when matching file patterns are referenced
 - **Agent Requested** - Available for AI to include when relevant
 - **Manual** - Only included when explicitly mentioned
@@ -55,12 +52,10 @@ You can manually reference any rule using the `@ruleName` syntax:
 # Testing
 npx nx test twenty-front                    # Run unit tests
 npx nx storybook:build twenty-front         # Build Storybook
-npx nx storybook:test                       # Run Storybook tests
+npx nx storybook:serve-and-test:static     # Run Storybook tests
 
 # Development
-npx nx lint:diff-with-main twenty-front            # Lint files changed vs main (fastest)
-npx nx lint:diff-with-main twenty-front --configuration=fix  # Auto-fix changed files
-npx nx lint twenty-front                    # Lint all files (slower)
+npx nx lint twenty-front                    # Run linter
 npx nx typecheck twenty-front               # Type checking
 npx nx run twenty-front:graphql:generate    # Generate GraphQL types
 ```
@@ -74,9 +69,7 @@ npx nx run twenty-server:database:migrate:prod # Run migrations
 
 # Development
 npx nx run twenty-server:start             # Start the server
-npx nx lint:diff-with-main twenty-server          # Lint files changed vs main (fastest)
-npx nx lint:diff-with-main twenty-server --configuration=fix  # Auto-fix changed files
-npx nx run twenty-server:lint              # Lint all files (slower)
+npx nx run twenty-server:lint              # Run linter (add --fix to auto-fix)
 npx nx run twenty-server:typecheck         # Type checking
 npx nx run twenty-server:test              # Run unit tests
 npx nx run twenty-server:test:integration:with-db-reset # Run integration tests

.cursor/rules/architecture.mdc

@@ -7,7 +7,7 @@ alwaysApply: true
 # Twenty Architecture
 
 ## Tech Stack
-- **Frontend**: React 18, TypeScript, Jotai, Styled Components, Vite
+- **Frontend**: React 18, TypeScript, Recoil, Styled Components, Vite
 - **Backend**: NestJS, TypeORM, PostgreSQL, Redis, GraphQL
 - **Monorepo**: Nx workspace with yarn
 

.cursor/rules/changelog-process.mdc

@@ -1,324 +0,0 @@
----
-description: Process and guidelines for creating release changelogs for Twenty CRM
-globs: ["**/releases/*.mdx", "**/releases/**"]
-alwaysApply: false
----
-# Twenty Release Changelog Process
-
-Complete guide for creating release changelogs, including codebase research, file structure, and content guidelines.
-
-## Prerequisites
-
-Before starting, gather the following information:
-
-### Required Information
-
-**Version Number**: `{VERSION}` (e.g., 1.9.0, 2.0.0, 2.1.0)
-
-**Release Date**: Use today's date in format: YYYY-MM-DD
-
-### Changes/Features to Document
-
-List the features and changes to include in this release:
-
-1. **Feature Name**: ______________________________
-   - Brief description: ______________________________
-   - Related area (workflow, UI, backend, etc.): ______________________________
-
-2. **Feature Name**: ______________________________
-   - Brief description: ______________________________
-   - Related area: ______________________________
-
-3. **Feature Name**: ______________________________
-   - Brief description: ______________________________
-   - Related area: ______________________________
-
-## Codebase Research Guide
-
-If feature descriptions are not provided or need enhancement, research the codebase:
-
-### Where to Look
-
-**For Workflow Features:**
-- Frontend: `packages/twenty-front/src/modules/workflow/`
-- Backend: `packages/twenty-server/src/modules/workflow/`
-- Components: `packages/twenty-front/src/modules/workflow/components/`
-
-**For UI/UX Changes:**
-- Components: `packages/twenty-front/src/modules/ui/`
-- Layout: `packages/twenty-front/src/modules/layout/`
-- Design system: `packages/twenty-ui/src/`
-
-**For Backend/API Features:**
-- Server modules: `packages/twenty-server/src/modules/`
-- Entities: `packages/twenty-server/src/entities/`
-- Services: Look for `*.service.ts` files
-
-**For Database/ORM Changes:**
-- Migrations: `packages/twenty-server/src/database/typeorm/`
-- Entities: `packages/twenty-server/src/entities/`
-
-### Research Commands
-
-```bash
-# Find recent merged PRs (adjust date as needed)
-gh pr list --search "merged:>2025-10-01" --limit 50 --state merged
-
-# View recent commits
-git log --since="2 weeks ago" --oneline --no-merges
-
-# View commits between releases (replace with actual release tags)
-git log v1.7.0..v1.8.0 --oneline
-
-# Search for specific feature keywords in code
-grep -r "iterator" packages/twenty-front/src/modules/workflow/
-grep -r "bulk select" packages/twenty-front/src/modules/workflow/
-
-# Find recent changes in specific directory
-git log --since="2 weeks ago" --oneline -- packages/twenty-front/src/modules/workflow/
-```
-
-### Using Codebase Search
-
-Use the AI codebase search to find:
-- "How does the workflow iterator node work?"
-- "Where is bulk select implemented for workflows?"
-- "What changes were made to the search node limit?"
-
-## Step-by-Step Process
-
-### 1. Setup Git Branch
-
-**IMPORTANT**: Always start from an up-to-date main branch to avoid merge conflicts and ensure the changelog is based on the latest code.
-
-```bash
-cd /Users/thomascolasdesfrancs/code/twenty
-git checkout main
-git pull origin main
-git checkout -b {VERSION}
-```
-
-Replace `{VERSION}` with the actual version number (e.g., `1.9.0`)
-
-⚠️ **Do this first** before making any file changes. This ensures your branch is based on the latest main.
-
-### 2. Create File Structure
-
-**Create changelog file:**
-- Path: `packages/twenty-website/src/content/releases/{VERSION}.mdx`
-- Example: `packages/twenty-website/src/content/releases/1.9.0.mdx`
-
-**Create image folder:**
-- Path: `packages/twenty-website/public/images/releases/{MINOR_VERSION}/`
-- Example for version 1.9.0: `packages/twenty-website/public/images/releases/1.9/`
-- Example for version 2.0.0: `packages/twenty-website/public/images/releases/2.0/`
-
-```bash
-# Create the image folder
-mkdir -p packages/twenty-website/public/images/releases/{MINOR_VERSION}
-```
-
-### 3. Move Illustration Files
-
-**Source:** `/Users/thomascolasdesfrancs/Downloads/🆕`
-
-**Destination:** `packages/twenty-website/public/images/releases/{MINOR_VERSION}/`
-
-**Naming Convention:** `{VERSION}-descriptive-name.png`
-
-Examples:
-- `1.9.0-feature-name.png`
-- `1.9.0-another-feature.png`
-
-```bash
-# Move and rename files
-cp ~/Downloads/🆕/source-file.png packages/twenty-website/public/images/releases/{MINOR_VERSION}/{VERSION}-feature-name.png
-```
-
-### 4. Research Features (if needed)
-
-If descriptions are not provided:
-1. Use the research commands above to find recent PRs and commits
-2. Search the codebase for feature-related code
-3. Read PR descriptions for context
-4. Check component comments and documentation
-
-### 5. Write Changelog Content
-
-Create the MDX file with this structure:
-
-```markdown
----
-release: {VERSION}
-Date: {YYYY-MM-DD}
----
-
-# Feature 1 Name
-
-Short description explaining what the feature does and why it's useful. Keep it user-focused and concise (1-2 sentences).
-
-![](/images/releases/{MINOR_VERSION}/{VERSION}-feature-1.png)
-
-# Feature 2 Name
-
-Another short description of the second feature.
-
-![](/images/releases/{MINOR_VERSION}/{VERSION}-feature-2.png)
-
-# Feature 3 Name
-
-Description of the third feature.
-
-![](/images/releases/{MINOR_VERSION}/{VERSION}-feature-3.png)
-```
-
-**Style Guidelines:**
-- Use H1 (`#`) for feature names
-- Keep descriptions to 1-2 sentences
-- Focus on user benefits, not technical implementation
-- Use active voice
-- Start with what the user can now do
-- **NEVER mention the brand name "Twenty"** in changelog text - use "your workspace", "the platform", or similar neutral references instead
-
-**Reference Previous Changelogs:**
-- Check `packages/twenty-website/src/content/releases/` for examples
-- Recent releases: 1.7.0.mdx, 1.6.0.mdx, 1.5.0.mdx
-
-### 6. Review
-
-Open the changelog file for review:
-```bash
-# Open in Cursor
-cursor packages/twenty-website/src/content/releases/{VERSION}.mdx
-
-# Open image folder to verify illustrations
-open packages/twenty-website/public/images/releases/{MINOR_VERSION}
-```
-
-Review checklist:
-- [ ] Version number is correct in frontmatter
-- [ ] Date is today's date
-- [ ] All features are documented
-- [ ] Image paths are correct
-- [ ] Image files exist in the folder
-- [ ] Descriptions are clear and user-focused
-- [ ] Spelling and grammar are correct
-
-### 7. Present Changelog for User Approval
-
-**IMPORTANT**: Before committing and creating the PR, always show the complete changelog content to the user and wait for explicit approval.
-
-**What to show:**
-1. Display the full MDX content of the changelog file
-2. Confirm that illustration files were moved to the correct location
-3. List the image file names and paths
-
-**What to say:**
-```
-I've created the changelog for version {VERSION}. Here's the content for your review:
-
-[Show full MDX content]
-
-Images moved to:
-- packages/twenty-website/public/images/releases/{MINOR_VERSION}/{VERSION}-feature-1.png
-- packages/twenty-website/public/images/releases/{MINOR_VERSION}/{VERSION}-feature-2.png
-
-Please review the content. Once you approve, I'll commit the changes and create the pull request.
-```
-
-**Wait for user approval before proceeding to step 8.**
-
-Possible user responses:
-- "Looks good" / "Approve" / "Create the PR" → Proceed to step 8
-- Requests changes → Make the requested edits, then show content again
-- Asks questions → Answer them, then wait for approval
-
-### 8. Commit Changes
-
-```bash
-# Check status
-git status
-
-# Add files
-git add packages/twenty-website/src/content/releases/{VERSION}.mdx
-git add packages/twenty-website/public/images/releases/{MINOR_VERSION}/
-
-# Commit
-git commit -m "Add {VERSION} release changelog"
-
-# Push branch
-git push -u origin {VERSION}
-```
-
-### 9. Create Pull Request
-
-```bash
-# Create PR using GitHub CLI
-gh pr create \
-  --title "Release {VERSION}" \
-  --body "## Release {VERSION}
-
-This release includes:
-
-- Feature 1
-- Feature 2
-- Feature 3
-
-Changelog file: \`packages/twenty-website/src/content/releases/{VERSION}.mdx\`
-Release date: {DATE}" \
-  --base main \
-  --head {VERSION}
-```
-
-Or visit: `https://github.com/twentyhq/twenty/pull/new/{VERSION}`
-
-## File Naming Conventions
-
-### Changelog Files
-- **Format**: `{MAJOR}.{MINOR}.{PATCH}.mdx`
-- **Convention**: One file per complete version
-- **Examples**: `1.6.0.mdx`, `1.7.0.mdx`, `2.0.0.mdx`
-- **Location**: `packages/twenty-website/src/content/releases/`
-
-### Image Folders
-- **Format**: `{MAJOR}.{MINOR}/`
-- **Convention**: One folder per minor version (shared across patches)
-- **Examples**: `1.6/`, `1.7/`, `2.0/`
-- **Location**: `packages/twenty-website/public/images/releases/`
-
-### Image Files
-- **Format**: `{VERSION}-descriptive-name.png`
-- **Convention**: Kebab-case descriptive names
-- **Examples**: 
-  - `1.8.0-workflow-iterator.png`
-  - `1.8.0-bulk-select.png`
-  - `1.9.0-new-feature.png`
-
-## Quick Reference Template
-
-Copy and fill this for each release:
-
-```
-VERSION: ___________
-DATE: ___________
-MINOR_VERSION: ___________
-
-Features to document:
-1. ___________________________
-2. ___________________________
-3. ___________________________
-
-Branch name: {VERSION}
-Changelog path: packages/twenty-website/src/content/releases/{VERSION}.mdx
-Images path: packages/twenty-website/public/images/releases/{MINOR_VERSION}/
-```
-
-## Tips
-
-- **Start early**: Begin documenting features as they're developed
-- **User perspective**: Write for users, not developers
-- **Be concise**: 1-2 sentences per feature
-- **Visual first**: Illustrations should showcase the feature clearly
-- **Consistent style**: Match tone and structure of previous changelogs
-- **Test links**: Verify all image paths work before committing
-- **Research thoroughly**: Use codebase search to understand features deeply

.cursor/rules/code-style.mdc

@@ -30,18 +30,6 @@ type ButtonProps = {}; // Component props suffix with 'Props'
 // ✅ Files and directories - kebab-case
 // user-profile.component.tsx
 // user-profile.styles.ts
-
-// ❌ NEVER use abbreviations in variable names
-// Bad
-const users = data.map((u) => u.name);
-const field = items.find((f) => f.id === id);
-
-// Good
-const users = data.map((user) => user.name);
-const field = items.find((item) => item.id === id);
-const fieldMetadata = inlineFields.find(
-  (fieldMetadataItem) => fieldMetadataItem.name === fieldName,
-);
 ```
 
 ## Import Organization
@@ -71,11 +59,11 @@ const processUserData = (
 ): ProcessedUser => {
   const processedUser = transformUserData(user);
   applyOptions(processedUser, options);
-
+  
   if (callback) {
     callback(processedUser);
   }
-
+  
   return processedUser;
 };
 ```
@@ -83,7 +71,7 @@ const processUserData = (
 ## Comments
 ```typescript
 // ✅ Use short-form comments, NOT JSDoc blocks
-// ✅ Explain business logic and non-obvious intentions (WHY, not WHAT)
+// ✅ Explain business logic and non-obvious intentions
 // Apply 15% discount for premium users with orders > $100
 const discount = isPremiumUser && orderTotal > 100 ? 0.15 : 0;
 
@@ -97,55 +85,12 @@ const calculateTotalPrice = (basePrice: number): number => {
   // Implementation
 };
 
-// ❌ AVOID obvious comments that just describe what code does
-// Bad: Get all inline fields dynamically
-const { inlineFieldMetadataItems } = useFieldListFieldMetadataItems({...});
-
-// Bad: Define standard fields in display order
-const standardFieldOrder = ['startsAt', 'endsAt', 'conferenceLink'];
-
-// Bad: Split fields into standard and custom
-const standardFields = standardFieldOrder.map(...)
-
-// ✅ GOOD: Only comment if explaining non-obvious business logic
-// Calendar events display standard fields first, then custom fields after participants
-// to maintain consistency with the legacy UI behavior
-const standardFields = standardFieldOrder.map(...)
-
 // ❌ AVOID JSDoc blocks - use short comments instead
 /**
  * This style is NOT preferred in this codebase
  */
 ```
 
-**Comment Guidelines:**
-- **DO** comment complex business rules or domain-specific logic
-- **DO** comment non-obvious algorithmic decisions
-- **DO** add TODOs for future improvements
-- **DON'T** comment obvious variable declarations or function calls
-- **DON'T** comment what is already clear from well-named variables/functions
-- **DON'T** add comments that just repeat what the code says
-
-## Utility Helpers
-```typescript
-// ✅ Use existing utility helpers instead of manual checks
-import { isDefined } from 'twenty-shared/utils';
-import { isNonEmptyString, isNonEmptyArray } from '@sniptt/guards';
-
-// ❌ Manual type guards
-const validItems = items.filter((item): item is Item => item !== undefined);
-const hasValue = value !== null && value !== undefined;
-
-// ✅ Use utility helpers
-const validItems = items.filter(isDefined);
-const hasValue = isDefined(value);
-
-// Other useful helpers:
-// - isDefined(value) - checks !== null && !== undefined
-// - isNonEmptyString(value) - checks string is defined and not empty
-// - isNonEmptyArray(value) - checks array is defined and has items
-```
-
 ## Security Patterns
 ```typescript
 // ✅ CSV Export: Always apply security first, then formatting

.cursor/rules/creating-syncable-entity.mdc

@@ -1,219 +0,0 @@
----
-description: Main guide for creating syncable entities in Twenty's workspace migration system
-globs: ["**/metadata-modules/**", "**/workspace-migration/**"]
-alwaysApply: false
----
-
-# Creating a New Syncable Entity - Main Guide
-
-This is the main guide for creating **syncable entities** in Twenty's workspace migration architecture.
-
-## Documentation Structure
-
-This main guide provides a high-level overview and navigation hub.
-
-**⚡ Skills** (`.cursor/skills/syncable-entity-*/SKILL.md`) - Concise, action-oriented implementation guides for each step. Reference these when creating a new syncable entity.
-
-**When to use:**
-- Start here for architecture overview and workflow
-- Reference specific skills (`@syncable-entity-types-and-constants`) when implementing each step
-
-## What is a Syncable Entity?
-
-A syncable entity is a metadata entity that:
-- Has a **`universalIdentifier`**: A unique identifier used for syncing entities across workspaces/applications
-- Has an **`applicationId`**: Links the entity to an application (Twenty Standard or Custom applications)
-- Participates in the **workspace migration system**: Can be created, updated, and deleted through the migration pipeline
-- Is **cached as a flat entity**: Denormalized representation for efficient validation and change detection
-
-Examples: `skill`, `agent`, `view`, `viewField`, `role`, `pageLayout`, etc.
-
-## Architecture Overview
-
-```
-Input DTO → Transform → Universal Flat Entity → Builder/Validator → Runner → Database
-                              ↓
-                        Cache Service
-```
-
-**Key Components:**
-- **TypeORM Entity**: Database model extending `SyncableEntity`
-- **Flat Entity**: Denormalized type (no relations, dates as strings) - for caching
-- **Universal Flat Entity**: Flat entity with foreign keys mapped to universal identifiers - for migrations
-- **Transform Utils**: Convert DTOs to universal flat entities
-- **Builder/Validator**: Validate and create migration actions
-- **Runner**: Execute actions against the database
-
-## Implementation Steps
-
-Follow these skills in order:
-
-### 1️⃣ **Foundation: Types & Constants** → `@syncable-entity-types-and-constants`
-
-**What:** Define all types, entities, and register in central constants
-
-**Tasks:**
-- Create TypeORM entity (extends `SyncableEntity`)
-- Define flat entity types
-- Define action types (universal + flat)
-- Register in 5 central constants
-
-**Why first:** Everything else depends on these types
-
----
-
-### 2️⃣ **Data Layer: Cache & Transform** → `@syncable-entity-cache-and-transform`
-
-**What:** Handle conversion between different representations
-
-**Tasks:**
-- Create cache service
-- Create entity-to-flat conversion
-- Create input transform utils
-- Handle foreign key resolution
-
-**Dependencies:** Requires Step 1
-
----
-
-### 3️⃣ **Business Logic: Builder & Validation** → `@syncable-entity-builder-and-validation`
-
-**What:** Validate business rules and create actions
-
-**Tasks:**
-- Create validator service (never throws, never mutates)
-- Create builder service
-- Wire into orchestrator (⚠️ critical!)
-
-**Dependencies:** Requires Steps 1-2
-
----
-
-### 4️⃣ **Execution: Runner & Actions** → `@syncable-entity-runner-and-actions`
-
-**What:** Execute migration actions against the database
-
-**Tasks:**
-- Create action handlers (create/update/delete)
-- Implement transpilation methods
-- Create universal-to-flat conversion utilities
-
-**Dependencies:** Requires Steps 1-3
-
----
-
-### 5️⃣ **Assembly: Integration** → `@syncable-entity-integration`
-
-**What:** Wire everything together
-
-**Tasks:**
-- Register in 3 NestJS modules
-- Create service and resolver layers
-- Use exception interceptor
-
-**Dependencies:** Requires Steps 1-4
-
----
-
-### 6️⃣ **Testing: Integration Tests** (**MANDATORY**) → `@syncable-entity-testing`
-
-**What:** Comprehensive test suite
-
-**Tasks:**
-- Create test utilities
-- Write failing tests (all validator exceptions)
-- Write successful tests (all CRUD operations)
-- Use snapshot testing
-
-**Dependencies:** Requires all previous steps
-
----
-
-## Quick Reference
-
-### Multi-Agent Workflow
-
-For parallel development:
-1. **Agent 1** (Foundation): Complete Step 1 first - unblocks everyone
-2. **Agent 2** (Cache): Can start immediately after Step 1
-3. **Agent 3** (Builder): Can work in parallel with Agent 4 after Step 1
-4. **Agent 4** (Runner): Can work in parallel with Agent 3 after Step 1
-5. **Agent 5** (Integration): Assembles everything after Steps 2-4
-
-### Key Design Principles
-
-| Layer | Responsibility | Can Throw? | Can Mutate? |
-|-------|---------------|------------|-------------|
-| Transform Utils | Data transformation | Yes (input validation) | N/A (creates new) |
-| Validator | Business rule validation | **No** (returns errors) | **No** |
-| Builder | Action creation | **No** (returns errors) | **No** |
-| Runner | Database operations | Yes (DB errors) | Yes (via TypeORM) |
-
-### Common Pitfalls
-
-⚠️ **Most Commonly Forgotten:**
-1. Wiring builder in orchestrator service
-2. Registering in all 3 modules (builder, validators, action handlers)
-3. Setting `universalIdentifier` correctly in entity-to-flat conversion
-
-⚠️ **Common Mistakes:**
-1. Using regular IDs instead of universal identifiers in transform utils
-2. Throwing exceptions in validators/builders
-3. Mutating entity maps in validators/builders
-4. Forgetting to handle JSONB properties with `SerializedRelation`
-
-### File Locations
-
-```
-packages/twenty-shared/src/metadata/
-└── all-metadata-name.constant.ts
-
-packages/twenty-server/src/engine/metadata-modules/
-├── my-entity/                           # Step 1
-│   └── entities/
-├── flat-my-entity/                      # Steps 1-2
-│   ├── types/
-│   ├── constants/
-│   ├── services/
-│   └── utils/
-└── flat-entity/constant/                # Step 1 (central registries)
-    ├── all-entity-properties-configuration-by-metadata-name.constant.ts
-    ├── all-one-to-many-metadata-relations.constant.ts
-    ├── all-many-to-one-metadata-foreign-key.constant.ts
-    └── all-many-to-one-metadata-relations.constant.ts
-
-packages/twenty-server/src/engine/workspace-manager/workspace-migration/
-├── workspace-migration-builder/         # Step 3
-│   ├── builders/my-entity/
-│   └── validators/services/
-└── workspace-migration-runner/          # Step 4
-    └── action-handlers/my-entity/
-```
-
-### Complete Checklist
-
-Before considering complete:
-- [ ] All 6 guides completed
-- [ ] TypeORM entity extends `SyncableEntity`
-- [ ] All constants registered (5 central registries)
-- [ ] Cache service with correct decorator
-- [ ] Transform utils return universal flat entities
-- [ ] Validator never throws/mutates
-- [ ] Builder wired in orchestrator (⚠️ critical!)
-- [ ] All 3 action handlers implemented
-- [ ] All 3 modules updated
-- [ ] **Integration tests written (MANDATORY)**
-- [ ] **All failing scenarios covered**
-- [ ] **All successful use cases tested**
-
----
-
-## Need Help?
-
-Reference the appropriate skill for step-by-step guidance:
-- `@syncable-entity-types-and-constants` - Types, entities, constants
-- `@syncable-entity-cache-and-transform` - Cache & transform
-- `@syncable-entity-builder-and-validation` - Builder & validation
-- `@syncable-entity-runner-and-actions` - Runner & actions
-- `@syncable-entity-integration` - Integration & wiring
-- `@syncable-entity-testing` - Testing patterns

.cursor/rules/nx-rules.mdc

@@ -12,12 +12,7 @@ alwaysApply: true
 npx nx run twenty-front:build
 npx nx run twenty-server:test
 
-# Lint diff with main (recommended - much faster!)
-npx nx lint:diff-with-main twenty-front           # Lint only files changed vs main
-npx nx lint:diff-with-main twenty-server
-npx nx lint:diff-with-main twenty-front --configuration=fix  # Auto-fix changed files
-
-# Run target for all projects (slower)
+# Run target for all projects
 npx nx run-many --target=build --all
 npx nx run-many --target=test --projects=twenty-front,twenty-server
 
@@ -48,18 +43,12 @@ npx nx g @nx/react:component my-component
 }
 ```
 
-## Linting Strategy
-For faster development, always prefer linting only changed files:
-- Use `npx nx lint:diff-with-main <project>` to lint only files changed vs main branch
-- Use `--configuration=fix` to auto-fix issues in changed files
-- Only use `npx nx lint <project>` when you need to lint the entire project
-
 ## Dependency Graph
 ```bash
 # View project dependencies
 npx nx graph
 
-# Check what's affected by changes (runs target on affected projects)
+# Check what's affected by changes
 npx nx affected --target=test
 npx nx affected --target=build --base=main
 ```

.cursor/rules/react-state-management.mdc

@@ -4,20 +4,16 @@ alwaysApply: false
 ---
 # React State Management
 
-## Jotai Patterns
+## Recoil Patterns
 ```typescript
-// ✅ Atoms for primitive state (use createAtomState for keyed state with optional persistence)
-import { createAtomState } from '@/ui/utilities/state/jotai/utils/createAtomState';
-
-export const currentUserState = createAtomState<User | null>({
+// ✅ Atoms for primitive state
+export const currentUserState = atom<User | null>({
   key: 'currentUserState',
-  defaultValue: null,
+  default: null,
 });
 
-// ✅ Derived atoms for computed state (use createAtomSelector)
-import { createAtomSelector } from '@/ui/utilities/state/jotai/utils/createAtomSelector';
-
-export const userDisplayNameSelector = createAtomSelector({
+// ✅ Selectors for derived state
+export const userDisplayNameSelector = selector({
   key: 'userDisplayNameSelector',
   get: ({ get }) => {
     const user = get(currentUserState);
@@ -25,30 +21,13 @@ export const userDisplayNameSelector = createAtomSelector({
   },
 });
 
-// ✅ Atom factory pattern for dynamic atoms (use createAtomFamilyState)
-import { createAtomFamilyState } from '@/ui/utilities/state/jotai/utils/createAtomFamilyState';
-
-export const userByIdState = createAtomFamilyState<User | null, string>({
+// ✅ Atom families for dynamic atoms
+export const userByIdState = atomFamily<User | null, string>({
   key: 'userByIdState',
-  defaultValue: null,
+  default: null,
 });
 ```
 
-## Jotai Hooks
-```typescript
-// useAtomState - read and write
-import { useAtomState } from '@/ui/utilities/state/jotai/hooks/useAtomState';
-
-// useAtomStateValue - read only
-import { useAtomStateValue } from '@/ui/utilities/state/jotai/hooks/useAtomStateValue';
-
-// useSetAtomState - write only
-import { useSetAtomState } from '@/ui/utilities/state/jotai/hooks/useSetAtomState';
-```
-
-## Provider
-Jotai works without a Provider by default. For scoped stores or testing, use `Provider` from `jotai`.
-
 ## Local State Guidelines
 ```typescript
 // ✅ Multiple useState for unrelated state
@@ -95,7 +74,7 @@ const increment = useCallback(() => {
 ```
 
 ## Performance Tips
-- Use atom factory pattern (createAtomFamilyState) for dynamic data collections
-- Derived atoms (createAtomSelector) are automatically memoized by Jotai
-- Avoid heavy computations in derived atoms
+- Use atom families for dynamic data collections
+- Implement proper selector caching
+- Avoid heavy computations in selectors
 - Batch state updates when possible

.cursor/rules/server-migrations.mdc

@@ -1,29 +0,0 @@
----
-description: Guidelines for generating and managing TypeORM migrations in twenty-server
-globs: [
-  "packages/twenty-server/src/**/*.entity.ts",
-  "packages/twenty-server/src/database/typeorm/**/*.ts"
-]
-alwaysApply: false
----
-
-## Server Migrations (twenty-server)
-
-- **When changing an entity, always generate a migration**
-  - If you modify a `*.entity.ts` file in `packages/twenty-server/src`, you **must** generate a corresponding TypeORM migration instead of manually editing the database schema.
-  - Use the Nx + TypeORM command from the project root:
-
-    ```bash
-    npx nx run twenty-server:typeorm migration:generate src/database/typeorm/core/migrations/common/[name] -d src/database/typeorm/core/core.datasource.ts
-    ```
-
-  - Replace `[name]` with a descriptive, kebab-case migration name that reflects the change (for example, `add-agent-turn-evaluation`).
-
-- **Prefer generated migrations over manual edits**
-  - Let TypeORM infer schema changes from the updated entities; only adjust the generated migration file manually if absolutely necessary (for example, for data backfills or complex constraints).
-  - Keep schema changes (DDL) in these generated migrations and avoid mixing in heavy data migrations unless there is a strong reason and clear comments.
-
-- **Keep migrations consistent and reversible**
-  - Ensure the generated migration includes both `up` and `down` logic that correctly applies and reverts the entity change when possible.
-  - Do not delete or rewrite existing, committed migrations unless you are explicitly working on a pre-release branch where history rewrites are allowed by team conventions.
-

.cursor/skills/syncable-entity-builder-and-validation/SKILL.md

@@ -1,393 +0,0 @@
----
-name: syncable-entity-builder-and-validation
-description: Create validation logic and migration action builders for syncable entities in Twenty. Use when implementing business rule validation, uniqueness checks, foreign key validation, or building workspace migration actions for syncable entities. Validators never throw and never mutate.
----
-
-# Syncable Entity: Builder & Validation (Step 3/6)
-
-**Purpose**: Implement business rule validation and create migration action builders.
-
-**When to use**: After completing Steps 1-2 (Types, Cache, Transform). Required before implementing action handlers.
-
----
-
-## Quick Start
-
-This step creates:
-1. Validator service (business logic validation)
-2. Builder service (action creation)
-3. Orchestrator wiring (**CRITICAL** - often forgotten!)
-
-**Key principles**:
-- Validators **never throw** - return error arrays
-- Validators **never mutate** - pass optimistic entity maps
-- Use indexed lookups (O(1)) not `Object.values().find()` (O(n))
-
----
-
-## Step 1: Create Validator Service
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/validators/services/flat-my-entity-validator.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { t, msg } from '@lingui/macro';
-import { isDefined } from 'twenty-shared/utils';
-
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-import { type FlatMyEntityMaps } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity-maps.type';
-import { WorkspaceMigrationValidationError } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/validators/types/workspace-migration-validation-error.type';
-import { MyEntityExceptionCode } from 'src/engine/metadata-modules/my-entity/exceptions/my-entity-exception-code.enum';
-
-@Injectable()
-export class FlatMyEntityValidatorService {
-  validateMyEntityForCreate(
-    flatMyEntity: FlatMyEntity,
-    optimisticFlatMyEntityMaps: FlatMyEntityMaps,
-  ): WorkspaceMigrationValidationError[] {
-    const errors: WorkspaceMigrationValidationError[] = [];
-
-    // Pattern 1: Required field validation
-    if (!isDefined(flatMyEntity.name) || flatMyEntity.name.trim() === '') {
-      errors.push({
-        code: MyEntityExceptionCode.NAME_REQUIRED,
-        message: t`Name is required`,
-        userFriendlyMessage: msg`Please provide a name for this entity`,
-      });
-    }
-
-    // Pattern 2: Uniqueness check - use indexed map (O(1))
-    const existingEntityWithName = optimisticFlatMyEntityMaps.byName[flatMyEntity.name];
-
-    if (isDefined(existingEntityWithName) && existingEntityWithName.id !== flatMyEntity.id) {
-      errors.push({
-        code: MyEntityExceptionCode.MY_ENTITY_ALREADY_EXISTS,
-        message: t`Entity with name ${flatMyEntity.name} already exists`,
-        userFriendlyMessage: msg`An entity with this name already exists`,
-      });
-    }
-
-    // Pattern 3: Foreign key validation
-    if (isDefined(flatMyEntity.parentEntityId)) {
-      const parentEntity = optimisticFlatParentEntityMaps.byId[flatMyEntity.parentEntityId];
-
-      if (!isDefined(parentEntity)) {
-        errors.push({
-          code: MyEntityExceptionCode.PARENT_ENTITY_NOT_FOUND,
-          message: t`Parent entity with ID ${flatMyEntity.parentEntityId} not found`,
-          userFriendlyMessage: msg`The specified parent entity does not exist`,
-        });
-      } else if (isDefined(parentEntity.deletedAt)) {
-        errors.push({
-          code: MyEntityExceptionCode.PARENT_ENTITY_DELETED,
-          message: t`Parent entity is deleted`,
-          userFriendlyMessage: msg`Cannot reference a deleted parent entity`,
-        });
-      }
-    }
-
-    // Pattern 4: Standard entity protection
-    if (flatMyEntity.isCustom === false) {
-      errors.push({
-        code: MyEntityExceptionCode.STANDARD_ENTITY_CANNOT_BE_CREATED,
-        message: t`Cannot create standard entity`,
-        userFriendlyMessage: msg`Standard entities can only be created by the system`,
-      });
-    }
-
-    return errors;
-  }
-
-  validateMyEntityForUpdate(
-    flatMyEntity: FlatMyEntity,
-    updates: Partial<FlatMyEntity>,
-    optimisticFlatMyEntityMaps: FlatMyEntityMaps,
-  ): WorkspaceMigrationValidationError[] {
-    const errors: WorkspaceMigrationValidationError[] = [];
-
-    // Standard entity protection
-    if (flatMyEntity.isCustom === false) {
-      errors.push({
-        code: MyEntityExceptionCode.STANDARD_ENTITY_CANNOT_BE_UPDATED,
-        message: t`Cannot update standard entity`,
-        userFriendlyMessage: msg`Standard entities cannot be modified`,
-      });
-      return errors; // Early return if standard
-    }
-
-    // Uniqueness check for name changes
-    if (isDefined(updates.name) && updates.name !== flatMyEntity.name) {
-      const existingEntityWithName = optimisticFlatMyEntityMaps.byName[updates.name];
-
-      if (isDefined(existingEntityWithName) && existingEntityWithName.id !== flatMyEntity.id) {
-        errors.push({
-          code: MyEntityExceptionCode.MY_ENTITY_ALREADY_EXISTS,
-          message: t`Entity with name ${updates.name} already exists`,
-          userFriendlyMessage: msg`An entity with this name already exists`,
-        });
-      }
-    }
-
-    return errors;
-  }
-
-  validateMyEntityForDelete(
-    flatMyEntity: FlatMyEntity,
-  ): WorkspaceMigrationValidationError[] {
-    const errors: WorkspaceMigrationValidationError[] = [];
-
-    // Standard entity protection
-    if (flatMyEntity.isCustom === false) {
-      errors.push({
-        code: MyEntityExceptionCode.STANDARD_ENTITY_CANNOT_BE_DELETED,
-        message: t`Cannot delete standard entity`,
-        userFriendlyMessage: msg`Standard entities cannot be deleted`,
-      });
-    }
-
-    return errors;
-  }
-}
-```
-
-**Performance warning**: Avoid `Object.values().find()` - use indexed maps instead!
-
-```typescript
-// ❌ BAD: O(n) - slow for large datasets
-const duplicate = Object.values(optimisticFlatMyEntityMaps.byId).find(
-  (entity) => entity.name === flatMyEntity.name && entity.id !== flatMyEntity.id
-);
-
-// ✅ GOOD: O(1) - use indexed map
-const existingEntityWithName = optimisticFlatMyEntityMaps.byName[flatMyEntity.name];
-if (isDefined(existingEntityWithName) && existingEntityWithName.id !== flatMyEntity.id) {
-  // Handle duplicate
-}
-```
-
----
-
-## Step 2: Create Builder Service
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/builders/my-entity/workspace-migration-my-entity-actions-builder.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-
-import { WorkspaceEntityMigrationBuilderService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/workspace-entity-migration-builder.service';
-import { FlatMyEntityValidatorService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/validators/services/flat-my-entity-validator.service';
-import { type UniversalFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/types/universal-flat-my-entity.type';
-import {
-  type UniversalCreateMyEntityAction,
-  type UniversalUpdateMyEntityAction,
-  type UniversalDeleteMyEntityAction,
-} from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/builders/my-entity/types/workspace-migration-my-entity-action.type';
-
-@Injectable()
-export class WorkspaceMigrationMyEntityActionsBuilderService extends WorkspaceEntityMigrationBuilderService<
-  'myEntity',
-  UniversalFlatMyEntity,
-  UniversalCreateMyEntityAction,
-  UniversalUpdateMyEntityAction,
-  UniversalDeleteMyEntityAction
-> {
-  constructor(
-    private readonly flatMyEntityValidatorService: FlatMyEntityValidatorService,
-  ) {
-    super();
-  }
-
-  protected buildCreateAction(
-    universalFlatMyEntity: UniversalFlatMyEntity,
-    flatEntityMaps: AllFlatEntityMapsByMetadataName,
-  ): BuildWorkspaceMigrationActionReturnType<UniversalCreateMyEntityAction> {
-    const validationResult = this.flatMyEntityValidatorService.validateMyEntityForCreate(
-      universalFlatMyEntity,
-      flatEntityMaps.flatMyEntityMaps,
-    );
-
-    if (validationResult.length > 0) {
-      return {
-        status: 'failed',
-        errors: validationResult,
-      };
-    }
-
-    return {
-      status: 'success',
-      action: {
-        type: 'create',
-        metadataName: 'myEntity',
-        universalFlatEntity: universalFlatMyEntity,
-      },
-    };
-  }
-
-  protected buildUpdateAction(
-    universalFlatMyEntity: UniversalFlatMyEntity,
-    universalUpdates: Partial<UniversalFlatMyEntity>,
-    flatEntityMaps: AllFlatEntityMapsByMetadataName,
-  ): BuildWorkspaceMigrationActionReturnType<UniversalUpdateMyEntityAction> {
-    const validationResult = this.flatMyEntityValidatorService.validateMyEntityForUpdate(
-      universalFlatMyEntity,
-      universalUpdates,
-      flatEntityMaps.flatMyEntityMaps,
-    );
-
-    if (validationResult.length > 0) {
-      return {
-        status: 'failed',
-        errors: validationResult,
-      };
-    }
-
-    return {
-      status: 'success',
-      action: {
-        type: 'update',
-        metadataName: 'myEntity',
-        universalFlatEntity: universalFlatMyEntity,
-        universalUpdates,
-      },
-    };
-  }
-
-  protected buildDeleteAction(
-    universalFlatMyEntity: UniversalFlatMyEntity,
-  ): BuildWorkspaceMigrationActionReturnType<UniversalDeleteMyEntityAction> {
-    const validationResult = this.flatMyEntityValidatorService.validateMyEntityForDelete(
-      universalFlatMyEntity,
-    );
-
-    if (validationResult.length > 0) {
-      return {
-        status: 'failed',
-        errors: validationResult,
-      };
-    }
-
-    return {
-      status: 'success',
-      action: {
-        type: 'delete',
-        metadataName: 'myEntity',
-        universalFlatEntity: universalFlatMyEntity,
-      },
-    };
-  }
-}
-```
-
----
-
-## Step 3: Wire into Orchestrator (**CRITICAL**)
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/workspace-migration-build-orchestrator.service.ts`
-
-```typescript
-@Injectable()
-export class WorkspaceMigrationBuildOrchestratorService {
-  constructor(
-    // ... existing builders
-    private readonly workspaceMigrationMyEntityActionsBuilderService: WorkspaceMigrationMyEntityActionsBuilderService,
-  ) {}
-
-  async buildWorkspaceMigration({
-    allFlatEntityOperationByMetadataName,
-    flatEntityMaps,
-    isSystemBuild,
-  }: BuildWorkspaceMigrationInput): Promise<BuildWorkspaceMigrationOutput> {
-    // ... existing code
-
-    // Add your entity builder
-    const myEntityResult = await this.workspaceMigrationMyEntityActionsBuilderService.build({
-      flatEntitiesToCreate: allFlatEntityOperationByMetadataName.myEntity?.flatEntityToCreate ?? [],
-      flatEntitiesToUpdate: allFlatEntityOperationByMetadataName.myEntity?.flatEntityToUpdate ?? [],
-      flatEntitiesToDelete: allFlatEntityOperationByMetadataName.myEntity?.flatEntityToDelete ?? [],
-      flatEntityMaps,
-      isSystemBuild,
-    });
-
-    // ... aggregate errors
-
-    return {
-      status: aggregatedErrors.length > 0 ? 'failed' : 'success',
-      errors: aggregatedErrors,
-      actions: [
-        ...existingActions,
-        ...myEntityResult.actions,
-      ],
-    };
-  }
-}
-```
-
-**⚠️ This step is the most commonly forgotten!** Your entity won't sync without orchestrator wiring.
-
----
-
-## Validation Patterns
-
-### Pattern 1: Required Field
-```typescript
-if (!isDefined(field) || field.trim() === '') {
-  errors.push({ code: ..., message: ..., userFriendlyMessage: ... });
-}
-```
-
-### Pattern 2: Uniqueness (O(1) lookup)
-```typescript
-const existing = optimisticMaps.byName[entity.name];
-if (isDefined(existing) && existing.id !== entity.id) {
-  errors.push({ ... });
-}
-```
-
-### Pattern 3: Foreign Key Validation
-```typescript
-if (isDefined(entity.parentId)) {
-  const parent = parentMaps.byId[entity.parentId];
-  if (!isDefined(parent)) {
-    errors.push({ code: NOT_FOUND, ... });
-  } else if (isDefined(parent.deletedAt)) {
-    errors.push({ code: DELETED, ... });
-  }
-}
-```
-
-### Pattern 4: Standard Entity Protection
-```typescript
-if (entity.isCustom === false) {
-  errors.push({ code: STANDARD_ENTITY_PROTECTED, ... });
-  return errors; // Early return
-}
-```
-
----
-
-## Checklist
-
-Before moving to Step 4:
-
-- [ ] Validator service created
-- [ ] Validator **never throws** (returns error arrays)
-- [ ] Validator **never mutates** (uses optimistic maps)
-- [ ] All uniqueness checks use indexed maps (O(1))
-- [ ] Required field validation implemented
-- [ ] Foreign key validation implemented
-- [ ] Standard entity protection implemented
-- [ ] Builder service extends `WorkspaceEntityMigrationBuilderService`
-- [ ] Builder creates actions with universal entities
-- [ ] **Builder wired into orchestrator** (**CRITICAL**)
-- [ ] **Builder injected in orchestrator constructor**
-- [ ] **Builder called in `buildWorkspaceMigration`**
-- [ ] **Actions added to orchestrator return statement**
-
----
-
-## Next Step
-
-Once builder and validation are complete, proceed to:
-**[Syncable Entity: Runner & Actions (Step 4/6)](../syncable-entity-runner-and-actions/SKILL.md)**
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/skills/syncable-entity-cache-and-transform/SKILL.md

@@ -1,303 +0,0 @@
----
-name: syncable-entity-cache-and-transform
-description: Create cache services and transformation utilities for syncable entities in Twenty. Use when implementing entity-to-flat conversions, input DTO transpilation to universal flat entities, or cache recomputation for syncable entities.
----
-
-# Syncable Entity: Cache & Transform (Step 2/6)
-
-**Purpose**: Create cache layer and transformation utilities to convert between different entity representations.
-
-**When to use**: After completing Step 1 (Types & Constants). Required before building validators and action handlers.
-
----
-
-## Quick Start
-
-This step creates:
-1. Cache service for flat entity maps
-2. Entity-to-flat conversion utility
-3. Input transform utils (DTO → Universal Flat Entity)
-
-**Key principle**: Input transform utils must output **universal flat entities** (with `universalIdentifier` and foreign keys mapped to universal identifiers).
-
----
-
-## Step 1: Create Cache Service
-
-**File**: `src/engine/metadata-modules/flat-my-entity/services/flat-my-entity-cache.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { InjectRepository } from '@nestjs/typeorm';
-import { Repository } from 'typeorm';
-import { v4 } from 'uuid';
-
-import { WorkspaceCache } from 'src/engine/twenty-orm/decorators/workspace-cache.decorator';
-import { MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { type FlatMyEntityMaps } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity-maps.type';
-import { fromMyEntityEntityToFlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/utils/from-my-entity-entity-to-flat-my-entity.util';
-
-@Injectable()
-export class FlatMyEntityCacheService {
-  constructor(
-    @InjectRepository(MyEntityEntity, 'metadata')
-    private readonly myEntityRepository: Repository<MyEntityEntity>,
-  ) {}
-
-  @WorkspaceCache({ flatMapsKey: 'flatMyEntityMaps' })
-  async getFlatMyEntityMaps(): Promise<FlatMyEntityMaps> {
-    const myEntities = await this.myEntityRepository.find({
-      withDeleted: true, // CRITICAL: Include soft-deleted entities
-    });
-
-    const flatMyEntities = myEntities.map((entity) =>
-      fromMyEntityEntityToFlatMyEntity(entity),
-    );
-
-    return {
-      byId: Object.fromEntries(flatMyEntities.map((e) => [e.id, e])),
-      byName: Object.fromEntries(flatMyEntities.map((e) => [e.name, e])),
-    };
-  }
-}
-```
-
-**Critical rules**:
-- Use `@WorkspaceCache` decorator with unique `flatMapsKey`
-- **Always** use `withDeleted: true` to include soft-deleted entities
-- Cache key pattern: `flat{EntityName}Maps` (camelCase)
-
----
-
-## Step 2: Entity-to-Flat Conversion
-
-**File**: `src/engine/metadata-modules/flat-my-entity/utils/from-my-entity-entity-to-flat-my-entity.util.ts`
-
-```typescript
-import { v4 } from 'uuid';
-import { type MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-
-export const fromMyEntityEntityToFlatMyEntity = (
-  entity: MyEntityEntity,
-): FlatMyEntity => {
-  return {
-    id: entity.id,
-    // Critical: generate a new UUID for universalIdentifier
-    universalIdentifier: v4(),
-    workspaceId: entity.workspaceId,
-    applicationId: entity.applicationId,
-    name: entity.name,
-    label: entity.label,
-    description: entity.description,
-    isCustom: entity.isCustom,
-    parentEntityId: entity.parentEntityId,
-    settings: entity.settings,
-    createdAt: entity.createdAt.toISOString(),
-    updatedAt: entity.updatedAt.toISOString(),
-    deletedAt: entity.deletedAt?.toISOString() ?? null,
-  };
-};
-```
-
-**Critical**: `universalIdentifier` must be a new UUID generated with `v4()` (not `entity.id`)
-
----
-
-## Step 3: Input Transform Utils (DTO → Universal Flat Entity)
-
-**File**: `src/engine/metadata-modules/flat-my-entity/utils/from-create-my-entity-input-to-universal-flat-my-entity.util.ts`
-
-```typescript
-import { v4 } from 'uuid';
-import { sanitizeString } from 'twenty-shared/string';
-import { type CreateMyEntityInput } from 'src/engine/metadata-modules/my-entity/dtos/create-my-entity.input';
-import { type UniversalFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/types/universal-flat-my-entity.type';
-import { resolveEntityRelationUniversalIdentifiers } from 'src/engine/metadata-modules/flat-entity/utils/resolve-entity-relation-universal-identifiers.util';
-import { type AllFlatEntityMapsByMetadataName } from 'src/engine/metadata-modules/flat-entity/types/all-flat-entity-maps-by-metadata-name.type';
-
-export const fromCreateMyEntityInputToUniversalFlatMyEntity = ({
-  input,
-  workspaceId,
-  flatEntityMaps,
-}: {
-  input: CreateMyEntityInput;
-  workspaceId: string;
-  flatEntityMaps?: AllFlatEntityMapsByMetadataName;
-}): UniversalFlatMyEntity => {
-  const id = v4();
-  const universalIdentifier = v4();
-
-  // 1. Extract foreign key IDs BEFORE sanitization
-  const parentEntityId = input.parentEntityId ?? null;
-
-  // 2. Sanitize string properties
-  const name = sanitizeString(input.name);
-  const label = sanitizeString(input.label);
-  const description = input.description ? sanitizeString(input.description) : null;
-
-  // 3. Build base flat entity
-  const baseFlatEntity = {
-    id,
-    universalIdentifier,
-    workspaceId,
-    applicationId: null,
-    name,
-    label,
-    description,
-    isCustom: true,
-    parentEntityId,
-    settings: input.settings ?? null,
-    createdAt: new Date().toISOString(),
-    updatedAt: new Date().toISOString(),
-    deletedAt: null,
-  };
-
-  // 4. Resolve foreign keys to universal identifiers (if flatEntityMaps provided)
-  if (flatEntityMaps) {
-    return resolveEntityRelationUniversalIdentifiers({
-      metadataName: 'myEntity',
-      flatEntity: baseFlatEntity,
-      flatEntityMaps,
-    });
-  }
-
-  // 5. Return with null universal foreign keys if no maps
-  return {
-    ...baseFlatEntity,
-    parentEntityUniversalIdentifier: null,
-  };
-};
-```
-
-**Key steps**:
-1. Generate IDs (`id` and `universalIdentifier` with `v4()`)
-2. Extract foreign keys **before** sanitization
-3. Sanitize all string properties
-4. Build base flat entity
-5. Resolve foreign keys → universal identifiers
-
----
-
-## Step 4: Create Flat Entity Module
-
-**File**: `src/engine/metadata-modules/flat-my-entity/flat-my-entity.module.ts`
-
-```typescript
-import { Module } from '@nestjs/common';
-import { TypeOrmModule } from '@nestjs/typeorm';
-
-import { MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { FlatMyEntityCacheService } from 'src/engine/metadata-modules/flat-my-entity/services/flat-my-entity-cache.service';
-
-@Module({
-  imports: [TypeOrmModule.forFeature([MyEntityEntity], 'metadata')],
-  providers: [FlatMyEntityCacheService],
-  exports: [FlatMyEntityCacheService],
-})
-export class FlatMyEntityModule {}
-```
-
-**Rules**:
-- Import entity with `'metadata'` datasource
-- Export cache service for use in other modules
-
----
-
-## Common Patterns
-
-### Pattern: Foreign Key Resolution
-
-```typescript
-// Extract foreign keys BEFORE sanitization
-const parentEntityId = input.parentEntityId ?? null;
-
-// After building base entity, resolve to universal identifiers
-const universalFlatEntity = resolveEntityRelationUniversalIdentifiers({
-  metadataName: 'myEntity',
-  flatEntity: baseFlatEntity,
-  flatEntityMaps,
-});
-```
-
-### Pattern: JSONB with SerializedRelation
-
-```typescript
-// For JSONB properties containing foreign keys
-const settings = input.settings
-  ? {
-      ...input.settings,
-      fieldMetadataId: input.settings.fieldMetadataId,
-    }
-  : null;
-
-// After resolution, JSONB foreign keys become universal identifiers
-return resolveEntityRelationUniversalIdentifiers({
-  metadataName: 'myEntity',
-  flatEntity: { ...baseFlatEntity, settings },
-  flatEntityMaps,
-});
-```
-
-### Pattern: Update Transform
-
-```typescript
-// from-update-my-entity-input-to-universal-flat-my-entity-updates.util.ts
-export const fromUpdateMyEntityInputToUniversalFlatMyEntityUpdates = ({
-  input,
-  flatEntityMaps,
-}: {
-  input: UpdateMyEntityInput;
-  flatEntityMaps?: AllFlatEntityMapsByMetadataName;
-}): Partial<UniversalFlatMyEntity> => {
-  const updates: Partial<UniversalFlatMyEntity> = {};
-
-  if (input.name !== undefined) {
-    updates.name = sanitizeString(input.name);
-  }
-
-  if (input.parentEntityId !== undefined) {
-    updates.parentEntityId = input.parentEntityId;
-  }
-
-  updates.updatedAt = new Date().toISOString();
-
-  // Resolve foreign keys if maps provided
-  if (flatEntityMaps) {
-    return resolveEntityRelationUniversalIdentifiers({
-      metadataName: 'myEntity',
-      flatEntity: updates as any,
-      flatEntityMaps,
-    });
-  }
-
-  return updates;
-};
-```
-
----
-
-## Checklist
-
-Before moving to Step 3:
-
-- [ ] Cache service created with `@WorkspaceCache` decorator
-- [ ] Cache uses `withDeleted: true`
-- [ ] Cache key follows `flat{EntityName}Maps` pattern
-- [ ] Entity-to-flat conversion implemented
-- [ ] `universalIdentifier` set correctly (generated with `v4()`)
-- [ ] Create input transform implemented
-- [ ] Update input transform implemented (if needed)
-- [ ] Foreign keys extracted before sanitization
-- [ ] String properties sanitized
-- [ ] Foreign keys resolved to universal identifiers
-- [ ] Flat entity module created and exports cache service
-
----
-
-## Next Step
-
-Once cache and transform utilities are complete, proceed to:
-**[Syncable Entity: Builder & Validation (Step 3/6)](../syncable-entity-builder-and-validation/SKILL.md)**
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/skills/syncable-entity-integration/SKILL.md

@@ -1,326 +0,0 @@
----
-name: syncable-entity-integration
-description: Wire syncable entity services into NestJS modules, create service layer and resolvers for Twenty entities. Use when registering builders, validators, and action handlers in modules, creating business services, or exposing entities via GraphQL API with proper exception handling.
----
-
-# Syncable Entity: Integration (Step 5/6)
-
-**Purpose**: Wire everything together, register in modules, create services and resolvers.
-
-**When to use**: After completing Steps 1-4 (all previous steps). Required before testing.
-
----
-
-## Quick Start
-
-This step:
-1. Registers services in 3 NestJS modules
-2. Creates service layer (returns flat entities)
-3. Creates resolver layer (converts flat → DTO)
-4. Uses exception interceptor for GraphQL
-
-**Key principle**: Services return flat entities, resolvers transpile flat → DTO.
-
----
-
-## Step 1: Register in Builder Module
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/workspace-migration-builder.module.ts`
-
-```typescript
-import { WorkspaceMigrationMyEntityActionsBuilderService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/builders/my-entity/workspace-migration-my-entity-actions-builder.service';
-
-@Module({
-  imports: [
-    // ... existing imports
-  ],
-  providers: [
-    // ... existing providers
-    WorkspaceMigrationMyEntityActionsBuilderService,
-  ],
-  exports: [
-    // ... existing exports
-    WorkspaceMigrationMyEntityActionsBuilderService,
-  ],
-})
-export class WorkspaceMigrationBuilderModule {}
-```
-
-**Important**: Add to both `providers` AND `exports` (builder needs to be exported for orchestrator).
-
----
-
-## Step 2: Register in Validators Module
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/validators/workspace-migration-builder-validators.module.ts`
-
-```typescript
-import { FlatMyEntityValidatorService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/validators/services/flat-my-entity-validator.service';
-
-@Module({
-  imports: [
-    // ... existing imports
-  ],
-  providers: [
-    // ... existing providers
-    FlatMyEntityValidatorService,
-  ],
-  exports: [
-    // ... existing exports
-    FlatMyEntityValidatorService,
-  ],
-})
-export class WorkspaceMigrationBuilderValidatorsModule {}
-```
-
----
-
-## Step 3: Register Action Handlers
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/workspace-schema-migration-runner-action-handlers.module.ts`
-
-```typescript
-import { CreateMyEntityActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/create-my-entity-action-handler.service';
-import { UpdateMyEntityActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/update-my-entity-action-handler.service';
-import { DeleteMyEntityActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/delete-my-entity-action-handler.service';
-
-@Module({
-  imports: [
-    // ... existing imports
-  ],
-  providers: [
-    // ... existing providers
-    CreateMyEntityActionHandlerService,
-    UpdateMyEntityActionHandlerService,
-    DeleteMyEntityActionHandlerService,
-  ],
-  exports: [
-    // ... existing exports (action handlers typically not exported)
-  ],
-})
-export class WorkspaceSchemaMigrationRunnerActionHandlersModule {}
-```
-
-**Note**: Action handlers are typically only in `providers`, not `exports`.
-
----
-
-## Step 4: Create Service Layer
-
-**File**: `src/engine/metadata-modules/my-entity/my-entity.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { isDefined } from 'twenty-shared/utils';
-
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-import { WorkspaceManyOrAllFlatEntityMapsCacheService } from 'src/engine/metadata-modules/flat-entity/services/workspace-many-or-all-flat-entity-maps-cache.service';
-import { findFlatEntityByIdInFlatEntityMapsOrThrow } from 'src/engine/metadata-modules/flat-entity/utils/find-flat-entity-by-id-in-flat-entity-maps-or-throw.util';
-import { fromCreateMyEntityInputToUniversalFlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/utils/from-create-my-entity-input-to-universal-flat-my-entity.util';
-import { WorkspaceMigrationBuilderException } from 'src/engine/workspace-manager/workspace-migration/exceptions/workspace-migration-builder-exception';
-import { WorkspaceMigrationValidateBuildAndRunService } from 'src/engine/workspace-manager/workspace-migration/services/workspace-migration-validate-build-and-run-service';
-
-@Injectable()
-export class MyEntityService {
-  constructor(
-    private readonly workspaceMigrationValidateBuildAndRunService: WorkspaceMigrationValidateBuildAndRunService,
-    private readonly workspaceManyOrAllFlatEntityMapsCacheService: WorkspaceManyOrAllFlatEntityMapsCacheService,
-  ) {}
-
-  async create(input: CreateMyEntityInput, workspaceId: string): Promise<FlatMyEntity> {
-    // 1. Transform input to universal flat entity
-    const universalFlatMyEntityToCreate = fromCreateMyEntityInputToUniversalFlatMyEntity({
-      input,
-      workspaceId,
-    });
-
-    // 2. Validate, build, and run
-    const result =
-      await this.workspaceMigrationValidateBuildAndRunService.validateBuildAndRunWorkspaceMigration(
-        {
-          allFlatEntityOperationByMetadataName: {
-            myEntity: {
-              flatEntityToCreate: [universalFlatMyEntityToCreate],
-              flatEntityToDelete: [],
-              flatEntityToUpdate: [],
-            },
-          },
-          workspaceId,
-          isSystemBuild: false,
-        },
-      );
-
-    // 3. Throw if validation failed
-    if (isDefined(result)) {
-      throw new WorkspaceMigrationBuilderException(
-        result,
-        'Validation errors occurred while creating entity',
-      );
-    }
-
-    // 4. Return freshly cached flat entity
-    const { flatMyEntityMaps } =
-      await this.workspaceManyOrAllFlatEntityMapsCacheService.getOrRecomputeManyOrAllFlatEntityMaps(
-        {
-          workspaceId,
-          flatMapsKeys: ['flatMyEntityMaps'],
-        },
-      );
-
-    return findFlatEntityByIdInFlatEntityMapsOrThrow({
-      flatEntityId: universalFlatMyEntityToCreate.id,
-      flatEntityMaps: flatMyEntityMaps,
-    });
-  }
-}
-```
-
-**Service pattern**:
-1. Transform input → universal flat entity
-2. Call `validateBuildAndRunWorkspaceMigration`
-3. Throw if validation errors
-4. **Return flat entity** (not DTO)
-
----
-
-## Step 5: Create Resolver Layer
-
-**File**: `src/engine/metadata-modules/my-entity/my-entity.resolver.ts`
-
-```typescript
-import { UseInterceptors } from '@nestjs/common';
-import { Args, Mutation, Resolver } from '@nestjs/graphql';
-
-import { WorkspaceMigrationGraphqlApiExceptionInterceptor } from 'src/engine/workspace-manager/workspace-migration/interceptors/workspace-migration-graphql-api-exception.interceptor';
-import { MyEntityService } from 'src/engine/metadata-modules/my-entity/my-entity.service';
-import { fromFlatMyEntityToMyEntityDto } from 'src/engine/metadata-modules/my-entity/utils/from-flat-my-entity-to-my-entity-dto.util';
-
-@Resolver(() => MyEntityDto)
-@UseInterceptors(WorkspaceMigrationGraphqlApiExceptionInterceptor)
-export class MyEntityResolver {
-  constructor(private readonly myEntityService: MyEntityService) {}
-
-  @Mutation(() => MyEntityDto)
-  async createMyEntity(
-    @Args('input') input: CreateMyEntityInput,
-    @Workspace() { id: workspaceId }: Workspace,
-  ): Promise<MyEntityDto> {
-    // Service returns flat entity
-    const flatMyEntity = await this.myEntityService.create(input, workspaceId);
-    
-    // Resolver converts flat entity to DTO
-    return fromFlatMyEntityToMyEntityDto(flatMyEntity);
-  }
-
-  @Mutation(() => MyEntityDto)
-  async updateMyEntity(
-    @Args('id') id: string,
-    @Args('input') input: UpdateMyEntityInput,
-    @Workspace() { id: workspaceId }: Workspace,
-  ): Promise<MyEntityDto> {
-    const flatMyEntity = await this.myEntityService.update(id, input, workspaceId);
-    return fromFlatMyEntityToMyEntityDto(flatMyEntity);
-  }
-
-  @Mutation(() => Boolean)
-  async deleteMyEntity(
-    @Args('id') id: string,
-    @Workspace() { id: workspaceId }: Workspace,
-  ) {
-    await this.myEntityService.delete(id, workspaceId);
-    return true;
-  }
-}
-```
-
-**Resolver responsibilities**:
-- Receives flat entities from service
-- **Converts flat → DTO** using conversion utility
-- Returns DTOs to GraphQL API
-- Uses exception interceptor for error formatting
-
----
-
-## Step 6: Flat-to-DTO Conversion
-
-**File**: `src/engine/metadata-modules/my-entity/utils/from-flat-my-entity-to-my-entity-dto.util.ts`
-
-```typescript
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-import { type MyEntityDto } from 'src/engine/metadata-modules/my-entity/dtos/my-entity.dto';
-
-export const fromFlatMyEntityToMyEntityDto = (
-  flatMyEntity: FlatMyEntity,
-): MyEntityDto => {
-  return {
-    id: flatMyEntity.id,
-    name: flatMyEntity.name,
-    label: flatMyEntity.label,
-    description: flatMyEntity.description,
-    isCustom: flatMyEntity.isCustom,
-    createdAt: flatMyEntity.createdAt,
-    updatedAt: flatMyEntity.updatedAt,
-    // Convert foreign key IDs to relation objects if needed
-    // parentEntity: flatMyEntity.parentEntityId ? { id: flatMyEntity.parentEntityId } : null,
-  };
-};
-```
-
----
-
-## Layer Responsibilities
-
-| Layer | Input | Output | Responsibility |
-|-------|-------|--------|----------------|
-| **Service** | Input DTO | Flat Entity | Business logic, validation orchestration |
-| **Resolver** | Service result | DTO | Flat → DTO conversion, GraphQL exposure |
-
-**Service Layer**:
-- Works with flat entities internally
-- Returns `FlatMyEntity` type
-- No knowledge of DTOs or GraphQL types
-
-**Resolver Layer**:
-- Receives flat entities from service
-- Converts flat entities to DTOs
-- Returns DTOs to GraphQL API
-
----
-
-## Exception Interceptor
-
-The `WorkspaceMigrationGraphqlApiExceptionInterceptor` automatically handles:
-
-1. `FlatEntityMapsException` → Converts to GraphQL errors (NotFoundError, etc.)
-2. `WorkspaceMigrationBuilderException` → Formats validation errors with i18n
-3. `WorkspaceMigrationRunnerException` → Formats runner errors
-
-**What it does**:
-- Catches exceptions and formats for API responses
-- Translates error messages based on user locale
-- Ensures consistent error structure for frontend
-
----
-
-## Checklist
-
-Before moving to Step 6 (Testing):
-
-- [ ] Builder registered in builder module (providers + exports)
-- [ ] Validator registered in validators module (providers + exports)
-- [ ] All 3 action handlers registered in action handlers module (providers)
-- [ ] Service layer created
-- [ ] Service returns flat entities (not DTOs)
-- [ ] Resolver layer created
-- [ ] Resolver uses exception interceptor
-- [ ] Resolver converts flat → DTO
-- [ ] Flat-to-DTO conversion utility created
-
----
-
-## Next Step
-
-Once integration is complete, proceed to (**MANDATORY**):
-**[Syncable Entity: Integration Testing (Step 6/6)](../syncable-entity-testing/SKILL.md)**
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/skills/syncable-entity-runner-and-actions/SKILL.md

@@ -1,355 +0,0 @@
----
-name: syncable-entity-runner-and-actions
-description: Implement action handlers for executing workspace migrations in Twenty. Use when creating database operations for syncable entities, implementing universal-to-flat entity transpilation, or handling create/update/delete actions in the runner layer.
----
-
-# Syncable Entity: Runner & Actions (Step 4/6)
-
-**Purpose**: Execute migration actions against the database with proper transpilation from universal to flat entities.
-
-**When to use**: After completing Steps 1-3 (Types, Cache, Builder). Required before integration.
-
----
-
-## Quick Start
-
-This step creates:
-1. Create action handler
-2. Update action handler
-3. Delete action handler
-4. Universal-to-flat conversion utilities
-
-**Key pattern**: Each handler has two phases:
-1. **Transpilation**: Universal action → Flat action
-2. **Execution**: Flat action → Database operation
-
----
-
-## Step 1: Create Action Handler
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/create-my-entity-action-handler.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { InjectRepository } from '@nestjs/typeorm';
-import { Repository } from 'typeorm';
-
-import { WorkspaceCreateActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/workspace-create-action-handler.service';
-import { MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { fromUniversalFlatMyEntityToFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/utils/from-universal-flat-my-entity-to-flat-my-entity.util';
-import {
-  type UniversalCreateMyEntityAction,
-  type FlatCreateMyEntityAction,
-} from 'src/engine/workspace-manager/workspace-migration/workspace-migration-builder/builders/my-entity/types/workspace-migration-my-entity-action.type';
-
-@Injectable()
-export class CreateMyEntityActionHandlerService extends WorkspaceCreateActionHandlerService<
-  'myEntity',
-  UniversalCreateMyEntityAction,
-  FlatCreateMyEntityAction
-> {
-  constructor(
-    @InjectRepository(MyEntityEntity, 'metadata')
-    private readonly myEntityRepository: Repository<MyEntityEntity>,
-  ) {
-    super();
-  }
-
-  // Phase 1: Transpile universal action to flat action
-  protected transpileUniversalActionToFlatAction(
-    universalAction: UniversalCreateMyEntityAction,
-    flatEntityMaps: AllFlatEntityMapsByMetadataName,
-  ): FlatCreateMyEntityAction {
-    return {
-      type: 'create',
-      metadataName: 'myEntity',
-      flatEntity: fromUniversalFlatMyEntityToFlatMyEntity(
-        universalAction.universalFlatEntity,
-        flatEntityMaps,
-      ),
-    };
-  }
-
-  // Phase 2: Execute flat action against database
-  protected async executeForMetadata(
-    flatActions: FlatCreateMyEntityAction[],
-  ): Promise<void> {
-    const flatEntities = flatActions.map((action) => action.flatEntity);
-
-    await this.insertFlatEntitiesInRepository({
-      repository: this.myEntityRepository,
-      flatEntities,
-    });
-  }
-
-  protected async executeForWorkspaceSchema(): Promise<void> {
-    // No workspace schema changes needed for metadata-only entity
-    return;
-  }
-}
-```
-
-**Key helper methods**:
-- `transpileUniversalActionToFlatAction`: Converts universal → flat
-- `insertFlatEntitiesInRepository`: Base class helper for inserts
-- `executeForMetadata`: Metadata database operations
-- `executeForWorkspaceSchema`: Workspace schema changes (if needed)
-
----
-
-## Step 2: Update Action Handler
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/update-my-entity-action-handler.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { InjectRepository } from '@nestjs/typeorm';
-import { Repository } from 'typeorm';
-
-import { WorkspaceUpdateActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/workspace-update-action-handler.service';
-import { MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { fromUniversalFlatMyEntityToFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/utils/from-universal-flat-my-entity-to-flat-my-entity.util';
-import { resolveUniversalUpdateRelationIdentifiersToIds } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/utils/resolve-universal-relation-identifiers-to-ids.util';
-
-@Injectable()
-export class UpdateMyEntityActionHandlerService extends WorkspaceUpdateActionHandlerService<
-  'myEntity',
-  UniversalUpdateMyEntityAction,
-  FlatUpdateMyEntityAction
-> {
-  constructor(
-    @InjectRepository(MyEntityEntity, 'metadata')
-    private readonly myEntityRepository: Repository<MyEntityEntity>,
-  ) {
-    super();
-  }
-
-  protected transpileUniversalActionToFlatAction(
-    universalAction: UniversalUpdateMyEntityAction,
-    flatEntityMaps: AllFlatEntityMapsByMetadataName,
-  ): FlatUpdateMyEntityAction {
-    const flatEntity = fromUniversalFlatMyEntityToFlatMyEntity(
-      universalAction.universalFlatEntity,
-      flatEntityMaps,
-    );
-
-    // Resolve universal foreign keys in updates to regular IDs
-    const flatUpdates = resolveUniversalUpdateRelationIdentifiersToIds({
-      metadataName: 'myEntity',
-      universalUpdates: universalAction.universalUpdates,
-      flatEntityMaps,
-    });
-
-    return {
-      type: 'update',
-      metadataName: 'myEntity',
-      flatEntity,
-      updates: flatUpdates,
-    };
-  }
-
-  protected async executeForMetadata(
-    flatActions: FlatUpdateMyEntityAction[],
-  ): Promise<void> {
-    for (const action of flatActions) {
-      await this.myEntityRepository.update(
-        { id: action.flatEntity.id },
-        action.updates,
-      );
-    }
-  }
-
-  protected async executeForWorkspaceSchema(): Promise<void> {
-    return;
-  }
-}
-```
-
-**Update-specific helper**:
-- `resolveUniversalUpdateRelationIdentifiersToIds`: Maps universal identifiers back to regular IDs in the updates object
-
----
-
-## Step 3: Delete Action Handler
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/services/delete-my-entity-action-handler.service.ts`
-
-```typescript
-import { Injectable } from '@nestjs/common';
-import { InjectRepository } from '@nestjs/typeorm';
-import { Repository } from 'typeorm';
-
-import { WorkspaceDeleteActionHandlerService } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/workspace-delete-action-handler.service';
-import { MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-import { fromUniversalFlatMyEntityToFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/utils/from-universal-flat-my-entity-to-flat-my-entity.util';
-
-@Injectable()
-export class DeleteMyEntityActionHandlerService extends WorkspaceDeleteActionHandlerService<
-  'myEntity',
-  UniversalDeleteMyEntityAction,
-  FlatDeleteMyEntityAction
-> {
-  constructor(
-    @InjectRepository(MyEntityEntity, 'metadata')
-    private readonly myEntityRepository: Repository<MyEntityEntity>,
-  ) {
-    super();
-  }
-
-  protected transpileUniversalActionToFlatAction(
-    universalAction: UniversalDeleteMyEntityAction,
-    flatEntityMaps: AllFlatEntityMapsByMetadataName,
-  ): FlatDeleteMyEntityAction {
-    // Use base class helper for delete transpilation
-    return this.transpileUniversalDeleteActionToFlatDeleteAction({
-      universalAction,
-      flatEntityMaps,
-      fromUniversalFlatEntityToFlatEntity: fromUniversalFlatMyEntityToFlatMyEntity,
-    });
-  }
-
-  protected async executeForMetadata(
-    flatActions: FlatDeleteMyEntityAction[],
-  ): Promise<void> {
-    const ids = flatActions.map((action) => action.flatEntity.id);
-
-    await this.myEntityRepository.delete(ids);
-  }
-
-  protected async executeForWorkspaceSchema(): Promise<void> {
-    return;
-  }
-}
-```
-
-**Delete-specific helper**:
-- `transpileUniversalDeleteActionToFlatDeleteAction`: Base class helper that handles standard delete transpilation
-
----
-
-## Step 4: Universal-to-Flat Conversion
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-runner/action-handlers/my-entity/utils/from-universal-flat-my-entity-to-flat-my-entity.util.ts`
-
-```typescript
-import { resolveUniversalRelationIdentifiersToIds } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/utils/resolve-universal-relation-identifiers-to-ids.util';
-import { type UniversalFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/types/universal-flat-my-entity.type';
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-import { type AllFlatEntityMapsByMetadataName } from 'src/engine/metadata-modules/flat-entity/types/all-flat-entity-maps-by-metadata-name.type';
-
-export const fromUniversalFlatMyEntityToFlatMyEntity = (
-  universalFlatMyEntity: UniversalFlatMyEntity,
-  flatEntityMaps: AllFlatEntityMapsByMetadataName,
-): FlatMyEntity => {
-  // Resolve universal foreign keys back to regular IDs
-  return resolveUniversalRelationIdentifiersToIds({
-    metadataName: 'myEntity',
-    universalFlatEntity: universalFlatMyEntity,
-    flatEntityMaps,
-  }) as FlatMyEntity;
-};
-```
-
-**Key utility**:
-- `resolveUniversalRelationIdentifiersToIds`: Maps universal identifiers → regular IDs (reverse of `resolveEntityRelationUniversalIdentifiers`)
-
----
-
-## Action Handler Patterns
-
-### Pattern: Create Handler
-```typescript
-// 1. Transpile: Universal → Flat
-protected transpileUniversalActionToFlatAction(
-  universalAction,
-  flatEntityMaps,
-) {
-  return {
-    type: 'create',
-    metadataName: 'myEntity',
-    flatEntity: fromUniversalFlatMyEntityToFlatMyEntity(
-      universalAction.universalFlatEntity,
-      flatEntityMaps,
-    ),
-  };
-}
-
-// 2. Execute: Flat → Database
-protected async executeForMetadata(flatActions) {
-  await this.insertFlatEntitiesInRepository({
-    repository: this.myEntityRepository,
-    flatEntities: flatActions.map(a => a.flatEntity),
-  });
-}
-```
-
-### Pattern: Update Handler
-```typescript
-// Transpile with update-specific resolution
-protected transpileUniversalActionToFlatAction(
-  universalAction,
-  flatEntityMaps,
-) {
-  const flatEntity = fromUniversalFlatMyEntityToFlatMyEntity(
-    universalAction.universalFlatEntity,
-    flatEntityMaps,
-  );
-
-  const flatUpdates = resolveUniversalUpdateRelationIdentifiersToIds({
-    metadataName: 'myEntity',
-    universalUpdates: universalAction.universalUpdates,
-    flatEntityMaps,
-  });
-
-  return { type: 'update', metadataName: 'myEntity', flatEntity, updates: flatUpdates };
-}
-```
-
-### Pattern: Delete Handler
-```typescript
-// Use base class helper
-protected transpileUniversalActionToFlatAction(
-  universalAction,
-  flatEntityMaps,
-) {
-  return this.transpileUniversalDeleteActionToFlatDeleteAction({
-    universalAction,
-    flatEntityMaps,
-    fromUniversalFlatEntityToFlatEntity: fromUniversalFlatMyEntityToFlatMyEntity,
-  });
-}
-
-// Delete
-protected async executeForMetadata(flatActions) {
-  const ids = flatActions.map(a => a.flatEntity.id);
-  await this.myEntityRepository.delete(ids);
-}
-```
-
----
-
-## Checklist
-
-Before moving to Step 5:
-
-- [ ] Create action handler implemented
-- [ ] Update action handler implemented
-- [ ] Delete action handler implemented
-- [ ] All handlers extend appropriate base class
-- [ ] `transpileUniversalActionToFlatAction` implemented in all handlers
-- [ ] `executeForMetadata` implemented in all handlers
-- [ ] `executeForWorkspaceSchema` implemented (or returns empty)
-- [ ] Universal-to-flat conversion utility created
-- [ ] Create handler uses `insertFlatEntitiesInRepository`
-- [ ] Update handler uses `resolveUniversalUpdateRelationIdentifiersToIds`
-- [ ] Delete handler uses `transpileUniversalDeleteActionToFlatDeleteAction`
-- [ ] Delete handler uses hard delete (`delete()`)
-
----
-
-## Next Step
-
-Once action handlers are complete, proceed to:
-**[Syncable Entity: Integration (Step 5/6)](../syncable-entity-integration/SKILL.md)**
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/skills/syncable-entity-testing/SKILL.md

@@ -1,494 +0,0 @@
----
-name: syncable-entity-testing
-description: Create comprehensive integration tests for syncable entities in Twenty. Use when writing integration tests for metadata entities, covering validator exceptions, input transpilation errors, and CRUD operations. Tests are MANDATORY for all syncable entities.
----
-
-# Syncable Entity: Integration Testing (Step 6/6 - MANDATORY)
-
-**Purpose**: Create comprehensive test suite covering all validation scenarios, input transpilation exceptions, and successful use cases.
-
-**When to use**: After completing Steps 1-5. Integration tests are **REQUIRED** for all syncable entities.
-
----
-
-## Quick Start
-
-Tests must cover:
-1. **Failing scenarios** - All validator exceptions and input transpilation errors
-2. **Successful scenarios** - All CRUD operations and edge cases
-3. **Test utilities** - Reusable query factories and helper functions
-
-**Test pattern**: Two-file pattern (query factory + wrapper) for each operation.
-
----
-
-## Step 1: Create Test Utilities
-
-### Pattern: Query Factory
-
-**File**: `test/integration/metadata/suites/my-entity/utils/create-my-entity-query-factory.util.ts`
-
-```typescript
-import gql from 'graphql-tag';
-import { type PerformMetadataQueryParams } from 'test/integration/metadata/types/perform-metadata-query.type';
-import { type CreateMyEntityInput } from 'src/engine/metadata-modules/my-entity/dtos/create-my-entity.input';
-
-export type CreateMyEntityFactoryInput = CreateMyEntityInput;
-
-const DEFAULT_MY_ENTITY_GQL_FIELDS = `
-  id
-  name
-  label
-  description
-  isCustom
-  createdAt
-  updatedAt
-`;
-
-export const createMyEntityQueryFactory = ({
-  input,
-  gqlFields = DEFAULT_MY_ENTITY_GQL_FIELDS,
-}: PerformMetadataQueryParams<CreateMyEntityFactoryInput>) => ({
-  query: gql`
-    mutation CreateMyEntity($input: CreateMyEntityInput!) {
-      createMyEntity(input: $input) {
-        ${gqlFields}
-      }
-    }
-  `,
-  variables: {
-    input,
-  },
-});
-```
-
-### Pattern: Wrapper Utility
-
-**File**: `test/integration/metadata/suites/my-entity/utils/create-my-entity.util.ts`
-
-```typescript
-import {
-  type CreateMyEntityFactoryInput,
-  createMyEntityQueryFactory,
-} from 'test/integration/metadata/suites/my-entity/utils/create-my-entity-query-factory.util';
-import { makeMetadataAPIRequest } from 'test/integration/metadata/suites/utils/make-metadata-api-request.util';
-import { type CommonResponseBody } from 'test/integration/metadata/types/common-response-body.type';
-import { type PerformMetadataQueryParams } from 'test/integration/metadata/types/perform-metadata-query.type';
-import { warnIfErrorButNotExpectedToFail } from 'test/integration/metadata/utils/warn-if-error-but-not-expected-to-fail.util';
-import { warnIfNoErrorButExpectedToFail } from 'test/integration/metadata/utils/warn-if-no-error-but-expected-to-fail.util';
-import { type MyEntityDto } from 'src/engine/metadata-modules/my-entity/dtos/my-entity.dto';
-
-export const createMyEntity = async ({
-  input,
-  gqlFields,
-  expectToFail = false,
-  token,
-}: PerformMetadataQueryParams<CreateMyEntityFactoryInput>): CommonResponseBody<{
-  createMyEntity: MyEntityDto;
-}> => {
-  const graphqlOperation = createMyEntityQueryFactory({
-    input,
-    gqlFields,
-  });
-
-  const response = await makeMetadataAPIRequest(graphqlOperation, token);
-
-  if (expectToFail === true) {
-    warnIfNoErrorButExpectedToFail({
-      response,
-      errorMessage: 'My entity creation should have failed but did not',
-    });
-  }
-
-  if (expectToFail === false) {
-    warnIfErrorButNotExpectedToFail({
-      response,
-      errorMessage: 'My entity creation has failed but should not',
-    });
-  }
-
-  return { data: response.body.data, errors: response.body.errors };
-};
-```
-
-**Required utilities** (follow same pattern):
-- `update-my-entity-query-factory.util.ts` + `update-my-entity.util.ts`
-- `delete-my-entity-query-factory.util.ts` + `delete-my-entity.util.ts`
-
----
-
-## Step 2: Failing Creation Tests
-
-**File**: `test/integration/metadata/suites/my-entity/failing-my-entity-creation.integration-spec.ts`
-
-```typescript
-import { expectOneNotInternalServerErrorSnapshot } from 'test/integration/graphql/utils/expect-one-not-internal-server-error-snapshot.util';
-import { createMyEntity } from 'test/integration/metadata/suites/my-entity/utils/create-my-entity.util';
-import { deleteMyEntity } from 'test/integration/metadata/suites/my-entity/utils/delete-my-entity.util';
-import {
-  eachTestingContextFilter,
-  type EachTestingContext,
-} from 'twenty-shared/testing';
-import { isDefined } from 'twenty-shared/utils';
-import { type CreateMyEntityInput } from 'src/engine/metadata-modules/my-entity/dtos/create-my-entity.input';
-
-type TestContext = {
-  input: CreateMyEntityInput;
-};
-
-type GlobalTestContext = {
-  existingEntityLabel: string;
-  existingEntityName: string;
-};
-
-const globalTestContext: GlobalTestContext = {
-  existingEntityLabel: 'Existing Test Entity',
-  existingEntityName: 'existingTestEntity',
-};
-
-type CreateMyEntityTestingContext = EachTestingContext<TestContext>[];
-
-describe('My entity creation should fail', () => {
-  let existingEntityId: string | undefined;
-
-  beforeAll(async () => {
-    // Setup: Create entity for uniqueness tests
-    const { data } = await createMyEntity({
-      expectToFail: false,
-      input: {
-        name: globalTestContext.existingEntityName,
-        label: globalTestContext.existingEntityLabel,
-      },
-    });
-
-    existingEntityId = data.createMyEntity.id;
-  });
-
-  afterAll(async () => {
-    // Cleanup
-    if (isDefined(existingEntityId)) {
-      await deleteMyEntity({
-        expectToFail: false,
-        input: { id: existingEntityId },
-      });
-    }
-  });
-
-  const failingMyEntityCreationTestCases: CreateMyEntityTestingContext = [
-    // Input transpilation validation
-    {
-      title: 'when name is missing',
-      context: {
-        input: {
-          label: 'Entity Missing Name',
-        } as CreateMyEntityInput,
-      },
-    },
-    {
-      title: 'when label is missing',
-      context: {
-        input: {
-          name: 'entityMissingLabel',
-        } as CreateMyEntityInput,
-      },
-    },
-    {
-      title: 'when name is empty string',
-      context: {
-        input: {
-          name: '',
-          label: 'Empty Name Entity',
-        },
-      },
-    },
-
-    // Validator business logic
-    {
-      title: 'when name already exists (uniqueness)',
-      context: {
-        input: {
-          name: globalTestContext.existingEntityName,
-          label: 'Duplicate Name Entity',
-        },
-      },
-    },
-    {
-      title: 'when trying to create standard entity',
-      context: {
-        input: {
-          name: 'myEntity',
-          label: 'Standard Entity',
-          isCustom: false,
-        } as CreateMyEntityInput,
-      },
-    },
-
-    // Foreign key validation
-    {
-      title: 'when parentEntityId does not exist',
-      context: {
-        input: {
-          name: 'invalidParentEntity',
-          label: 'Invalid Parent Entity',
-          parentEntityId: '00000000-0000-0000-0000-000000000000',
-        },
-      },
-    },
-  ];
-
-  it.each(eachTestingContextFilter(failingMyEntityCreationTestCases))(
-    '$title',
-    async ({ context }) => {
-      const { errors } = await createMyEntity({
-        expectToFail: true,
-        input: context.input,
-      });
-
-      expectOneNotInternalServerErrorSnapshot({
-        errors,
-      });
-    },
-  );
-});
-```
-
-**Test coverage requirements**:
-- ✅ Missing required fields
-- ✅ Empty strings
-- ✅ Invalid format
-- ✅ Uniqueness violations
-- ✅ Standard entity protection
-- ✅ Foreign key validation
-
----
-
-## Step 3: Successful Creation Tests
-
-**File**: `test/integration/metadata/suites/my-entity/successful-my-entity-creation.integration-spec.ts`
-
-```typescript
-import { createMyEntity } from 'test/integration/metadata/suites/my-entity/utils/create-my-entity.util';
-import { deleteMyEntity } from 'test/integration/metadata/suites/my-entity/utils/delete-my-entity.util';
-import { type CreateMyEntityInput } from 'src/engine/metadata-modules/my-entity/dtos/create-my-entity.input';
-
-describe('My entity creation should succeed', () => {
-  let createdEntityId: string;
-
-  afterEach(async () => {
-    if (createdEntityId) {
-      await deleteMyEntity({
-        expectToFail: false,
-        input: { id: createdEntityId },
-      });
-    }
-  });
-
-  it('should create entity with minimal required input', async () => {
-    const { data } = await createMyEntity({
-      expectToFail: false,
-      input: {
-        name: 'minimalEntity',
-        label: 'Minimal Entity',
-      },
-    });
-
-    createdEntityId = data?.createMyEntity?.id;
-
-    expect(data.createMyEntity).toMatchObject({
-      id: expect.any(String),
-      name: 'minimalEntity',
-      label: 'Minimal Entity',
-      description: null,
-      isCustom: true,
-      createdAt: expect.any(String),
-      updatedAt: expect.any(String),
-    });
-  });
-
-  it('should create entity with all optional fields', async () => {
-    const input = {
-      name: 'fullEntity',
-      label: 'Full Entity',
-      description: 'Entity with all fields specified',
-    } as const satisfies CreateMyEntityInput;
-
-    const { data } = await createMyEntity({
-      expectToFail: false,
-      input,
-    });
-
-    createdEntityId = data?.createMyEntity?.id;
-
-    expect(data.createMyEntity).toMatchObject({
-      id: expect.any(String),
-      name: 'fullEntity',
-      label: 'Full Entity',
-      description: 'Entity with all fields specified',
-      isCustom: true,
-    });
-  });
-
-  it('should sanitize input by trimming whitespace', async () => {
-    const { data } = await createMyEntity({
-      expectToFail: false,
-      input: {
-        name: '  entityWithSpaces  ',
-        label: '  Entity With Spaces  ',
-        description: '  Description with spaces  ',
-      },
-    });
-
-    createdEntityId = data?.createMyEntity?.id;
-
-    expect(data.createMyEntity).toMatchObject({
-      id: expect.any(String),
-      name: 'entityWithSpaces',
-      label: 'Entity With Spaces',
-      description: 'Description with spaces',
-    });
-  });
-
-  it('should handle long text content', async () => {
-    const longDescription = 'A'.repeat(1000);
-
-    const { data } = await createMyEntity({
-      expectToFail: false,
-      input: {
-        name: 'longDescEntity',
-        label: 'Long Description Entity',
-        description: longDescription,
-      },
-    });
-
-    createdEntityId = data?.createMyEntity?.id;
-
-    expect(data.createMyEntity).toMatchObject({
-      id: expect.any(String),
-      description: longDescription,
-    });
-  });
-});
-```
-
-**Test coverage requirements**:
-- ✅ Minimal required input
-- ✅ All optional fields
-- ✅ Input sanitization
-- ✅ Long text content
-- ✅ Special characters
-
----
-
-## Step 4: Update and Delete Tests
-
-Create similar test files for update and delete operations:
-
-**Required files**:
-- `failing-my-entity-update.integration-spec.ts`
-- `successful-my-entity-update.integration-spec.ts`
-- `failing-my-entity-deletion.integration-spec.ts`
-- `successful-my-entity-deletion.integration-spec.ts`
-
----
-
-## Testing Best Practices
-
-### Pattern: Cleanup
-```typescript
-afterEach(async () => {
-  if (createdEntityId) {
-    await deleteMyEntity({
-      expectToFail: false,
-      input: { id: createdEntityId },
-    });
-  }
-});
-```
-
-### Pattern: Type-Safe Inputs
-```typescript
-const input = {
-  name: 'myEntity',
-  label: 'My Entity',
-} as const satisfies CreateMyEntityInput;
-```
-
-### Pattern: Snapshot Testing
-```typescript
-expectOneNotInternalServerErrorSnapshot({
-  errors,
-});
-```
-
----
-
-## Running Tests
-
-```bash
-# Run all entity tests
-npx jest test/integration/metadata/suites/my-entity --config=packages/twenty-server/jest.config.mjs
-
-# Run specific test file
-npx jest test/integration/metadata/suites/my-entity/failing-my-entity-creation.integration-spec.ts --config=packages/twenty-server/jest.config.mjs
-
-# Update snapshots
-npx jest test/integration/metadata/suites/my-entity --updateSnapshot --config=packages/twenty-server/jest.config.mjs
-```
-
----
-
-## Complete Test Checklist
-
-### Test Utilities
-- [ ] `create-my-entity-query-factory.util.ts` created
-- [ ] `create-my-entity.util.ts` created
-- [ ] `update-my-entity-query-factory.util.ts` created
-- [ ] `update-my-entity.util.ts` created
-- [ ] `delete-my-entity-query-factory.util.ts` created
-- [ ] `delete-my-entity.util.ts` created
-
-### Failing Tests Coverage
-- [ ] Missing required fields
-- [ ] Empty string validation
-- [ ] Uniqueness violations
-- [ ] Standard entity protection
-- [ ] Foreign key validation
-- [ ] JSONB property validation (if applicable)
-
-### Successful Tests Coverage
-- [ ] Create with minimal input
-- [ ] Create with all optional fields
-- [ ] Input sanitization (whitespace)
-- [ ] Long text content
-- [ ] Update single field
-- [ ] Update multiple fields
-- [ ] Successful deletion
-
-### Snapshot Tests
-- [ ] All failing tests use `expectOneNotInternalServerErrorSnapshot`
-- [ ] Snapshots committed to `__snapshots__/` directory
-
----
-
-## Success Criteria
-
-Your integration tests are complete when:
-
-✅ All test utilities created (minimum 6 files)
-✅ Failing creation tests cover all validators
-✅ Failing update tests cover business rules
-✅ Failing deletion tests cover protection rules
-✅ Successful tests cover all use cases
-✅ All snapshots generated and committed
-✅ All tests pass consistently
-✅ Test coverage meets requirements (>80%)
-
----
-
-## Final Step
-
-✅ **Step 6 Complete!** → Your syncable entity is fully tested and production-ready!
-
-**Congratulations!** You've successfully created a new syncable entity in Twenty's workspace migration system.
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/skills/syncable-entity-types-and-constants/SKILL.md

@@ -1,340 +0,0 @@
----
-name: syncable-entity-types-and-constants
-description: Define types, entities, and central constant registrations for syncable entities in Twenty's workspace migration system. Use when creating new syncable entities, defining TypeORM entities, flat entity types, or registering in central constants (ALL_ENTITY_PROPERTIES_CONFIGURATION_BY_METADATA_NAME, ALL_ONE_TO_MANY_METADATA_RELATIONS, ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY, ALL_MANY_TO_ONE_METADATA_RELATIONS).
----
-
-# Syncable Entity: Types & Constants (Step 1/6)
-
-**Purpose**: Define all types, entities, and register in central constants. This is the foundation - everything else depends on these types being correct.
-
-**When to use**: First step when creating any new syncable entity. Must be completed before other steps.
-
----
-
-## Quick Start
-
-This step creates:
-1. Metadata name constant (twenty-shared)
-2. TypeORM entity (extends `SyncableEntity`)
-3. Flat entity types
-4. Action types (universal + flat)
-5. Central constant registrations (5 constants)
-
----
-
-## Step 1: Add Metadata Name
-
-**File**: `packages/twenty-shared/src/metadata/all-metadata-name.constant.ts`
-
-```typescript
-export const ALL_METADATA_NAME = {
-  // ... existing entries
-  myEntity: 'myEntity',
-} as const;
-```
-
----
-
-## Step 2: Create TypeORM Entity
-
-**File**: `src/engine/metadata-modules/my-entity/entities/my-entity.entity.ts`
-
-```typescript
-import { Entity, Column, ManyToOne, JoinColumn } from 'typeorm';
-import { SyncableEntity } from 'src/engine/workspace-manager/types/syncable-entity.interface';
-
-@Entity({ name: 'myEntity' })
-export class MyEntityEntity extends SyncableEntity {
-  @Column({ type: 'varchar' })
-  name: string;
-
-  @Column({ type: 'varchar' })
-  label: string;
-
-  @Column({ type: 'boolean', default: true })
-  isCustom: boolean;
-
-  // Foreign key example (optional)
-  @Column({ type: 'uuid', nullable: true })
-  parentEntityId: string | null;
-
-  @ManyToOne(() => ParentEntityEntity, { nullable: true })
-  @JoinColumn({ name: 'parentEntityId' })
-  parentEntity: ParentEntityEntity | null;
-
-  // JSONB column example (optional)
-  @Column({ type: 'jsonb', nullable: true })
-  settings: Record<string, any> | null;
-}
-```
-
-**Key rules**:
-- Must extend `SyncableEntity` (provides `id`, `universalIdentifier`, `applicationId`, etc.)
-- Must have `isCustom` boolean column
-- Use `@Column({ type: 'jsonb' })` for JSON data
-
----
-
-## Step 3: Define Flat Entity Types
-
-**File**: `src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type.ts`
-
-```typescript
-import { type FlatEntityFrom } from 'src/engine/metadata-modules/flat-entity/types/flat-entity-from.type';
-import { type MyEntityEntity } from 'src/engine/metadata-modules/my-entity/entities/my-entity.entity';
-
-export type FlatMyEntity = FlatEntityFrom<MyEntityEntity>;
-```
-
-**Maps file** (if entity has indexed lookups):
-
-```typescript
-// flat-my-entity-maps.type.ts
-export type FlatMyEntityMaps = {
-  byId: Record<string, FlatMyEntity>;
-  byName: Record<string, FlatMyEntity>;
-  // Add other indexes as needed
-};
-```
-
----
-
-## Step 4: Define Editable Properties
-
-**File**: `src/engine/metadata-modules/flat-my-entity/constants/editable-flat-my-entity-properties.constant.ts`
-
-```typescript
-export const EDITABLE_FLAT_MY_ENTITY_PROPERTIES = [
-  'name',
-  'label',
-  'description',
-  'parentEntityId',
-  'settings',
-] as const satisfies ReadonlyArray<keyof FlatMyEntity>;
-```
-
-**Rule**: Only include properties that can be updated (exclude `id`, `createdAt`, `universalIdentifier`, etc.)
-
----
-
-## Step 5: Define Action Types
-
-**File**: `src/engine/workspace-manager/workspace-migration/workspace-migration-builder/builders/my-entity/types/workspace-migration-my-entity-action.type.ts`
-
-```typescript
-import { type FlatMyEntity } from 'src/engine/metadata-modules/flat-my-entity/types/flat-my-entity.type';
-import { type UniversalFlatMyEntity } from 'src/engine/workspace-manager/workspace-migration/universal-flat-entity/types/universal-flat-my-entity.type';
-
-// Universal actions (used by builder/runner)
-export type UniversalCreateMyEntityAction = {
-  type: 'create';
-  metadataName: 'myEntity';
-  universalFlatEntity: UniversalFlatMyEntity;
-};
-
-export type UniversalUpdateMyEntityAction = {
-  type: 'update';
-  metadataName: 'myEntity';
-  universalFlatEntity: UniversalFlatMyEntity;
-  universalUpdates: Partial<UniversalFlatMyEntity>;
-};
-
-export type UniversalDeleteMyEntityAction = {
-  type: 'delete';
-  metadataName: 'myEntity';
-  universalFlatEntity: UniversalFlatMyEntity;
-};
-
-// Flat actions (internal to runner)
-export type FlatCreateMyEntityAction = {
-  type: 'create';
-  metadataName: 'myEntity';
-  flatEntity: FlatMyEntity;
-};
-
-export type FlatUpdateMyEntityAction = {
-  type: 'update';
-  metadataName: 'myEntity';
-  flatEntity: FlatMyEntity;
-  updates: Partial<FlatMyEntity>;
-};
-
-export type FlatDeleteMyEntityAction = {
-  type: 'delete';
-  metadataName: 'myEntity';
-  flatEntity: FlatMyEntity;
-};
-```
-
----
-
-## Step 6: Register in Central Constants
-
-### 6a. AllFlatEntityTypesByMetadataName
-
-**File**: `src/engine/metadata-modules/flat-entity/types/all-flat-entity-types-by-metadata-name.ts`
-
-```typescript
-export type AllFlatEntityTypesByMetadataName = {
-  // ... existing entries
-  myEntity: {
-    flatEntityMaps: FlatMyEntityMaps;
-    universalActions: {
-      create: UniversalCreateMyEntityAction;
-      update: UniversalUpdateMyEntityAction;
-      delete: UniversalDeleteMyEntityAction;
-    };
-    flatActions: {
-      create: FlatCreateMyEntityAction;
-      update: FlatUpdateMyEntityAction;
-      delete: FlatDeleteMyEntityAction;
-    };
-    flatEntity: FlatMyEntity;
-    universalFlatEntity: UniversalFlatMyEntity;
-    entity: MyEntityEntity;
-  };
-};
-```
-
-### 6b. ALL_ENTITY_PROPERTIES_CONFIGURATION_BY_METADATA_NAME
-
-**File**: `src/engine/metadata-modules/flat-entity/constant/all-entity-properties-configuration-by-metadata-name.constant.ts`
-
-```typescript
-export const ALL_ENTITY_PROPERTIES_CONFIGURATION_BY_METADATA_NAME = {
-  // ... existing entries
-  myEntity: {
-    name: { toCompare: true },
-    label: { toCompare: true },
-    description: { toCompare: true },
-    parentEntityId: {
-      toCompare: true,
-      universalProperty: 'parentEntityUniversalIdentifier',
-    },
-    settings: {
-      toCompare: true,
-      toStringify: true,
-      universalProperty: 'universalSettings',
-    },
-  },
-} as const;
-```
-
-**Rules**:
-- `toCompare: true` → Editable property (checked for changes)
-- `toStringify: true` → JSONB/object property (needs JSON serialization)
-- `universalProperty` → Maps to universal version (for foreign keys & JSONB with `SerializedRelation`)
-
-### 6c. ALL_ONE_TO_MANY_METADATA_RELATIONS
-
-**File**: `src/engine/metadata-modules/flat-entity/constant/all-one-to-many-metadata-relations.constant.ts`
-
-This constant is **type-checked** — values for `metadataName`, `flatEntityForeignKeyAggregator`, and `universalFlatEntityForeignKeyAggregator` are derived from entity type definitions. The aggregator names follow the pattern: remove trailing `'s'` from the relation property name, then append `Ids` or `UniversalIdentifiers`.
-
-```typescript
-export const ALL_ONE_TO_MANY_METADATA_RELATIONS = {
-  // ... existing entries
-  myEntity: {
-    // If myEntity has a `childEntities: ChildEntityEntity[]` property:
-    childEntities: {
-      metadataName: 'childEntity',
-      flatEntityForeignKeyAggregator: 'childEntityIds',
-      universalFlatEntityForeignKeyAggregator: 'childEntityUniversalIdentifiers',
-    },
-    // null for relations to non-syncable entities
-    someNonSyncableRelation: null,
-  },
-} as const;
-```
-
-### 6d. ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY
-
-**File**: `src/engine/metadata-modules/flat-entity/constant/all-many-to-one-metadata-foreign-key.constant.ts`
-
-Low-level primitive constant. Only contains `foreignKey` — the column name ending in `Id` that stores the foreign key. Type-checked against entity properties.
-
-```typescript
-export const ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY = {
-  // ... existing entries
-  myEntity: {
-    workspace: null,
-    application: null,
-    parentEntity: {
-      foreignKey: 'parentEntityId',
-    },
-  },
-} as const;
-```
-
-### 6e. ALL_MANY_TO_ONE_METADATA_RELATIONS
-
-**File**: `src/engine/metadata-modules/flat-entity/constant/all-many-to-one-metadata-relations.constant.ts`
-
-Derived from both `ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY` (for `foreignKey` type and `universalForeignKey` derivation) and `ALL_ONE_TO_MANY_METADATA_RELATIONS` (for `inverseOneToManyProperty` key constraint). This is the main constant consumed by utils and optimistic tooling.
-
-```typescript
-export const ALL_MANY_TO_ONE_METADATA_RELATIONS = {
-  // ... existing entries
-  myEntity: {
-    workspace: null,
-    application: null,
-    parentEntity: {
-      metadataName: 'parentEntity',
-      foreignKey: 'parentEntityId',
-      inverseOneToManyProperty: 'myEntities',  // key in ALL_ONE_TO_MANY_METADATA_RELATIONS['parentEntity'], or null if no inverse
-      isNullable: false,
-      universalForeignKey: 'parentEntityUniversalIdentifier',
-    },
-  },
-} as const;
-```
-
-**Derivation dependency graph**:
-
-```
-ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY     ALL_ONE_TO_MANY_METADATA_RELATIONS
-(foreignKey only)                        (metadataName, aggregators)
-  │                                        │
-  │ FK type + universalFK derivation       │ inverseOneToManyProperty keys
-  │                                        │
-  └────────────────┬───────────────────────┘
-                   ▼
-    ALL_MANY_TO_ONE_METADATA_RELATIONS
-    (metadataName, foreignKey, inverseOneToManyProperty,
-     isNullable, universalForeignKey)
-```
-
-**Rules**:
-- `workspace: null`, `application: null` — always present, always null (non-syncable relations)
-- `inverseOneToManyProperty` — must be a key in `ALL_ONE_TO_MANY_METADATA_RELATIONS[targetMetadataName]`, or `null` if the target entity doesn't expose an inverse one-to-many relation
-- `universalForeignKey` — derived from `foreignKey` by replacing the `Id` suffix with `UniversalIdentifier`
-- Optimistic utils resolve `flatEntityForeignKeyAggregator` / `universalFlatEntityForeignKeyAggregator` at runtime by looking up `inverseOneToManyProperty` in `ALL_ONE_TO_MANY_METADATA_RELATIONS`
-
----
-
-## Checklist
-
-Before moving to Step 2:
-
-- [ ] Metadata name added to `ALL_METADATA_NAME`
-- [ ] TypeORM entity created (extends `SyncableEntity`)
-- [ ] `isCustom` column added
-- [ ] Flat entity type defined
-- [ ] Flat entity maps type defined (if needed)
-- [ ] Editable properties constant defined
-- [ ] Universal and flat action types defined
-- [ ] Registered in `AllFlatEntityTypesByMetadataName`
-- [ ] Registered in `ALL_ENTITY_PROPERTIES_CONFIGURATION_BY_METADATA_NAME`
-- [ ] Registered in `ALL_ONE_TO_MANY_METADATA_RELATIONS` (if entity has one-to-many relations)
-- [ ] Registered in `ALL_MANY_TO_ONE_METADATA_FOREIGN_KEY`
-- [ ] Registered in `ALL_MANY_TO_ONE_METADATA_RELATIONS`
-- [ ] TypeScript compiles without errors
-
----
-
-## Next Step
-
-Once all types and constants are defined, proceed to:
-**[Syncable Entity: Cache & Transform (Step 2/6)](../syncable-entity-cache-and-transform/SKILL.md)**
-
-For complete workflow, see `@creating-syncable-entity` rule.

.cursor/worktrees.json

@@ -1,8 +0,0 @@
-{
-  "setup-worktree": [
-    "nvm use",
-    "yarn",
-    "cp $ROOT_WORKTREE_PATH/packages/twenty-server/.env packages/twenty-server/.env || true",
-    "cp $ROOT_WORKTREE_PATH/packages/twenty-front/.env packages/twenty-front/.env || true"
-  ]
-}

.github/CONTRIBUTING.md

@@ -63,4 +63,4 @@ git push origin your-branch-name
 
 ## Reporting Issues
 
-If you face any issues or have suggestions, please feel free to [create an issue on Twenty's GitHub repository](https://github.com/twentyhq/twenty/issues/new). Please provide as much detail as possible.
+If you face any issues or have suggestions, please feel free to (create an issue on Twenty's GitHub repository)[https://github.com/twentyhq/twenty/issues/new]. Please provide as much detail as possible.

.github/actions/nx-affected/action.yaml

@@ -1,28 +0,0 @@
-name: Nx Affected CI
-inputs:
-  parallel:
-    required: false
-    default: '3'
-  tag:
-    required: false
-  tasks:
-    required: true
-  configuration:
-    required: false
-    default: 'ci'
-  args:
-    required: false
-runs:
-  using: "composite"
-  steps:
-    - name: Get last successful commit
-      uses: nrwl/nx-set-shas@v4
-    - name: Run affected command
-      shell: bash
-      env:
-        NX_CONFIGURATION: ${{ inputs.configuration }}
-        NX_TASKS: ${{ inputs.tasks }}
-        NX_PARALLEL: ${{ inputs.parallel }}
-        NX_TAG: ${{ inputs.tag }}
-        NX_ARGS: ${{ inputs.args }}
-      run: npx nx affected --nxBail --configuration="$NX_CONFIGURATION" -t="$NX_TASKS" --parallel="$NX_PARALLEL" --exclude="*,!tag:$NX_TAG" $NX_ARGS

.github/actions/restore-cache/action.yaml

@@ -1,38 +0,0 @@
-name: Restore cache
-inputs:
-  key:
-    required: true
-    description: Prefix to the cache key
-  additional-paths:
-    required: false
-outputs:
-  cache-primary-key:
-    description: actions/cache/restore cache-primary-key outputs proxy
-    value: ${{ steps.restore-cache.outputs.cache-primary-key }}
-  cache-hit:
-    description: String bool indicating whether cache has been directly or indirectly hit
-    value: ${{ steps.restore-cache.outputs.cache-hit == 'true' || steps.restore-cache.outputs.cache-matched-key != '' }}
-
-runs:
-  using: composite
-  steps:
-    - name: Cache primary key builder
-      id: cache-primary-key-builder
-      shell: bash
-      env:
-        CACHE_KEY: ${{ inputs.key }}
-        REF_NAME: ${{ github.ref_name }}
-      run: |
-        echo "CACHE_PRIMARY_KEY_PREFIX=v4-${CACHE_KEY}-${REF_NAME}" >> "${GITHUB_OUTPUT}"
-    - name: Restore cache
-      uses: actions/cache/restore@v4
-      id: restore-cache
-      with:
-        key: ${{ steps.cache-primary-key-builder.outputs.CACHE_PRIMARY_KEY_PREFIX }}-${{ github.sha }}
-        restore-keys: ${{ steps.cache-primary-key-builder.outputs.CACHE_PRIMARY_KEY_PREFIX }}-
-        path: |
-          .cache
-          .nx
-          node_modules/.cache
-          packages/*/node_modules/.cache
-          ${{ inputs.additional-paths }}

.github/actions/spawn-twenty-docker-image/action.yaml

@@ -1,80 +0,0 @@
-name: Spawn Twenty Docker Image
-description: >
-  Starts a full Twenty instance (server, worker, database, redis) using Docker
-  Compose. The server is available at http://localhost:3000 for subsequent steps
-  in the caller's job.
-  Pulls the specified semver image tag from Docker Hub.
-  Designed to be consumed from external repositories (e.g., twenty-app).
-
-inputs:
-  twenty-version:
-    description: 'Twenty Docker Hub image tag as semver (e.g., v0.40.0, v1.0.0).'
-    required: true
-  twenty-repository:
-    description: 'Twenty repository to checkout docker compose files from.'
-    required: false
-    default: 'twentyhq/twenty'
-  github-token:
-    description: 'GitHub token for cross-repo checkout. Required when calling from an external repository.'
-    required: false
-    default: ${{ github.token }}
-
-outputs:
-  server-url:
-    description: 'URL where the Twenty server can be reached'
-    value: http://localhost:3000
-  access-token:
-    description: 'Admin access token for the Twenty instance'
-    value: ${{ steps.admin-token.outputs.access-token }}
-
-runs:
-  using: 'composite'
-  steps:
-    - name: Validate version
-      shell: bash
-      run: |
-        VERSION="${{ inputs.twenty-version }}"
-        if ! echo "$VERSION" | grep -qE '^v[0-9]+\.[0-9]+\.[0-9]+$'; then
-          echo "::error::twenty-version must be a semver tag (e.g., v0.40.0). Got: '$VERSION'"
-          exit 1
-        fi
-
-    - name: Checkout docker compose files
-      uses: actions/checkout@v4
-      with:
-        repository: ${{ inputs.twenty-repository }}
-        ref: ${{ inputs.twenty-version }}
-        token: ${{ inputs.github-token }}
-        sparse-checkout: |
-          packages/twenty-docker
-        sparse-checkout-cone-mode: false
-        path: .twenty-spawn
-
-    - name: Prepare environment
-      shell: bash
-      working-directory: ./.twenty-spawn/packages/twenty-docker
-      run: |
-        cp .env.example .env
-        echo "" >> .env
-        echo "TAG=${{ inputs.twenty-version }}" >> .env
-        echo "APP_SECRET=replace_me_with_a_random_string" >> .env
-        echo "SERVER_URL=http://localhost:3000" >> .env
-
-    - name: Start Twenty instance
-      shell: bash
-      working-directory: ./.twenty-spawn/packages/twenty-docker
-      run: |
-        docker compose up -d --wait || {
-          echo "::error::Docker compose failed to start or health checks timed out"
-          docker compose logs
-          exit 1
-        }
-        echo "Twenty instance is ready at http://localhost:3000"
-
-    - name: Set admin access token
-      id: admin-token
-      shell: bash
-      run: |
-        ACCESS_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ1c2VySWQiOiIyMDIwMjAyMC1lNmI1LTQ2ODAtOGEzMi1iODIwOTczNzE1NmIiLCJ3b3Jrc3BhY2VJZCI6IjIwMjAyMDIwLTFjMjUtNGQwMi1iZjI1LTZhZWNjZjdlYTQxOSIsIndvcmtzcGFjZU1lbWJlcklkIjoiMjAyMDIwMjAtNDYzZi00MzViLTgyOGMtMTA3ZTAwN2EyNzExIiwidXNlcldvcmtzcGFjZUlkIjoiMjAyMDIwMjAtMWU3Yy00M2Q5LWE1ZGItNjg1YjUwNjlkODE2IiwidHlwZSI6IkFDQ0VTUyIsImF1dGhQcm92aWRlciI6InBhc3N3b3JkIiwiaWF0IjoxNzUxMjgxNzA0LCJleHAiOjIwNjY4NTc3MDR9.HMGqCsVlOAPVUBhKSGlD1X86VoHKt4LIUtET3CGIdik"
-        echo "::add-mask::$ACCESS_TOKEN"
-        echo "access-token=$ACCESS_TOKEN" >> "$GITHUB_OUTPUT"

.github/agents/speckit.analyze.agent.md

@@ -1,184 +0,0 @@
----
-description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Goal
-
-Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit.tasks` has successfully produced a complete `tasks.md`.
-
-## Operating Constraints
-
-**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
-
-**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit.analyze`.
-
-## Execution Steps
-
-### 1. Initialize Analysis Context
-
-Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
-
-- SPEC = FEATURE_DIR/spec.md
-- PLAN = FEATURE_DIR/plan.md
-- TASKS = FEATURE_DIR/tasks.md
-
-Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command).
-For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-### 2. Load Artifacts (Progressive Disclosure)
-
-Load only the minimal necessary context from each artifact:
-
-**From spec.md:**
-
-- Overview/Context
-- Functional Requirements
-- Non-Functional Requirements
-- User Stories
-- Edge Cases (if present)
-
-**From plan.md:**
-
-- Architecture/stack choices
-- Data Model references
-- Phases
-- Technical constraints
-
-**From tasks.md:**
-
-- Task IDs
-- Descriptions
-- Phase grouping
-- Parallel markers [P]
-- Referenced file paths
-
-**From constitution:**
-
-- Load `.specify/memory/constitution.md` for principle validation
-
-### 3. Build Semantic Models
-
-Create internal representations (do not include raw artifacts in output):
-
-- **Requirements inventory**: Each functional + non-functional requirement with a stable key (derive slug based on imperative phrase; e.g., "User can upload file" → `user-can-upload-file`)
-- **User story/action inventory**: Discrete user actions with acceptance criteria
-- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases)
-- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements
-
-### 4. Detection Passes (Token-Efficient Analysis)
-
-Focus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.
-
-#### A. Duplication Detection
-
-- Identify near-duplicate requirements
-- Mark lower-quality phrasing for consolidation
-
-#### B. Ambiguity Detection
-
-- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria
-- Flag unresolved placeholders (TODO, TKTK, ???, `<placeholder>`, etc.)
-
-#### C. Underspecification
-
-- Requirements with verbs but missing object or measurable outcome
-- User stories missing acceptance criteria alignment
-- Tasks referencing files or components not defined in spec/plan
-
-#### D. Constitution Alignment
-
-- Any requirement or plan element conflicting with a MUST principle
-- Missing mandated sections or quality gates from constitution
-
-#### E. Coverage Gaps
-
-- Requirements with zero associated tasks
-- Tasks with no mapped requirement/story
-- Non-functional requirements not reflected in tasks (e.g., performance, security)
-
-#### F. Inconsistency
-
-- Terminology drift (same concept named differently across files)
-- Data entities referenced in plan but absent in spec (or vice versa)
-- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)
-- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)
-
-### 5. Severity Assignment
-
-Use this heuristic to prioritize findings:
-
-- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality
-- **HIGH**: Duplicate or conflicting requirement, ambiguous security/performance attribute, untestable acceptance criterion
-- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case
-- **LOW**: Style/wording improvements, minor redundancy not affecting execution order
-
-### 6. Produce Compact Analysis Report
-
-Output a Markdown report (no file writes) with the following structure:
-
-## Specification Analysis Report
-
-| ID | Category | Severity | Location(s) | Summary | Recommendation |
-|----|----------|----------|-------------|---------|----------------|
-| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |
-
-(Add one row per finding; generate stable IDs prefixed by category initial.)
-
-**Coverage Summary Table:**
-
-| Requirement Key | Has Task? | Task IDs | Notes |
-|-----------------|-----------|----------|-------|
-
-**Constitution Alignment Issues:** (if any)
-
-**Unmapped Tasks:** (if any)
-
-**Metrics:**
-
-- Total Requirements
-- Total Tasks
-- Coverage % (requirements with >=1 task)
-- Ambiguity Count
-- Duplication Count
-- Critical Issues Count
-
-### 7. Provide Next Actions
-
-At end of report, output a concise Next Actions block:
-
-- If CRITICAL issues exist: Recommend resolving before `/speckit.implement`
-- If only LOW/MEDIUM: User may proceed, but provide improvement suggestions
-- Provide explicit command suggestions: e.g., "Run /speckit.specify with refinement", "Run /speckit.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
-
-### 8. Offer Remediation
-
-Ask the user: "Would you like me to suggest concrete remediation edits for the top N issues?" (Do NOT apply them automatically.)
-
-## Operating Principles
-
-### Context Efficiency
-
-- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation
-- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis
-- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow
-- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts
-
-### Analysis Guidelines
-
-- **NEVER modify files** (this is read-only analysis)
-- **NEVER hallucinate missing sections** (if absent, report them accurately)
-- **Prioritize constitution violations** (these are always CRITICAL)
-- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)
-- **Report zero issues gracefully** (emit success report with coverage statistics)
-
-## Context
-
-$ARGUMENTS

.github/agents/speckit.checklist.agent.md

@@ -1,295 +0,0 @@
----
-description: Generate a custom checklist for the current feature based on user requirements.
----
-
-## Checklist Purpose: "Unit Tests for English"
-
-**CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain.
-
-**NOT for verification/testing**:
-
-- ❌ NOT "Verify the button clicks correctly"
-- ❌ NOT "Test error handling works"
-- ❌ NOT "Confirm the API returns 200"
-- ❌ NOT checking if code/implementation matches the spec
-
-**FOR requirements quality validation**:
-
-- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
-- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
-- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
-- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
-- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases)
-
-**Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Execution Steps
-
-1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list.
-   - All file paths must be absolute.
-   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. **Clarify intent (dynamic)**: Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST:
-   - Be generated from the user's phrasing + extracted signals from spec/plan/tasks
-   - Only ask about information that materially changes checklist content
-   - Be skipped individually if already unambiguous in `$ARGUMENTS`
-   - Prefer precision over breadth
-
-   Generation algorithm:
-   1. Extract signals: feature domain keywords (e.g., auth, latency, UX, API), risk indicators ("critical", "must", "compliance"), stakeholder hints ("QA", "review", "security team"), and explicit deliverables ("a11y", "rollback", "contracts").
-   2. Cluster signals into candidate focus areas (max 4) ranked by relevance.
-   3. Identify probable audience & timing (author, reviewer, QA, release) if not explicit.
-   4. Detect missing dimensions: scope breadth, depth/rigor, risk emphasis, exclusion boundaries, measurable acceptance criteria.
-   5. Formulate questions chosen from these archetypes:
-      - Scope refinement (e.g., "Should this include integration touchpoints with X and Y or stay limited to local module correctness?")
-      - Risk prioritization (e.g., "Which of these potential risk areas should receive mandatory gating checks?")
-      - Depth calibration (e.g., "Is this a lightweight pre-commit sanity list or a formal release gate?")
-      - Audience framing (e.g., "Will this be used by the author only or peers during PR review?")
-      - Boundary exclusion (e.g., "Should we explicitly exclude performance tuning items this round?")
-      - Scenario class gap (e.g., "No recovery flows detected—are rollback / partial failure paths in scope?")
-
-   Question formatting rules:
-   - If presenting options, generate a compact table with columns: Option | Candidate | Why It Matters
-   - Limit to A–E options maximum; omit table if a free-form answer is clearer
-   - Never ask the user to restate what they already said
-   - Avoid speculative categories (no hallucination). If uncertain, ask explicitly: "Confirm whether X belongs in scope."
-
-   Defaults when interaction impossible:
-   - Depth: Standard
-   - Audience: Reviewer (PR) if code-related; Author otherwise
-   - Focus: Top 2 relevance clusters
-
-   Output the questions (label Q1/Q2/Q3). After answers: if ≥2 scenario classes (Alternate / Exception / Recovery / Non-Functional domain) remain unclear, you MAY ask up to TWO more targeted follow‑ups (Q4/Q5) with a one-line justification each (e.g., "Unresolved recovery path risk"). Do not exceed five total questions. Skip escalation if user explicitly declines more.
-
-3. **Understand user request**: Combine `$ARGUMENTS` + clarifying answers:
-   - Derive checklist theme (e.g., security, review, deploy, ux)
-   - Consolidate explicit must-have items mentioned by user
-   - Map focus selections to category scaffolding
-   - Infer any missing context from spec/plan/tasks (do NOT hallucinate)
-
-4. **Load feature context**: Read from FEATURE_DIR:
-   - spec.md: Feature requirements and scope
-   - plan.md (if exists): Technical details, dependencies
-   - tasks.md (if exists): Implementation tasks
-
-   **Context Loading Strategy**:
-   - Load only necessary portions relevant to active focus areas (avoid full-file dumping)
-   - Prefer summarizing long sections into concise scenario/requirement bullets
-   - Use progressive disclosure: add follow-on retrieval only if gaps detected
-   - If source docs are large, generate interim summary items instead of embedding raw text
-
-5. **Generate checklist** - Create "Unit Tests for Requirements":
-   - Create `FEATURE_DIR/checklists/` directory if it doesn't exist
-   - Generate unique checklist filename:
-     - Use short, descriptive name based on domain (e.g., `ux.md`, `api.md`, `security.md`)
-     - Format: `[domain].md`
-   - File handling behavior:
-     - If file does NOT exist: Create new file and number items starting from CHK001
-     - If file exists: Append new items to existing file, continuing from the last CHK ID (e.g., if last item is CHK015, start new items at CHK016)
-   - Never delete or replace existing checklist content - always preserve and append
-
-   **CORE PRINCIPLE - Test the Requirements, Not the Implementation**:
-   Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for:
-   - **Completeness**: Are all necessary requirements present?
-   - **Clarity**: Are requirements unambiguous and specific?
-   - **Consistency**: Do requirements align with each other?
-   - **Measurability**: Can requirements be objectively verified?
-   - **Coverage**: Are all scenarios/edge cases addressed?
-
-   **Category Structure** - Group items by requirement quality dimensions:
-   - **Requirement Completeness** (Are all necessary requirements documented?)
-   - **Requirement Clarity** (Are requirements specific and unambiguous?)
-   - **Requirement Consistency** (Do requirements align without conflicts?)
-   - **Acceptance Criteria Quality** (Are success criteria measurable?)
-   - **Scenario Coverage** (Are all flows/cases addressed?)
-   - **Edge Case Coverage** (Are boundary conditions defined?)
-   - **Non-Functional Requirements** (Performance, Security, Accessibility, etc. - are they specified?)
-   - **Dependencies & Assumptions** (Are they documented and validated?)
-   - **Ambiguities & Conflicts** (What needs clarification?)
-
-   **HOW TO WRITE CHECKLIST ITEMS - "Unit Tests for English"**:
-
-   ❌ **WRONG** (Testing implementation):
-   - "Verify landing page displays 3 episode cards"
-   - "Test hover states work on desktop"
-   - "Confirm logo click navigates home"
-
-   ✅ **CORRECT** (Testing requirements quality):
-   - "Are the exact number and layout of featured episodes specified?" [Completeness]
-   - "Is 'prominent display' quantified with specific sizing/positioning?" [Clarity]
-   - "Are hover state requirements consistent across all interactive elements?" [Consistency]
-   - "Are keyboard navigation requirements defined for all interactive UI?" [Coverage]
-   - "Is the fallback behavior specified when logo image fails to load?" [Edge Cases]
-   - "Are loading states defined for asynchronous episode data?" [Completeness]
-   - "Does the spec define visual hierarchy for competing UI elements?" [Clarity]
-
-   **ITEM STRUCTURE**:
-   Each item should follow this pattern:
-   - Question format asking about requirement quality
-   - Focus on what's WRITTEN (or not written) in the spec/plan
-   - Include quality dimension in brackets [Completeness/Clarity/Consistency/etc.]
-   - Reference spec section `[Spec §X.Y]` when checking existing requirements
-   - Use `[Gap]` marker when checking for missing requirements
-
-   **EXAMPLES BY QUALITY DIMENSION**:
-
-   Completeness:
-   - "Are error handling requirements defined for all API failure modes? [Gap]"
-   - "Are accessibility requirements specified for all interactive elements? [Completeness]"
-   - "Are mobile breakpoint requirements defined for responsive layouts? [Gap]"
-
-   Clarity:
-   - "Is 'fast loading' quantified with specific timing thresholds? [Clarity, Spec §NFR-2]"
-   - "Are 'related episodes' selection criteria explicitly defined? [Clarity, Spec §FR-5]"
-   - "Is 'prominent' defined with measurable visual properties? [Ambiguity, Spec §FR-4]"
-
-   Consistency:
-   - "Do navigation requirements align across all pages? [Consistency, Spec §FR-10]"
-   - "Are card component requirements consistent between landing and detail pages? [Consistency]"
-
-   Coverage:
-   - "Are requirements defined for zero-state scenarios (no episodes)? [Coverage, Edge Case]"
-   - "Are concurrent user interaction scenarios addressed? [Coverage, Gap]"
-   - "Are requirements specified for partial data loading failures? [Coverage, Exception Flow]"
-
-   Measurability:
-   - "Are visual hierarchy requirements measurable/testable? [Acceptance Criteria, Spec §FR-1]"
-   - "Can 'balanced visual weight' be objectively verified? [Measurability, Spec §FR-2]"
-
-   **Scenario Classification & Coverage** (Requirements Quality Focus):
-   - Check if requirements exist for: Primary, Alternate, Exception/Error, Recovery, Non-Functional scenarios
-   - For each scenario class, ask: "Are [scenario type] requirements complete, clear, and consistent?"
-   - If scenario class missing: "Are [scenario type] requirements intentionally excluded or missing? [Gap]"
-   - Include resilience/rollback when state mutation occurs: "Are rollback requirements defined for migration failures? [Gap]"
-
-   **Traceability Requirements**:
-   - MINIMUM: ≥80% of items MUST include at least one traceability reference
-   - Each item should reference: spec section `[Spec §X.Y]`, or use markers: `[Gap]`, `[Ambiguity]`, `[Conflict]`, `[Assumption]`
-   - If no ID system exists: "Is a requirement & acceptance criteria ID scheme established? [Traceability]"
-
-   **Surface & Resolve Issues** (Requirements Quality Problems):
-   Ask questions about the requirements themselves:
-   - Ambiguities: "Is the term 'fast' quantified with specific metrics? [Ambiguity, Spec §NFR-1]"
-   - Conflicts: "Do navigation requirements conflict between §FR-10 and §FR-10a? [Conflict]"
-   - Assumptions: "Is the assumption of 'always available podcast API' validated? [Assumption]"
-   - Dependencies: "Are external podcast API requirements documented? [Dependency, Gap]"
-   - Missing definitions: "Is 'visual hierarchy' defined with measurable criteria? [Gap]"
-
-   **Content Consolidation**:
-   - Soft cap: If raw candidate items > 40, prioritize by risk/impact
-   - Merge near-duplicates checking the same requirement aspect
-   - If >5 low-impact edge cases, create one item: "Are edge cases X, Y, Z addressed in requirements? [Coverage]"
-
-   **🚫 ABSOLUTELY PROHIBITED** - These make it an implementation test, not a requirements test:
-   - ❌ Any item starting with "Verify", "Test", "Confirm", "Check" + implementation behavior
-   - ❌ References to code execution, user actions, system behavior
-   - ❌ "Displays correctly", "works properly", "functions as expected"
-   - ❌ "Click", "navigate", "render", "load", "execute"
-   - ❌ Test cases, test plans, QA procedures
-   - ❌ Implementation details (frameworks, APIs, algorithms)
-
-   **✅ REQUIRED PATTERNS** - These test requirements quality:
-   - ✅ "Are [requirement type] defined/specified/documented for [scenario]?"
-   - ✅ "Is [vague term] quantified/clarified with specific criteria?"
-   - ✅ "Are requirements consistent between [section A] and [section B]?"
-   - ✅ "Can [requirement] be objectively measured/verified?"
-   - ✅ "Are [edge cases/scenarios] addressed in requirements?"
-   - ✅ "Does the spec define [missing aspect]?"
-
-6. **Structure Reference**: Generate the checklist following the canonical template in `.specify/templates/checklist-template.md` for title, meta section, category headings, and ID formatting. If template is unavailable, use: H1 title, purpose/created meta lines, `##` category sections containing `- [ ] CHK### <requirement item>` lines with globally incrementing IDs starting at CHK001.
-
-7. **Report**: Output full path to checklist file, item count, and summarize whether the run created a new file or appended to an existing one. Summarize:
-   - Focus areas selected
-   - Depth level
-   - Actor/timing
-   - Any explicit user-specified must-have items incorporated
-
-**Important**: Each `/speckit.checklist` command invocation uses a short, descriptive checklist filename and either creates a new file or appends to an existing one. This allows:
-
-- Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`)
-- Simple, memorable filenames that indicate checklist purpose
-- Easy identification and navigation in the `checklists/` folder
-
-To avoid clutter, use descriptive types and clean up obsolete checklists when done.
-
-## Example Checklist Types & Sample Items
-
-**UX Requirements Quality:** `ux.md`
-
-Sample items (testing the requirements, NOT the implementation):
-
-- "Are visual hierarchy requirements defined with measurable criteria? [Clarity, Spec §FR-1]"
-- "Is the number and positioning of UI elements explicitly specified? [Completeness, Spec §FR-1]"
-- "Are interaction state requirements (hover, focus, active) consistently defined? [Consistency]"
-- "Are accessibility requirements specified for all interactive elements? [Coverage, Gap]"
-- "Is fallback behavior defined when images fail to load? [Edge Case, Gap]"
-- "Can 'prominent display' be objectively measured? [Measurability, Spec §FR-4]"
-
-**API Requirements Quality:** `api.md`
-
-Sample items:
-
-- "Are error response formats specified for all failure scenarios? [Completeness]"
-- "Are rate limiting requirements quantified with specific thresholds? [Clarity]"
-- "Are authentication requirements consistent across all endpoints? [Consistency]"
-- "Are retry/timeout requirements defined for external dependencies? [Coverage, Gap]"
-- "Is versioning strategy documented in requirements? [Gap]"
-
-**Performance Requirements Quality:** `performance.md`
-
-Sample items:
-
-- "Are performance requirements quantified with specific metrics? [Clarity]"
-- "Are performance targets defined for all critical user journeys? [Coverage]"
-- "Are performance requirements under different load conditions specified? [Completeness]"
-- "Can performance requirements be objectively measured? [Measurability]"
-- "Are degradation requirements defined for high-load scenarios? [Edge Case, Gap]"
-
-**Security Requirements Quality:** `security.md`
-
-Sample items:
-
-- "Are authentication requirements specified for all protected resources? [Coverage]"
-- "Are data protection requirements defined for sensitive information? [Completeness]"
-- "Is the threat model documented and requirements aligned to it? [Traceability]"
-- "Are security requirements consistent with compliance obligations? [Consistency]"
-- "Are security failure/breach response requirements defined? [Gap, Exception Flow]"
-
-## Anti-Examples: What NOT To Do
-
-**❌ WRONG - These test implementation, not requirements:**
-
-```markdown
-- [ ] CHK001 - Verify landing page displays 3 episode cards [Spec §FR-001]
-- [ ] CHK002 - Test hover states work correctly on desktop [Spec §FR-003]
-- [ ] CHK003 - Confirm logo click navigates to home page [Spec §FR-010]
-- [ ] CHK004 - Check that related episodes section shows 3-5 items [Spec §FR-005]
-```
-
-**✅ CORRECT - These test requirements quality:**
-
-```markdown
-- [ ] CHK001 - Are the number and layout of featured episodes explicitly specified? [Completeness, Spec §FR-001]
-- [ ] CHK002 - Are hover state requirements consistently defined for all interactive elements? [Consistency, Spec §FR-003]
-- [ ] CHK003 - Are navigation requirements clear for all clickable brand elements? [Clarity, Spec §FR-010]
-- [ ] CHK004 - Is the selection criteria for related episodes documented? [Gap, Spec §FR-005]
-- [ ] CHK005 - Are loading state requirements defined for asynchronous episode data? [Gap]
-- [ ] CHK006 - Can "visual hierarchy" requirements be objectively measured? [Measurability, Spec §FR-001]
-```
-
-**Key Differences:**
-
-- Wrong: Tests if the system works correctly
-- Correct: Tests if the requirements are written correctly
-- Wrong: Verification of behavior
-- Correct: Validation of requirement quality
-- Wrong: "Does it do X?"
-- Correct: "Is X clearly specified?"

.github/agents/speckit.clarify.agent.md

@@ -1,181 +0,0 @@
----
-description: Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
-handoffs: 
-  - label: Build Technical Plan
-    agent: speckit.plan
-    prompt: Create a plan for the spec. I am building with...
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.
-
-Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/speckit.plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
-
-Execution steps:
-
-1. Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode / `-Json -PathsOnly`). Parse minimal JSON payload fields:
-   - `FEATURE_DIR`
-   - `FEATURE_SPEC`
-   - (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)
-   - If JSON parsing fails, abort and instruct user to re-run `/speckit.specify` or verify feature branch environment.
-   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked).
-
-   Functional Scope & Behavior:
-   - Core user goals & success criteria
-   - Explicit out-of-scope declarations
-   - User roles / personas differentiation
-
-   Domain & Data Model:
-   - Entities, attributes, relationships
-   - Identity & uniqueness rules
-   - Lifecycle/state transitions
-   - Data volume / scale assumptions
-
-   Interaction & UX Flow:
-   - Critical user journeys / sequences
-   - Error/empty/loading states
-   - Accessibility or localization notes
-
-   Non-Functional Quality Attributes:
-   - Performance (latency, throughput targets)
-   - Scalability (horizontal/vertical, limits)
-   - Reliability & availability (uptime, recovery expectations)
-   - Observability (logging, metrics, tracing signals)
-   - Security & privacy (authN/Z, data protection, threat assumptions)
-   - Compliance / regulatory constraints (if any)
-
-   Integration & External Dependencies:
-   - External services/APIs and failure modes
-   - Data import/export formats
-   - Protocol/versioning assumptions
-
-   Edge Cases & Failure Handling:
-   - Negative scenarios
-   - Rate limiting / throttling
-   - Conflict resolution (e.g., concurrent edits)
-
-   Constraints & Tradeoffs:
-   - Technical constraints (language, storage, hosting)
-   - Explicit tradeoffs or rejected alternatives
-
-   Terminology & Consistency:
-   - Canonical glossary terms
-   - Avoided synonyms / deprecated terms
-
-   Completion Signals:
-   - Acceptance criteria testability
-   - Measurable Definition of Done style indicators
-
-   Misc / Placeholders:
-   - TODO markers / unresolved decisions
-   - Ambiguous adjectives ("robust", "intuitive") lacking quantification
-
-   For each category with Partial or Missing status, add a candidate question opportunity unless:
-   - Clarification would not materially change implementation or validation strategy
-   - Information is better deferred to planning phase (note internally)
-
-3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:
-    - Maximum of 5 total questions across the whole session.
-    - Each question must be answerable with EITHER:
-       - A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR
-       - A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words").
-    - Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.
-    - Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.
-    - Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness).
-    - Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests.
-    - If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic.
-
-4. Sequential questioning loop (interactive):
-    - Present EXACTLY ONE question at a time.
-    - For multiple‑choice questions:
-       - **Analyze all options** and determine the **most suitable option** based on:
-          - Best practices for the project type
-          - Common patterns in similar implementations
-          - Risk reduction (security, performance, maintainability)
-          - Alignment with any explicit project goals or constraints visible in the spec
-       - Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).
-       - Format as: `**Recommended:** Option [X] - <reasoning>`
-       - Then render all options as a Markdown table:
-
-       | Option | Description |
-       |--------|-------------|
-       | A | <Option A description> |
-       | B | <Option B description> |
-       | C | <Option C description> (add D/E as needed up to 5) |
-       | Short | Provide a different short answer (<=5 words) (Include only if free-form alternative is appropriate) |
-
-       - After the table, add: `You can reply with the option letter (e.g., "A"), accept the recommendation by saying "yes" or "recommended", or provide your own short answer.`
-    - For short‑answer style (no meaningful discrete options):
-       - Provide your **suggested answer** based on best practices and context.
-       - Format as: `**Suggested:** <your proposed answer> - <brief reasoning>`
-       - Then output: `Format: Short answer (<=5 words). You can accept the suggestion by saying "yes" or "suggested", or provide your own answer.`
-    - After the user answers:
-       - If the user replies with "yes", "recommended", or "suggested", use your previously stated recommendation/suggestion as the answer.
-       - Otherwise, validate the answer maps to one option or fits the <=5 word constraint.
-       - If ambiguous, ask for a quick disambiguation (count still belongs to same question; do not advance).
-       - Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.
-    - Stop asking further questions when:
-       - All critical ambiguities resolved early (remaining queued items become unnecessary), OR
-       - User signals completion ("done", "good", "no more"), OR
-       - You reach 5 asked questions.
-    - Never reveal future queued questions in advance.
-    - If no valid questions exist at start, immediately report no critical ambiguities.
-
-5. Integration after EACH accepted answer (incremental update approach):
-    - Maintain in-memory representation of the spec (loaded once at start) plus the raw file contents.
-    - For the first integrated answer in this session:
-       - Ensure a `## Clarifications` section exists (create it just after the highest-level contextual/overview section per the spec template if missing).
-       - Under it, create (if not present) a `### Session YYYY-MM-DD` subheading for today.
-    - Append a bullet line immediately after acceptance: `- Q: <question> → A: <final answer>`.
-    - Then immediately apply the clarification to the most appropriate section(s):
-       - Functional ambiguity → Update or add a bullet in Functional Requirements.
-       - User interaction / actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.
-       - Data shape / entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.
-       - Non-functional constraint → Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).
-       - Edge case / negative flow → Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).
-       - Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.
-    - If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.
-    - Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).
-    - Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.
-    - Keep each inserted clarification minimal and testable (avoid narrative drift).
-
-6. Validation (performed after EACH write plus final pass):
-   - Clarifications session contains exactly one bullet per accepted answer (no duplicates).
-   - Total asked (accepted) questions ≤ 5.
-   - Updated sections contain no lingering vague placeholders the new answer was meant to resolve.
-   - No contradictory earlier statement remains (scan for now-invalid alternative choices removed).
-   - Markdown structure valid; only allowed new headings: `## Clarifications`, `### Session YYYY-MM-DD`.
-   - Terminology consistency: same canonical term used across all updated sections.
-
-7. Write the updated spec back to `FEATURE_SPEC`.
-
-8. Report completion (after questioning loop ends or early termination):
-   - Number of questions asked & answered.
-   - Path to updated spec.
-   - Sections touched (list names).
-   - Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
-   - If any Outstanding or Deferred remain, recommend whether to proceed to `/speckit.plan` or run `/speckit.clarify` again later post-plan.
-   - Suggested next command.
-
-Behavior rules:
-
-- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: "No critical ambiguities detected worth formal clarification." and suggest proceeding.
-- If spec file missing, instruct user to run `/speckit.specify` first (do not create a new spec here).
-- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).
-- Avoid speculative tech stack questions unless the absence blocks functional clarity.
-- Respect user early termination signals ("stop", "done", "proceed").
-- If no questions asked due to full coverage, output a compact coverage summary (all categories Clear) then suggest advancing.
-- If quota reached with unresolved high-impact categories remaining, explicitly flag them under Deferred with rationale.
-
-Context for prioritization: $ARGUMENTS

.github/agents/speckit.constitution.agent.md

@@ -1,84 +0,0 @@
----
-description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
-handoffs: 
-  - label: Build Specification
-    agent: speckit.specify
-    prompt: Implement the feature specification based on the updated constitution. I want to build...
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-You are updating the project constitution at `.specify/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
-
-**Note**: If `.specify/memory/constitution.md` does not exist yet, it should have been initialized from `.specify/templates/constitution-template.md` during project setup. If it's missing, copy the template first.
-
-Follow this execution flow:
-
-1. Load the existing constitution at `.specify/memory/constitution.md`.
-   - Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
-   **IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
-
-2. Collect/derive values for placeholders:
-   - If user input (conversation) supplies a value, use it.
-   - Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
-   - For governance dates: `RATIFICATION_DATE` is the original adoption date (if unknown ask or mark TODO), `LAST_AMENDED_DATE` is today if changes are made, otherwise keep previous.
-   - `CONSTITUTION_VERSION` must increment according to semantic versioning rules:
-     - MAJOR: Backward incompatible governance/principle removals or redefinitions.
-     - MINOR: New principle/section added or materially expanded guidance.
-     - PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
-   - If version bump type ambiguous, propose reasoning before finalizing.
-
-3. Draft the updated constitution content:
-   - Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
-   - Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
-   - Ensure each Principle section: succinct name line, paragraph (or bullet list) capturing non‑negotiable rules, explicit rationale if not obvious.
-   - Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
-
-4. Consistency propagation checklist (convert prior checklist into active validations):
-   - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
-   - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
-   - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
-   - Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
-   - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
-
-5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
-   - Version change: old → new
-   - List of modified principles (old title → new title if renamed)
-   - Added sections
-   - Removed sections
-   - Templates requiring updates (✅ updated / ⚠ pending) with file paths
-   - Follow-up TODOs if any placeholders intentionally deferred.
-
-6. Validation before final output:
-   - No remaining unexplained bracket tokens.
-   - Version line matches report.
-   - Dates ISO format YYYY-MM-DD.
-   - Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
-
-7. Write the completed constitution back to `.specify/memory/constitution.md` (overwrite).
-
-8. Output a final summary to the user with:
-   - New version and bump rationale.
-   - Any files flagged for manual follow-up.
-   - Suggested commit message (e.g., `docs: amend constitution to vX.Y.Z (principle additions + governance update)`).
-
-Formatting & Style Requirements:
-
-- Use Markdown headings exactly as in the template (do not demote/promote levels).
-- Wrap long rationale lines to keep readability (<100 chars ideally) but do not hard enforce with awkward breaks.
-- Keep a single blank line between sections.
-- Avoid trailing whitespace.
-
-If the user supplies partial updates (e.g., only one principle revision), still perform validation and version decision steps.
-
-If critical info missing (e.g., ratification date truly unknown), insert `TODO(<FIELD_NAME>): explanation` and include in the Sync Impact Report under deferred items.
-
-Do not create a new template; always operate on the existing `.specify/memory/constitution.md` file.

.github/agents/speckit.implement.agent.md

@@ -1,135 +0,0 @@
----
-description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. **Check checklists status** (if FEATURE_DIR/checklists/ exists):
-   - Scan all checklist files in the checklists/ directory
-   - For each checklist, count:
-     - Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`
-     - Completed items: Lines matching `- [X]` or `- [x]`
-     - Incomplete items: Lines matching `- [ ]`
-   - Create a status table:
-
-     ```text
-     | Checklist | Total | Completed | Incomplete | Status |
-     |-----------|-------|-----------|------------|--------|
-     | ux.md     | 12    | 12        | 0          | ✓ PASS |
-     | test.md   | 8     | 5         | 3          | ✗ FAIL |
-     | security.md | 6   | 6         | 0          | ✓ PASS |
-     ```
-
-   - Calculate overall status:
-     - **PASS**: All checklists have 0 incomplete items
-     - **FAIL**: One or more checklists have incomplete items
-
-   - **If any checklist is incomplete**:
-     - Display the table with incomplete item counts
-     - **STOP** and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
-     - Wait for user response before continuing
-     - If user says "no" or "wait" or "stop", halt execution
-     - If user says "yes" or "proceed" or "continue", proceed to step 3
-
-   - **If all checklists are complete**:
-     - Display the table showing all checklists passed
-     - Automatically proceed to step 3
-
-3. Load and analyze the implementation context:
-   - **REQUIRED**: Read tasks.md for the complete task list and execution plan
-   - **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
-   - **IF EXISTS**: Read data-model.md for entities and relationships
-   - **IF EXISTS**: Read contracts/ for API specifications and test requirements
-   - **IF EXISTS**: Read research.md for technical decisions and constraints
-   - **IF EXISTS**: Read quickstart.md for integration scenarios
-
-4. **Project Setup Verification**:
-   - **REQUIRED**: Create/verify ignore files based on actual project setup:
-
-   **Detection & Creation Logic**:
-   - Check if the following command succeeds to determine if the repository is a git repo (create/verify .gitignore if so):
-
-     ```sh
-     git rev-parse --git-dir 2>/dev/null
-     ```
-
-   - Check if Dockerfile* exists or Docker in plan.md → create/verify .dockerignore
-   - Check if .eslintrc* exists → create/verify .eslintignore
-   - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns
-   - Check if .prettierrc* exists → create/verify .prettierignore
-   - Check if .npmrc or package.json exists → create/verify .npmignore (if publishing)
-   - Check if terraform files (*.tf) exist → create/verify .terraformignore
-   - Check if .helmignore needed (helm charts present) → create/verify .helmignore
-
-   **If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
-   **If ignore file missing**: Create with full pattern set for detected technology
-
-   **Common Patterns by Technology** (from plan.md tech stack):
-   - **Node.js/JavaScript/TypeScript**: `node_modules/`, `dist/`, `build/`, `*.log`, `.env*`
-   - **Python**: `__pycache__/`, `*.pyc`, `.venv/`, `venv/`, `dist/`, `*.egg-info/`
-   - **Java**: `target/`, `*.class`, `*.jar`, `.gradle/`, `build/`
-   - **C#/.NET**: `bin/`, `obj/`, `*.user`, `*.suo`, `packages/`
-   - **Go**: `*.exe`, `*.test`, `vendor/`, `*.out`
-   - **Ruby**: `.bundle/`, `log/`, `tmp/`, `*.gem`, `vendor/bundle/`
-   - **PHP**: `vendor/`, `*.log`, `*.cache`, `*.env`
-   - **Rust**: `target/`, `debug/`, `release/`, `*.rs.bk`, `*.rlib`, `*.prof*`, `.idea/`, `*.log`, `.env*`
-   - **Kotlin**: `build/`, `out/`, `.gradle/`, `.idea/`, `*.class`, `*.jar`, `*.iml`, `*.log`, `.env*`
-   - **C++**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.so`, `*.a`, `*.exe`, `*.dll`, `.idea/`, `*.log`, `.env*`
-   - **C**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.a`, `*.so`, `*.exe`, `autom4te.cache/`, `config.status`, `config.log`, `.idea/`, `*.log`, `.env*`
-   - **Swift**: `.build/`, `DerivedData/`, `*.swiftpm/`, `Packages/`
-   - **R**: `.Rproj.user/`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat/`, `renv/`
-   - **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode/`, `.idea/`
-
-   **Tool-Specific Patterns**:
-   - **Docker**: `node_modules/`, `.git/`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage/`
-   - **ESLint**: `node_modules/`, `dist/`, `build/`, `coverage/`, `*.min.js`
-   - **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
-   - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`
-   - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`
-
-5. Parse tasks.md structure and extract:
-   - **Task phases**: Setup, Tests, Core, Integration, Polish
-   - **Task dependencies**: Sequential vs parallel execution rules
-   - **Task details**: ID, description, file paths, parallel markers [P]
-   - **Execution flow**: Order and dependency requirements
-
-6. Execute implementation following the task plan:
-   - **Phase-by-phase execution**: Complete each phase before moving to the next
-   - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together  
-   - **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
-   - **File-based coordination**: Tasks affecting the same files must run sequentially
-   - **Validation checkpoints**: Verify each phase completion before proceeding
-
-7. Implementation execution rules:
-   - **Setup first**: Initialize project structure, dependencies, configuration
-   - **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
-   - **Core development**: Implement models, services, CLI commands, endpoints
-   - **Integration work**: Database connections, middleware, logging, external services
-   - **Polish and validation**: Unit tests, performance optimization, documentation
-
-8. Progress tracking and error handling:
-   - Report progress after each completed task
-   - Halt execution if any non-parallel task fails
-   - For parallel tasks [P], continue with successful tasks, report failed ones
-   - Provide clear error messages with context for debugging
-   - Suggest next steps if implementation cannot proceed
-   - **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.
-
-9. Completion validation:
-   - Verify all required tasks are completed
-   - Check that implemented features match the original specification
-   - Validate that tests pass and coverage meets requirements
-   - Confirm the implementation follows the technical plan
-   - Report final status with summary of completed work
-
-Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `/speckit.tasks` first to regenerate the task list.

.github/agents/speckit.plan.agent.md

@@ -1,90 +0,0 @@
----
-description: Execute the implementation planning workflow using the plan template to generate design artifacts.
-handoffs: 
-  - label: Create Tasks
-    agent: speckit.tasks
-    prompt: Break the plan into tasks
-    send: true
-  - label: Create Checklist
-    agent: speckit.checklist
-    prompt: Create a checklist for the following domain...
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. **Setup**: Run `.specify/scripts/bash/setup-plan.sh --json` from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`. Load IMPL_PLAN template (already copied).
-
-3. **Execute plan workflow**: Follow the structure in IMPL_PLAN template to:
-   - Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
-   - Fill Constitution Check section from constitution
-   - Evaluate gates (ERROR if violations unjustified)
-   - Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
-   - Phase 1: Generate data-model.md, contracts/, quickstart.md
-   - Phase 1: Update agent context by running the agent script
-   - Re-evaluate Constitution Check post-design
-
-4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
-
-## Phases
-
-### Phase 0: Outline & Research
-
-1. **Extract unknowns from Technical Context** above:
-   - For each NEEDS CLARIFICATION → research task
-   - For each dependency → best practices task
-   - For each integration → patterns task
-
-2. **Generate and dispatch research agents**:
-
-   ```text
-   For each unknown in Technical Context:
-     Task: "Research {unknown} for {feature context}"
-   For each technology choice:
-     Task: "Find best practices for {tech} in {domain}"
-   ```
-
-3. **Consolidate findings** in `research.md` using format:
-   - Decision: [what was chosen]
-   - Rationale: [why chosen]
-   - Alternatives considered: [what else evaluated]
-
-**Output**: research.md with all NEEDS CLARIFICATION resolved
-
-### Phase 1: Design & Contracts
-
-**Prerequisites:** `research.md` complete
-
-1. **Extract entities from feature spec** → `data-model.md`:
-   - Entity name, fields, relationships
-   - Validation rules from requirements
-   - State transitions if applicable
-
-2. **Define interface contracts** (if project has external interfaces) → `/contracts/`:
-   - Identify what interfaces the project exposes to users or other systems
-   - Document the contract format appropriate for the project type
-   - Examples: public APIs for libraries, command schemas for CLI tools, endpoints for web services, grammars for parsers, UI contracts for applications
-   - Skip if project is purely internal (build scripts, one-off tools, etc.)
-
-3. **Agent context update**:
-   - Run `.specify/scripts/bash/update-agent-context.sh copilot`
-   - These scripts detect which AI agent is in use
-   - Update the appropriate agent-specific context file
-   - Add only new technology from current plan
-   - Preserve manual additions between markers
-
-**Output**: data-model.md, /contracts/*, quickstart.md, agent-specific file
-
-## Key rules
-
-- Use absolute paths
-- ERROR on gate failures or unresolved clarifications

.github/agents/speckit.specify.agent.md

@@ -1,258 +0,0 @@
----
-description: Create or update the feature specification from a natural language feature description.
-handoffs: 
-  - label: Build Technical Plan
-    agent: speckit.plan
-    prompt: Create a plan for the spec. I am building with...
-  - label: Clarify Spec Requirements
-    agent: speckit.clarify
-    prompt: Clarify specification requirements
-    send: true
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-The text the user typed after `/speckit.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `$ARGUMENTS` appears literally below. Do not ask the user to repeat it unless they provided an empty command.
-
-Given that feature description, do this:
-
-1. **Generate a concise short name** (2-4 words) for the branch:
-   - Analyze the feature description and extract the most meaningful keywords
-   - Create a 2-4 word short name that captures the essence of the feature
-   - Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
-   - Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
-   - Keep it concise but descriptive enough to understand the feature at a glance
-   - Examples:
-     - "I want to add user authentication" → "user-auth"
-     - "Implement OAuth2 integration for the API" → "oauth2-api-integration"
-     - "Create a dashboard for analytics" → "analytics-dashboard"
-     - "Fix payment processing timeout bug" → "fix-payment-timeout"
-
-2. **Check for existing branches before creating new one**:
-
-   a. First, fetch all remote branches to ensure we have the latest information:
-
-      ```bash
-      git fetch --all --prune
-      ```
-
-   b. Find the highest feature number across all sources for the short-name:
-      - Remote branches: `git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$'`
-      - Local branches: `git branch | grep -E '^[* ]*[0-9]+-<short-name>$'`
-      - Specs directories: Check for directories matching `specs/[0-9]+-<short-name>`
-
-   c. Determine the next available number:
-      - Extract all numbers from all three sources
-      - Find the highest number N
-      - Use N+1 for the new branch number
-
-   d. Run the script `.specify/scripts/bash/create-new-feature.sh --json "$ARGUMENTS"` with the calculated number and short-name:
-      - Pass `--number N+1` and `--short-name "your-short-name"` along with the feature description
-      - Bash example: `.specify/scripts/bash/create-new-feature.sh --json "$ARGUMENTS" --json --number 5 --short-name "user-auth" "Add user authentication"`
-      - PowerShell example: `.specify/scripts/bash/create-new-feature.sh --json "$ARGUMENTS" -Json -Number 5 -ShortName "user-auth" "Add user authentication"`
-
-   **IMPORTANT**:
-   - Check all three sources (remote branches, local branches, specs directories) to find the highest number
-   - Only match branches/directories with the exact short-name pattern
-   - If no existing branches/directories found with this short-name, start with number 1
-   - You must only ever run this script once per feature
-   - The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
-   - The JSON output will contain BRANCH_NAME and SPEC_FILE paths
-   - For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot")
-
-3. Load `.specify/templates/spec-template.md` to understand required sections.
-
-4. Follow this execution flow:
-
-    1. Parse user description from Input
-       If empty: ERROR "No feature description provided"
-    2. Extract key concepts from description
-       Identify: actors, actions, data, constraints
-    3. For unclear aspects:
-       - Make informed guesses based on context and industry standards
-       - Only mark with [NEEDS CLARIFICATION: specific question] if:
-         - The choice significantly impacts feature scope or user experience
-         - Multiple reasonable interpretations exist with different implications
-         - No reasonable default exists
-       - **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total**
-       - Prioritize clarifications by impact: scope > security/privacy > user experience > technical details
-    4. Fill User Scenarios & Testing section
-       If no clear user flow: ERROR "Cannot determine user scenarios"
-    5. Generate Functional Requirements
-       Each requirement must be testable
-       Use reasonable defaults for unspecified details (document assumptions in Assumptions section)
-    6. Define Success Criteria
-       Create measurable, technology-agnostic outcomes
-       Include both quantitative metrics (time, performance, volume) and qualitative measures (user satisfaction, task completion)
-       Each criterion must be verifiable without implementation details
-    7. Identify Key Entities (if data involved)
-    8. Return: SUCCESS (spec ready for planning)
-
-5. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
-
-6. **Specification Quality Validation**: After writing the initial spec, validate it against quality criteria:
-
-   a. **Create Spec Quality Checklist**: Generate a checklist file at `FEATURE_DIR/checklists/requirements.md` using the checklist template structure with these validation items:
-
-      ```markdown
-      # Specification Quality Checklist: [FEATURE NAME]
-      
-      **Purpose**: Validate specification completeness and quality before proceeding to planning
-      **Created**: [DATE]
-      **Feature**: [Link to spec.md]
-      
-      ## Content Quality
-      
-      - [ ] No implementation details (languages, frameworks, APIs)
-      - [ ] Focused on user value and business needs
-      - [ ] Written for non-technical stakeholders
-      - [ ] All mandatory sections completed
-      
-      ## Requirement Completeness
-      
-      - [ ] No [NEEDS CLARIFICATION] markers remain
-      - [ ] Requirements are testable and unambiguous
-      - [ ] Success criteria are measurable
-      - [ ] Success criteria are technology-agnostic (no implementation details)
-      - [ ] All acceptance scenarios are defined
-      - [ ] Edge cases are identified
-      - [ ] Scope is clearly bounded
-      - [ ] Dependencies and assumptions identified
-      
-      ## Feature Readiness
-      
-      - [ ] All functional requirements have clear acceptance criteria
-      - [ ] User scenarios cover primary flows
-      - [ ] Feature meets measurable outcomes defined in Success Criteria
-      - [ ] No implementation details leak into specification
-      
-      ## Notes
-      
-      - Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`
-      ```
-
-   b. **Run Validation Check**: Review the spec against each checklist item:
-      - For each item, determine if it passes or fails
-      - Document specific issues found (quote relevant spec sections)
-
-   c. **Handle Validation Results**:
-
-      - **If all items pass**: Mark checklist complete and proceed to step 6
-
-      - **If items fail (excluding [NEEDS CLARIFICATION])**:
-        1. List the failing items and specific issues
-        2. Update the spec to address each issue
-        3. Re-run validation until all items pass (max 3 iterations)
-        4. If still failing after 3 iterations, document remaining issues in checklist notes and warn user
-
-      - **If [NEEDS CLARIFICATION] markers remain**:
-        1. Extract all [NEEDS CLARIFICATION: ...] markers from the spec
-        2. **LIMIT CHECK**: If more than 3 markers exist, keep only the 3 most critical (by scope/security/UX impact) and make informed guesses for the rest
-        3. For each clarification needed (max 3), present options to user in this format:
-
-           ```markdown
-           ## Question [N]: [Topic]
-           
-           **Context**: [Quote relevant spec section]
-           
-           **What we need to know**: [Specific question from NEEDS CLARIFICATION marker]
-           
-           **Suggested Answers**:
-           
-           | Option | Answer | Implications |
-           |--------|--------|--------------|
-           | A      | [First suggested answer] | [What this means for the feature] |
-           | B      | [Second suggested answer] | [What this means for the feature] |
-           | C      | [Third suggested answer] | [What this means for the feature] |
-           | Custom | Provide your own answer | [Explain how to provide custom input] |
-           
-           **Your choice**: _[Wait for user response]_
-           ```
-
-        4. **CRITICAL - Table Formatting**: Ensure markdown tables are properly formatted:
-           - Use consistent spacing with pipes aligned
-           - Each cell should have spaces around content: `| Content |` not `|Content|`
-           - Header separator must have at least 3 dashes: `|--------|`
-           - Test that the table renders correctly in markdown preview
-        5. Number questions sequentially (Q1, Q2, Q3 - max 3 total)
-        6. Present all questions together before waiting for responses
-        7. Wait for user to respond with their choices for all questions (e.g., "Q1: A, Q2: Custom - [details], Q3: B")
-        8. Update the spec by replacing each [NEEDS CLARIFICATION] marker with the user's selected or provided answer
-        9. Re-run validation after all clarifications are resolved
-
-   d. **Update Checklist**: After each validation iteration, update the checklist file with current pass/fail status
-
-7. Report completion with branch name, spec file path, checklist results, and readiness for the next phase (`/speckit.clarify` or `/speckit.plan`).
-
-**NOTE:** The script creates and checks out the new branch and initializes the spec file before writing.
-
-## General Guidelines
-
-## Quick Guidelines
-
-- Focus on **WHAT** users need and **WHY**.
-- Avoid HOW to implement (no tech stack, APIs, code structure).
-- Written for business stakeholders, not developers.
-- DO NOT create any checklists that are embedded in the spec. That will be a separate command.
-
-### Section Requirements
-
-- **Mandatory sections**: Must be completed for every feature
-- **Optional sections**: Include only when relevant to the feature
-- When a section doesn't apply, remove it entirely (don't leave as "N/A")
-
-### For AI Generation
-
-When creating this spec from a user prompt:
-
-1. **Make informed guesses**: Use context, industry standards, and common patterns to fill gaps
-2. **Document assumptions**: Record reasonable defaults in the Assumptions section
-3. **Limit clarifications**: Maximum 3 [NEEDS CLARIFICATION] markers - use only for critical decisions that:
-   - Significantly impact feature scope or user experience
-   - Have multiple reasonable interpretations with different implications
-   - Lack any reasonable default
-4. **Prioritize clarifications**: scope > security/privacy > user experience > technical details
-5. **Think like a tester**: Every vague requirement should fail the "testable and unambiguous" checklist item
-6. **Common areas needing clarification** (only if no reasonable default exists):
-   - Feature scope and boundaries (include/exclude specific use cases)
-   - User types and permissions (if multiple conflicting interpretations possible)
-   - Security/compliance requirements (when legally/financially significant)
-
-**Examples of reasonable defaults** (don't ask about these):
-
-- Data retention: Industry-standard practices for the domain
-- Performance targets: Standard web/mobile app expectations unless specified
-- Error handling: User-friendly messages with appropriate fallbacks
-- Authentication method: Standard session-based or OAuth2 for web apps
-- Integration patterns: Use project-appropriate patterns (REST/GraphQL for web services, function calls for libraries, CLI args for tools, etc.)
-
-### Success Criteria Guidelines
-
-Success criteria must be:
-
-1. **Measurable**: Include specific metrics (time, percentage, count, rate)
-2. **Technology-agnostic**: No mention of frameworks, languages, databases, or tools
-3. **User-focused**: Describe outcomes from user/business perspective, not system internals
-4. **Verifiable**: Can be tested/validated without knowing implementation details
-
-**Good examples**:
-
-- "Users can complete checkout in under 3 minutes"
-- "System supports 10,000 concurrent users"
-- "95% of searches return results in under 1 second"
-- "Task completion rate improves by 40%"
-
-**Bad examples** (implementation-focused):
-
-- "API response time is under 200ms" (too technical, use "Users see results instantly")
-- "Database can handle 1000 TPS" (implementation detail, use user-facing metric)
-- "React components render efficiently" (framework-specific)
-- "Redis cache hit rate above 80%" (technology-specific)

.github/agents/speckit.tasks.agent.md

@@ -1,137 +0,0 @@
----
-description: Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
-handoffs: 
-  - label: Analyze For Consistency
-    agent: speckit.analyze
-    prompt: Run a project analysis for consistency
-    send: true
-  - label: Implement Project
-    agent: speckit.implement
-    prompt: Start the implementation in phases
-    send: true
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. **Load design documents**: Read from FEATURE_DIR:
-   - **Required**: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
-   - **Optional**: data-model.md (entities), contracts/ (interface contracts), research.md (decisions), quickstart.md (test scenarios)
-   - Note: Not all projects have all documents. Generate tasks based on what's available.
-
-3. **Execute task generation workflow**:
-   - Load plan.md and extract tech stack, libraries, project structure
-   - Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
-   - If data-model.md exists: Extract entities and map to user stories
-   - If contracts/ exists: Map interface contracts to user stories
-   - If research.md exists: Extract decisions for setup tasks
-   - Generate tasks organized by user story (see Task Generation Rules below)
-   - Generate dependency graph showing user story completion order
-   - Create parallel execution examples per user story
-   - Validate task completeness (each user story has all needed tasks, independently testable)
-
-4. **Generate tasks.md**: Use `.specify/templates/tasks-template.md` as structure, fill with:
-   - Correct feature name from plan.md
-   - Phase 1: Setup tasks (project initialization)
-   - Phase 2: Foundational tasks (blocking prerequisites for all user stories)
-   - Phase 3+: One phase per user story (in priority order from spec.md)
-   - Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
-   - Final Phase: Polish & cross-cutting concerns
-   - All tasks must follow the strict checklist format (see Task Generation Rules below)
-   - Clear file paths for each task
-   - Dependencies section showing story completion order
-   - Parallel execution examples per story
-   - Implementation strategy section (MVP first, incremental delivery)
-
-5. **Report**: Output path to generated tasks.md and summary:
-   - Total task count
-   - Task count per user story
-   - Parallel opportunities identified
-   - Independent test criteria for each story
-   - Suggested MVP scope (typically just User Story 1)
-   - Format validation: Confirm ALL tasks follow the checklist format (checkbox, ID, labels, file paths)
-
-Context for task generation: $ARGUMENTS
-
-The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.
-
-## Task Generation Rules
-
-**CRITICAL**: Tasks MUST be organized by user story to enable independent implementation and testing.
-
-**Tests are OPTIONAL**: Only generate test tasks if explicitly requested in the feature specification or if user requests TDD approach.
-
-### Checklist Format (REQUIRED)
-
-Every task MUST strictly follow this format:
-
-```text
-- [ ] [TaskID] [P?] [Story?] Description with file path
-```
-
-**Format Components**:
-
-1. **Checkbox**: ALWAYS start with `- [ ]` (markdown checkbox)
-2. **Task ID**: Sequential number (T001, T002, T003...) in execution order
-3. **[P] marker**: Include ONLY if task is parallelizable (different files, no dependencies on incomplete tasks)
-4. **[Story] label**: REQUIRED for user story phase tasks only
-   - Format: [US1], [US2], [US3], etc. (maps to user stories from spec.md)
-   - Setup phase: NO story label
-   - Foundational phase: NO story label  
-   - User Story phases: MUST have story label
-   - Polish phase: NO story label
-5. **Description**: Clear action with exact file path
-
-**Examples**:
-
-- ✅ CORRECT: `- [ ] T001 Create project structure per implementation plan`
-- ✅ CORRECT: `- [ ] T005 [P] Implement authentication middleware in src/middleware/auth.py`
-- ✅ CORRECT: `- [ ] T012 [P] [US1] Create User model in src/models/user.py`
-- ✅ CORRECT: `- [ ] T014 [US1] Implement UserService in src/services/user_service.py`
-- ❌ WRONG: `- [ ] Create User model` (missing ID and Story label)
-- ❌ WRONG: `T001 [US1] Create model` (missing checkbox)
-- ❌ WRONG: `- [ ] [US1] Create User model` (missing Task ID)
-- ❌ WRONG: `- [ ] T001 [US1] Create model` (missing file path)
-
-### Task Organization
-
-1. **From User Stories (spec.md)** - PRIMARY ORGANIZATION:
-   - Each user story (P1, P2, P3...) gets its own phase
-   - Map all related components to their story:
-     - Models needed for that story
-     - Services needed for that story
-     - Interfaces/UI needed for that story
-     - If tests requested: Tests specific to that story
-   - Mark story dependencies (most stories should be independent)
-
-2. **From Contracts**:
-   - Map each interface contract → to the user story it serves
-   - If tests requested: Each interface contract → contract test task [P] before implementation in that story's phase
-
-3. **From Data Model**:
-   - Map each entity to the user story(ies) that need it
-   - If entity serves multiple stories: Put in earliest story or Setup phase
-   - Relationships → service layer tasks in appropriate story phase
-
-4. **From Setup/Infrastructure**:
-   - Shared infrastructure → Setup phase (Phase 1)
-   - Foundational/blocking tasks → Foundational phase (Phase 2)
-   - Story-specific setup → within that story's phase
-
-### Phase Structure
-
-- **Phase 1**: Setup (project initialization)
-- **Phase 2**: Foundational (blocking prerequisites - MUST complete before user stories)
-- **Phase 3+**: User Stories in priority order (P1, P2, P3...)
-  - Within each story: Tests (if requested) → Models → Services → Endpoints → Integration
-  - Each phase should be a complete, independently testable increment
-- **Final Phase**: Polish & Cross-Cutting Concerns

.github/agents/speckit.taskstoissues.agent.md

@@ -1,30 +0,0 @@
----
-description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
-tools: ['github/github-mcp-server/issue_write']
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-1. From the executed script, extract the path to **tasks**.
-1. Get the Git remote by running:
-
-```bash
-git config --get remote.origin.url
-```
-
-> [!CAUTION]
-> ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
-
-1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
-
-> [!CAUTION]
-> UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL

.github/crowdin-app.yml

@@ -1,23 +0,0 @@
-#
-# Crowdin CLI configuration for App translations (twenty-front, twenty-server, twenty-emails)
-# Project ID: 1
-# See https://crowdin.github.io/crowdin-cli/configuration for more information
-#
-
-"preserve_hierarchy": true
-"base_path": ".."
-
-files: [
-  {
-    #
-    # Source files filter - PO files for Lingui
-    #
-    "source": "**/en.po",
-
-    #
-    # Translation files path
-    #
-    "translation": "%original_path%/%locale%.po",
-  }
-]
-

.github/crowdin-docs.yml

@@ -1,45 +0,0 @@
-#
-# Crowdin CLI configuration for Documentation translations
-# See https://crowdin.github.io/crowdin-cli/configuration for more information
-#
-
-"project_id": 2
-"preserve_hierarchy": true
-"base_url": "https://twenty.api.crowdin.com"
-"base_path": ".."
-
-files: [
-  {
-    #
-    # MDX documentation files - user-guide
-    # Using md type to preserve JSX component structure
-    # This prevents Crowdin from reformatting <Warning>, <Accordion>, etc.
-    #
-    "source": "packages/twenty-docs/user-guide/**/*.mdx",
-    "translation": "packages/twenty-docs/l/%two_letters_code%/user-guide/**/%original_file_name%",
-  },
-  {
-    #
-    # MDX documentation files - developers
-    # Using md type to preserve JSX component structure
-    #
-    "source": "packages/twenty-docs/developers/**/*.mdx",
-    "translation": "packages/twenty-docs/l/%two_letters_code%/developers/**/%original_file_name%",
-  },
-  {
-    #
-    # MDX documentation files - twenty-ui
-    # Using md type to preserve JSX component structure
-    #
-    "source": "packages/twenty-docs/twenty-ui/**/*.mdx",
-    "translation": "packages/twenty-docs/l/%two_letters_code%/twenty-ui/**/%original_file_name%",
-  },
-  {
-    #
-    # Navigation labels template - translated into per-locale navigation.json
-    #
-    "source": "packages/twenty-docs/navigation/navigation.template.json",
-    "translation": "packages/twenty-docs/l/%two_letters_code%/navigation.json",
-  }
-]
-

.github/dependabot.yml

@@ -1,17 +0,0 @@
-version: 2
-updates:
-  - package-ecosystem: "npm"
-    directory: "/"
-    exclude-paths:
-      - "packages/twenty-apps/community/**"
-    schedule:
-      interval: "weekly"
-    open-pull-requests-limit: 3
-    versioning-strategy: "lockfile-only"
-    assignees:
-      - "mabdullahabaid"
-    ignore:
-      - dependency-name: "@graphql-yoga/nestjs"
-      - dependency-name: "@nestjs/graphql"
-      - dependency-name: "@ptc-org/nestjs-query-graphql"
-      - dependency-name: "typeorm"

.github/prompts/speckit.analyze.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.analyze
----

.github/prompts/speckit.checklist.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.checklist
----

.github/prompts/speckit.clarify.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.clarify
----

.github/prompts/speckit.constitution.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.constitution
----

.github/prompts/speckit.implement.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.implement
----

.github/prompts/speckit.plan.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.plan
----

.github/prompts/speckit.specify.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.specify
----

.github/prompts/speckit.tasks.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.tasks
----

.github/prompts/speckit.taskstoissues.prompt.md

@@ -1,3 +0,0 @@
----
-agent: speckit.taskstoissues
----

.github/workflows/actions/nx-affected/action.yaml

@@ -0,0 +1,22 @@
+name: Nx Affected CI
+inputs:
+  parallel:
+    required: false
+    default: '3'
+  tag:
+    required: false
+  tasks:
+    required: true
+  configuration:
+    required: false
+    default: 'ci'
+  args:
+    required: false
+runs:
+  using: "composite"
+  steps:
+    - name: Get last successful commit
+      uses: nrwl/nx-set-shas@v4
+    - name: Run affected command
+      shell: bash
+      run: npx nx affected --nxBail --configuration=${{ inputs.configuration }} -t=${{ inputs.tasks }} --parallel=${{ inputs.parallel }} --exclude='*,!tag:${{ inputs.tag }}' ${{ inputs.args }}

.github/workflows/actions/restore-cache/action.yaml

@@ -0,0 +1,35 @@
+name: Restore cache
+inputs:
+  key:
+    required: true
+    description: Prefix to the cache key
+  additional-paths:
+    required: false
+outputs:
+  cache-primary-key:
+    description: actions/cache/restore cache-primary-key outputs proxy
+    value: ${{ steps.restore-cache.outputs.cache-primary-key }}
+  cache-hit:
+    description: String bool indicating whether cache has been directly or indirectly hit
+    value: ${{ steps.restore-cache.outputs.cache-hit == 'true' || steps.restore-cache.outputs.cache-matched-key != '' }}
+
+runs:
+  using: composite
+  steps:
+    - name: Cache primary key builder
+      id: cache-primary-key-builder
+      shell: bash
+      run: |
+        echo "CACHE_PRIMARY_KEY_PREFIX=v3-${{ inputs.key }}-${{ github.ref_name }}" >> "${GITHUB_OUTPUT}"
+    - name: Restore cache
+      uses: actions/cache/restore@v4
+      id: restore-cache
+      with:
+        key: ${{ steps.cache-primary-key-builder.outputs.CACHE_PRIMARY_KEY_PREFIX }}-${{ github.sha }}
+        restore-keys: ${{ steps.cache-primary-key-builder.outputs.CACHE_PRIMARY_KEY_PREFIX }}-
+        path: |
+          .cache
+          .nx
+          node_modules/.cache
+          packages/*/node_modules/.cache
+          ${{ inputs.additional-paths }}

.github/workflows/ci-breaking-changes.yaml

@@ -16,6 +16,8 @@ env:
 
 permissions:
   contents: read
+  pull-requests: write
+  checks: write
 
 jobs:
   changed-files-check:
@@ -61,9 +63,9 @@ jobs:
           - 8123:8123
           - 9000:9000
         options: >-
-          --health-cmd "clickhouse-client --host=localhost --port=9000 --user=default --password=clickhousePassword --query='SELECT 1'"
-          --health-interval 10s
-          --health-timeout 5s
+          --health-cmd "clickhouse-client --host=localhost --port=9000 --user=default --password=clickhousePassword --query='SELECT 1'" 
+          --health-interval 10s 
+          --health-timeout 5s 
           --health-retries 5
 
     steps:
@@ -76,12 +78,12 @@ jobs:
         id: merge_attempt
         run: |
           echo "Attempting to merge main into current branch..."
-
+          
           git fetch origin main
-
+          
           CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
           echo "Current branch: $CURRENT_BRANCH"
-
+          
           if git merge origin/main --no-edit; then
             echo "✅ Successfully merged main into current branch"
             echo "merged=true" >> $GITHUB_OUTPUT
@@ -89,16 +91,16 @@ jobs:
           else
             echo "❌ Merge failed due to conflicts"
             echo "⚠️ Falling back to comparing current branch against main without merge"
-
+            
             # Abort the failed merge
             git merge --abort
-
+            
             echo "merged=false" >> $GITHUB_OUTPUT
             echo "BRANCH_STATE=conflicts" >> $GITHUB_ENV
           fi
 
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
 
       - name: Build shared dependencies
         run: |
@@ -126,22 +128,22 @@ jobs:
             local var_name="$1"
             local var_value="$2"
             local env_file="packages/twenty-server/.env"
-
+            
             echo "" >> "$env_file"
-
+            
             if grep -q "^${var_name}=" "$env_file" 2>/dev/null; then
               sed -i "s|^${var_name}=.*|${var_name}=${var_value}|" "$env_file"
             else
               echo "${var_name}=${var_value}" >> "$env_file"
             fi
           }
-
+          
           set_env_var "PG_DATABASE_URL" "postgres://postgres:postgres@localhost:5432/current_branch"
           set_env_var "NODE_PORT" "${{ env.CURRENT_SERVER_PORT }}"
           set_env_var "REDIS_URL" "redis://localhost:6379"
           set_env_var "CLICKHOUSE_URL" "http://default:clickhousePassword@localhost:8123/twenty"
           set_env_var "CLICKHOUSE_PASSWORD" "clickhousePassword"
-
+          
           npx nx run twenty-server:database:init:prod
           npx nx run twenty-server:database:migrate:prod
 
@@ -164,19 +166,19 @@ jobs:
           timeout=300
           interval=5
           elapsed=0
-
+          
           while [ $elapsed -lt $timeout ]; do
             if curl -s "http://localhost:${{ env.CURRENT_SERVER_PORT }}/graphql" > /dev/null 2>&1 && \
                curl -s "http://localhost:${{ env.CURRENT_SERVER_PORT }}/rest/open-api/core" > /dev/null 2>&1; then
               echo "Current branch server is ready!"
               break
             fi
-
+            
             echo "Current branch server not ready yet, waiting ${interval}s..."
             sleep $interval
             elapsed=$((elapsed + interval))
           done
-
+          
           if [ $elapsed -ge $timeout ]; then
             echo "Timeout waiting for current branch server to start"
             echo "Current server log:"
@@ -186,15 +188,15 @@ jobs:
 
       - name: Download GraphQL and REST responses from current branch
         run: |
-          # Read admin token from shared test tokens file (single source of truth)
-          ADMIN_TOKEN=$(jq -r '.APPLE_JANE_ADMIN_ACCESS_TOKEN' packages/twenty-server/test/integration/constants/test-tokens.json)
-
+          # Admin token from jest-integration.config.ts
+          ADMIN_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIyMDIwMjAyMC05ZTNiLTQ2ZDQtYTU1Ni04OGI5ZGRjMmIwMzQiLCJ3b3Jrc3BhY2VJZCI6IjIwMjAyMDIwLTFjMjUtNGQwMi1iZjI1LTZhZWNjZjdlYTQxOSIsIndvcmtzcGFjZU1lbWJlcklkIjoiMjAyMDIwMjAtMDY4Ny00YzQxLWI3MDctZWQxYmZjYTk3MmE3IiwidXNlcldvcmtzcGFjZUlkIjoiMjAyMDIwMjAtOWUzYi00NmQ0LWE1NTYtODhiOWRkYzJiMDM1IiwiaWF0IjoxNzM5NTQ3NjYxLCJleHAiOjMzMjk3MTQ3NjYxfQ.fbOM9yhr3jWDicPZ1n771usUURiPGmNdeFApsgrbxOw"
+          
           # Load introspection query from file
           INTROSPECTION_QUERY=$(cat packages/twenty-utils/graphql-introspection-query.graphql)
-
+          
           # Prepare the query payload
           QUERY_PAYLOAD=$(echo "$INTROSPECTION_QUERY" | tr '\n' ' ' | sed 's/"/\\"/g')
-
+          
           echo "Downloading GraphQL schema from current server..."
           curl -X POST "http://localhost:${{ env.CURRENT_SERVER_PORT }}/graphql" \
             -H "Content-Type: application/json" \
@@ -203,7 +205,7 @@ jobs:
             -o current-schema-introspection.json \
             -w "HTTP Status: %{http_code}\n" \
             -s
-
+          
           echo "Downloading GraphQL metadata schema from current server..."
           curl -X POST "http://localhost:${{ env.CURRENT_SERVER_PORT }}/metadata" \
             -H "Content-Type: application/json" \
@@ -212,32 +214,32 @@ jobs:
             -o current-metadata-schema-introspection.json \
             -w "HTTP Status: %{http_code}\n" \
             -s
-
+          
           # Download current branch OpenAPI specs
           echo "Downloading OpenAPI specifications from current server..."
           curl -s "http://localhost:${{ env.CURRENT_SERVER_PORT }}/rest/open-api/core" \
             -H "Authorization: Bearer ${ADMIN_TOKEN}" \
             -o current-rest-api.json \
             -w "HTTP Status: %{http_code}\n"
-
+          
           curl -s "http://localhost:${{ env.CURRENT_SERVER_PORT }}/rest/open-api/metadata" \
             -H "Authorization: Bearer ${ADMIN_TOKEN}" \
             -o current-rest-metadata-api.json \
             -w "HTTP Status: %{http_code}\n"
-
+          
           # Verify the downloads
           echo "Current branch files downloaded:"
           ls -la current-*
-
+          
 
       - name: Preserve current branch files
         run: |
           # Create a temp directory to store current branch files
           mkdir -p /tmp/current-branch-files
-
+          
           # Move current branch files to temp directory
           mv current-* /tmp/current-branch-files/ 2>/dev/null || echo "No current-* files to preserve"
-
+          
           echo "Preserved current branch files for later restoration"
 
       - name: Stop current branch server
@@ -261,7 +263,7 @@ jobs:
           rm -rf node_modules packages/*/node_modules packages/*/dist dist .nx/cache
 
       - name: Install dependencies for main branch
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
 
       - name: Build main branch dependencies
         run: |
@@ -279,22 +281,22 @@ jobs:
             local var_name="$1"
             local var_value="$2"
             local env_file="packages/twenty-server/.env"
-
+            
             echo "" >> "$env_file"
-
+            
             if grep -q "^${var_name}=" "$env_file" 2>/dev/null; then
               sed -i "s|^${var_name}=.*|${var_name}=${var_value}|" "$env_file"
             else
               echo "${var_name}=${var_value}" >> "$env_file"
             fi
           }
-
+          
           set_env_var "PG_DATABASE_URL" "postgres://postgres:postgres@localhost:5432/main_branch"
           set_env_var "NODE_PORT" "${{ env.MAIN_SERVER_PORT }}"
           set_env_var "REDIS_URL" "redis://localhost:6379"
           set_env_var "CLICKHOUSE_URL" "http://default:clickhousePassword@localhost:8123/twenty"
           set_env_var "CLICKHOUSE_PASSWORD" "clickhousePassword"
-
+          
           npx nx run twenty-server:database:init:prod
           npx nx run twenty-server:database:migrate:prod
 
@@ -317,19 +319,19 @@ jobs:
           timeout=300
           interval=5
           elapsed=0
-
+          
           while [ $elapsed -lt $timeout ]; do
             if curl -s "http://localhost:${{ env.MAIN_SERVER_PORT }}/graphql" > /dev/null 2>&1 && \
                curl -s "http://localhost:${{ env.MAIN_SERVER_PORT }}/rest/open-api/core" > /dev/null 2>&1; then
               echo "Main branch server is ready!"
               break
             fi
-
+            
             echo "Main branch server not ready yet, waiting ${interval}s..."
             sleep $interval
             elapsed=$((elapsed + interval))
           done
-
+          
           if [ $elapsed -ge $timeout ]; then
             echo "Timeout waiting for main branch server to start"
             echo "Main server log:"
@@ -339,15 +341,15 @@ jobs:
 
       - name: Download GraphQL and REST responses from main branch
         run: |
-          # Read admin token from shared test tokens file (single source of truth)
-          ADMIN_TOKEN=$(jq -r '.APPLE_JANE_ADMIN_ACCESS_TOKEN' packages/twenty-server/test/integration/constants/test-tokens.json)
-
+          # Admin token from jest-integration.config.ts
+          ADMIN_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIyMDIwMjAyMC05ZTNiLTQ2ZDQtYTU1Ni04OGI5ZGRjMmIwMzQiLCJ3b3Jrc3BhY2VJZCI6IjIwMjAyMDIwLTFjMjUtNGQwMi1iZjI1LTZhZWNjZjdlYTQxOSIsIndvcmtzcGFjZU1lbWJlcklkIjoiMjAyMDIwMjAtMDY4Ny00YzQxLWI3MDctZWQxYmZjYTk3MmE3IiwidXNlcldvcmtzcGFjZUlkIjoiMjAyMDIwMjAtOWUzYi00NmQ0LWE1NTYtODhiOWRkYzJiMDM1IiwiaWF0IjoxNzM5NTQ3NjYxLCJleHAiOjMzMjk3MTQ3NjYxfQ.fbOM9yhr3jWDicPZ1n771usUURiPGmNdeFApsgrbxOw"
+          
           # Load introspection query from file
           INTROSPECTION_QUERY=$(cat packages/twenty-utils/graphql-introspection-query.graphql)
-
+          
           # Prepare the query payload
           QUERY_PAYLOAD=$(echo "$INTROSPECTION_QUERY" | tr '\n' ' ' | sed 's/"/\\"/g')
-
+          
           echo "Downloading GraphQL schema from main server..."
           curl -X POST "http://localhost:${{ env.MAIN_SERVER_PORT }}/graphql" \
             -H "Content-Type: application/json" \
@@ -356,7 +358,7 @@ jobs:
             -o main-schema-introspection.json \
             -w "HTTP Status: %{http_code}\n" \
             -s
-
+          
           echo "Downloading GraphQL metadata schema from main server..."
           curl -X POST "http://localhost:${{ env.MAIN_SERVER_PORT }}/metadata" \
             -H "Content-Type: application/json" \
@@ -365,33 +367,33 @@ jobs:
             -o main-metadata-schema-introspection.json \
             -w "HTTP Status: %{http_code}\n" \
             -s
-
+          
           # Download main branch OpenAPI specs
           echo "Downloading OpenAPI specifications from main server..."
           curl -s "http://localhost:${{ env.MAIN_SERVER_PORT }}/rest/open-api/core" \
             -H "Authorization: Bearer ${ADMIN_TOKEN}" \
             -o main-rest-api.json \
             -w "HTTP Status: %{http_code}\n"
-
+          
           curl -s "http://localhost:${{ env.MAIN_SERVER_PORT }}/rest/open-api/metadata" \
             -H "Authorization: Bearer ${ADMIN_TOKEN}" \
             -o main-rest-metadata-api.json \
             -w "HTTP Status: %{http_code}\n"
-
+          
           # Verify the downloads
           echo "Main branch files downloaded:"
           ls -la main-*
-
+          
 
       - name: Restore current branch files
         run: |
           # Move current branch files back to working directory
           mv /tmp/current-branch-files/* . 2>/dev/null || echo "No files to restore"
-
+          
           # Verify all files are present
           echo "All API files restored:"
           ls -la current-* main-* 2>/dev/null || echo "Some files may be missing"
-
+          
           # Clean up temp directory
           rm -rf /tmp/current-branch-files
 
@@ -404,9 +406,9 @@ jobs:
         run: |
           echo "=== INSTALLING GRAPHQL INSPECTOR CLI ==="
           npm install -g @graphql-inspector/cli
-
+          
           echo "=== GENERATING GRAPHQL DIFF REPORTS ==="
-
+          
           # Check if GraphQL schema has changes
           echo "Checking GraphQL schema for changes..."
           if graphql-inspector diff main-schema-introspection.json current-schema-introspection.json >/dev/null 2>&1; then
@@ -424,7 +426,7 @@ jobs:
               echo "\`\`\`" >> graphql-schema-diff.md
             }
           fi
-
+          
           # Check if GraphQL metadata schema has changes
           echo "Checking GraphQL metadata schema for changes..."
           if graphql-inspector diff main-metadata-schema-introspection.json current-metadata-schema-introspection.json >/dev/null 2>&1; then
@@ -442,7 +444,7 @@ jobs:
               echo "\`\`\`" >> graphql-metadata-diff.md
             }
           fi
-
+          
           # Show summary
           echo "Generated diff files:"
           ls -la *-diff.md 2>/dev/null || echo "No diff files generated (no changes detected)"
@@ -450,32 +452,32 @@ jobs:
       - name: Check REST API Breaking Changes
         run: |
           echo "=== CHECKING REST API FOR BREAKING CHANGES ==="
-
+          
           # Use the Java-based openapi-diff via Docker
           docker run --rm -v "$(pwd):/specs" openapitools/openapi-diff:latest \
             --json /specs/rest-api-diff.json \
             /specs/main-rest-api.json /specs/current-rest-api.json || echo "OpenAPI diff completed with exit code $?"
-
+          
           # Check if the output file was created and is valid JSON
           if [ -f "rest-api-diff.json" ] && jq empty rest-api-diff.json 2>/dev/null; then
             # Check for breaking changes using Java openapi-diff JSON structure
             incompatible=$(jq -r '.incompatible // false' rest-api-diff.json)
             different=$(jq -r '.different // false' rest-api-diff.json)
-
+            
             # Count changes
             new_endpoints=$(jq -r '.newEndpoints | length' rest-api-diff.json 2>/dev/null || echo "0")
             missing_endpoints=$(jq -r '.missingEndpoints | length' rest-api-diff.json 2>/dev/null || echo "0")
             changed_operations=$(jq -r '.changedOperations | length' rest-api-diff.json 2>/dev/null || echo "0")
-
+            
             if [ "$incompatible" = "true" ]; then
               echo "❌ Breaking changes detected in REST API"
-
+              
               # Generate breaking changes report
               echo "# REST API Breaking Changes" > rest-api-diff.md
               echo "" >> rest-api-diff.md
               echo "⚠️ **Breaking changes detected that may affect existing API consumers**" >> rest-api-diff.md
               echo "" >> rest-api-diff.md
-
+              
               # Parse and format the changes from Java openapi-diff
               jq -r '
                 if (.missingEndpoints | length) > 0 then
@@ -491,7 +493,7 @@ jobs:
                   (.newEndpoints | map("- " + .method + " " + .pathUrl + ": " + (.summary // "")) | join("\n"))
                 else "" end
               ' rest-api-diff.json >> rest-api-diff.md
-
+              
             elif [ "$different" = "true" ]; then
               echo "📝 Non-breaking changes detected ($new_endpoints new endpoints, $missing_endpoints removed, $changed_operations changed) - no PR comment will be posted"
               # Don't create markdown file for non-breaking changes to avoid PR comments
@@ -501,7 +503,7 @@ jobs:
             fi
           else
             echo "⚠️ OpenAPI diff tool could not process the files"
-
+            
             echo "# REST API Analysis Error" > rest-api-diff.md
             echo "" >> rest-api-diff.md
             echo "⚠️ **Error occurred while analyzing REST API changes**" >> rest-api-diff.md
@@ -510,7 +512,7 @@ jobs:
             echo "\`\`\`" >> rest-api-diff.md
             docker run --rm -v "$(pwd):/specs" openapitools/openapi-diff:latest /specs/main-rest-api.json /specs/current-rest-api.json 2>&1 >> rest-api-diff.md || echo "Could not capture error output"
             echo "\`\`\`" >> rest-api-diff.md
-
+            
             # Don't fail the workflow for tool errors
             echo "::warning::REST API analysis tool error - continuing workflow"
           fi
@@ -518,33 +520,33 @@ jobs:
       - name: Check REST Metadata API Breaking Changes
         run: |
           echo "=== CHECKING REST METADATA API FOR BREAKING CHANGES ==="
-
+          
           # Use the Java-based openapi-diff for metadata API as well
           docker run --rm -v "$(pwd):/specs" openapitools/openapi-diff:latest \
             --json /specs/rest-metadata-api-diff.json \
             /specs/main-rest-metadata-api.json /specs/current-rest-metadata-api.json || echo "OpenAPI diff completed with exit code $?"
-
+          
           # Check if the output file was created and is valid JSON
           if [ -f "rest-metadata-api-diff.json" ] && jq empty rest-metadata-api-diff.json 2>/dev/null; then
             # Check for breaking changes using Java openapi-diff JSON structure
             incompatible=$(jq -r '.incompatible // false' rest-metadata-api-diff.json)
             different=$(jq -r '.different // false' rest-metadata-api-diff.json)
-
+            
             # Count changes
             new_endpoints=$(jq -r '.newEndpoints | length' rest-metadata-api-diff.json 2>/dev/null || echo "0")
             missing_endpoints=$(jq -r '.missingEndpoints | length' rest-metadata-api-diff.json 2>/dev/null || echo "0")
             changed_operations=$(jq -r '.changedOperations | length' rest-metadata-api-diff.json 2>/dev/null || echo "0")
-
+            
             if [ "$incompatible" = "true" ]; then
               echo "❌ Breaking changes detected in REST Metadata API"
-
+              
               # Generate breaking changes report (only for breaking changes)
               echo "# REST Metadata API Breaking Changes" > rest-metadata-api-diff.md
               echo "" >> rest-metadata-api-diff.md
               echo "⚠️ **Breaking changes detected that may affect existing API consumers**" >> rest-metadata-api-diff.md
               echo "" >> rest-metadata-api-diff.md
-
-              # Parse and format the changes from Java openapi-diff
+              
+              # Parse and format the changes from Java openapi-diff 
               jq -r '
                 if (.missingEndpoints | length) > 0 then
                   "## 🚨 Removed Endpoints (" + (.missingEndpoints | length | tostring) + ")\n" +
@@ -568,7 +570,7 @@ jobs:
             fi
           else
             echo "⚠️ OpenAPI diff tool could not process the metadata API files"
-
+            
             echo "# REST Metadata API Analysis Error" > rest-metadata-api-diff.md
             echo "" >> rest-metadata-api-diff.md
             echo "⚠️ **Error occurred while analyzing REST Metadata API changes**" >> rest-metadata-api-diff.md
@@ -577,21 +579,187 @@ jobs:
             echo "\`\`\`" >> rest-metadata-api-diff.md
             docker run --rm -v "$(pwd):/specs" openapitools/openapi-diff:latest /specs/main-rest-metadata-api.json /specs/current-rest-metadata-api.json 2>&1 >> rest-metadata-api-diff.md || echo "Could not capture error output"
             echo "\`\`\`" >> rest-metadata-api-diff.md
-
+            
             # Don't fail the workflow for tool errors
             echo "::warning::REST Metadata API analysis tool error - continuing workflow"
           fi
 
-      - name: Upload breaking changes report
+      - name: Comment API Changes on PR
         if: always()
-        uses: actions/upload-artifact@v4
+        uses: actions/github-script@v7
         with:
-          name: breaking-changes-report
-          path: |
-            *-diff.md
-            *-diff.json
-          if-no-files-found: ignore
-          retention-days: 3
+          script: |
+            const fs = require('fs');
+            let hasChanges = false;
+            let comment = '';
+            
+            try {
+              if (fs.existsSync('graphql-schema-diff.md')) {
+                const graphqlDiff = fs.readFileSync('graphql-schema-diff.md', 'utf8');
+                if (graphqlDiff.trim()) {
+                  if (!hasChanges) {
+                    comment = '## 📊 API Changes Report\n\n';
+                    hasChanges = true;
+                  }
+                  comment += '### GraphQL Schema Changes\n' + graphqlDiff + '\n\n';
+                }
+              }
+              
+              if (fs.existsSync('graphql-metadata-diff.md')) {
+                const graphqlMetadataDiff = fs.readFileSync('graphql-metadata-diff.md', 'utf8');
+                if (graphqlMetadataDiff.trim()) {
+                  if (!hasChanges) {
+                    comment = '## 📊 API Changes Report\n\n';
+                    hasChanges = true;
+                  }
+                  comment += '### GraphQL Metadata Schema Changes\n' + graphqlMetadataDiff + '\n\n';
+                }
+              }
+              
+              if (fs.existsSync('rest-api-diff.md')) {
+                const restDiff = fs.readFileSync('rest-api-diff.md', 'utf8');
+                if (restDiff.trim()) {
+                  if (!hasChanges) {
+                    comment = '## 📊 API Changes Report\n\n';
+                    hasChanges = true;
+                  }
+                  comment += restDiff + '\n\n';
+                }
+              }
+              
+              if (fs.existsSync('rest-metadata-api-diff.md')) {
+                const metadataDiff = fs.readFileSync('rest-metadata-api-diff.md', 'utf8');
+                if (metadataDiff.trim()) {
+                  if (!hasChanges) {
+                    comment = '## 📊 API Changes Report\n\n';
+                    hasChanges = true;
+                  }
+                  comment += metadataDiff + '\n\n';
+                }
+              }
+              
+              // Only post comment if there are changes
+              if (hasChanges) {
+                // Add branch state information only if there were conflicts
+                const branchState = process.env.BRANCH_STATE || 'unknown';
+                let branchStateNote = '';
+                
+                if (branchState === 'conflicts') {
+                  branchStateNote = '\n\n⚠️ **Note**: Could not merge with `main` due to conflicts. This comparison shows changes between the current branch and `main` as separate states.\n';
+                }
+                // Check if there are any breaking changes detected
+                let hasBreakingChanges = false;
+                let breakingChangeNote = '';
+                
+                // Check for breaking changes in any of the diff files
+                if (fs.existsSync('rest-api-diff.md')) {
+                  const restDiff = fs.readFileSync('rest-api-diff.md', 'utf8');
+                  if (restDiff.includes('Breaking Changes') || restDiff.includes('🚨') || 
+                      restDiff.includes('Removed Endpoints') || restDiff.includes('Changed Operations')) {
+                    hasBreakingChanges = true;
+                  }
+                }
+                
+                if (fs.existsSync('rest-metadata-api-diff.md')) {
+                  const metadataDiff = fs.readFileSync('rest-metadata-api-diff.md', 'utf8');
+                  if (metadataDiff.includes('Breaking Changes') || metadataDiff.includes('🚨') || 
+                      metadataDiff.includes('Removed Endpoints') || metadataDiff.includes('Changed Operations')) {
+                    hasBreakingChanges = true;
+                  }
+                }
+                
+                // Also check GraphQL changes for breaking changes indicators
+                if (fs.existsSync('graphql-schema-diff.md')) {
+                  const graphqlDiff = fs.readFileSync('graphql-schema-diff.md', 'utf8');
+                  if (graphqlDiff.includes('Breaking changes') || graphqlDiff.includes('BREAKING')) {
+                    hasBreakingChanges = true;
+                  }
+                }
+                
+                if (fs.existsSync('graphql-metadata-diff.md')) {
+                  const graphqlMetadataDiff = fs.readFileSync('graphql-metadata-diff.md', 'utf8');
+                  if (graphqlMetadataDiff.includes('Breaking changes') || graphqlMetadataDiff.includes('BREAKING')) {
+                    hasBreakingChanges = true;
+                  }
+                }
+                
+                // Check PR title for "breaking"
+                const prTitle = ${{ toJSON(github.event.pull_request.title) }};
+                const titleContainsBreaking = prTitle.toLowerCase().includes('breaking');
+                
+                if (hasBreakingChanges) {
+                  if (titleContainsBreaking) {
+                    breakingChangeNote = '\n\n## ✅ Breaking Change Protocol\n\n' +
+                      '**This PR title contains "breaking" and breaking changes were detected - the CI will fail as expected.**\n\n' +
+                      '📝 **Action Required**: Please add `BREAKING CHANGE:` to your commit message to trigger a major version bump.\n\n' +
+                      'Example:\n```\nfeat: add new API endpoint\n\nBREAKING CHANGE: removed deprecated field from User schema\n```';
+                  } else {
+                    breakingChangeNote = '\n\n## ⚠️ Breaking Change Protocol\n\n' +
+                      '**Breaking changes detected but PR title does not contain "breaking" - CI will pass but action needed.**\n\n' +
+                      '🔄 **Options**:\n' +
+                      '1. **If this IS a breaking change**: Add "breaking" to your PR title and add `BREAKING CHANGE:` to your commit message\n' +
+                      '2. **If this is NOT a breaking change**: The API diff tool may have false positives - please review carefully\n\n' +
+                      'For breaking changes, add to commit message:\n```\nfeat: add new API endpoint\n\nBREAKING CHANGE: removed deprecated field from User schema\n```';
+                  }
+                }
+                
+                const COMMENT_MARKER = '<!-- API_CHANGES_REPORT -->';
+                const commentBody = COMMENT_MARKER + '\n' + comment + branchStateNote + '\n⚠️ **Please review these API changes carefully before merging.**' + breakingChangeNote;
+                
+                // Get all comments to find existing API changes comment
+                const {data: comments} = await github.rest.issues.listComments({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: context.issue.number,
+                });
+                
+                // Find our existing comment
+                const botComment = comments.find(comment => comment.body.includes(COMMENT_MARKER));
+                
+                if (botComment) {
+                  // Update existing comment
+                  await github.rest.issues.updateComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    comment_id: botComment.id,
+                    body: commentBody
+                  });
+                  console.log('Updated existing API changes comment');
+                } else {
+                  // Create new comment
+                  await github.rest.issues.createComment({
+                    issue_number: context.issue.number,
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    body: commentBody
+                  });
+                  console.log('Created new API changes comment');
+                }
+              } else {
+                console.log('No API changes detected - skipping PR comment');
+                
+                // Check if there's an existing comment to remove
+                const {data: comments} = await github.rest.issues.listComments({
+                  owner: context.repo.owner,
+                  repo: context.repo.repo,
+                  issue_number: context.issue.number,
+                });
+                
+                const COMMENT_MARKER = '<!-- API_CHANGES_REPORT -->';
+                const botComment = comments.find(comment => comment.body.includes(COMMENT_MARKER));
+                
+                if (botComment) {
+                  await github.rest.issues.deleteComment({
+                    owner: context.repo.owner,
+                    repo: context.repo.repo,
+                    comment_id: botComment.id,
+                  });
+                  console.log('Deleted existing API changes comment (no changes detected)');
+                }
+              }
+            } catch (error) {
+              console.log('Could not post comment:', error);
+            }
 
       - name: Cleanup servers
         if: always()
@@ -603,4 +771,16 @@ jobs:
             kill $(cat /tmp/main-server.pid) || true
           fi
 
+      - name: Upload API specifications and diffs
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: api-specifications-and-diffs
+          path: |
+            /tmp/main-server.log
+            /tmp/current-server.log
+            *-api.json
+            *-schema-introspection.json  
+            *-diff.md
+            *-diff.json
 

.github/workflows/ci-cli.yaml

@@ -0,0 +1,103 @@
+name: CI CLI
+
+on:
+  push:
+    branches:
+      - main
+
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+
+jobs:
+  changed-files-check:
+    uses: ./.github/workflows/changed-files.yaml
+    with:
+      files: |
+        packages/twenty-cli/**
+        packages/twenty-server/**
+  cli-test:
+    needs: changed-files-check
+    if: needs.changed-files-check.outputs.any_changed == 'true'
+    timeout-minutes: 30
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        task: [lint, typecheck, test, build]
+    steps:
+      - name: Cancel Previous Runs
+        uses: styfle/[email protected]
+        with:
+          access_token: ${{ github.token }}
+      - name: Fetch custom Github Actions and base branch history
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install dependencies
+        uses: ./.github/workflows/actions/yarn-install
+      - name: Run ${{ matrix.task }} task
+        uses: ./.github/workflows/actions/nx-affected
+        with:
+          tag: scope:cli
+          tasks: ${{ matrix.task }}
+  cli-e2e-test:
+    timeout-minutes: 30
+    runs-on: depot-ubuntu-24.04-8
+    needs: [changed-files-check, cli-test]
+    if: needs.changed-files-check.outputs.any_changed == 'true'
+    services:
+      postgres:
+        image: twentycrm/twenty-postgres-spilo
+        env:
+          PGUSER_SUPERUSER: postgres
+          PGPASSWORD_SUPERUSER: postgres
+          ALLOW_NOSSL: 'true'
+          SPILO_PROVIDER: 'local'
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+      redis:
+        image: redis
+        ports:
+          - 6379:6379
+    env:
+      NODE_ENV: test
+    steps:
+      - name: Fetch custom Github Actions and base branch history
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install dependencies
+        uses: ./.github/workflows/actions/yarn-install
+      - name: Server / Append billing config to .env.test
+        working-directory: packages/twenty-server
+        run: |
+          echo "" >> .env.test
+          echo "IS_BILLING_ENABLED=true" >> .env.test
+          echo "BILLING_STRIPE_API_KEY=test-api-key" >> .env.test
+          echo "BILLING_STRIPE_BASE_PLAN_PRODUCT_ID=test-base-plan-product-id" >> .env.test
+          echo "BILLING_STRIPE_WEBHOOK_SECRET=test-webhook-secret" >> .env.test
+          echo "BILLING_PLAN_REQUIRED_LINK=http://localhost:3001/stripe-redirection" >> .env.test
+      - name: Server / Create Test DB
+        run: |
+          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "test";'
+      - name: CLI / Run E2E Tests
+        run: npx nx test:e2e twenty-cli
+  ci-cli-status-check:
+    if: always() && !cancelled()
+    timeout-minutes: 5
+    runs-on: ubuntu-latest
+    needs: [changed-files-check, cli-test, cli-e2e-test]
+    steps:
+      - name: Fail job if any needs failed
+        if: contains(needs.*.result, 'failure')
+        run: exit 1

.github/workflows/ci-create-app.yaml

@@ -1,58 +0,0 @@
-name: CI Create App
-
-on:
-  push:
-    branches:
-      - main
-
-  pull_request:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  changed-files-check:
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        packages/create-twenty-app/**
-        !packages/create-twenty-app/package.json
-  create-app-test:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        task: [lint, typecheck, test]
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build
-        run: npx nx build create-twenty-app
-      - name: Run ${{ matrix.task }} task
-        uses: ./.github/actions/nx-affected
-        with:
-          tag: scope:create-app
-          tasks: ${{ matrix.task }}
-  ci-create-app-status-check:
-    if: always() && !cancelled()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    needs: [changed-files-check, create-app-test]
-    steps:
-      - name: Fail job if any needs failed
-        if: contains(needs.*.result, 'failure')
-        run: exit 1

.github/workflows/ci-docs.yaml

@@ -1,47 +0,0 @@
-name: CI Docs
-
-on:
-  push:
-    branches:
-      - main
-
-  pull_request:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  changed-files-check:
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        package.json
-        packages/twenty-docs/**
-        eslint.config.mjs
-
-  docs-lint:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 10
-    runs-on: ubuntu-latest
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-
-      - name: Fetch local actions
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Docs / Lint English MDX files
-        run: npx eslint "packages/twenty-docs/{developers,user-guide,twenty-ui,getting-started,snippets}/**/*.mdx" --max-warnings 0
-

.github/workflows/ci-e2e.yaml

@@ -0,0 +1,136 @@
+name: CI E2E Playwright Tests
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    types: [opened, synchronize, reopened, labeled]
+
+permissions:
+  contents: read
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
+
+jobs:
+  changed-files-check:
+    uses: ./.github/workflows/changed-files.yaml
+    with:
+      files: |
+          packages/**
+          playwright.config.ts
+          .github/workflows/ci-e2e.yaml
+  test:
+    runs-on: ubuntu-latest
+    needs: changed-files-check
+    if: needs.changed-files-check.outputs.any_changed == 'true' && ( github.event_name == 'push' || (github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'run-e2e')))
+    timeout-minutes: 30
+    env:
+      # https://github.com/actions/runner-images/issues/70#issuecomment-589562148
+      NODE_OPTIONS: "--max-old-space-size=10240"
+    services:
+      postgres:
+        image: twentycrm/twenty-postgres-spilo
+        env:
+          PGUSER_SUPERUSER: postgres
+          PGPASSWORD_SUPERUSER: postgres
+          ALLOW_NOSSL: "true"
+          SPILO_PROVIDER: "local"
+        ports:
+          - 5432:5432
+        options: >-
+          --health-cmd pg_isready
+          --health-interval 10s
+          --health-timeout 5s
+          --health-retries 5
+      redis:
+        image: redis
+        ports:
+          - 6379:6379
+    steps:
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+    - uses: actions/setup-node@v4
+      with:
+        node-version: lts/*
+
+    - name: Check system resources
+      run: |
+        echo "Available memory:"
+        free -h
+        echo "Available disk space:"
+        df -h
+        echo "CPU info:"
+        lscpu
+
+    - name: Install dependencies
+      uses: ./.github/workflows/actions/yarn-install
+
+    - name: Build twenty-shared
+      run: npx nx build twenty-shared
+
+    - name: Install Playwright Browsers
+      run: npx nx setup twenty-e2e-testing
+
+    - name: Setup environment files
+      run: |
+        cp packages/twenty-front/.env.example packages/twenty-front/.env
+        npx nx reset:env twenty-server
+
+    - name: Build frontend
+      run: NODE_ENV=production NODE_OPTIONS="--max-old-space-size=10240" npx nx build twenty-front
+
+    - name: Build server
+      run: npx nx build twenty-server
+
+    - name: Create and setup database
+      run: |
+        PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "default";'
+        PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "test";'
+        npx nx run twenty-server:database:reset
+
+    - name: Start server
+      run: |
+        npx nx start twenty-server &
+        echo "Waiting for server to be ready..."
+        timeout 60 bash -c 'until curl -s http://localhost:3000/health; do sleep 2; done'
+
+    - name: Start frontend
+      run: |
+        npm_config_yes=true npx serve -s packages/twenty-front/build -l 3001 &
+        echo "Waiting for frontend to be ready..."
+        timeout 60 bash -c 'until curl -s http://localhost:3001; do sleep 2; done'
+        
+    - name: Start worker
+      run: |
+        npx nx run twenty-server:worker &
+        echo "Worker started"
+
+    - name: Run Playwright tests
+      run: npx nx test twenty-e2e-testing
+
+    - uses: actions/upload-artifact@v4
+      if: always()
+      with:
+        name: playwright-report
+        path: packages/twenty-e2e-testing/run_results/
+        retention-days: 30
+
+    - uses: actions/upload-artifact@v4
+      if: always()
+      with:
+        name: playwright-report
+        path: packages/twenty-e2e-testing/playwright-report/
+        retention-days: 30
+  ci-e2e-status-check:
+      if: always() && !cancelled()
+      timeout-minutes: 5
+      runs-on: ubuntu-latest
+      needs: [changed-files-check, test]
+      steps:
+        - name: Fail job if any needs failed
+          if: contains(needs.*.result, 'failure')
+          run: exit 1

.github/workflows/ci-emails.yaml

@@ -25,14 +25,14 @@ jobs:
     needs: changed-files-check
     if: needs.changed-files-check.outputs.any_changed == 'true'
     timeout-minutes: 10
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     steps:
       - name: Fetch custom Github Actions and base branch history
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Build twenty-emails
         run: npx nx build twenty-emails
       - name: Run email tests
@@ -40,17 +40,17 @@ jobs:
           # Start the email server in the background
           npx nx run twenty-emails:start &
           SERVER_PID=$!
-
+          
           # Wait for server to start
           sleep 20
-
+          
           # Check if server is running
           if ! curl -s http://localhost:4001/preview/test.email > /dev/null; then
             echo "Email server failed to start"
             kill $SERVER_PID
             exit 1
           fi
-
+          
           # Kill the server
           kill $SERVER_PID
   ci-emails-status-check:
@@ -61,4 +61,4 @@ jobs:
     steps:
       - name: Fail job if any needs failed
         if: contains(needs.*.result, 'failure')
-        run: exit 1
+        run: exit 1 

.github/workflows/ci-front.yaml

@@ -1,9 +1,11 @@
-name: CI Front and E2E
+name: CI Front
 
 on:
-  pull_request:
+  push:
+    branches:
+      - main
 
-  merge_group:
+  pull_request:
 
 permissions:
   contents: read
@@ -13,9 +15,8 @@ concurrency:
   cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
 
 env:
-  # restore-cache action adds 'v4-' prefix and '-<branch>-<sha>' suffix to the key
-  STORYBOOK_BUILD_CACHE_KEY_FOR_RESTORE_ACTION: storybook-build-ubuntu-latest-8-cores-runner
-  STORYBOOK_BUILD_CACHE_KEY_FOR_SAVE_ACTION: v4-storybook-build-ubuntu-latest-8-cores-runner-${{ github.ref_name }}-${{ github.sha }}
+  STORYBOOK_BUILD_CACHE_KEY_FOR_RESTORE_ACTION: storybook-build-depot-ubuntu-24.04-8-runner
+  STORYBOOK_BUILD_CACHE_KEY_FOR_SAVE_ACTION: v3-storybook-build-depot-ubuntu-24.04-8-runner-${{ github.ref_name }}-${{ github.sha }}
 
 jobs:
   changed-files-check:
@@ -27,22 +28,11 @@ jobs:
         packages/twenty-front/**
         packages/twenty-ui/**
         packages/twenty-shared/**
-        packages/twenty-sdk/**
-        !packages/twenty-sdk/package.json
-  changed-files-check-e2e:
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        packages/**
-        !packages/create-twenty-app/package.json
-        !packages/twenty-sdk/package.json
-        playwright.config.ts
-        .github/workflows/ci-front.yaml
   front-sb-build:
     needs: changed-files-check
     if: needs.changed-files-check.outputs.any_changed == 'true'
     timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     env:
       REACT_APP_SERVER_BASE_URL: http://localhost:3000
     steps:
@@ -55,7 +45,7 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Diagnostic disk space issue
         run: df -h
       - name: Front / Write .env
@@ -63,12 +53,12 @@ jobs:
       - name: Front / Build storybook
         run: npx nx storybook:build twenty-front
       - name: Save storybook build cache
-        uses: ./.github/actions/save-cache
+        uses: ./.github/workflows/actions/save-cache
         with:
           key: ${{ env.STORYBOOK_BUILD_CACHE_KEY_FOR_SAVE_ACTION }}
   front-sb-test:
     timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     needs: front-sb-build
     strategy:
       fail-fast: false
@@ -84,66 +74,56 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build dependencies
-        run: |
-          npx nx build twenty-shared
-          npx nx build twenty-ui
-          npx nx build twenty-sdk
+        uses: ./.github/workflows/actions/yarn-install
       - name: Install Playwright
-        run: |
-          cd packages/twenty-front
-          npx playwright install
+        run: cd packages/twenty-front && npx playwright install
+      - name: Restore storybook build cache
+        uses: ./.github/workflows/actions/restore-cache
+        with:
+          key: ${{ env.STORYBOOK_BUILD_CACHE_KEY_FOR_RESTORE_ACTION }}
       - name: Front / Write .env
         run: npx nx reset:env twenty-front
       - name: Run storybook tests
-        run: npx nx storybook:test twenty-front --configuration=${{ matrix.storybook_scope }} --shard=${{ matrix.shard }}/${{ env.SHARD_COUNTER }}
-      # - name: Rename coverage file
-      #   run: |
-      #     if [ -f "packages/twenty-front/coverage/storybook/coverage-final.json" ]; then
-      #       mv packages/twenty-front/coverage/storybook/coverage-final.json packages/twenty-front/coverage/storybook/coverage-shard-${{matrix.shard}}.json
-      #     else
-      #       echo "Error: coverage-final.json not found"
-      #       ls -la packages/twenty-front/coverage/storybook/ || echo "Coverage directory does not exist"
-      #       exit 1
-      #     fi
-      # - name: Upload coverage artifact
-      #   uses: actions/upload-artifact@v4
-      #   with:
-      #     retention-days: 1
-      #     name: coverage-artifacts-${{ matrix.storybook_scope }}-${{ github.run_id }}-${{ matrix.shard }}
-      #     path: packages/twenty-front/coverage/storybook/coverage-shard-${{matrix.shard}}.json
-  # merge-reports-and-check-coverage:
-  #   timeout-minutes: 30
-  #   runs-on: ubuntu-latest
-  #   needs: front-sb-test
-  #   env:
-  #     PATH_TO_COVERAGE: packages/twenty-front/coverage/storybook
-  #   strategy:
-  #     matrix:
-  #       storybook_scope: [modules, pages, performance]
-  #   steps:
-  #     - uses: actions/checkout@v4
-  #       with:
-  #         fetch-depth: 0
-  #     - name: Install dependencies
-  #       uses: ./.github/actions/yarn-install
-  #     - uses: actions/download-artifact@v4
-  #       with:
-  #         pattern: coverage-artifacts-${{ matrix.storybook_scope }}-${{ github.run_id }}-*
-  #         merge-multiple: true
-  #         path: coverage-artifacts
-  #     - name: Merge coverage reports
-  #       run: |
-  #         mkdir -p ${{ env.PATH_TO_COVERAGE }}
-  #         npx nyc merge coverage-artifacts ${{ env.PATH_TO_COVERAGE }}/coverage-storybook.json
-  #     - name: Checking coverage
-  #       run: npx nx storybook:coverage twenty-front --checkCoverage=true --configuration=${{ matrix.storybook_scope }}
+        run: npx nx storybook:serve-and-test:static twenty-front --configuration=${{ matrix.storybook_scope }} --shard=${{ matrix.shard }}/${{ env.SHARD_COUNTER }} --checkCoverage=false
+      - name: Rename coverage file
+        run: mv packages/twenty-front/coverage/storybook/coverage-storybook.json packages/twenty-front/coverage/storybook/coverage-shard-${{matrix.shard}}.json
+      - name: Upload coverage artifact
+        uses: actions/upload-artifact@v4
+        with:
+          retention-days: 1
+          name: coverage-artifacts-${{ matrix.storybook_scope }}-${{ github.run_id }}-${{ matrix.shard }}
+          path: packages/twenty-front/coverage/storybook/coverage-shard-${{matrix.shard}}.json
+  merge-reports-and-check-coverage:
+    timeout-minutes: 30
+    runs-on: ubuntu-latest
+    needs: front-sb-test
+    env:
+      PATH_TO_COVERAGE: packages/twenty-front/coverage/storybook
+    strategy:
+      matrix:
+        storybook_scope: [modules, pages, performance]
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install dependencies
+        uses: ./.github/workflows/actions/yarn-install
+      - uses: actions/download-artifact@v4
+        with:
+          pattern: coverage-artifacts-${{ matrix.storybook_scope }}-${{ github.run_id }}-*
+          merge-multiple: true
+          path: coverage-artifacts
+      - name: Merge coverage reports
+        run: |
+          mkdir -p ${{ env.PATH_TO_COVERAGE }}
+          npx nyc merge coverage-artifacts ${{ env.PATH_TO_COVERAGE }}/coverage-storybook.json
+      - name: Checking coverage
+        run: npx nx storybook:coverage twenty-front --checkCoverage=true --configuration=${{ matrix.storybook_scope }}
   front-chromatic-deployment:
     timeout-minutes: 30
-    if: false
+    if: contains(github.event.pull_request.labels.*.name, 'run-chromatic') || github.event_name == 'push'
     needs: front-sb-build
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     env:
       REACT_APP_SERVER_BASE_URL: http://127.0.0.1:3000
       CHROMATIC_PROJECT_TOKEN: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
@@ -152,11 +132,11 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Restore storybook build cache
-        uses: ./.github/actions/restore-cache
+        uses: ./.github/workflows/actions/restore-cache
         with:
-          key: ${{ env.STORYBOOK_BUILD_CACHE_KEY_FOR_RESTORE_ACTION }}
+          key: ${{ env.STORYBOOK_BUILD_CACHE_KEY }}
       - name: Front / Write .env
         run: |
           cd packages/twenty-front
@@ -171,7 +151,6 @@ jobs:
     timeout-minutes: 30
     runs-on: ubuntu-latest
     env:
-      NODE_OPTIONS: '--max-old-space-size=4096'
       TASK_CACHE_KEY: front-task-${{ matrix.task }}
     strategy:
       matrix:
@@ -186,166 +165,26 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Restore ${{ matrix.task }} cache
         id: restore-task-cache
-        uses: ./.github/actions/restore-cache
+        uses: ./.github/workflows/actions/restore-cache
         with:
           key: ${{ env.TASK_CACHE_KEY }}
       - name: Reset .env
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:frontend
           tasks: reset:env
       - name: Run ${{ matrix.task }} task
-        id: run-task
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:frontend
           tasks: ${{ matrix.task }}
       - name: Save ${{ matrix.task }} cache
-        uses: ./.github/actions/save-cache
+        uses: ./.github/workflows/actions/save-cache
         with:
           key: ${{ steps.restore-task-cache.outputs.cache-primary-key }}
-  front-build:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
-    env:
-      NODE_OPTIONS: "--max-old-space-size=10240"
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Front / Write .env
-        run: npx nx reset:env twenty-front
-      - name: Build frontend
-        run: npx nx build twenty-front
-      # - name: Upload frontend build artifact
-      #   uses: actions/upload-artifact@v4
-      #   with:
-      #     name: frontend-build
-      #     path: packages/twenty-front/build
-      #     retention-days: 1
-  e2e-test:
-    runs-on: ubuntu-latest
-    needs: [changed-files-check-e2e, front-build]
-    if: |
-      always() &&
-      needs.changed-files-check-e2e.outputs.any_changed == 'true' &&
-      (needs.front-build.result == 'success' || needs.front-build.result == 'skipped') &&
-      (github.event_name == 'push' || github.event_name == 'merge_group' || (github.event_name == 'pull_request' && contains(github.event.pull_request.labels.*.name, 'run-e2e')))
-    timeout-minutes: 30
-    env:
-      NODE_OPTIONS: "--max-old-space-size=10240"
-    services:
-      postgres:
-        image: twentycrm/twenty-postgres-spilo
-        env:
-          PGUSER_SUPERUSER: postgres
-          PGPASSWORD_SUPERUSER: postgres
-          ALLOW_NOSSL: "true"
-          SPILO_PROVIDER: "local"
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - uses: actions/setup-node@v4
-        with:
-          node-version: lts/*
-
-      - name: Check system resources
-        run: |
-          echo "Available memory:"
-          free -h
-          echo "Available disk space:"
-          df -h
-          echo "CPU info:"
-          lscpu
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Build twenty-shared
-        run: npx nx build twenty-shared
-
-      - name: Install Playwright Browsers
-        run: npx nx setup twenty-e2e-testing
-
-      - name: Setup environment files
-        run: |
-          cp packages/twenty-front/.env.example packages/twenty-front/.env
-          npx nx reset:env:e2e-testing-server twenty-server
-
-      # - name: Download frontend build artifact
-      #   if: needs.front-build.result == 'success'
-      #   uses: actions/download-artifact@v4
-      #   with:
-      #     name: frontend-build
-      #     path: packages/twenty-front/build
-
-      # - name: Build frontend (if not available from front-build)
-      #   if: needs.front-build.result == 'skipped'
-      #   run: NODE_ENV=production NODE_OPTIONS="--max-old-space-size=10240" npx nx build twenty-front
-
-      - name: Build frontend
-        run: NODE_ENV=production NODE_OPTIONS="--max-old-space-size=10240" npx nx build twenty-front
-
-      - name: Build server
-        run: npx nx build twenty-server
-
-      - name: Create and setup database
-        run: |
-          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "default";'
-          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "test";'
-          npx nx run twenty-server:database:reset
-
-      - name: Start server
-        run: |
-          npx nx start twenty-server &
-          echo "Waiting for server to be ready..."
-          timeout 60 bash -c 'until curl -s http://localhost:3000/health; do sleep 2; done'
-
-      - name: Start frontend
-        run: |
-          npm_config_yes=true npx serve -s packages/twenty-front/build -l 3001 &
-          echo "Waiting for frontend to be ready..."
-          timeout 60 bash -c 'until curl -s http://localhost:3001; do sleep 2; done'
-
-      - name: Start worker
-        run: |
-          npx nx run twenty-server:worker &
-          echo "Worker started"
-
-      - name: Run Playwright tests
-        run: npx nx test twenty-e2e-testing
-
-      # - uses: actions/upload-artifact@v4
-      #   if: always()
-      #   with:
-      #     name: playwright-report
-      #     path: packages/twenty-e2e-testing/run_results/
-      #     retention-days: 30
-
   ci-front-status-check:
     if: always() && !cancelled()
     timeout-minutes: 5
@@ -354,8 +193,8 @@ jobs:
       [
         changed-files-check,
         front-task,
-        front-build,
-        # merge-reports-and-check-coverage,
+        front-chromatic-deployment,
+        merge-reports-and-check-coverage,
         front-sb-test,
         front-sb-build,
       ]
@@ -363,12 +202,3 @@ jobs:
       - name: Fail job if any needs failed
         if: contains(needs.*.result, 'failure')
         run: exit 1
-  ci-e2e-status-check:
-    if: always() && !cancelled()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    needs: [changed-files-check-e2e, e2e-test]
-    steps:
-      - name: Fail job if any needs failed
-        if: contains(needs.*.result, 'failure')
-        run: exit 1

.github/workflows/ci-release-create.yaml

@@ -56,4 +56,4 @@ jobs:
           title: Release v${{ steps.sanitize.outputs.version }}
           labels: |
             release
-            ${{ github.event.inputs.create_release == true && 'create_release' || '' }}
+            ${{ github.event.inputs.create_release == true && 'create_release' || '' }}

.github/workflows/ci-sdk.yaml

@@ -1,102 +0,0 @@
-name: CI SDK
-
-on:
-  merge_group:
-
-  pull_request:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  changed-files-check:
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        packages/twenty-sdk/**
-        !packages/twenty-sdk/package.json
-  sdk-test:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        task: [lint, typecheck, test:unit, storybook:build, storybook:test, test:integration]
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build
-        run: npx nx build twenty-sdk
-      - name: Install Playwright
-        if: contains(matrix.task, 'storybook')
-        run: npx playwright install chromium
-      - name: Run ${{ matrix.task }} task
-        uses: ./.github/actions/nx-affected
-        with:
-          tag: scope:sdk
-          tasks: ${{ matrix.task }}
-  sdk-e2e-test:
-    timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
-    needs: [changed-files-check, sdk-test]
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    services:
-      postgres:
-        image: twentycrm/twenty-postgres-spilo
-        env:
-          PGUSER_SUPERUSER: postgres
-          PGPASSWORD_SUPERUSER: postgres
-          ALLOW_NOSSL: 'true'
-          SPILO_PROVIDER: 'local'
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    env:
-      NODE_ENV: test
-    steps:
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build
-        run: npx nx build twenty-sdk
-      - name: Server / Create Test DB
-        run: |
-          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "test";'
-      - name: SDK / Run e2e Tests
-        uses: ./.github/actions/nx-affected
-        with:
-          tag: scope:sdk
-          tasks: test:e2e
-  ci-sdk-status-check:
-    if: always() && !cancelled()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    needs: [changed-files-check, sdk-test, sdk-e2e-test]
-    steps:
-      - name: Fail job if any needs failed
-        if: contains(needs.*.result, 'failure')
-        run: exit 1

.github/workflows/ci-server.yaml

@@ -1,9 +1,11 @@
 name: CI Server
 
 on:
-  pull_request:
+  push:
+    branches:
+      - main
 
-  merge_group:
+  pull_request:
 
 permissions:
   contents: read
@@ -31,7 +33,7 @@ jobs:
     needs: changed-files-check
     if: needs.changed-files-check.outputs.any_changed == 'true'
     timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     services:
       postgres:
         image: twentycrm/twenty-postgres-spilo
@@ -57,16 +59,16 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Restore server setup
         id: restore-server-setup-cache
-        uses: ./.github/actions/restore-cache
+        uses: ./.github/workflows/actions/restore-cache
         with:
           key: ${{ env.SERVER_SETUP_CACHE_KEY }}
       - name: Build twenty-shared
         run: npx nx build twenty-shared
       - name: Server / Run lint & typecheck
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:backend
           tasks: lint,typecheck
@@ -124,13 +126,13 @@ jobs:
           npx nx run twenty-front:graphql:generate
           npx nx run twenty-front:graphql:generate --configuration=metadata
 
-          # Check if GraphQL generated files were modified
-          if ! git diff --quiet -- packages/twenty-front/src/generated packages/twenty-front/src/generated-metadata; then
+          # Check if any files were modified
+          if ! git diff --quiet; then
             echo "::error::GraphQL schema changes detected. Please run 'npx nx run twenty-front:graphql:generate' and 'npx nx run twenty-front:graphql:generate --configuration=metadata' and commit the changes."
             echo ""
             echo "The following GraphQL schema changes were detected:"
             echo "==================================================="
-            git diff -- packages/twenty-front/src/generated packages/twenty-front/src/generated-metadata
+            git diff
             echo "==================================================="
             echo ""
             echo "Please run 'npx nx run twenty-front:graphql:generate' and 'npx nx run twenty-front:graphql:generate --configuration=metadata' and commit the changes."
@@ -138,12 +140,12 @@ jobs:
             exit 1
           fi
       - name: Save server setup
-        uses: ./.github/actions/save-cache
+        uses: ./.github/workflows/actions/save-cache
         with:
           key: ${{ steps.restore-server-setup-cache.outputs.cache-primary-key }}
   server-test:
     timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     needs: server-setup
     steps:
       - name: Fetch custom Github Actions and base branch history
@@ -151,25 +153,25 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Restore server setup
-        uses: ./.github/actions/restore-cache
+        uses: ./.github/workflows/actions/restore-cache
         with:
           key: ${{ env.SERVER_SETUP_CACHE_KEY }}
       - name: Server / Run Tests
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:backend
           tasks: test
 
   server-integration-test:
     timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
+    runs-on: depot-ubuntu-24.04-8
     needs: server-setup
     strategy:
       fail-fast: false
       matrix:
-        shard: [1, 2, 3, 4, 5, 6, 7, 8]
+        shard: [1, 2, 3, 4, 5]
     services:
       postgres:
         image: twentycrm/twenty-postgres-spilo
@@ -207,14 +209,14 @@ jobs:
       ANALYTICS_ENABLED: true
       CLICKHOUSE_URL: "http://default:clickhousePassword@localhost:8123/twenty"
       CLICKHOUSE_PASSWORD: clickhousePassword
-      SHARD_COUNTER: 8
+      SHARD_COUNTER: 5
     steps:
       - name: Fetch custom Github Actions and base branch history
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Update .env.test for integrations tests
         run: |
           echo "" >> .env.test
@@ -224,7 +226,7 @@ jobs:
           echo "BILLING_STRIPE_WEBHOOK_SECRET=test-webhook-secret" >> .env.test
           echo "BILLING_PLAN_REQUIRED_LINK=http://localhost:3001/stripe-redirection" >> .env.test
       - name: Restore server setup
-        uses: ./.github/actions/restore-cache
+        uses: ./.github/workflows/actions/restore-cache
         with:
           key: ${{ env.SERVER_SETUP_CACHE_KEY }}
       - name: Server / Build
@@ -241,7 +243,7 @@ jobs:
       - name: Run ClickHouse seeds
         run: npx nx clickhouse:seed twenty-server
       - name: Server / Run Integration Tests
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:backend
           tasks: 'test:integration'

.github/workflows/ci-shared.yaml

@@ -1,7 +1,9 @@
 name: CI Shared
 
 on:
-  merge_group:
+  push:
+    branches:
+      - main
 
   pull_request:
 
@@ -23,8 +25,6 @@ jobs:
     if: needs.changed-files-check.outputs.any_changed == 'true'
     timeout-minutes: 30
     runs-on: ubuntu-latest
-    env:
-      NODE_OPTIONS: '--max-old-space-size=4096'
     strategy:
       matrix:
         task: [lint, typecheck, test]
@@ -38,9 +38,9 @@ jobs:
         with:
           fetch-depth: 0
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Run ${{ matrix.task }} task
-        uses: ./.github/actions/nx-affected
+        uses: ./.github/workflows/actions/nx-affected
         with:
           tag: scope:frontend
           tasks: ${{ matrix.task }}

.github/workflows/ci-test-docker-compose.yaml

@@ -1,11 +1,5 @@
-name: CI Docker Compose
-
-permissions:
-  contents: read
-
+name: 'Test Docker Compose'
 on:
-  merge_group:
-
   pull_request:
 
 concurrency:

.github/workflows/ci-utils.yaml

@@ -9,7 +9,10 @@ on:
     types: [opened, synchronize, reopened, closed]
 
 permissions:
+  actions: write
   checks: write
+  contents: write
+  issues: write
   pull-requests: write
   statuses: write
 
@@ -27,12 +30,12 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Utils / Run Danger.js
         run: cd packages/twenty-utils && npx nx danger:ci
         env:
           DANGER_GITHUB_API_TOKEN: ${{ github.token }}
-
+  
   congratulate:
     timeout-minutes: 3
     runs-on: ubuntu-latest
@@ -40,7 +43,7 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
       - name: Run congratulate-dangerfile.js
         run: cd packages/twenty-utils && npx nx danger:congratulate
         env:

.github/workflows/ci-website.yaml

@@ -4,7 +4,9 @@ permissions:
   contents: read
 
 on:
-  merge_group:
+  push:
+    branches:
+      - main
 
   pull_request:
 
@@ -45,7 +47,7 @@ jobs:
           fetch-depth: 0
 
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
 
       - name: Server / Create DB
         run: PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "default";'

.github/workflows/ci-zapier.yaml

@@ -1,128 +0,0 @@
-name: CI Zapier
-
-on:
-  pull_request:
-
-  merge_group:
-
-permissions:
-  contents: read
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-env:
-  SERVER_SETUP_CACHE_KEY: server-setup
-
-jobs:
-  changed-files-check:
-    uses: ./.github/workflows/changed-files.yaml
-    with:
-      files: |
-        packages/twenty-zapier/**
-        packages/twenty-server/**
-        !packages/twenty-zapier/package.json
-        !packages/twenty-zapier/CHANGELOG.md
-  server-setup:
-    needs: changed-files-check
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest-8-cores
-    services:
-      postgres:
-        image: twentycrm/twenty-postgres-spilo
-        env:
-          PGUSER_SUPERUSER: postgres
-          PGPASSWORD_SUPERUSER: postgres
-          ALLOW_NOSSL: 'true'
-          SPILO_PROVIDER: 'local'
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    steps:
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Build twenty-shared
-        run: npx nx build twenty-shared
-
-      - name: Server / Write .env
-        run: npx nx reset:env:e2e-testing-server twenty-server
-
-      - name: Server / Build
-        run: npx nx build twenty-server
-
-      - name: Create and setup database
-        run: |
-          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "default";'
-          PGPASSWORD=postgres psql -h localhost -p 5432 -U postgres -d postgres -c 'CREATE DATABASE "test";'
-          npx nx run twenty-server:database:reset
-
-      - name: Server / Start
-        run: |
-          npx nx start twenty-server &
-          echo "Waiting for server to be ready..."
-          timeout 60 bash -c 'until curl -s http://localhost:3000/health; do sleep 2; done'
-
-      - name: Start worker
-        run: |
-          npx nx run twenty-server:worker &
-          echo "Worker started"
-
-      - name: Zapier / Build
-        run: npx nx build twenty-zapier
-
-      - name: Zapier / Run Tests
-        uses: ./.github/actions/nx-affected
-        with:
-          tag: scope:zapier
-          tasks: test
-
-  zapier-test:
-    needs: server-setup
-    if: needs.changed-files-check.outputs.any_changed == 'true'
-    timeout-minutes: 30
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        task: [lint, typecheck, validate]
-    steps:
-      - name: Cancel Previous Runs
-        uses: styfle/[email protected]
-        with:
-          access_token: ${{ github.token }}
-      - name: Fetch custom Github Actions and base branch history
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build
-        run: npx nx build twenty-zapier
-      - name: Run ${{ matrix.task }} task
-        uses: ./.github/actions/nx-affected
-        with:
-          tag: scope:zapier
-          tasks: ${{ matrix.task }}
-  ci-zapier-status-check:
-    if: always() && !cancelled()
-    timeout-minutes: 5
-    runs-on: ubuntu-latest
-    needs: [changed-files-check, zapier-test]
-    steps:
-      - name: Fail job if any needs failed
-        if: contains(needs.*.result, 'failure')
-        run: exit 1

.github/workflows/claude.yml

@@ -1,167 +0,0 @@
-name: Claude Code
-
-on:
-  issue_comment:
-    types: [created]
-  pull_request_review_comment:
-    types: [created]
-  pull_request_review:
-    types: [submitted]
-  issues:
-    types: [opened, assigned]
-  repository_dispatch:
-    types: [claude-core-team-issues]
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.event.issue.number || github.event.pull_request.number || github.event.client_payload.issue_number }}
-  cancel-in-progress: false
-
-jobs:
-  claude:
-    if: |
-      (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude') && github.event.comment.user.type != 'Bot') ||
-      (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude') && github.event.comment.user.type != 'Bot') ||
-      (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude') && github.event.review.user.type != 'Bot') ||
-      (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    permissions:
-      contents: write
-      pull-requests: write
-      issues: write
-      id-token: write
-    services:
-      postgres:
-        image: postgres:16
-        env:
-          POSTGRES_USER: postgres
-          POSTGRES_PASSWORD: postgres
-          POSTGRES_DB: postgres
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Run Claude Code
-        id: claude-code
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          additional_permissions: |
-            actions: read
-          claude_args: '--max-turns 200 --model opus --allowedTools "Edit,Write,WebFetch,Bash(bash packages/twenty-utils/setup-dev-env.sh),Bash(npx nx *),Bash(npx jest *),Bash(yarn *),Bash(git *),Bash(gh *),Bash(sed *),Bash(python3 *),Bash(rm *),Bash(find *),Bash(grep *),Bash(cat *),Bash(ls *),Bash(head *),Bash(tail *),Bash(wc *),Bash(sort *),Bash(uniq *),Bash(mkdir *),Bash(cp *),Bash(mv *),Bash(touch *),Bash(chmod *),Bash(echo *),Bash(curl *),Bash(cd *),Bash(pwd *),Bash(diff *),Bash(xargs *),Bash(awk *),Bash(cut *),Bash(tee *),Bash(tr *)"'
-          settings: |
-            {
-              "env": {
-                "PG_DATABASE_URL": "postgres://postgres:postgres@localhost:5432/default"
-              }
-            }
-      - name: Post Create-PR link if Claude ran out of turns
-        if: failure()
-        env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        run: |
-          BRANCH=$(git branch --show-current)
-          if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "" ]; then
-            exit 0
-          fi
-          AHEAD=$(git rev-list --count main.."$BRANCH" 2>/dev/null || echo "0")
-          if [ "$AHEAD" = "0" ]; then
-            exit 0
-          fi
-          EXISTING_PR=$(gh pr list --head "$BRANCH" --json number --jq '.[0].number' 2>/dev/null || echo "")
-          if [ -n "$EXISTING_PR" ]; then
-            exit 0
-          fi
-          ISSUE_NUMBER="${{ github.event.issue.number || github.event.pull_request.number }}"
-          ENCODED_BRANCH=$(python3 -c "import urllib.parse, sys; print(urllib.parse.quote(sys.argv[1], safe=''))" "$BRANCH")
-          PR_URL="https://github.com/${{ github.repository }}/compare/main...${ENCODED_BRANCH}?quick_pull=1"
-          BODY="⚠️ Claude ran out of turns before creating a PR. Work has been pushed to [\`$BRANCH\`](https://github.com/${{ github.repository }}/tree/$ENCODED_BRANCH).\n\n[**Create PR →**]($PR_URL)"
-          if [ -n "$ISSUE_NUMBER" ]; then
-            gh issue comment "$ISSUE_NUMBER" --body "$(echo -e "$BODY")"
-          fi
-
-  claude-cross-repo:
-    if: github.event_name == 'repository_dispatch'
-    runs-on: ubuntu-latest
-    timeout-minutes: 60
-    permissions:
-      contents: write
-      pull-requests: write
-      issues: write
-      id-token: write
-    services:
-      postgres:
-        image: postgres:16
-        env:
-          POSTGRES_USER: postgres
-          POSTGRES_PASSWORD: postgres
-          POSTGRES_DB: postgres
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd pg_isready
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 5
-      redis:
-        image: redis
-        ports:
-          - 6379:6379
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-      - name: Build prompt from dispatch payload
-        id: prompt
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const p = context.payload.client_payload;
-            let prompt;
-            if (p.comment_body) {
-              prompt = `You are responding to a comment on issue #${p.issue_number} ("${p.issue_title}") in the ${p.repo_full_name} repository.\n\nThe comment by @${p.sender} says:\n\n${p.comment_body}\n\nIssue body:\n\n${p.issue_body}\n\nPlease help with this request. The code you are working with is the twenty codebase (this repository).`;
-            } else {
-              prompt = `You are responding to issue #${p.issue_number} ("${p.issue_title}") in the ${p.repo_full_name} repository, opened by @${p.sender}.\n\nIssue body:\n\n${p.issue_body}\n\nPlease help with this request. The code you are working with is the twenty codebase (this repository).`;
-            }
-            core.setOutput('prompt', prompt);
-            core.setOutput('repo', p.repo_full_name);
-            core.setOutput('issue_number', p.issue_number);
-      - name: Run Claude Code
-        id: claude
-        uses: anthropics/claude-code-action@v1
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          prompt: ${{ steps.prompt.outputs.prompt }}
-          additional_permissions: |
-            actions: read
-          claude_args: '--max-turns 200 --model opus --allowedTools "Edit,Write,WebFetch,Bash(bash packages/twenty-utils/setup-dev-env.sh),Bash(npx nx *),Bash(npx jest *),Bash(yarn *),Bash(git *),Bash(gh *),Bash(sed *),Bash(python3 *),Bash(rm *),Bash(find *),Bash(grep *),Bash(cat *),Bash(ls *),Bash(head *),Bash(tail *),Bash(wc *),Bash(sort *),Bash(uniq *),Bash(mkdir *),Bash(cp *),Bash(mv *),Bash(touch *),Bash(chmod *),Bash(echo *),Bash(curl *),Bash(cd *),Bash(pwd *),Bash(diff *),Bash(xargs *),Bash(awk *),Bash(cut *),Bash(tee *),Bash(tr *)"'
-          settings: |
-            {
-              "env": {
-                "PG_DATABASE_URL": "postgres://postgres:postgres@localhost:5432/default"
-              }
-            }
-      - name: Dispatch response to ci-privileged
-        if: always()
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.CI_PRIVILEGED_DISPATCH_TOKEN }}
-          repository: twentyhq/ci-privileged
-          event-type: claude-cross-repo-response
-          client-payload: '{"repo": ${{ toJSON(steps.prompt.outputs.repo) }}, "issue_number": ${{ toJSON(steps.prompt.outputs.issue_number) }}, "run_id": ${{ toJSON(github.run_id) }}, "run_url": ${{ toJSON(format('{0}/{1}/actions/runs/{2}', github.server_url, github.repository, github.run_id)) }}}'

.github/workflows/docs-i18n-pull.yaml

@@ -1,152 +0,0 @@
-name: 'Pull docs translations from Crowdin'
-
-permissions:
-  contents: write
-  pull-requests: write
-
-on:
-  schedule:
-    - cron: '0 */2 * * *' # Every two hours
-  workflow_dispatch:
-    inputs:
-      force_pull:
-        description: 'Force pull translations regardless of status'
-        required: false
-        type: boolean
-        default: false
-  workflow_call:
-    inputs:
-      force_pull:
-        description: 'Force pull translations regardless of status'
-        required: false
-        type: boolean
-        default: false
-  pull_request:
-    paths:
-      - 'packages/twenty-docs/**'
-      - '.github/crowdin-docs.yml'
-      - '.github/workflows/docs-i18n-pull.yaml'
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  pull_docs_translations:
-    name: Pull docs translations
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          token: ${{ github.token }}
-          ref: ${{ github.event_name == 'pull_request' && github.head_ref || github.ref }}
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Setup i18n-docs branch
-        if: github.event_name != 'pull_request'
-        run: |
-          git fetch origin i18n-docs || true
-          git checkout -B i18n-docs origin/i18n-docs || git checkout -b i18n-docs
-
-      - name: Configure git
-        run: |
-          git config --global user.name 'github-actions'
-          git config --global user.email '[email protected]'
-
-      - name: Stash any changes before pulling translations
-        if: github.event_name != 'pull_request'
-        run: |
-          git add .
-          git stash || true
-
-      # Install Crowdin CLI for downloading translations
-      - name: Install Crowdin CLI
-        if: github.event_name != 'pull_request' && (inputs.force_pull == true || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
-        run: npm install -g @crowdin/cli
-
-      # Pull docs translations from Crowdin one language at a time
-      # This avoids build timeout issues when processing all languages at once
-      - name: Pull translated docs from Crowdin
-        if: github.event_name != 'pull_request' && (inputs.force_pull == true || github.event_name == 'schedule' || github.event_name == 'workflow_dispatch')
-        run: |
-          # Languages supported by Mintlify (see packages/twenty-docs/src/shared/supported-languages.ts)
-          LANGUAGES="fr ar cs de es it ja ko pt ro ru tr zh-CN"
-
-          for lang in $LANGUAGES; do
-            echo "=== Pulling translations for $lang ==="
-            crowdin download \
-              --config .github/crowdin-docs.yml \
-              --token "$CROWDIN_PERSONAL_TOKEN" \
-              --base-url "https://twenty.api.crowdin.com" \
-              --language "$lang" \
-              --skip-untranslated-strings=false \
-              --skip-untranslated-files=false \
-              --export-only-approved=false \
-              --verbose || echo "Warning: Failed to pull $lang, continuing with other languages..."
-            echo ""
-          done
-
-          echo "=== Download complete ==="
-        env:
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-
-      - name: Fix file permissions
-        if: github.event_name != 'pull_request'
-        run: sudo chown -R runner:docker . || true
-
-      - name: Fix translated documentation links
-        run: bash packages/twenty-docs/scripts/fix-translated-links.sh
-
-      - name: Regenerate navigation template
-        if: github.event_name == 'pull_request'
-        run: yarn docs:generate-navigation-template
-
-      - name: Regenerate docs.json
-        run: yarn docs:generate
-
-      - name: Regenerate documentation paths constants
-        run: yarn docs:generate-paths
-
-      - name: Commit artifacts to pull request branch
-        if: github.event_name == 'pull_request'
-        run: |
-          git add packages/twenty-docs/docs.json packages/twenty-docs/navigation/navigation.template.json packages/twenty-shared/src/constants/DocumentationPaths.ts
-          if git diff --staged --quiet --exit-code; then
-            echo "No navigation/doc changes to commit."
-            exit 0
-          fi
-          git commit -m "chore: sync docs artifacts"
-          git push origin "HEAD:$HEAD_REF"
-        env:
-          HEAD_REF: ${{ github.head_ref }}
-
-      - name: Check for changes and commit
-        if: github.event_name != 'pull_request'
-        id: check_changes
-        run: |
-          git add .
-          if ! git diff --staged --quiet --exit-code; then
-            git commit -m "chore: update docs translations from Crowdin and fix internal links"
-            echo "changes_detected=true" >> $GITHUB_OUTPUT
-          else
-            echo "changes_detected=false" >> $GITHUB_OUTPUT
-          fi
-
-      - name: Push changes
-        if: github.event_name != 'pull_request' && steps.check_changes.outputs.changes_detected == 'true'
-        run: git push origin HEAD:i18n-docs
-
-      - name: Create pull request
-        if: github.event_name != 'pull_request' && steps.check_changes.outputs.changes_detected == 'true'
-        run: |
-          if git diff --name-only origin/main..HEAD | grep -q .; then
-            gh pr create -B main -H i18n-docs --title 'i18n - docs translations' --body 'Created by Github action' || true
-          else
-            echo "No file differences between branches, skipping PR creation"
-          fi
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-

.github/workflows/docs-i18n-push.yaml

@@ -1,51 +0,0 @@
-name: 'Push docs to Crowdin'
-
-permissions:
-  contents: write
-
-on:
-  workflow_dispatch:
-  workflow_call:
-  push:
-    branches: ['main']
-    paths:
-      - 'packages/twenty-docs/**/*.mdx'
-      - '!packages/twenty-docs/l/**'
-      - 'packages/twenty-docs/navigation/navigation.template.json'
-      - '.github/crowdin-docs.yml'
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  push_docs:
-    name: Push documentation to Crowdin
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-        with:
-          token: ${{ github.token }}
-          ref: ${{ github.ref }}
-
-      - name: Install dependencies
-        uses: ./.github/actions/yarn-install
-
-      - name: Generate navigation template for Crowdin
-        run: yarn docs:generate-navigation-template
-
-      - name: Upload docs to Crowdin
-        uses: crowdin/github-action@v2
-        with:
-          upload_sources: true
-          upload_translations: false
-          download_translations: false
-          localization_branch_name: i18n-docs
-          base_url: 'https://twenty.api.crowdin.com'
-          config: '.github/crowdin-docs.yml'
-        env:
-          # Docs translations project
-          CROWDIN_PROJECT_ID: '2'
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-

.github/workflows/i18n-pull.yaml

@@ -46,7 +46,7 @@ jobs:
           git checkout -B i18n origin/i18n || git checkout -b i18n
 
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
 
       - name: Build twenty-shared
         run: npx nx build twenty-shared
@@ -74,8 +74,6 @@ jobs:
           upload_sources: false
           upload_translations: false
           download_translations: true
-          source: '**/en.po'
-          translation: '%original_path%/%locale%.po'
           export_only_approved: false
           localization_branch_name: i18n
           base_url: 'https://twenty.api.crowdin.com'
@@ -85,37 +83,31 @@ jobs:
           push_sources: false
           skip_untranslated_strings: false
           skip_untranslated_files: false
-          push_translations: false
+          push_translations: true
           create_pull_request: false
           skip_ref_checkout: true
           dryrun_action: false
-          config: '.github/crowdin-app.yml'
         env:
           GITHUB_TOKEN: ${{ github.token }}
-          # App translations project
           CROWDIN_PROJECT_ID: '1'
           CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-
+      
       # As the files are extracted from a Docker container, they belong to root:root
       # We need to fix this before the next steps
       - name: Fix file permissions
         run: sudo chown -R runner:docker .
 
-      # Fix encoding issues (escaped Unicode like \u62db -> 招) and push fixes back to Crowdin
-      - name: Fix translation encoding and sync to Crowdin
-        run: npx ts-node packages/twenty-utils/fix-crowdin-translations.ts
-        env:
-          CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
-
       - name: Compile translations
         id: compile_translations
         # Because we have set English as a fallback locale, this condition does not work anymore
         # if: inputs.force_pull || steps.compile_translations_strict.outcome == 'failure'
         run: |
           npx nx run twenty-server:lingui:compile
-          npx nx run twenty-emails:lingui:compile
+          npx nx run twenty-emails:lingui:compile 
           npx nx run twenty-front:lingui:compile
           git status
+          git config --global user.name 'github-actions'
+          git config --global user.email '[email protected]'
           git add .
           if ! git diff --staged --quiet --exit-code; then
             git commit -m "chore: compile translations"

.github/workflows/i18n-push.yaml

@@ -31,7 +31,7 @@ jobs:
           git checkout -B i18n origin/i18n || git checkout -b i18n
 
       - name: Install dependencies
-        uses: ./.github/actions/yarn-install
+        uses: ./.github/workflows/actions/yarn-install
 
       - name: Build dependencies
         run: npx nx build twenty-shared
@@ -87,10 +87,11 @@ jobs:
           download_translations: false
           localization_branch_name: i18n
           base_url: 'https://twenty.api.crowdin.com'
-          config: '.github/crowdin-app.yml'
         env:
-          # App translations project
-          CROWDIN_PROJECT_ID: '1'
+          # A numeric ID, found at https://crowdin.com/project/<projectName>/tools/api
+          CROWDIN_PROJECT_ID: 1
+
+          # Visit https://crowdin.com/settings#api-key to create this token
           CROWDIN_PERSONAL_TOKEN: ${{ secrets.CROWDIN_PERSONAL_TOKEN }}
       - name: Create a pull request
         if: steps.check_extract_changes.outputs.changes_detected == 'true' || steps.check_compile_changes.outputs.changes_detected == 'true'

.github/workflows/post-ci-comments.yaml

@@ -1,71 +0,0 @@
-name: Post CI Comments
-
-on:
-  workflow_run:
-    workflows: ['GraphQL and OpenAPI Breaking Changes Detection']
-    types: [completed]
-
-permissions:
-  actions: read
-
-jobs:
-  dispatch-breaking-changes:
-    if: github.event.workflow_run.conclusion == 'success'
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    steps:
-      - name: Get PR number from workflow run
-        id: pr-info
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const runId = context.payload.workflow_run.id;
-            const headSha = context.payload.workflow_run.head_sha;
-            const headBranch = context.payload.workflow_run.head_branch;
-            const headRepo = context.payload.workflow_run.head_repository;
-
-            // workflow_run.pull_requests is empty for fork PRs,
-            // so fall back to searching by head SHA
-            let pullRequests = context.payload.workflow_run.pull_requests;
-            let prNumber;
-
-            if (pullRequests && pullRequests.length > 0) {
-              prNumber = pullRequests[0].number;
-            } else {
-              core.info(`pull_requests is empty (likely a fork PR), searching by SHA ${headSha}`);
-              const owner = context.repo.owner;
-              const repo = context.repo.repo;
-              const headLabel = `${headRepo.owner.login}:${headBranch}`;
-
-              const { data: prs } = await github.rest.pulls.list({
-                owner,
-                repo,
-                state: 'open',
-                head: headLabel,
-                per_page: 1,
-              });
-
-              if (prs.length > 0) {
-                prNumber = prs[0].number;
-              }
-            }
-
-            if (!prNumber) {
-              core.info('No pull request found for this workflow run');
-              core.setOutput('has_pr', 'false');
-              return;
-            }
-
-            core.setOutput('pr_number', prNumber);
-            core.setOutput('run_id', runId);
-            core.setOutput('has_pr', 'true');
-            core.info(`PR #${prNumber}, Run ID: ${runId}`);
-
-      - name: Dispatch to ci-privileged
-        if: steps.pr-info.outputs.has_pr == 'true'
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.CI_PRIVILEGED_DISPATCH_TOKEN }}
-          repository: twentyhq/ci-privileged
-          event-type: breaking-changes-report
-          client-payload: '{"pr_number": ${{ toJSON(steps.pr-info.outputs.pr_number) }}, "run_id": ${{ toJSON(steps.pr-info.outputs.run_id) }}, "repo": ${{ toJSON(github.repository) }}, "branch_state": ${{ toJSON(github.event.workflow_run.head_branch) }}}'

.github/workflows/preview-env-dispatch.yaml

@@ -2,8 +2,13 @@ name: 'Preview Environment Dispatch'
 
 permissions:
   contents: write
+  actions: write
+  pull-requests: read
 
 on:
+  # Using pull_request_target instead of pull_request to have access to secrets for external contributors
+  # Security note: This is safe because we're only using the repository-dispatch action with limited scope
+  # and not checking out or running any code from the external contributor's PR
   pull_request_target:
     types: [opened, synchronize, reopened, labeled]
     paths:
@@ -19,19 +24,7 @@ concurrency:
 
 jobs:
   trigger-preview:
-    if: |
-      (github.event.action == 'labeled' && github.event.label.name == 'preview-app') ||
-      (
-        (
-          github.event.pull_request.author_association == 'MEMBER' ||
-          github.event.pull_request.author_association == 'OWNER' ||
-          github.event.pull_request.author_association == 'COLLABORATOR'
-        ) && (
-          github.event.action == 'opened' ||
-          github.event.action == 'synchronize' ||
-          github.event.action == 'reopened'
-        )
-      )
+    if: github.event.action == 'opened' || github.event.action == 'synchronize' || github.event.action == 'reopened' || (github.event.action == 'labeled' && github.event.label.name == 'preview-app')
     timeout-minutes: 5
     runs-on: ubuntu-latest
     steps:
@@ -42,11 +35,3 @@ jobs:
           repository: ${{ github.repository }}
           event-type: preview-environment
           client-payload: '{"pr_number": "${{ github.event.pull_request.number }}", "pr_head_sha": "${{ github.event.pull_request.head.sha }}", "repo_full_name": "${{ github.repository }}"}'
-
-      - name: Dispatch to ci-privileged for PR comment
-        uses: peter-evans/repository-dispatch@v2
-        with:
-          token: ${{ secrets.CI_PRIVILEGED_DISPATCH_TOKEN }}
-          repository: twentyhq/ci-privileged
-          event-type: preview-env-url
-          client-payload: '{"pr_number": ${{ toJSON(github.event.pull_request.number) }}, "keepalive_dispatch_time": ${{ toJSON(github.event.pull_request.updated_at) }}, "repo": ${{ toJSON(github.repository) }}}'

.github/workflows/preview-env-keepalive.yaml

@@ -2,6 +2,7 @@ name: 'Preview Environment Keep Alive'
 
 permissions:
   contents: read
+  pull-requests: write
 
 on:
   repository_dispatch:
@@ -16,7 +17,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           ref: ${{ github.event.client_payload.pr_head_sha }}
-
+      
       - name: Run compose setup
         run: |
           echo "Patching docker-compose.yml..."
@@ -24,17 +25,17 @@ jobs:
           yq eval 'del(.services.server.image)' -i packages/twenty-docker/docker-compose.yml
           yq eval '.services.server.build.context = "../../"' -i packages/twenty-docker/docker-compose.yml
           yq eval '.services.server.build.dockerfile = "./packages/twenty-docker/twenty/Dockerfile"' -i packages/twenty-docker/docker-compose.yml
-
+          
           yq eval 'del(.services.worker.image)' -i packages/twenty-docker/docker-compose.yml
           yq eval '.services.worker.build.context = "../../"' -i packages/twenty-docker/docker-compose.yml
           yq eval '.services.worker.build.dockerfile = "./packages/twenty-docker/twenty/Dockerfile"' -i packages/twenty-docker/docker-compose.yml
-
+          
           echo "Adding SIGN_IN_PREFILLED environment variable to server service..."
           yq eval '.services.server.environment.SIGN_IN_PREFILLED = "${SIGN_IN_PREFILLED}"' -i packages/twenty-docker/docker-compose.yml
-
+          
           echo "Setting up .env file..."
           cp packages/twenty-docker/.env.example packages/twenty-docker/.env
-
+          
           echo "Generating secrets..."
           echo "" >> packages/twenty-docker/.env
           echo "# === Randomly generated secrets ===" >> packages/twenty-docker/.env
@@ -45,25 +46,24 @@ jobs:
           cd packages/twenty-docker/
           docker compose build
         working-directory: ./
-
+      
       - name: Create Tunnel
         id: expose-tunnel
         uses: codetalkio/[email protected]
         with:
           service: bore.pub
           port: 3000
-
+      
       - name: Start services with correct SERVER_URL
-        env:
-          TUNNEL_URL: ${{ steps.expose-tunnel.outputs.tunnel-url }}
         run: |
           cd packages/twenty-docker/
-
-          echo "Setting SERVER_URL to $TUNNEL_URL"
+          
+          # Update the SERVER_URL with the tunnel URL
+          echo "Setting SERVER_URL to ${{ steps.expose-tunnel.outputs.tunnel-url }}"
           sed -i '/SERVER_URL=/d' .env
           echo "" >> .env
-          echo "SERVER_URL=$TUNNEL_URL" >> .env
-
+          echo "SERVER_URL=${{ steps.expose-tunnel.outputs.tunnel-url }}" >> .env
+          
           # Start the services
           echo "Docker compose up..."
           docker compose up -d || {
@@ -71,7 +71,7 @@ jobs:
               docker compose logs
               exit 1
           }
-
+          
           echo "Waiting for services to be ready..."
           count=0
           while [ ! $(docker inspect --format='{{.State.Health.Status}}' twenty-db-1) = "healthy" ] || [ ! $(docker inspect --format='{{.State.Health.Status}}' twenty-server-1) = "healthy" ]; do
@@ -84,7 +84,7 @@ jobs:
               fi
               echo "Still waiting for services... ($count/60)"
           done
-
+          
           echo "All services are up and running!"
         working-directory: ./
 
@@ -99,33 +99,61 @@ jobs:
           fi
         working-directory: ./
 
-      - name: Output tunnel URL
-        env:
-          TUNNEL_URL: ${{ steps.expose-tunnel.outputs.tunnel-url }}
+      - name: Output tunnel URL to logs
         run: |
           echo "✅ Preview Environment Ready!"
-          echo "🔗 Preview URL: $TUNNEL_URL"
+          echo "🔗 Preview URL: ${{ steps.expose-tunnel.outputs.tunnel-url }}"
           echo "⏱️ This environment will be available for 5 hours"
-          echo "## 🚀 Preview Environment Ready!" >> "$GITHUB_STEP_SUMMARY"
-          echo "" >> "$GITHUB_STEP_SUMMARY"
-          echo "Preview URL: $TUNNEL_URL" >> "$GITHUB_STEP_SUMMARY"
-          echo "" >> "$GITHUB_STEP_SUMMARY"
-          echo "This environment will automatically shut down after 5 hours." >> "$GITHUB_STEP_SUMMARY"
-          echo "$TUNNEL_URL" > tunnel-url.txt
-
-      - name: Upload tunnel URL artifact
-        uses: actions/upload-artifact@v4
+      
+      - name: Post comment on PR
+        uses: actions/github-script@v6
         with:
-          name: tunnel-url
-          path: tunnel-url.txt
-          retention-days: 1
-
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            const COMMENT_MARKER = '<!-- PR_PREVIEW_ENV -->';
+            const commentBody = `${COMMENT_MARKER}
+            🚀 **Preview Environment Ready!**
+            
+            Your preview environment is available at: ${{ steps.expose-tunnel.outputs.tunnel-url }}
+            
+            This environment will automatically shut down when the PR is closed or after 5 hours.`;
+            
+            // Get all comments
+            const {data: comments} = await github.rest.issues.listComments({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: ${{ github.event.client_payload.pr_number }},
+            });
+            
+            // Find our comment
+            const botComment = comments.find(comment => comment.body.includes(COMMENT_MARKER));
+            
+            if (botComment) {
+              // Update existing comment
+              await github.rest.issues.updateComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                comment_id: botComment.id,
+                body: commentBody
+              });
+              console.log('Updated existing comment');
+            } else {
+              // Create new comment
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: ${{ github.event.client_payload.pr_number }},
+                body: commentBody
+              });
+              console.log('Created new comment');
+            }
+      
       - name: Keep tunnel alive for 5 hours
         run: timeout 300m sleep 18000 # Stop on whichever we reach first (300m or 5hour sleep)
-
+      
       - name: Cleanup
         if: always()
         run: |
           cd packages/twenty-docker/
           docker compose down -v
-        working-directory: ./
+        working-directory: ./ 

.gitignore

@@ -10,7 +10,6 @@
 .nx/installation
 .nx/cache
 .nx/workspace-data
-.nx/nxw.js
 
 .pnp.*
 .yarn/*
@@ -49,5 +48,3 @@ dump.rdb
 
 mcp.json
 /.junie/
-TRANSLATION_QA_REPORT.md
-.playwright-mcp/

.mcp.json

@@ -2,9 +2,11 @@
   "mcpServers": {
     "postgres": {
       "type": "stdio",
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-postgres", "${PG_DATABASE_URL}"],
-      "env": {}
+      "command": "uv",
+      "args": ["run", "postgres-mcp", "--access-mode=unrestricted"],
+      "env": {
+        "DATABASE_URI": "${PG_DATABASE_URL}"
+      }
     },
     "playwright": {
       "type": "stdio",

.nx/nxw.js

@@ -0,0 +1,115 @@
+"use strict";
+// This file should be committed to your repository! It wraps Nx and ensures
+// that your local installation matches nx.json.
+// See: https://nx.dev/recipes/installation/install-non-javascript for more info.
+
+
+
+
+Object.defineProperty(exports, "__esModule", { value: true });
+const fs = require('fs');
+const path = require('path');
+const cp = require('child_process');
+const installationPath = path.join(__dirname, 'installation', 'package.json');
+function matchesCurrentNxInstall(currentInstallation, nxJsonInstallation) {
+    if (!currentInstallation.devDependencies ||
+        !Object.keys(currentInstallation.devDependencies).length) {
+        return false;
+    }
+    try {
+        if (currentInstallation.devDependencies['nx'] !==
+            nxJsonInstallation.version ||
+            require(path.join(path.dirname(installationPath), 'node_modules', 'nx', 'package.json')).version !== nxJsonInstallation.version) {
+            return false;
+        }
+        for (const [plugin, desiredVersion] of Object.entries(nxJsonInstallation.plugins || {})) {
+            if (currentInstallation.devDependencies[plugin] !== desiredVersion) {
+                return false;
+            }
+        }
+        return true;
+    }
+    catch {
+        return false;
+    }
+}
+function ensureDir(p) {
+    if (!fs.existsSync(p)) {
+        fs.mkdirSync(p, { recursive: true });
+    }
+}
+function getCurrentInstallation() {
+    try {
+        return require(installationPath);
+    }
+    catch {
+        return {
+            name: 'nx-installation',
+            version: '0.0.0',
+            devDependencies: {},
+        };
+    }
+}
+function performInstallation(currentInstallation, nxJson) {
+    fs.writeFileSync(installationPath, JSON.stringify({
+        name: 'nx-installation',
+        devDependencies: {
+            nx: nxJson.installation.version,
+            ...nxJson.installation.plugins,
+        },
+    }));
+    try {
+        cp.execSync('npm i', {
+            cwd: path.dirname(installationPath),
+            stdio: 'inherit',
+        });
+    }
+    catch (e) {
+        // revert possible changes to the current installation
+        fs.writeFileSync(installationPath, JSON.stringify(currentInstallation));
+        // rethrow
+        throw e;
+    }
+}
+function ensureUpToDateInstallation() {
+    const nxJsonPath = path.join(__dirname, '..', 'nx.json');
+    let nxJson;
+    try {
+        nxJson = require(nxJsonPath);
+        if (!nxJson.installation) {
+            console.error('[NX]: The "installation" entry in the "nx.json" file is required when running the nx wrapper. See https://nx.dev/recipes/installation/install-non-javascript');
+            process.exit(1);
+        }
+    }
+    catch {
+        console.error('[NX]: The "nx.json" file is required when running the nx wrapper. See https://nx.dev/recipes/installation/install-non-javascript');
+        process.exit(1);
+    }
+    try {
+        ensureDir(path.join(__dirname, 'installation'));
+        const currentInstallation = getCurrentInstallation();
+        if (!matchesCurrentNxInstall(currentInstallation, nxJson.installation)) {
+            performInstallation(currentInstallation, nxJson);
+        }
+    }
+    catch (e) {
+        const messageLines = [
+            '[NX]: Nx wrapper failed to synchronize installation.',
+        ];
+        if (e instanceof Error) {
+            messageLines.push('');
+            messageLines.push(e.message);
+            messageLines.push(e.stack);
+        }
+        else {
+            messageLines.push(e.toString());
+        }
+        console.error(messageLines.join('\n'));
+        process.exit(1);
+    }
+}
+if (!process.env.NX_WRAPPER_SKIP_INSTALL) {
+    ensureUpToDateInstallation();
+}
+
+require('./installation/node_modules/nx/bin/nx');

.prettierignore

@@ -0,0 +1,4 @@
+# Add files here to ignore them from prettier formatting
+/dist
+/coverage
+/.nx/cache

.prettierrc

@@ -0,0 +1,5 @@
+{
+  "singleQuote": true,
+  "trailingComma": "all",
+  "endOfLine": "lf"
+}

.specify/memory/constitution.md

@@ -1,268 +0,0 @@
-<!--
-  Sync Impact Report
-  ==================
-  Version change: N/A → 1.0.0 (initial ratification)
-  Modified principles: N/A (all new)
-  Added sections:
-    - Core Principles (7 principles)
-    - Technology Stack & Architecture
-    - Development Workflow & Quality Gates
-    - Governance
-  Removed sections: N/A
-  Templates requiring updates:
-    - .specify/templates/plan-template.md ✅ (Constitution Check section
-      already present; gates align with principles)
-    - .specify/templates/spec-template.md ✅ (no constitution-specific
-      references needed; structure is compatible)
-    - .specify/templates/tasks-template.md ✅ (task categorization supports
-      testing, migration, and lint phases per principles)
-    - .specify/templates/checklist-template.md ✅ (generic; compatible)
-    - .specify/templates/agent-file-template.md ✅ (generic; compatible)
-  Follow-up TODOs: none
--->
-
-# Twenty CRM Constitution
-
-## Core Principles
-
-### I. Strict TypeScript (NON-NEGOTIABLE)
-
-All code MUST use strict TypeScript with `noImplicitAny` enabled.
-
-- The `any` type is NEVER permitted. Use `unknown`, generics, or
-  explicit union types instead.
-- Use `type` for all type definitions. Use `interface` ONLY when
-  extending a third-party interface.
-- Use string literal unions (`'admin' | 'user' | 'guest'`) instead
-  of `enum`. Exception: GraphQL enums generated by codegen.
-- Generic type parameters MUST have descriptive names
-  (`TData`, `TResult`, not `T`, `U`).
-- Suffix component props types with `Props`
-  (e.g., `ButtonProps`, `RecordTableProps`).
-- Leverage type inference for obvious cases; explicitly annotate
-  when the type is ambiguous or when it serves as documentation.
-
-**Rationale**: Strict typing eliminates entire categories of runtime
-errors and makes refactoring safe across a large monorepo.
-
-### II. Functional Components & Named Exports
-
-All React components MUST be functional components. Class components
-are NEVER permitted.
-
-- Every module MUST use named exports exclusively. Default exports
-  are NEVER permitted.
-- Destructure props at the function signature level.
-- Prefer event handlers over `useEffect` for state updates triggered
-  by user actions.
-- Apply composition over inheritance: build complex UI by composing
-  smaller, single-responsibility components.
-- Extract complex logic into custom hooks; keep components focused
-  on rendering.
-- Use `memo` only for demonstrably expensive components; memoize
-  callbacks with `useCallback` when stable references are required.
-
-**Rationale**: Functional components with hooks are simpler to reason
-about, test, and compose. Named exports enable reliable tree-shaking
-and explicit dependency graphs.
-
-### III. Nx Monorepo Discipline
-
-The repository is an Nx workspace managed with Yarn 4. All packages
-live under `packages/`.
-
-- `twenty-shared` MUST be built before any dependent package.
-- Libraries MUST export through `index.ts` barrel files.
-- Internal imports MUST use the `@/` path alias (never relative
-  paths crossing package boundaries).
-- Import order: external libraries → internal (`@/`) → relative.
-- ALWAYS prefer `npx nx lint:diff-with-main <project>` over full
-  project lints. Use `--configuration=fix` for auto-fix.
-- File and directory names MUST be kebab-case with descriptive
-  suffixes (`.component.tsx`, `.service.ts`, `.entity.ts`,
-  `.dto.ts`, `.module.ts`, `.test.tsx`, `.spec.ts`).
-- Components MUST stay under 300 lines; services under 500 lines.
-  Split when approaching limits.
-
-**Rationale**: Consistent monorepo conventions enable fast CI,
-reliable caching, and predictable project navigation for all
-contributors.
-
-### IV. Behavior-Driven Testing
-
-Tests MUST validate user-visible behavior, not implementation
-details.
-
-- Follow the Arrange-Act-Assert (AAA) pattern in every test.
-- Use descriptive test names: `"should [behavior] when [condition]"`.
-- Query elements by user-visible attributes (text, roles, labels);
-  avoid test IDs unless no accessible alternative exists.
-- Use `@testing-library/user-event` for realistic interactions.
-- Target the test pyramid: 70% unit, 20% integration, 10% E2E.
-- Prefer single-file test execution
-  (`npx jest path/to/test --config=packages/PROJECT/jest.config.mjs`)
-  over full suite runs.
-- Clear mocks with `jest.clearAllMocks()` in `beforeEach`.
-- Frontend test files use `.test.ts(x)`; server test files use
-  `.spec.ts`.
-
-**Rationale**: Behavior-focused tests are resilient to refactoring,
-catch real regressions, and serve as living documentation of user
-expectations.
-
-### V. Database Migration Integrity
-
-Every change to a TypeORM entity MUST have a corresponding generated
-migration.
-
-- Generate migrations with:
-  ```
-  npx nx run twenty-server:typeorm migration:generate \
-    src/database/typeorm/core/migrations/common/[name] \
-    -d src/database/typeorm/core/core.datasource.ts
-  ```
-- Migration names MUST be descriptive and kebab-case
-  (e.g., `add-agent-turn-evaluation`).
-- Every migration MUST include both `up` and `down` logic.
-- Committed migrations MUST NEVER be deleted or rewritten.
-- Prefer TypeORM-generated schema diffs; manually adjust only for
-  data backfills or complex constraints.
-
-**Rationale**: Strict migration discipline ensures reproducible
-database states across environments and safe rollbacks.
-
-### VI. Unidirectional State Management
-
-Application state MUST flow in one direction: props down, events up.
-
-- Use Jotai for global state via Twenty's custom utilities:
-  `createAtomState`, `createAtomSelector`,
-  `createAtomFamilyState`.
-- Use the corresponding hooks: `useAtomState` (read+write),
-  `useAtomStateValue` (read-only), `useSetAtomState` (write-only).
-- Use `useState` for component-local state, but prefer Jotai atoms as default;
-- NEVER use `useReducer` nor `useRef` for state management.
-- Normalize complex data structures with lookup tables; avoid
-  deeply nested state.
-- GraphQL cache is managed by Apollo Client; do not duplicate
-  server state in Jotai atoms.
-
-**Rationale**: Unidirectional flow makes state changes predictable,
-debuggable, and testable.
-
-### VII. Code Clarity & Security First
-
-Code MUST be self-explanatory; security constraints MUST be applied
-before any formatting or display logic.
-
-- Variable and function names MUST NOT use abbreviations
-  (`user` not `u`, `fieldMetadata` not `fm`).
-- Comments MUST use short-form `//` only (no JSDoc `/** */` blocks).
-  Explain WHY (business logic), never WHAT (obvious code).
-  Multi-line comments use multiple `//` lines. ALWAYS Prefer better variable and function naming over comments, only use comments as a last resort option.
-- Use utility helpers from `twenty-shared`:
-  `isDefined()`, `isNonEmptyString()`, `isNonEmptyArray()` instead
-  of manual type guards.
-- ALWAYS use `isDefined()` instead of `if(!value)` or `if(value)`
-- Prefer long names over short ones if it helps clarifying the code.
-- Apply security processing before formatting
-  (e.g., sanitize → then format for CSV export).
-- Error handling MUST use proper error types with meaningful
-  messages and contextual logging.
-- Internationalization uses Lingui; translated strings MUST NEVER
-  be concatenated. English translations MUST be added first.
-
-**Rationale**: Readable code reduces onboarding time and review
-friction. Security-first processing prevents injection and data
-leakage vulnerabilities.
-
-## Technology Stack & Architecture
-
-The Twenty CRM is built on the following stack. All implementation
-decisions MUST align with these choices:
-
-| Layer        | Technology                                         |
-|--------------|----------------------------------------------------|
-| Frontend     | React 18, TypeScript, Jotai, Linaria, Vite         |
-| Backend      | NestJS, TypeORM, PostgreSQL, Redis, GraphQL Yoga    |
-| Monorepo     | Nx workspace, Yarn 4                               |
-| Email        | React Email (`twenty-emails`)                      |
-| Background   | BullMQ workers                                     |
-| Analytics    | ClickHouse (when enabled)                          |
-| E2E Testing  | Playwright                                         |
-| Unit Testing | Jest, React Testing Library                        |
-| i18n         | Lingui                                             |
-| Docs Website | Next.js (`twenty-website`)                         |
-
-**Package structure**:
-
-- `twenty-front` — React frontend application
-- `twenty-server` — NestJS backend API
-- `twenty-ui` — Shared UI component library
-- `twenty-shared` — Common types and utilities (build first)
-- `twenty-emails` — Email templates
-- `twenty-e2e-testing` — Playwright E2E tests
-- `twenty-website` — Documentation site
-- `twenty-zapier` — Zapier integration
-
-Backend architecture follows NestJS module conventions with
-TypeORM entities, GraphQL code-first resolvers, and Redis-backed
-caching and session management.
-
-## Development Workflow & Quality Gates
-
-Every change MUST pass these quality gates before merge:
-
-1. **Lint** — `npx nx lint:diff-with-main <project>` MUST report
-   zero errors. Always prefer diff-based linting.
-2. **Type Check** — `npx nx typecheck <project>` MUST pass with
-   zero errors.
-3. **Unit Tests** — Relevant test files MUST pass. New behavior
-   MUST have accompanying tests.
-4. **GraphQL Codegen** — After any GraphQL schema change, run
-   `npx nx run twenty-front:graphql:generate` (and the metadata
-   configuration variant). Generated types MUST be committed.
-5. **Migration** — If any `.entity.ts` file changed, a generated
-   migration MUST be included in the same changeset.
-6. **Build** — `npx nx build twenty-shared` MUST succeed first,
-   then `npx nx build <project>`.
-
-**CI environment note**: In GitHub Actions, run
-`bash packages/twenty-utils/setup-dev-env.sh` before any build,
-test, lint, or database operation. The script is idempotent.
-
-**Branching workflow**:
-
-- Feature branches branch from and merge into `main`.
-- Build each changeset incrementally: commit after each logical
-  unit of work.
-- Use `npx nx affected --target=<target>` to scope CI to changed
-  projects.
-
-## Governance
-
-This constitution is the authoritative source of engineering
-standards for the Twenty CRM project. It supersedes any conflicting
-guidance found elsewhere.
-
-**Amendment procedure**:
-
-1. Propose the change with a rationale and the affected principles.
-2. Update this file with the new or revised text.
-3. Increment the version following semantic versioning:
-   - MAJOR: Backward-incompatible principle removal or redefinition.
-   - MINOR: New principle or materially expanded guidance.
-   - PATCH: Clarification, wording, or typo fixes.
-4. Update `LAST_AMENDED_DATE` to the amendment date.
-5. Propagate changes to dependent templates in
-   `.specify/templates/` and to `.cursor/rules/` as needed.
-
-**Compliance**:
-
-- All code reviews MUST verify adherence to these principles.
-- Deviations MUST be justified in the PR description and tracked
-  in the Complexity Tracking table of the implementation plan.
-- Use `CLAUDE.md` and `.cursor/rules/` for runtime development
-  guidance that elaborates on these principles.
-
-**Version**: 1.0.0 | **Ratified**: 2026-03-05 | **Last Amended**: 2026-03-05

.specify/scripts/bash/check-prerequisites.sh

@@ -1,166 +0,0 @@
-#!/usr/bin/env bash
-
-# Consolidated prerequisite checking script
-#
-# This script provides unified prerequisite checking for Spec-Driven Development workflow.
-# It replaces the functionality previously spread across multiple scripts.
-#
-# Usage: ./check-prerequisites.sh [OPTIONS]
-#
-# OPTIONS:
-#   --json              Output in JSON format
-#   --require-tasks     Require tasks.md to exist (for implementation phase)
-#   --include-tasks     Include tasks.md in AVAILABLE_DOCS list
-#   --paths-only        Only output path variables (no validation)
-#   --help, -h          Show help message
-#
-# OUTPUTS:
-#   JSON mode: {"FEATURE_DIR":"...", "AVAILABLE_DOCS":["..."]}
-#   Text mode: FEATURE_DIR:... \n AVAILABLE_DOCS: \n ✓/✗ file.md
-#   Paths only: REPO_ROOT: ... \n BRANCH: ... \n FEATURE_DIR: ... etc.
-
-set -e
-
-# Parse command line arguments
-JSON_MODE=false
-REQUIRE_TASKS=false
-INCLUDE_TASKS=false
-PATHS_ONLY=false
-
-for arg in "$@"; do
-    case "$arg" in
-        --json)
-            JSON_MODE=true
-            ;;
-        --require-tasks)
-            REQUIRE_TASKS=true
-            ;;
-        --include-tasks)
-            INCLUDE_TASKS=true
-            ;;
-        --paths-only)
-            PATHS_ONLY=true
-            ;;
-        --help|-h)
-            cat << 'EOF'
-Usage: check-prerequisites.sh [OPTIONS]
-
-Consolidated prerequisite checking for Spec-Driven Development workflow.
-
-OPTIONS:
-  --json              Output in JSON format
-  --require-tasks     Require tasks.md to exist (for implementation phase)
-  --include-tasks     Include tasks.md in AVAILABLE_DOCS list
-  --paths-only        Only output path variables (no prerequisite validation)
-  --help, -h          Show this help message
-
-EXAMPLES:
-  # Check task prerequisites (plan.md required)
-  ./check-prerequisites.sh --json
-  
-  # Check implementation prerequisites (plan.md + tasks.md required)
-  ./check-prerequisites.sh --json --require-tasks --include-tasks
-  
-  # Get feature paths only (no validation)
-  ./check-prerequisites.sh --paths-only
-  
-EOF
-            exit 0
-            ;;
-        *)
-            echo "ERROR: Unknown option '$arg'. Use --help for usage information." >&2
-            exit 1
-            ;;
-    esac
-done
-
-# Source common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-# Get feature paths and validate branch
-eval $(get_feature_paths)
-check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
-
-# If paths-only mode, output paths and exit (support JSON + paths-only combined)
-if $PATHS_ONLY; then
-    if $JSON_MODE; then
-        # Minimal JSON paths payload (no validation performed)
-        printf '{"REPO_ROOT":"%s","BRANCH":"%s","FEATURE_DIR":"%s","FEATURE_SPEC":"%s","IMPL_PLAN":"%s","TASKS":"%s"}\n' \
-            "$REPO_ROOT" "$CURRENT_BRANCH" "$FEATURE_DIR" "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS"
-    else
-        echo "REPO_ROOT: $REPO_ROOT"
-        echo "BRANCH: $CURRENT_BRANCH"
-        echo "FEATURE_DIR: $FEATURE_DIR"
-        echo "FEATURE_SPEC: $FEATURE_SPEC"
-        echo "IMPL_PLAN: $IMPL_PLAN"
-        echo "TASKS: $TASKS"
-    fi
-    exit 0
-fi
-
-# Validate required directories and files
-if [[ ! -d "$FEATURE_DIR" ]]; then
-    echo "ERROR: Feature directory not found: $FEATURE_DIR" >&2
-    echo "Run /speckit.specify first to create the feature structure." >&2
-    exit 1
-fi
-
-if [[ ! -f "$IMPL_PLAN" ]]; then
-    echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
-    echo "Run /speckit.plan first to create the implementation plan." >&2
-    exit 1
-fi
-
-# Check for tasks.md if required
-if $REQUIRE_TASKS && [[ ! -f "$TASKS" ]]; then
-    echo "ERROR: tasks.md not found in $FEATURE_DIR" >&2
-    echo "Run /speckit.tasks first to create the task list." >&2
-    exit 1
-fi
-
-# Build list of available documents
-docs=()
-
-# Always check these optional docs
-[[ -f "$RESEARCH" ]] && docs+=("research.md")
-[[ -f "$DATA_MODEL" ]] && docs+=("data-model.md")
-
-# Check contracts directory (only if it exists and has files)
-if [[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]; then
-    docs+=("contracts/")
-fi
-
-[[ -f "$QUICKSTART" ]] && docs+=("quickstart.md")
-
-# Include tasks.md if requested and it exists
-if $INCLUDE_TASKS && [[ -f "$TASKS" ]]; then
-    docs+=("tasks.md")
-fi
-
-# Output results
-if $JSON_MODE; then
-    # Build JSON array of documents
-    if [[ ${#docs[@]} -eq 0 ]]; then
-        json_docs="[]"
-    else
-        json_docs=$(printf '"%s",' "${docs[@]}")
-        json_docs="[${json_docs%,}]"
-    fi
-    
-    printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
-else
-    # Text output
-    echo "FEATURE_DIR:$FEATURE_DIR"
-    echo "AVAILABLE_DOCS:"
-    
-    # Show status of each potential document
-    check_file "$RESEARCH" "research.md"
-    check_file "$DATA_MODEL" "data-model.md"
-    check_dir "$CONTRACTS_DIR" "contracts/"
-    check_file "$QUICKSTART" "quickstart.md"
-    
-    if $INCLUDE_TASKS; then
-        check_file "$TASKS" "tasks.md"
-    fi
-fi

.specify/scripts/bash/common.sh

@@ -1,156 +0,0 @@
-#!/usr/bin/env bash
-# Common functions and variables for all scripts
-
-# Get repository root, with fallback for non-git repositories
-get_repo_root() {
-    if git rev-parse --show-toplevel >/dev/null 2>&1; then
-        git rev-parse --show-toplevel
-    else
-        # Fall back to script location for non-git repos
-        local script_dir="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-        (cd "$script_dir/../../.." && pwd)
-    fi
-}
-
-# Get current branch, with fallback for non-git repositories
-get_current_branch() {
-    # First check if SPECIFY_FEATURE environment variable is set
-    if [[ -n "${SPECIFY_FEATURE:-}" ]]; then
-        echo "$SPECIFY_FEATURE"
-        return
-    fi
-
-    # Then check git if available
-    if git rev-parse --abbrev-ref HEAD >/dev/null 2>&1; then
-        git rev-parse --abbrev-ref HEAD
-        return
-    fi
-
-    # For non-git repos, try to find the latest feature directory
-    local repo_root=$(get_repo_root)
-    local specs_dir="$repo_root/specs"
-
-    if [[ -d "$specs_dir" ]]; then
-        local latest_feature=""
-        local highest=0
-
-        for dir in "$specs_dir"/*; do
-            if [[ -d "$dir" ]]; then
-                local dirname=$(basename "$dir")
-                if [[ "$dirname" =~ ^([0-9]{3})- ]]; then
-                    local number=${BASH_REMATCH[1]}
-                    number=$((10#$number))
-                    if [[ "$number" -gt "$highest" ]]; then
-                        highest=$number
-                        latest_feature=$dirname
-                    fi
-                fi
-            fi
-        done
-
-        if [[ -n "$latest_feature" ]]; then
-            echo "$latest_feature"
-            return
-        fi
-    fi
-
-    echo "main"  # Final fallback
-}
-
-# Check if we have git available
-has_git() {
-    git rev-parse --show-toplevel >/dev/null 2>&1
-}
-
-check_feature_branch() {
-    local branch="$1"
-    local has_git_repo="$2"
-
-    # For non-git repos, we can't enforce branch naming but still provide output
-    if [[ "$has_git_repo" != "true" ]]; then
-        echo "[specify] Warning: Git repository not detected; skipped branch validation" >&2
-        return 0
-    fi
-
-    if [[ ! "$branch" =~ ^[0-9]{3}- ]]; then
-        echo "ERROR: Not on a feature branch. Current branch: $branch" >&2
-        echo "Feature branches should be named like: 001-feature-name" >&2
-        return 1
-    fi
-
-    return 0
-}
-
-get_feature_dir() { echo "$1/specs/$2"; }
-
-# Find feature directory by numeric prefix instead of exact branch match
-# This allows multiple branches to work on the same spec (e.g., 004-fix-bug, 004-add-feature)
-find_feature_dir_by_prefix() {
-    local repo_root="$1"
-    local branch_name="$2"
-    local specs_dir="$repo_root/specs"
-
-    # Extract numeric prefix from branch (e.g., "004" from "004-whatever")
-    if [[ ! "$branch_name" =~ ^([0-9]{3})- ]]; then
-        # If branch doesn't have numeric prefix, fall back to exact match
-        echo "$specs_dir/$branch_name"
-        return
-    fi
-
-    local prefix="${BASH_REMATCH[1]}"
-
-    # Search for directories in specs/ that start with this prefix
-    local matches=()
-    if [[ -d "$specs_dir" ]]; then
-        for dir in "$specs_dir"/"$prefix"-*; do
-            if [[ -d "$dir" ]]; then
-                matches+=("$(basename "$dir")")
-            fi
-        done
-    fi
-
-    # Handle results
-    if [[ ${#matches[@]} -eq 0 ]]; then
-        # No match found - return the branch name path (will fail later with clear error)
-        echo "$specs_dir/$branch_name"
-    elif [[ ${#matches[@]} -eq 1 ]]; then
-        # Exactly one match - perfect!
-        echo "$specs_dir/${matches[0]}"
-    else
-        # Multiple matches - this shouldn't happen with proper naming convention
-        echo "ERROR: Multiple spec directories found with prefix '$prefix': ${matches[*]}" >&2
-        echo "Please ensure only one spec directory exists per numeric prefix." >&2
-        echo "$specs_dir/$branch_name"  # Return something to avoid breaking the script
-    fi
-}
-
-get_feature_paths() {
-    local repo_root=$(get_repo_root)
-    local current_branch=$(get_current_branch)
-    local has_git_repo="false"
-
-    if has_git; then
-        has_git_repo="true"
-    fi
-
-    # Use prefix-based lookup to support multiple branches per spec
-    local feature_dir=$(find_feature_dir_by_prefix "$repo_root" "$current_branch")
-
-    cat <<EOF
-REPO_ROOT='$repo_root'
-CURRENT_BRANCH='$current_branch'
-HAS_GIT='$has_git_repo'
-FEATURE_DIR='$feature_dir'
-FEATURE_SPEC='$feature_dir/spec.md'
-IMPL_PLAN='$feature_dir/plan.md'
-TASKS='$feature_dir/tasks.md'
-RESEARCH='$feature_dir/research.md'
-DATA_MODEL='$feature_dir/data-model.md'
-QUICKSTART='$feature_dir/quickstart.md'
-CONTRACTS_DIR='$feature_dir/contracts'
-EOF
-}
-
-check_file() { [[ -f "$1" ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
-check_dir() { [[ -d "$1" && -n $(ls -A "$1" 2>/dev/null) ]] && echo "  ✓ $2" || echo "  ✗ $2"; }
-

.specify/scripts/bash/create-new-feature.sh

@@ -1,313 +0,0 @@
-#!/usr/bin/env bash
-
-set -e
-
-JSON_MODE=false
-SHORT_NAME=""
-BRANCH_NUMBER=""
-ARGS=()
-i=1
-while [ $i -le $# ]; do
-    arg="${!i}"
-    case "$arg" in
-        --json) 
-            JSON_MODE=true 
-            ;;
-        --short-name)
-            if [ $((i + 1)) -gt $# ]; then
-                echo 'Error: --short-name requires a value' >&2
-                exit 1
-            fi
-            i=$((i + 1))
-            next_arg="${!i}"
-            # Check if the next argument is another option (starts with --)
-            if [[ "$next_arg" == --* ]]; then
-                echo 'Error: --short-name requires a value' >&2
-                exit 1
-            fi
-            SHORT_NAME="$next_arg"
-            ;;
-        --number)
-            if [ $((i + 1)) -gt $# ]; then
-                echo 'Error: --number requires a value' >&2
-                exit 1
-            fi
-            i=$((i + 1))
-            next_arg="${!i}"
-            if [[ "$next_arg" == --* ]]; then
-                echo 'Error: --number requires a value' >&2
-                exit 1
-            fi
-            BRANCH_NUMBER="$next_arg"
-            ;;
-        --help|-h) 
-            echo "Usage: $0 [--json] [--short-name <name>] [--number N] <feature_description>"
-            echo ""
-            echo "Options:"
-            echo "  --json              Output in JSON format"
-            echo "  --short-name <name> Provide a custom short name (2-4 words) for the branch"
-            echo "  --number N          Specify branch number manually (overrides auto-detection)"
-            echo "  --help, -h          Show this help message"
-            echo ""
-            echo "Examples:"
-            echo "  $0 'Add user authentication system' --short-name 'user-auth'"
-            echo "  $0 'Implement OAuth2 integration for API' --number 5"
-            exit 0
-            ;;
-        *) 
-            ARGS+=("$arg") 
-            ;;
-    esac
-    i=$((i + 1))
-done
-
-FEATURE_DESCRIPTION="${ARGS[*]}"
-if [ -z "$FEATURE_DESCRIPTION" ]; then
-    echo "Usage: $0 [--json] [--short-name <name>] [--number N] <feature_description>" >&2
-    exit 1
-fi
-
-# Trim whitespace and validate description is not empty (e.g., user passed only whitespace)
-FEATURE_DESCRIPTION=$(echo "$FEATURE_DESCRIPTION" | xargs)
-if [ -z "$FEATURE_DESCRIPTION" ]; then
-    echo "Error: Feature description cannot be empty or contain only whitespace" >&2
-    exit 1
-fi
-
-# Function to find the repository root by searching for existing project markers
-find_repo_root() {
-    local dir="$1"
-    while [ "$dir" != "/" ]; do
-        if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
-            echo "$dir"
-            return 0
-        fi
-        dir="$(dirname "$dir")"
-    done
-    return 1
-}
-
-# Function to get highest number from specs directory
-get_highest_from_specs() {
-    local specs_dir="$1"
-    local highest=0
-    
-    if [ -d "$specs_dir" ]; then
-        for dir in "$specs_dir"/*; do
-            [ -d "$dir" ] || continue
-            dirname=$(basename "$dir")
-            number=$(echo "$dirname" | grep -o '^[0-9]\+' || echo "0")
-            number=$((10#$number))
-            if [ "$number" -gt "$highest" ]; then
-                highest=$number
-            fi
-        done
-    fi
-    
-    echo "$highest"
-}
-
-# Function to get highest number from git branches
-get_highest_from_branches() {
-    local highest=0
-    
-    # Get all branches (local and remote)
-    branches=$(git branch -a 2>/dev/null || echo "")
-    
-    if [ -n "$branches" ]; then
-        while IFS= read -r branch; do
-            # Clean branch name: remove leading markers and remote prefixes
-            clean_branch=$(echo "$branch" | sed 's/^[* ]*//; s|^remotes/[^/]*/||')
-            
-            # Extract feature number if branch matches pattern ###-*
-            if echo "$clean_branch" | grep -q '^[0-9]\{3\}-'; then
-                number=$(echo "$clean_branch" | grep -o '^[0-9]\{3\}' || echo "0")
-                number=$((10#$number))
-                if [ "$number" -gt "$highest" ]; then
-                    highest=$number
-                fi
-            fi
-        done <<< "$branches"
-    fi
-    
-    echo "$highest"
-}
-
-# Function to check existing branches (local and remote) and return next available number
-check_existing_branches() {
-    local specs_dir="$1"
-
-    # Fetch all remotes to get latest branch info (suppress errors if no remotes)
-    git fetch --all --prune 2>/dev/null || true
-
-    # Get highest number from ALL branches (not just matching short name)
-    local highest_branch=$(get_highest_from_branches)
-
-    # Get highest number from ALL specs (not just matching short name)
-    local highest_spec=$(get_highest_from_specs "$specs_dir")
-
-    # Take the maximum of both
-    local max_num=$highest_branch
-    if [ "$highest_spec" -gt "$max_num" ]; then
-        max_num=$highest_spec
-    fi
-
-    # Return next number
-    echo $((max_num + 1))
-}
-
-# Function to clean and format a branch name
-clean_branch_name() {
-    local name="$1"
-    echo "$name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//'
-}
-
-# Resolve repository root. Prefer git information when available, but fall back
-# to searching for repository markers so the workflow still functions in repositories that
-# were initialised with --no-git.
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-
-if git rev-parse --show-toplevel >/dev/null 2>&1; then
-    REPO_ROOT=$(git rev-parse --show-toplevel)
-    HAS_GIT=true
-else
-    REPO_ROOT="$(find_repo_root "$SCRIPT_DIR")"
-    if [ -z "$REPO_ROOT" ]; then
-        echo "Error: Could not determine repository root. Please run this script from within the repository." >&2
-        exit 1
-    fi
-    HAS_GIT=false
-fi
-
-cd "$REPO_ROOT"
-
-SPECS_DIR="$REPO_ROOT/specs"
-mkdir -p "$SPECS_DIR"
-
-# Function to generate branch name with stop word filtering and length filtering
-generate_branch_name() {
-    local description="$1"
-    
-    # Common stop words to filter out
-    local stop_words="^(i|a|an|the|to|for|of|in|on|at|by|with|from|is|are|was|were|be|been|being|have|has|had|do|does|did|will|would|should|could|can|may|might|must|shall|this|that|these|those|my|your|our|their|want|need|add|get|set)$"
-    
-    # Convert to lowercase and split into words
-    local clean_name=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/ /g')
-    
-    # Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
-    local meaningful_words=()
-    for word in $clean_name; do
-        # Skip empty words
-        [ -z "$word" ] && continue
-        
-        # Keep words that are NOT stop words AND (length >= 3 OR are potential acronyms)
-        if ! echo "$word" | grep -qiE "$stop_words"; then
-            if [ ${#word} -ge 3 ]; then
-                meaningful_words+=("$word")
-            elif echo "$description" | grep -q "\b${word^^}\b"; then
-                # Keep short words if they appear as uppercase in original (likely acronyms)
-                meaningful_words+=("$word")
-            fi
-        fi
-    done
-    
-    # If we have meaningful words, use first 3-4 of them
-    if [ ${#meaningful_words[@]} -gt 0 ]; then
-        local max_words=3
-        if [ ${#meaningful_words[@]} -eq 4 ]; then max_words=4; fi
-        
-        local result=""
-        local count=0
-        for word in "${meaningful_words[@]}"; do
-            if [ $count -ge $max_words ]; then break; fi
-            if [ -n "$result" ]; then result="$result-"; fi
-            result="$result$word"
-            count=$((count + 1))
-        done
-        echo "$result"
-    else
-        # Fallback to original logic if no meaningful words found
-        local cleaned=$(clean_branch_name "$description")
-        echo "$cleaned" | tr '-' '\n' | grep -v '^$' | head -3 | tr '\n' '-' | sed 's/-$//'
-    fi
-}
-
-# Generate branch name
-if [ -n "$SHORT_NAME" ]; then
-    # Use provided short name, just clean it up
-    BRANCH_SUFFIX=$(clean_branch_name "$SHORT_NAME")
-else
-    # Generate from description with smart filtering
-    BRANCH_SUFFIX=$(generate_branch_name "$FEATURE_DESCRIPTION")
-fi
-
-# Determine branch number
-if [ -z "$BRANCH_NUMBER" ]; then
-    if [ "$HAS_GIT" = true ]; then
-        # Check existing branches on remotes
-        BRANCH_NUMBER=$(check_existing_branches "$SPECS_DIR")
-    else
-        # Fall back to local directory check
-        HIGHEST=$(get_highest_from_specs "$SPECS_DIR")
-        BRANCH_NUMBER=$((HIGHEST + 1))
-    fi
-fi
-
-# Force base-10 interpretation to prevent octal conversion (e.g., 010 → 8 in octal, but should be 10 in decimal)
-FEATURE_NUM=$(printf "%03d" "$((10#$BRANCH_NUMBER))")
-BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
-
-# GitHub enforces a 244-byte limit on branch names
-# Validate and truncate if necessary
-MAX_BRANCH_LENGTH=244
-if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
-    # Calculate how much we need to trim from suffix
-    # Account for: feature number (3) + hyphen (1) = 4 chars
-    MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - 4))
-    
-    # Truncate suffix at word boundary if possible
-    TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
-    # Remove trailing hyphen if truncation created one
-    TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
-    
-    ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
-    BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
-    
-    >&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
-    >&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
-    >&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"
-fi
-
-if [ "$HAS_GIT" = true ]; then
-    if ! git checkout -b "$BRANCH_NAME" 2>/dev/null; then
-        # Check if branch already exists
-        if git branch --list "$BRANCH_NAME" | grep -q .; then
-            >&2 echo "Error: Branch '$BRANCH_NAME' already exists. Please use a different feature name or specify a different number with --number."
-            exit 1
-        else
-            >&2 echo "Error: Failed to create git branch '$BRANCH_NAME'. Please check your git configuration and try again."
-            exit 1
-        fi
-    fi
-else
-    >&2 echo "[specify] Warning: Git repository not detected; skipped branch creation for $BRANCH_NAME"
-fi
-
-FEATURE_DIR="$SPECS_DIR/$BRANCH_NAME"
-mkdir -p "$FEATURE_DIR"
-
-TEMPLATE="$REPO_ROOT/.specify/templates/spec-template.md"
-SPEC_FILE="$FEATURE_DIR/spec.md"
-if [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
-
-# Set the SPECIFY_FEATURE environment variable for the current session
-export SPECIFY_FEATURE="$BRANCH_NAME"
-
-if $JSON_MODE; then
-    printf '{"BRANCH_NAME":"%s","SPEC_FILE":"%s","FEATURE_NUM":"%s"}\n' "$BRANCH_NAME" "$SPEC_FILE" "$FEATURE_NUM"
-else
-    echo "BRANCH_NAME: $BRANCH_NAME"
-    echo "SPEC_FILE: $SPEC_FILE"
-    echo "FEATURE_NUM: $FEATURE_NUM"
-    echo "SPECIFY_FEATURE environment variable set to: $BRANCH_NAME"
-fi

.specify/scripts/bash/setup-plan.sh

@@ -1,61 +0,0 @@
-#!/usr/bin/env bash
-
-set -e
-
-# Parse command line arguments
-JSON_MODE=false
-ARGS=()
-
-for arg in "$@"; do
-    case "$arg" in
-        --json) 
-            JSON_MODE=true 
-            ;;
-        --help|-h) 
-            echo "Usage: $0 [--json]"
-            echo "  --json    Output results in JSON format"
-            echo "  --help    Show this help message"
-            exit 0 
-            ;;
-        *) 
-            ARGS+=("$arg") 
-            ;;
-    esac
-done
-
-# Get script directory and load common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-# Get all paths and variables from common functions
-eval $(get_feature_paths)
-
-# Check if we're on a proper feature branch (only for git repos)
-check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
-
-# Ensure the feature directory exists
-mkdir -p "$FEATURE_DIR"
-
-# Copy plan template if it exists
-TEMPLATE="$REPO_ROOT/.specify/templates/plan-template.md"
-if [[ -f "$TEMPLATE" ]]; then
-    cp "$TEMPLATE" "$IMPL_PLAN"
-    echo "Copied plan template to $IMPL_PLAN"
-else
-    echo "Warning: Plan template not found at $TEMPLATE"
-    # Create a basic plan file if template doesn't exist
-    touch "$IMPL_PLAN"
-fi
-
-# Output results
-if $JSON_MODE; then
-    printf '{"FEATURE_SPEC":"%s","IMPL_PLAN":"%s","SPECS_DIR":"%s","BRANCH":"%s","HAS_GIT":"%s"}\n' \
-        "$FEATURE_SPEC" "$IMPL_PLAN" "$FEATURE_DIR" "$CURRENT_BRANCH" "$HAS_GIT"
-else
-    echo "FEATURE_SPEC: $FEATURE_SPEC"
-    echo "IMPL_PLAN: $IMPL_PLAN" 
-    echo "SPECS_DIR: $FEATURE_DIR"
-    echo "BRANCH: $CURRENT_BRANCH"
-    echo "HAS_GIT: $HAS_GIT"
-fi
-

.specify/scripts/bash/update-agent-context.sh

@@ -1,829 +0,0 @@
-#!/usr/bin/env bash
-
-# Update agent context files with information from plan.md
-#
-# This script maintains AI agent context files by parsing feature specifications 
-# and updating agent-specific configuration files with project information.
-#
-# MAIN FUNCTIONS:
-# 1. Environment Validation
-#    - Verifies git repository structure and branch information
-#    - Checks for required plan.md files and templates
-#    - Validates file permissions and accessibility
-#
-# 2. Plan Data Extraction
-#    - Parses plan.md files to extract project metadata
-#    - Identifies language/version, frameworks, databases, and project types
-#    - Handles missing or incomplete specification data gracefully
-#
-# 3. Agent File Management
-#    - Creates new agent context files from templates when needed
-#    - Updates existing agent files with new project information
-#    - Preserves manual additions and custom configurations
-#    - Supports multiple AI agent formats and directory structures
-#
-# 4. Content Generation
-#    - Generates language-specific build/test commands
-#    - Creates appropriate project directory structures
-#    - Updates technology stacks and recent changes sections
-#    - Maintains consistent formatting and timestamps
-#
-# 5. Multi-Agent Support
-#    - Handles agent-specific file paths and naming conventions
-#    - Supports: Claude, Gemini, Copilot, Cursor, Qwen, opencode, Codex, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy CLI, Qoder CLI, Amp, SHAI, Kiro CLI, or Antigravity
-#    - Can update single agents or all existing agent files
-#    - Creates default Claude file if no agent files exist
-#
-# Usage: ./update-agent-context.sh [agent_type]
-# Agent types: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|kiro-cli|agy|bob|qodercli
-# Leave empty to update all existing agent files
-
-set -e
-
-# Enable strict error handling
-set -u
-set -o pipefail
-
-#==============================================================================
-# Configuration and Global Variables
-#==============================================================================
-
-# Get script directory and load common functions
-SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-source "$SCRIPT_DIR/common.sh"
-
-# Get all paths and variables from common functions
-eval $(get_feature_paths)
-
-NEW_PLAN="$IMPL_PLAN"  # Alias for compatibility with existing code
-AGENT_TYPE="${1:-}"
-
-# Agent-specific file paths  
-CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"
-GEMINI_FILE="$REPO_ROOT/GEMINI.md"
-COPILOT_FILE="$REPO_ROOT/.github/agents/copilot-instructions.md"
-CURSOR_FILE="$REPO_ROOT/.cursor/rules/specify-rules.mdc"
-QWEN_FILE="$REPO_ROOT/QWEN.md"
-AGENTS_FILE="$REPO_ROOT/AGENTS.md"
-WINDSURF_FILE="$REPO_ROOT/.windsurf/rules/specify-rules.md"
-KILOCODE_FILE="$REPO_ROOT/.kilocode/rules/specify-rules.md"
-AUGGIE_FILE="$REPO_ROOT/.augment/rules/specify-rules.md"
-ROO_FILE="$REPO_ROOT/.roo/rules/specify-rules.md"
-CODEBUDDY_FILE="$REPO_ROOT/CODEBUDDY.md"
-QODER_FILE="$REPO_ROOT/QODER.md"
-AMP_FILE="$REPO_ROOT/AGENTS.md"
-SHAI_FILE="$REPO_ROOT/SHAI.md"
-KIRO_FILE="$REPO_ROOT/AGENTS.md"
-AGY_FILE="$REPO_ROOT/.agent/rules/specify-rules.md"
-BOB_FILE="$REPO_ROOT/AGENTS.md"
-
-# Template file
-TEMPLATE_FILE="$REPO_ROOT/.specify/templates/agent-file-template.md"
-
-# Global variables for parsed plan data
-NEW_LANG=""
-NEW_FRAMEWORK=""
-NEW_DB=""
-NEW_PROJECT_TYPE=""
-
-#==============================================================================
-# Utility Functions
-#==============================================================================
-
-log_info() {
-    echo "INFO: $1"
-}
-
-log_success() {
-    echo "✓ $1"
-}
-
-log_error() {
-    echo "ERROR: $1" >&2
-}
-
-log_warning() {
-    echo "WARNING: $1" >&2
-}
-
-# Cleanup function for temporary files
-cleanup() {
-    local exit_code=$?
-    rm -f /tmp/agent_update_*_$$
-    rm -f /tmp/manual_additions_$$
-    exit $exit_code
-}
-
-# Set up cleanup trap
-trap cleanup EXIT INT TERM
-
-#==============================================================================
-# Validation Functions
-#==============================================================================
-
-validate_environment() {
-    # Check if we have a current branch/feature (git or non-git)
-    if [[ -z "$CURRENT_BRANCH" ]]; then
-        log_error "Unable to determine current feature"
-        if [[ "$HAS_GIT" == "true" ]]; then
-            log_info "Make sure you're on a feature branch"
-        else
-            log_info "Set SPECIFY_FEATURE environment variable or create a feature first"
-        fi
-        exit 1
-    fi
-    
-    # Check if plan.md exists
-    if [[ ! -f "$NEW_PLAN" ]]; then
-        log_error "No plan.md found at $NEW_PLAN"
-        log_info "Make sure you're working on a feature with a corresponding spec directory"
-        if [[ "$HAS_GIT" != "true" ]]; then
-            log_info "Use: export SPECIFY_FEATURE=your-feature-name or create a new feature first"
-        fi
-        exit 1
-    fi
-    
-    # Check if template exists (needed for new files)
-    if [[ ! -f "$TEMPLATE_FILE" ]]; then
-        log_warning "Template file not found at $TEMPLATE_FILE"
-        log_warning "Creating new agent files will fail"
-    fi
-}
-
-#==============================================================================
-# Plan Parsing Functions
-#==============================================================================
-
-extract_plan_field() {
-    local field_pattern="$1"
-    local plan_file="$2"
-    
-    grep "^\*\*${field_pattern}\*\*: " "$plan_file" 2>/dev/null | \
-        head -1 | \
-        sed "s|^\*\*${field_pattern}\*\*: ||" | \
-        sed 's/^[ \t]*//;s/[ \t]*$//' | \
-        grep -v "NEEDS CLARIFICATION" | \
-        grep -v "^N/A$" || echo ""
-}
-
-parse_plan_data() {
-    local plan_file="$1"
-    
-    if [[ ! -f "$plan_file" ]]; then
-        log_error "Plan file not found: $plan_file"
-        return 1
-    fi
-    
-    if [[ ! -r "$plan_file" ]]; then
-        log_error "Plan file is not readable: $plan_file"
-        return 1
-    fi
-    
-    log_info "Parsing plan data from $plan_file"
-    
-    NEW_LANG=$(extract_plan_field "Language/Version" "$plan_file")
-    NEW_FRAMEWORK=$(extract_plan_field "Primary Dependencies" "$plan_file")
-    NEW_DB=$(extract_plan_field "Storage" "$plan_file")
-    NEW_PROJECT_TYPE=$(extract_plan_field "Project Type" "$plan_file")
-    
-    # Log what we found
-    if [[ -n "$NEW_LANG" ]]; then
-        log_info "Found language: $NEW_LANG"
-    else
-        log_warning "No language information found in plan"
-    fi
-    
-    if [[ -n "$NEW_FRAMEWORK" ]]; then
-        log_info "Found framework: $NEW_FRAMEWORK"
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
-        log_info "Found database: $NEW_DB"
-    fi
-    
-    if [[ -n "$NEW_PROJECT_TYPE" ]]; then
-        log_info "Found project type: $NEW_PROJECT_TYPE"
-    fi
-}
-
-format_technology_stack() {
-    local lang="$1"
-    local framework="$2"
-    local parts=()
-    
-    # Add non-empty parts
-    [[ -n "$lang" && "$lang" != "NEEDS CLARIFICATION" ]] && parts+=("$lang")
-    [[ -n "$framework" && "$framework" != "NEEDS CLARIFICATION" && "$framework" != "N/A" ]] && parts+=("$framework")
-    
-    # Join with proper formatting
-    if [[ ${#parts[@]} -eq 0 ]]; then
-        echo ""
-    elif [[ ${#parts[@]} -eq 1 ]]; then
-        echo "${parts[0]}"
-    else
-        # Join multiple parts with " + "
-        local result="${parts[0]}"
-        for ((i=1; i<${#parts[@]}; i++)); do
-            result="$result + ${parts[i]}"
-        done
-        echo "$result"
-    fi
-}
-
-#==============================================================================
-# Template and Content Generation Functions
-#==============================================================================
-
-get_project_structure() {
-    local project_type="$1"
-    
-    if [[ "$project_type" == *"web"* ]]; then
-        echo "backend/\\nfrontend/\\ntests/"
-    else
-        echo "src/\\ntests/"
-    fi
-}
-
-get_commands_for_language() {
-    local lang="$1"
-    
-    case "$lang" in
-        *"Python"*)
-            echo "cd src && pytest && ruff check ."
-            ;;
-        *"Rust"*)
-            echo "cargo test && cargo clippy"
-            ;;
-        *"JavaScript"*|*"TypeScript"*)
-            echo "npm test \\&\\& npm run lint"
-            ;;
-        *)
-            echo "# Add commands for $lang"
-            ;;
-    esac
-}
-
-get_language_conventions() {
-    local lang="$1"
-    echo "$lang: Follow standard conventions"
-}
-
-create_new_agent_file() {
-    local target_file="$1"
-    local temp_file="$2"
-    local project_name="$3"
-    local current_date="$4"
-    
-    if [[ ! -f "$TEMPLATE_FILE" ]]; then
-        log_error "Template not found at $TEMPLATE_FILE"
-        return 1
-    fi
-    
-    if [[ ! -r "$TEMPLATE_FILE" ]]; then
-        log_error "Template file is not readable: $TEMPLATE_FILE"
-        return 1
-    fi
-    
-    log_info "Creating new agent context file from template..."
-    
-    if ! cp "$TEMPLATE_FILE" "$temp_file"; then
-        log_error "Failed to copy template file"
-        return 1
-    fi
-    
-    # Replace template placeholders
-    local project_structure
-    project_structure=$(get_project_structure "$NEW_PROJECT_TYPE")
-    
-    local commands
-    commands=$(get_commands_for_language "$NEW_LANG")
-    
-    local language_conventions
-    language_conventions=$(get_language_conventions "$NEW_LANG")
-    
-    # Perform substitutions with error checking using safer approach
-    # Escape special characters for sed by using a different delimiter or escaping
-    local escaped_lang=$(printf '%s\n' "$NEW_LANG" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    local escaped_framework=$(printf '%s\n' "$NEW_FRAMEWORK" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    local escaped_branch=$(printf '%s\n' "$CURRENT_BRANCH" | sed 's/[\[\.*^$()+{}|]/\\&/g')
-    
-    # Build technology stack and recent change strings conditionally
-    local tech_stack
-    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
-        tech_stack="- $escaped_lang + $escaped_framework ($escaped_branch)"
-    elif [[ -n "$escaped_lang" ]]; then
-        tech_stack="- $escaped_lang ($escaped_branch)"
-    elif [[ -n "$escaped_framework" ]]; then
-        tech_stack="- $escaped_framework ($escaped_branch)"
-    else
-        tech_stack="- ($escaped_branch)"
-    fi
-
-    local recent_change
-    if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_lang + $escaped_framework"
-    elif [[ -n "$escaped_lang" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_lang"
-    elif [[ -n "$escaped_framework" ]]; then
-        recent_change="- $escaped_branch: Added $escaped_framework"
-    else
-        recent_change="- $escaped_branch: Added"
-    fi
-
-    local substitutions=(
-        "s|\[PROJECT NAME\]|$project_name|"
-        "s|\[DATE\]|$current_date|"
-        "s|\[EXTRACTED FROM ALL PLAN.MD FILES\]|$tech_stack|"
-        "s|\[ACTUAL STRUCTURE FROM PLANS\]|$project_structure|g"
-        "s|\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]|$commands|"
-        "s|\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]|$language_conventions|"
-        "s|\[LAST 3 FEATURES AND WHAT THEY ADDED\]|$recent_change|"
-    )
-    
-    for substitution in "${substitutions[@]}"; do
-        if ! sed -i.bak -e "$substitution" "$temp_file"; then
-            log_error "Failed to perform substitution: $substitution"
-            rm -f "$temp_file" "$temp_file.bak"
-            return 1
-        fi
-    done
-    
-    # Convert \n sequences to actual newlines
-    newline=$(printf '\n')
-    sed -i.bak2 "s/\\\\n/${newline}/g" "$temp_file"
-
-    # Clean up backup files
-    rm -f "$temp_file.bak" "$temp_file.bak2"
-
-    # Prepend Cursor frontmatter for .mdc files so rules are auto-included
-    if [[ "$target_file" == *.mdc ]]; then
-        local frontmatter_file
-        frontmatter_file=$(mktemp) || return 1
-        printf '%s\n' "---" "description: Project Development Guidelines" "globs: [\"**/*\"]" "alwaysApply: true" "---" "" > "$frontmatter_file"
-        cat "$temp_file" >> "$frontmatter_file"
-        mv "$frontmatter_file" "$temp_file"
-    fi
-
-    return 0
-}
-
-
-
-
-update_existing_agent_file() {
-    local target_file="$1"
-    local current_date="$2"
-    
-    log_info "Updating existing agent context file..."
-    
-    # Use a single temporary file for atomic update
-    local temp_file
-    temp_file=$(mktemp) || {
-        log_error "Failed to create temporary file"
-        return 1
-    }
-    
-    # Process the file in one pass
-    local tech_stack=$(format_technology_stack "$NEW_LANG" "$NEW_FRAMEWORK")
-    local new_tech_entries=()
-    local new_change_entry=""
-    
-    # Prepare new technology entries
-    if [[ -n "$tech_stack" ]] && ! grep -q "$tech_stack" "$target_file"; then
-        new_tech_entries+=("- $tech_stack ($CURRENT_BRANCH)")
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]] && ! grep -q "$NEW_DB" "$target_file"; then
-        new_tech_entries+=("- $NEW_DB ($CURRENT_BRANCH)")
-    fi
-    
-    # Prepare new change entry
-    if [[ -n "$tech_stack" ]]; then
-        new_change_entry="- $CURRENT_BRANCH: Added $tech_stack"
-    elif [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]]; then
-        new_change_entry="- $CURRENT_BRANCH: Added $NEW_DB"
-    fi
-    
-    # Check if sections exist in the file
-    local has_active_technologies=0
-    local has_recent_changes=0
-    
-    if grep -q "^## Active Technologies" "$target_file" 2>/dev/null; then
-        has_active_technologies=1
-    fi
-    
-    if grep -q "^## Recent Changes" "$target_file" 2>/dev/null; then
-        has_recent_changes=1
-    fi
-    
-    # Process file line by line
-    local in_tech_section=false
-    local in_changes_section=false
-    local tech_entries_added=false
-    local changes_entries_added=false
-    local existing_changes_count=0
-    local file_ended=false
-    
-    while IFS= read -r line || [[ -n "$line" ]]; do
-        # Handle Active Technologies section
-        if [[ "$line" == "## Active Technologies" ]]; then
-            echo "$line" >> "$temp_file"
-            in_tech_section=true
-            continue
-        elif [[ $in_tech_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
-            # Add new tech entries before closing the section
-            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-                tech_entries_added=true
-            fi
-            echo "$line" >> "$temp_file"
-            in_tech_section=false
-            continue
-        elif [[ $in_tech_section == true ]] && [[ -z "$line" ]]; then
-            # Add new tech entries before empty line in tech section
-            if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-                printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-                tech_entries_added=true
-            fi
-            echo "$line" >> "$temp_file"
-            continue
-        fi
-        
-        # Handle Recent Changes section
-        if [[ "$line" == "## Recent Changes" ]]; then
-            echo "$line" >> "$temp_file"
-            # Add new change entry right after the heading
-            if [[ -n "$new_change_entry" ]]; then
-                echo "$new_change_entry" >> "$temp_file"
-            fi
-            in_changes_section=true
-            changes_entries_added=true
-            continue
-        elif [[ $in_changes_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
-            echo "$line" >> "$temp_file"
-            in_changes_section=false
-            continue
-        elif [[ $in_changes_section == true ]] && [[ "$line" == "- "* ]]; then
-            # Keep only first 2 existing changes
-            if [[ $existing_changes_count -lt 2 ]]; then
-                echo "$line" >> "$temp_file"
-                ((existing_changes_count++))
-            fi
-            continue
-        fi
-        
-        # Update timestamp
-        if [[ "$line" =~ \*\*Last\ updated\*\*:.*[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9] ]]; then
-            echo "$line" | sed "s/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/$current_date/" >> "$temp_file"
-        else
-            echo "$line" >> "$temp_file"
-        fi
-    done < "$target_file"
-    
-    # Post-loop check: if we're still in the Active Technologies section and haven't added new entries
-    if [[ $in_tech_section == true ]] && [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-        tech_entries_added=true
-    fi
-    
-    # If sections don't exist, add them at the end of the file
-    if [[ $has_active_technologies -eq 0 ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
-        echo "" >> "$temp_file"
-        echo "## Active Technologies" >> "$temp_file"
-        printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
-        tech_entries_added=true
-    fi
-    
-    if [[ $has_recent_changes -eq 0 ]] && [[ -n "$new_change_entry" ]]; then
-        echo "" >> "$temp_file"
-        echo "## Recent Changes" >> "$temp_file"
-        echo "$new_change_entry" >> "$temp_file"
-        changes_entries_added=true
-    fi
-    
-    # Ensure Cursor .mdc files have YAML frontmatter for auto-inclusion
-    if [[ "$target_file" == *.mdc ]]; then
-        if ! head -1 "$temp_file" | grep -q '^---'; then
-            local frontmatter_file
-            frontmatter_file=$(mktemp) || { rm -f "$temp_file"; return 1; }
-            printf '%s\n' "---" "description: Project Development Guidelines" "globs: [\"**/*\"]" "alwaysApply: true" "---" "" > "$frontmatter_file"
-            cat "$temp_file" >> "$frontmatter_file"
-            mv "$frontmatter_file" "$temp_file"
-        fi
-    fi
-
-    # Move temp file to target atomically
-    if ! mv "$temp_file" "$target_file"; then
-        log_error "Failed to update target file"
-        rm -f "$temp_file"
-        return 1
-    fi
-
-    return 0
-}
-#==============================================================================
-# Main Agent File Update Function
-#==============================================================================
-
-update_agent_file() {
-    local target_file="$1"
-    local agent_name="$2"
-    
-    if [[ -z "$target_file" ]] || [[ -z "$agent_name" ]]; then
-        log_error "update_agent_file requires target_file and agent_name parameters"
-        return 1
-    fi
-    
-    log_info "Updating $agent_name context file: $target_file"
-    
-    local project_name
-    project_name=$(basename "$REPO_ROOT")
-    local current_date
-    current_date=$(date +%Y-%m-%d)
-    
-    # Create directory if it doesn't exist
-    local target_dir
-    target_dir=$(dirname "$target_file")
-    if [[ ! -d "$target_dir" ]]; then
-        if ! mkdir -p "$target_dir"; then
-            log_error "Failed to create directory: $target_dir"
-            return 1
-        fi
-    fi
-    
-    if [[ ! -f "$target_file" ]]; then
-        # Create new file from template
-        local temp_file
-        temp_file=$(mktemp) || {
-            log_error "Failed to create temporary file"
-            return 1
-        }
-        
-        if create_new_agent_file "$target_file" "$temp_file" "$project_name" "$current_date"; then
-            if mv "$temp_file" "$target_file"; then
-                log_success "Created new $agent_name context file"
-            else
-                log_error "Failed to move temporary file to $target_file"
-                rm -f "$temp_file"
-                return 1
-            fi
-        else
-            log_error "Failed to create new agent file"
-            rm -f "$temp_file"
-            return 1
-        fi
-    else
-        # Update existing file
-        if [[ ! -r "$target_file" ]]; then
-            log_error "Cannot read existing file: $target_file"
-            return 1
-        fi
-        
-        if [[ ! -w "$target_file" ]]; then
-            log_error "Cannot write to existing file: $target_file"
-            return 1
-        fi
-        
-        if update_existing_agent_file "$target_file" "$current_date"; then
-            log_success "Updated existing $agent_name context file"
-        else
-            log_error "Failed to update existing agent file"
-            return 1
-        fi
-    fi
-    
-    return 0
-}
-
-#==============================================================================
-# Agent Selection and Processing
-#==============================================================================
-
-update_specific_agent() {
-    local agent_type="$1"
-    
-    case "$agent_type" in
-        claude)
-            update_agent_file "$CLAUDE_FILE" "Claude Code"
-            ;;
-        gemini)
-            update_agent_file "$GEMINI_FILE" "Gemini CLI"
-            ;;
-        copilot)
-            update_agent_file "$COPILOT_FILE" "GitHub Copilot"
-            ;;
-        cursor-agent)
-            update_agent_file "$CURSOR_FILE" "Cursor IDE"
-            ;;
-        qwen)
-            update_agent_file "$QWEN_FILE" "Qwen Code"
-            ;;
-        opencode)
-            update_agent_file "$AGENTS_FILE" "opencode"
-            ;;
-        codex)
-            update_agent_file "$AGENTS_FILE" "Codex CLI"
-            ;;
-        windsurf)
-            update_agent_file "$WINDSURF_FILE" "Windsurf"
-            ;;
-        kilocode)
-            update_agent_file "$KILOCODE_FILE" "Kilo Code"
-            ;;
-        auggie)
-            update_agent_file "$AUGGIE_FILE" "Auggie CLI"
-            ;;
-        roo)
-            update_agent_file "$ROO_FILE" "Roo Code"
-            ;;
-        codebuddy)
-            update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
-            ;;
-        qodercli)
-            update_agent_file "$QODER_FILE" "Qoder CLI"
-            ;;
-        amp)
-            update_agent_file "$AMP_FILE" "Amp"
-            ;;
-        shai)
-            update_agent_file "$SHAI_FILE" "SHAI"
-            ;;
-        kiro-cli)
-            update_agent_file "$KIRO_FILE" "Kiro CLI"
-            ;;
-        agy)
-            update_agent_file "$AGY_FILE" "Antigravity"
-            ;;
-        bob)
-            update_agent_file "$BOB_FILE" "IBM Bob"
-            ;;
-        generic)
-            log_info "Generic agent: no predefined context file. Use the agent-specific update script for your agent."
-            ;;
-        *)
-            log_error "Unknown agent type '$agent_type'"
-            log_error "Expected: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|kiro-cli|agy|bob|qodercli|generic"
-            exit 1
-            ;;
-    esac
-}
-
-update_all_existing_agents() {
-    local found_agent=false
-    
-    # Check each possible agent file and update if it exists
-    if [[ -f "$CLAUDE_FILE" ]]; then
-        update_agent_file "$CLAUDE_FILE" "Claude Code"
-        found_agent=true
-    fi
-    
-    if [[ -f "$GEMINI_FILE" ]]; then
-        update_agent_file "$GEMINI_FILE" "Gemini CLI"
-        found_agent=true
-    fi
-    
-    if [[ -f "$COPILOT_FILE" ]]; then
-        update_agent_file "$COPILOT_FILE" "GitHub Copilot"
-        found_agent=true
-    fi
-    
-    if [[ -f "$CURSOR_FILE" ]]; then
-        update_agent_file "$CURSOR_FILE" "Cursor IDE"
-        found_agent=true
-    fi
-    
-    if [[ -f "$QWEN_FILE" ]]; then
-        update_agent_file "$QWEN_FILE" "Qwen Code"
-        found_agent=true
-    fi
-    
-    if [[ -f "$AGENTS_FILE" ]]; then
-        update_agent_file "$AGENTS_FILE" "Codex/opencode"
-        found_agent=true
-    fi
-    
-    if [[ -f "$WINDSURF_FILE" ]]; then
-        update_agent_file "$WINDSURF_FILE" "Windsurf"
-        found_agent=true
-    fi
-    
-    if [[ -f "$KILOCODE_FILE" ]]; then
-        update_agent_file "$KILOCODE_FILE" "Kilo Code"
-        found_agent=true
-    fi
-
-    if [[ -f "$AUGGIE_FILE" ]]; then
-        update_agent_file "$AUGGIE_FILE" "Auggie CLI"
-        found_agent=true
-    fi
-    
-    if [[ -f "$ROO_FILE" ]]; then
-        update_agent_file "$ROO_FILE" "Roo Code"
-        found_agent=true
-    fi
-
-    if [[ -f "$CODEBUDDY_FILE" ]]; then
-        update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$SHAI_FILE" ]]; then
-        update_agent_file "$SHAI_FILE" "SHAI"
-        found_agent=true
-    fi
-
-    if [[ -f "$QODER_FILE" ]]; then
-        update_agent_file "$QODER_FILE" "Qoder CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$KIRO_FILE" ]]; then
-        update_agent_file "$KIRO_FILE" "Kiro CLI"
-        found_agent=true
-    fi
-
-    if [[ -f "$AGY_FILE" ]]; then
-        update_agent_file "$AGY_FILE" "Antigravity"
-        found_agent=true
-    fi
-    if [[ -f "$BOB_FILE" ]]; then
-        update_agent_file "$BOB_FILE" "IBM Bob"
-        found_agent=true
-    fi
-    
-    # If no agent files exist, create a default Claude file
-    if [[ "$found_agent" == false ]]; then
-        log_info "No existing agent files found, creating default Claude file..."
-        update_agent_file "$CLAUDE_FILE" "Claude Code"
-    fi
-}
-print_summary() {
-    echo
-    log_info "Summary of changes:"
-    
-    if [[ -n "$NEW_LANG" ]]; then
-        echo "  - Added language: $NEW_LANG"
-    fi
-    
-    if [[ -n "$NEW_FRAMEWORK" ]]; then
-        echo "  - Added framework: $NEW_FRAMEWORK"
-    fi
-    
-    if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
-        echo "  - Added database: $NEW_DB"
-    fi
-    
-    echo
-
-    log_info "Usage: $0 [claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|codebuddy|amp|shai|kiro-cli|agy|bob|qodercli]"
-}
-
-#==============================================================================
-# Main Execution
-#==============================================================================
-
-main() {
-    # Validate environment before proceeding
-    validate_environment
-    
-    log_info "=== Updating agent context files for feature $CURRENT_BRANCH ==="
-    
-    # Parse the plan file to extract project information
-    if ! parse_plan_data "$NEW_PLAN"; then
-        log_error "Failed to parse plan data"
-        exit 1
-    fi
-    
-    # Process based on agent type argument
-    local success=true
-    
-    if [[ -z "$AGENT_TYPE" ]]; then
-        # No specific agent provided - update all existing agent files
-        log_info "No agent specified, updating all existing agent files..."
-        if ! update_all_existing_agents; then
-            success=false
-        fi
-    else
-        # Specific agent provided - update only that agent
-        log_info "Updating specific agent: $AGENT_TYPE"
-        if ! update_specific_agent "$AGENT_TYPE"; then
-            success=false
-        fi
-    fi
-    
-    # Print summary
-    print_summary
-    
-    if [[ "$success" == true ]]; then
-        log_success "Agent context update completed successfully"
-        exit 0
-    else
-        log_error "Agent context update completed with errors"
-        exit 1
-    fi
-}
-
-# Execute main function if script is run directly
-if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
-    main "$@"
-fi

.specify/templates/agent-file-template.md

@@ -1,28 +0,0 @@
-# [PROJECT NAME] Development Guidelines
-
-Auto-generated from all feature plans. Last updated: [DATE]
-
-## Active Technologies
-
-[EXTRACTED FROM ALL PLAN.MD FILES]
-
-## Project Structure
-
-```text
-[ACTUAL STRUCTURE FROM PLANS]
-```
-
-## Commands
-
-[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]
-
-## Code Style
-
-[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
-
-## Recent Changes
-
-[LAST 3 FEATURES AND WHAT THEY ADDED]
-
-<!-- MANUAL ADDITIONS START -->
-<!-- MANUAL ADDITIONS END -->

.specify/templates/checklist-template.md

@@ -1,40 +0,0 @@
-# [CHECKLIST TYPE] Checklist: [FEATURE NAME]
-
-**Purpose**: [Brief description of what this checklist covers]
-**Created**: [DATE]
-**Feature**: [Link to spec.md or relevant documentation]
-
-**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements.
-
-<!-- 
-  ============================================================================
-  IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
-  
-  The /speckit.checklist command MUST replace these with actual items based on:
-  - User's specific checklist request
-  - Feature requirements from spec.md
-  - Technical context from plan.md
-  - Implementation details from tasks.md
-  
-  DO NOT keep these sample items in the generated checklist file.
-  ============================================================================
--->
-
-## [Category 1]
-
-- [ ] CHK001 First checklist item with clear action
-- [ ] CHK002 Second checklist item
-- [ ] CHK003 Third checklist item
-
-## [Category 2]
-
-- [ ] CHK004 Another category item
-- [ ] CHK005 Item with specific criteria
-- [ ] CHK006 Final item in this category
-
-## Notes
-
-- Check items off as completed: `[x]`
-- Add comments or findings inline
-- Link to relevant resources or documentation
-- Items are numbered sequentially for easy reference

.specify/templates/constitution-template.md

@@ -1,50 +0,0 @@
-# [PROJECT_NAME] Constitution
-<!-- Example: Spec Constitution, TaskFlow Constitution, etc. -->
-
-## Core Principles
-
-### [PRINCIPLE_1_NAME]
-<!-- Example: I. Library-First -->
-[PRINCIPLE_1_DESCRIPTION]
-<!-- Example: Every feature starts as a standalone library; Libraries must be self-contained, independently testable, documented; Clear purpose required - no organizational-only libraries -->
-
-### [PRINCIPLE_2_NAME]
-<!-- Example: II. CLI Interface -->
-[PRINCIPLE_2_DESCRIPTION]
-<!-- Example: Every library exposes functionality via CLI; Text in/out protocol: stdin/args → stdout, errors → stderr; Support JSON + human-readable formats -->
-
-### [PRINCIPLE_3_NAME]
-<!-- Example: III. Test-First (NON-NEGOTIABLE) -->
-[PRINCIPLE_3_DESCRIPTION]
-<!-- Example: TDD mandatory: Tests written → User approved → Tests fail → Then implement; Red-Green-Refactor cycle strictly enforced -->
-
-### [PRINCIPLE_4_NAME]
-<!-- Example: IV. Integration Testing -->
-[PRINCIPLE_4_DESCRIPTION]
-<!-- Example: Focus areas requiring integration tests: New library contract tests, Contract changes, Inter-service communication, Shared schemas -->
-
-### [PRINCIPLE_5_NAME]
-<!-- Example: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity -->
-[PRINCIPLE_5_DESCRIPTION]
-<!-- Example: Text I/O ensures debuggability; Structured logging required; Or: MAJOR.MINOR.BUILD format; Or: Start simple, YAGNI principles -->
-
-## [SECTION_2_NAME]
-<!-- Example: Additional Constraints, Security Requirements, Performance Standards, etc. -->
-
-[SECTION_2_CONTENT]
-<!-- Example: Technology stack requirements, compliance standards, deployment policies, etc. -->
-
-## [SECTION_3_NAME]
-<!-- Example: Development Workflow, Review Process, Quality Gates, etc. -->
-
-[SECTION_3_CONTENT]
-<!-- Example: Code review requirements, testing gates, deployment approval process, etc. -->
-
-## Governance
-<!-- Example: Constitution supersedes all other practices; Amendments require documentation, approval, migration plan -->
-
-[GOVERNANCE_RULES]
-<!-- Example: All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance -->
-
-**Version**: [CONSTITUTION_VERSION] | **Ratified**: [RATIFICATION_DATE] | **Last Amended**: [LAST_AMENDED_DATE]
-<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->

.specify/templates/plan-template.md

@@ -1,104 +0,0 @@
-# Implementation Plan: [FEATURE]
-
-**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
-**Input**: Feature specification from `/specs/[###-feature-name]/spec.md`
-
-**Note**: This template is filled in by the `/speckit.plan` command. See `.specify/templates/plan-template.md` for the execution workflow.
-
-## Summary
-
-[Extract from feature spec: primary requirement + technical approach from research]
-
-## Technical Context
-
-<!--
-  ACTION REQUIRED: Replace the content in this section with the technical details
-  for the project. The structure here is presented in advisory capacity to guide
-  the iteration process.
--->
-
-**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]  
-**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]  
-**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]  
-**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]  
-**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
-**Project Type**: [e.g., library/cli/web-service/mobile-app/compiler/desktop-app or NEEDS CLARIFICATION]  
-**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]  
-**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]  
-**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]
-
-## Constitution Check
-
-*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
-
-[Gates determined based on constitution file]
-
-## Project Structure
-
-### Documentation (this feature)
-
-```text
-specs/[###-feature]/
-├── plan.md              # This file (/speckit.plan command output)
-├── research.md          # Phase 0 output (/speckit.plan command)
-├── data-model.md        # Phase 1 output (/speckit.plan command)
-├── quickstart.md        # Phase 1 output (/speckit.plan command)
-├── contracts/           # Phase 1 output (/speckit.plan command)
-└── tasks.md             # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)
-```
-
-### Source Code (repository root)
-<!--
-  ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
-  for this feature. Delete unused options and expand the chosen structure with
-  real paths (e.g., apps/admin, packages/something). The delivered plan must
-  not include Option labels.
--->
-
-```text
-# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
-src/
-├── models/
-├── services/
-├── cli/
-└── lib/
-
-tests/
-├── contract/
-├── integration/
-└── unit/
-
-# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
-backend/
-├── src/
-│   ├── models/
-│   ├── services/
-│   └── api/
-└── tests/
-
-frontend/
-├── src/
-│   ├── components/
-│   ├── pages/
-│   └── services/
-└── tests/
-
-# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
-api/
-└── [same as backend above]
-
-ios/ or android/
-└── [platform-specific structure: feature modules, UI flows, platform tests]
-```
-
-**Structure Decision**: [Document the selected structure and reference the real
-directories captured above]
-
-## Complexity Tracking
-
-> **Fill ONLY if Constitution Check has violations that must be justified**
-
-| Violation | Why Needed | Simpler Alternative Rejected Because |
-|-----------|------------|-------------------------------------|
-| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
-| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |

.specify/templates/spec-template.md

@@ -1,115 +0,0 @@
-# Feature Specification: [FEATURE NAME]
-
-**Feature Branch**: `[###-feature-name]`  
-**Created**: [DATE]  
-**Status**: Draft  
-**Input**: User description: "$ARGUMENTS"
-
-## User Scenarios & Testing *(mandatory)*
-
-<!--
-  IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.
-  Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,
-  you should still have a viable MVP (Minimum Viable Product) that delivers value.
-  
-  Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.
-  Think of each story as a standalone slice of functionality that can be:
-  - Developed independently
-  - Tested independently
-  - Deployed independently
-  - Demonstrated to users independently
--->
-
-### User Story 1 - [Brief Title] (Priority: P1)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently - e.g., "Can be fully tested by [specific action] and delivers [specific value]"]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-2. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-### User Story 2 - [Brief Title] (Priority: P2)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-### User Story 3 - [Brief Title] (Priority: P3)
-
-[Describe this user journey in plain language]
-
-**Why this priority**: [Explain the value and why it has this priority level]
-
-**Independent Test**: [Describe how this can be tested independently]
-
-**Acceptance Scenarios**:
-
-1. **Given** [initial state], **When** [action], **Then** [expected outcome]
-
----
-
-[Add more user stories as needed, each with an assigned priority]
-
-### Edge Cases
-
-<!--
-  ACTION REQUIRED: The content in this section represents placeholders.
-  Fill them out with the right edge cases.
--->
-
-- What happens when [boundary condition]?
-- How does system handle [error scenario]?
-
-## Requirements *(mandatory)*
-
-<!--
-  ACTION REQUIRED: The content in this section represents placeholders.
-  Fill them out with the right functional requirements.
--->
-
-### Functional Requirements
-
-- **FR-001**: System MUST [specific capability, e.g., "allow users to create accounts"]
-- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]  
-- **FR-003**: Users MUST be able to [key interaction, e.g., "reset their password"]
-- **FR-004**: System MUST [data requirement, e.g., "persist user preferences"]
-- **FR-005**: System MUST [behavior, e.g., "log all security events"]
-
-*Example of marking unclear requirements:*
-
-- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]
-- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]
-
-### Key Entities *(include if feature involves data)*
-
-- **[Entity 1]**: [What it represents, key attributes without implementation]
-- **[Entity 2]**: [What it represents, relationships to other entities]
-
-## Success Criteria *(mandatory)*
-
-<!--
-  ACTION REQUIRED: Define measurable success criteria.
-  These must be technology-agnostic and measurable.
--->
-
-### Measurable Outcomes
-
-- **SC-001**: [Measurable metric, e.g., "Users can complete account creation in under 2 minutes"]
-- **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
-- **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
-- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]

.specify/templates/tasks-template.md

@@ -1,251 +0,0 @@
----
-
-description: "Task list template for feature implementation"
----
-
-# Tasks: [FEATURE NAME]
-
-**Input**: Design documents from `/specs/[###-feature-name]/`
-**Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/
-
-**Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.
-
-**Organization**: Tasks are grouped by user story to enable independent implementation and testing of each story.
-
-## Format: `[ID] [P?] [Story] Description`
-
-- **[P]**: Can run in parallel (different files, no dependencies)
-- **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3)
-- Include exact file paths in descriptions
-
-## Path Conventions
-
-- **Single project**: `src/`, `tests/` at repository root
-- **Web app**: `backend/src/`, `frontend/src/`
-- **Mobile**: `api/src/`, `ios/src/` or `android/src/`
-- Paths shown below assume single project - adjust based on plan.md structure
-
-<!-- 
-  ============================================================================
-  IMPORTANT: The tasks below are SAMPLE TASKS for illustration purposes only.
-  
-  The /speckit.tasks command MUST replace these with actual tasks based on:
-  - User stories from spec.md (with their priorities P1, P2, P3...)
-  - Feature requirements from plan.md
-  - Entities from data-model.md
-  - Endpoints from contracts/
-  
-  Tasks MUST be organized by user story so each story can be:
-  - Implemented independently
-  - Tested independently
-  - Delivered as an MVP increment
-  
-  DO NOT keep these sample tasks in the generated tasks.md file.
-  ============================================================================
--->
-
-## Phase 1: Setup (Shared Infrastructure)
-
-**Purpose**: Project initialization and basic structure
-
-- [ ] T001 Create project structure per implementation plan
-- [ ] T002 Initialize [language] project with [framework] dependencies
-- [ ] T003 [P] Configure linting and formatting tools
-
----
-
-## Phase 2: Foundational (Blocking Prerequisites)
-
-**Purpose**: Core infrastructure that MUST be complete before ANY user story can be implemented
-
-**⚠️ CRITICAL**: No user story work can begin until this phase is complete
-
-Examples of foundational tasks (adjust based on your project):
-
-- [ ] T004 Setup database schema and migrations framework
-- [ ] T005 [P] Implement authentication/authorization framework
-- [ ] T006 [P] Setup API routing and middleware structure
-- [ ] T007 Create base models/entities that all stories depend on
-- [ ] T008 Configure error handling and logging infrastructure
-- [ ] T009 Setup environment configuration management
-
-**Checkpoint**: Foundation ready - user story implementation can now begin in parallel
-
----
-
-## Phase 3: User Story 1 - [Title] (Priority: P1) 🎯 MVP
-
-**Goal**: [Brief description of what this story delivers]
-
-**Independent Test**: [How to verify this story works on its own]
-
-### Tests for User Story 1 (OPTIONAL - only if tests requested) ⚠️
-
-> **NOTE: Write these tests FIRST, ensure they FAIL before implementation**
-
-- [ ] T010 [P] [US1] Contract test for [endpoint] in tests/contract/test_[name].py
-- [ ] T011 [P] [US1] Integration test for [user journey] in tests/integration/test_[name].py
-
-### Implementation for User Story 1
-
-- [ ] T012 [P] [US1] Create [Entity1] model in src/models/[entity1].py
-- [ ] T013 [P] [US1] Create [Entity2] model in src/models/[entity2].py
-- [ ] T014 [US1] Implement [Service] in src/services/[service].py (depends on T012, T013)
-- [ ] T015 [US1] Implement [endpoint/feature] in src/[location]/[file].py
-- [ ] T016 [US1] Add validation and error handling
-- [ ] T017 [US1] Add logging for user story 1 operations
-
-**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
-
----
-
-## Phase 4: User Story 2 - [Title] (Priority: P2)
-
-**Goal**: [Brief description of what this story delivers]
-
-**Independent Test**: [How to verify this story works on its own]
-
-### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
-
-- [ ] T018 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
-- [ ] T019 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
-
-### Implementation for User Story 2
-
-- [ ] T020 [P] [US2] Create [Entity] model in src/models/[entity].py
-- [ ] T021 [US2] Implement [Service] in src/services/[service].py
-- [ ] T022 [US2] Implement [endpoint/feature] in src/[location]/[file].py
-- [ ] T023 [US2] Integrate with User Story 1 components (if needed)
-
-**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
-
----
-
-## Phase 5: User Story 3 - [Title] (Priority: P3)
-
-**Goal**: [Brief description of what this story delivers]
-
-**Independent Test**: [How to verify this story works on its own]
-
-### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
-
-- [ ] T024 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
-- [ ] T025 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
-
-### Implementation for User Story 3
-
-- [ ] T026 [P] [US3] Create [Entity] model in src/models/[entity].py
-- [ ] T027 [US3] Implement [Service] in src/services/[service].py
-- [ ] T028 [US3] Implement [endpoint/feature] in src/[location]/[file].py
-
-**Checkpoint**: All user stories should now be independently functional
-
----
-
-[Add more user story phases as needed, following the same pattern]
-
----
-
-## Phase N: Polish & Cross-Cutting Concerns
-
-**Purpose**: Improvements that affect multiple user stories
-
-- [ ] TXXX [P] Documentation updates in docs/
-- [ ] TXXX Code cleanup and refactoring
-- [ ] TXXX Performance optimization across all stories
-- [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/
-- [ ] TXXX Security hardening
-- [ ] TXXX Run quickstart.md validation
-
----
-
-## Dependencies & Execution Order
-
-### Phase Dependencies
-
-- **Setup (Phase 1)**: No dependencies - can start immediately
-- **Foundational (Phase 2)**: Depends on Setup completion - BLOCKS all user stories
-- **User Stories (Phase 3+)**: All depend on Foundational phase completion
-  - User stories can then proceed in parallel (if staffed)
-  - Or sequentially in priority order (P1 → P2 → P3)
-- **Polish (Final Phase)**: Depends on all desired user stories being complete
-
-### User Story Dependencies
-
-- **User Story 1 (P1)**: Can start after Foundational (Phase 2) - No dependencies on other stories
-- **User Story 2 (P2)**: Can start after Foundational (Phase 2) - May integrate with US1 but should be independently testable
-- **User Story 3 (P3)**: Can start after Foundational (Phase 2) - May integrate with US1/US2 but should be independently testable
-
-### Within Each User Story
-
-- Tests (if included) MUST be written and FAIL before implementation
-- Models before services
-- Services before endpoints
-- Core implementation before integration
-- Story complete before moving to next priority
-
-### Parallel Opportunities
-
-- All Setup tasks marked [P] can run in parallel
-- All Foundational tasks marked [P] can run in parallel (within Phase 2)
-- Once Foundational phase completes, all user stories can start in parallel (if team capacity allows)
-- All tests for a user story marked [P] can run in parallel
-- Models within a story marked [P] can run in parallel
-- Different user stories can be worked on in parallel by different team members
-
----
-
-## Parallel Example: User Story 1
-
-```bash
-# Launch all tests for User Story 1 together (if tests requested):
-Task: "Contract test for [endpoint] in tests/contract/test_[name].py"
-Task: "Integration test for [user journey] in tests/integration/test_[name].py"
-
-# Launch all models for User Story 1 together:
-Task: "Create [Entity1] model in src/models/[entity1].py"
-Task: "Create [Entity2] model in src/models/[entity2].py"
-```
-
----
-
-## Implementation Strategy
-
-### MVP First (User Story 1 Only)
-
-1. Complete Phase 1: Setup
-2. Complete Phase 2: Foundational (CRITICAL - blocks all stories)
-3. Complete Phase 3: User Story 1
-4. **STOP and VALIDATE**: Test User Story 1 independently
-5. Deploy/demo if ready
-
-### Incremental Delivery
-
-1. Complete Setup + Foundational → Foundation ready
-2. Add User Story 1 → Test independently → Deploy/Demo (MVP!)
-3. Add User Story 2 → Test independently → Deploy/Demo
-4. Add User Story 3 → Test independently → Deploy/Demo
-5. Each story adds value without breaking previous stories
-
-### Parallel Team Strategy
-
-With multiple developers:
-
-1. Team completes Setup + Foundational together
-2. Once Foundational is done:
-   - Developer A: User Story 1
-   - Developer B: User Story 2
-   - Developer C: User Story 3
-3. Stories complete and integrate independently
-
----
-
-## Notes
-
-- [P] tasks = different files, no dependencies
-- [Story] label maps task to specific user story for traceability
-- Each user story should be independently completable and testable
-- Verify tests fail before implementing
-- Commit after each task or logical group
-- Stop at any checkpoint to validate story independently
-- Avoid: vague tasks, same file conflicts, cross-story dependencies that break independence

.vscode/launch.json

@@ -67,15 +67,13 @@
         "--config",
         "./jest-integration.config.ts",
         "${relativeFile}",
-        "--silent=false",
-        "${input:updateSnapshot}"
+        "--silent=false"
       ],
       "cwd": "${workspaceFolder}/packages/twenty-server",
       "console": "integratedTerminal",
       "internalConsoleOptions": "neverOpen",
       "env": {
-        "NODE_ENV": "test",
-        "NODE_OPTIONS": "--max-old-space-size=12288 --import tsx/esm"
+        "NODE_ENV": "test"
       }
     },
     {
@@ -99,14 +97,5 @@
         "NODE_ENV": "test"
       }
     }
-  ],
-  "inputs": [
-    {
-      "id": "updateSnapshot",
-      "type": "pickString",
-      "description": "Update snapshots?",
-      "options": ["", "--updateSnapshot"],
-      "default": ""
-    }
   ]
 }

.vscode/settings.json

@@ -1,70 +1,56 @@
 {
+  "editor.formatOnSave": false,
+  "files.eol": "\n",
+  "files.insertFinalNewline": true,
+  "files.trimTrailingWhitespace": true,
+  "[typescript]": {
     "editor.formatOnSave": false,
-    "files.eol": "\n",
-    "files.insertFinalNewline": true,
-    "files.trimTrailingWhitespace": true,
-    "[typescript]": {
-        "editor.formatOnSave": false,
-        "editor.codeActionsOnSave": {
-            "source.fixAll.eslint": "explicit",
-            "source.addMissingImports": "always",
-            "source.organizeImports": "always"
-        }
-    },
-    "[javascript]": {
-        "editor.formatOnSave": false,
-        "editor.codeActionsOnSave": {
-            "source.fixAll.eslint": "explicit",
-            "source.addMissingImports": "always",
-            "source.organizeImports": "always"
-        }
-    },
-    "[typescriptreact]": {
-        "editor.formatOnSave": false,
-        "editor.codeActionsOnSave": {
-            "source.fixAll.eslint": "explicit",
-            "source.addMissingImports": "always",
-            "source.organizeImports": "always"
-        }
-    },
-    "[json]": {
-        "editor.formatOnSave": true
-    },
-    "javascript.format.enable": false,
-    "javascript.preferences.importModuleSpecifier": "non-relative",
-    "typescript.format.enable": false,
-    "cSpell.enableFiletypes": [
-        "!javascript",
-        "!json",
-        "!typescript",
-        "!typescriptreact",
-        "md",
-        "mdx"
-    ],
-    "cSpell.words": [
-        "twentyhq"
-    ],
-    "typescript.preferences.importModuleSpecifier": "non-relative",
-    "search.exclude": {
-        "**/.yarn": true
-    },
-    "eslint.useFlatConfig": true,
-    "eslint.debug": true,
-    "files.associations": {
-        ".cursorrules": "markdown"
-    },
-    "jestrunner.codeLensSelector": "**/*.{test,spec,integration-spec}.{js,jsx,ts,tsx}",
-    "typescript.tsdk": "node_modules/typescript/lib",
-    "typescript.experimental.useTsgo": false,
-    "chat.promptFilesRecommendations": {
-        "speckit.constitution": true,
-        "speckit.specify": true,
-        "speckit.plan": true,
-        "speckit.tasks": true,
-        "speckit.implement": true
-    },
-    "chat.tools.terminal.autoApprove": {
-        ".specify/scripts/bash/": true,
-        ".specify/scripts/powershell/": true
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": "explicit",
+      "source.addMissingImports": "always",
+      "source.organizeImports": "always"
     }
+  },
+  "[javascript]": {
+    "editor.formatOnSave": false,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": "explicit",
+      "source.addMissingImports": "always",
+      "source.organizeImports": "always"
+    }
+  },
+  "[typescriptreact]": {
+    "editor.formatOnSave": false,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.eslint": "explicit",
+      "source.addMissingImports": "always",
+      "source.organizeImports": "always"
+    }
+  },
+  "[json]": {
+    "editor.formatOnSave": true
+  },
+  "javascript.format.enable": false,
+  "typescript.format.enable": false,
+  "cSpell.enableFiletypes": [
+    "!javascript",
+    "!json",
+    "!typescript",
+    "!typescriptreact",
+    "md",
+    "mdx"
+  ],
+  "cSpell.words": [
+    "twentyhq"
+  ],
+  "typescript.preferences.importModuleSpecifier": "non-relative",
+  "search.exclude": {
+    "**/.yarn": true
+  },
+  "eslint.debug": true,
+  "files.associations": {
+    ".cursorrules": "markdown"
+  },
+  "jestrunner.codeLensSelector": "**/*.{test,spec,integration-spec}.{js,jsx,ts,tsx}",
+  "typescript.tsdk": "node_modules/typescript/lib"
 }

.vscode/tasks.json

@@ -2,64 +2,12 @@
 	"version": "2.0.0",
 	"tasks": [
 		{
-			"label": "twenty-server - run integration test file",
-			"type": "shell",
-			"command": "npx nx run twenty-server:jest -- --config ./jest-integration.config.ts ${relativeFile} --silent=false ${input:watchMode} ${input:updateSnapshot}",
-			"options": {
-				"cwd": "${workspaceFolder}/packages/twenty-server",
-				"env": {
-					"NODE_ENV": "test",
-					"NODE_OPTIONS": "--max-old-space-size=12288 --import tsx/esm"
-				},
-				"shell": {
-					"executable": "/bin/zsh",
-					"args": ["-l", "-c"]
-				}
-			},
-			"presentation": {
-				"reveal": "always",
-				"panel": "new",
-				"close": false
-			},
-			"problemMatcher": []
-		},
-		{
-			"label": "twenty-server - run unit test file",
-			"type": "shell",
-			"command": "npx nx run twenty-server:jest -- --config ./jest.config.mjs ${relativeFile} --silent=false ${input:watchMode} ${input:updateSnapshot}",
-			"options": {
-				"cwd": "${workspaceFolder}/packages/twenty-server",
-				"env": {
-					"NODE_ENV": "test",
-					"NODE_OPTIONS": "--max-old-space-size=12288 --import tsx/esm"
-				},
-				"shell": {
-					"executable": "/bin/zsh",
-					"args": ["-l", "-c"]
-				}
-			},
-			"presentation": {
-				"reveal": "always",
-				"panel": "new",
-				"close": false
-			},
-			"problemMatcher": []
-		}
-	],
-	"inputs": [
-		{
-			"id": "watchMode",
-			"type": "pickString",
-			"description": "Enable watch mode?",
-			"options": ["", "--watch"],
-			"default": ""
-		},
-		{
-			"id": "updateSnapshot",
-			"type": "pickString",
-			"description": "Update snapshots?",
-			"options": ["", "--updateSnapshot"],
-			"default": ""
+			"type": "npm",
+			"script": "start",
+			"path": "server",
+			"problemMatcher": [],
+			"label": "yarn: start - server",
+			"detail": "yarn start"
 		}
 	]
-}
+}

.yarn/patches/@wyw-in-js-transform-npm-0.7.0-ba641dc99f.patch

@@ -1,58 +0,0 @@
-diff --git a/esm/cache.js b/esm/cache.js
-index 07cf6d7dd99effb9c3464b620ba67a7f445224f5..248bb527923499a6be8065ee7a3613b55819c58c 100644
---- a/esm/cache.js
-+++ b/esm/cache.js
-@@ -69,17 +69,20 @@ export class TransformCacheCollection {
-       this.invalidate(cacheName, filename);
-     });
-   }
--  invalidateIfChanged(filename, content) {
-+  invalidateIfChanged(filename, content, _visited) {
-+    const visited = _visited || new Set();
-+    if (visited.has(filename)) {
-+      return false;
-+    }
-+    visited.add(filename);
-     const fileEntrypoint = this.get('entrypoints', filename);
- 
--    // We need to check all dependencies of the file
--    // because they might have changed as well.
-     if (fileEntrypoint) {
-       for (const [, dependency] of fileEntrypoint.dependencies) {
-         const dependencyFilename = dependency.resolved;
-         if (dependencyFilename) {
-           const dependencyContent = fs.readFileSync(dependencyFilename, 'utf8');
--          this.invalidateIfChanged(dependencyFilename, dependencyContent);
-+          this.invalidateIfChanged(dependencyFilename, dependencyContent, visited);
-         }
-       }
-     }
-diff --git a/lib/cache.js b/lib/cache.js
-index 0762ed7d3c39b31000f7aa7d8156da15403c8e64..6955410cd3c9ec53cf7a01c8346abc4c47fff791 100644
---- a/lib/cache.js
-+++ b/lib/cache.js
-@@ -77,17 +77,20 @@ class TransformCacheCollection {
-       this.invalidate(cacheName, filename);
-     });
-   }
--  invalidateIfChanged(filename, content) {
-+  invalidateIfChanged(filename, content, _visited) {
-+    const visited = _visited || new Set();
-+    if (visited.has(filename)) {
-+      return false;
-+    }
-+    visited.add(filename);
-     const fileEntrypoint = this.get('entrypoints', filename);
- 
--    // We need to check all dependencies of the file
--    // because they might have changed as well.
-     if (fileEntrypoint) {
-       for (const [, dependency] of fileEntrypoint.dependencies) {
-         const dependencyFilename = dependency.resolved;
-         if (dependencyFilename) {
-           const dependencyContent = _nodeFs.default.readFileSync(dependencyFilename, 'utf8');
--          this.invalidateIfChanged(dependencyFilename, dependencyContent);
-+          this.invalidateIfChanged(dependencyFilename, dependencyContent, visited);
-         }
-       }
-     }

CLAUDE.md

@@ -21,33 +21,25 @@ 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
+# Run tests
 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
+npx nx storybook:build twenty-front         # Build Storybook
+npx nx storybook:serve-and-test:static twenty-front     # Run Storybook tests
 
-# When testing the UI end to end, click on "Continue with Email" and use the prefilled credentials.
+
+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
+# Linting
+npx nx lint twenty-front      # Frontend linting
+npx nx lint twenty-server     # Backend linting
+npx nx lint twenty-front --fix  # Auto-fix linting issues
 
 # Type checking
 npx nx typecheck twenty-front
@@ -60,8 +52,7 @@ npx nx fmt twenty-server
 
 ### Build
 ```bash
-# Build packages (twenty-shared must be built first)
-npx nx build twenty-shared
+# Build packages
 npx nx build twenty-front
 npx nx build twenty-server
 ```
@@ -73,8 +64,8 @@ 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 migrations
 
-# Generate migration (replace [name] with kebab-case descriptive name)
-npx nx run twenty-server:typeorm migration:generate src/database/typeorm/core/migrations/common/[name] -d src/database/typeorm/core/core.datasource.ts
+# Generate migration
+npx nx run twenty-server:typeorm migration:generate src/database/typeorm/core/migrations/[name] -d src/database/typeorm/core/core.datasource.ts
 
 # Sync metadata
 npx nx run twenty-server:command workspace:sync-metadata
@@ -82,15 +73,14 @@ npx nx run twenty-server:command workspace:sync-metadata
 
 ### GraphQL
 ```bash
-# Generate GraphQL types (run after schema changes)
+# Generate GraphQL types
 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
+- **Frontend**: React 18, TypeScript, Recoil (state management), Emotion (styling), Vite
 - **Backend**: NestJS, TypeORM, PostgreSQL, Redis, GraphQL (with GraphQL Yoga)
 - **Monorepo**: Nx workspace managed with Yarn 4
 
@@ -112,36 +102,13 @@ packages/
 - **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
+- **No 'any' type allowed**
 - **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)
+- **Recoil** for global state management
+- Component-specific state with React hooks
 - GraphQL cache managed by Apollo Client
-- Use functional state updates: `setState(prev => prev + 1)`
 
 ### Backend Architecture
 - **NestJS modules** for feature organization
@@ -150,54 +117,36 @@ packages/
 - **Redis** for caching and session management
 - **BullMQ** for background job processing
 
-### Database & Migrations
+### Database
 - **PostgreSQL** as primary database
 - **Redis** for caching and sessions
+- **TypeORM migrations** for schema management
 - **ClickHouse** for analytics (when enabled)
-- Always generate migrations when changing entity files
-- Migration names must be kebab-case (e.g. `add-agent-turn-evaluation`)
-- Include both `up` and `down` logic in migrations
-- Never delete or rewrite committed migrations
-
-### 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 database migrations are generated for entity changes
+1. Always run linting and type checking after code changes
+2. Test changes with relevant test suites
+3. Ensure database migrations are properly structured
 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)
+- Use **Emotion** for styling with styled-components pattern
 - Follow **Nx** workspace conventions for imports
 - Use **Lingui** for internationalization
-- Apply security first, then formatting (sanitize before format)
+- Components should be in their own directories with tests and stories
 
 ### 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()`
-
-## CI Environment (GitHub Actions)
-
-When running in CI, the dev environment is **not** pre-configured. Dependencies are installed but builds, env files, and databases are not set up.
-
-- **Before running tests, builds, lint, type checks, or DB operations**, run: `bash packages/twenty-utils/setup-dev-env.sh`
-- **Skip the setup script** for tasks that only read code — architecture questions, code review, documentation, etc.
-- The script is idempotent and safe to run multiple times.
+- **Unit tests** with Jest for both frontend and backend
+- **Integration tests** for critical backend workflows
+- **Storybook** for component development and testing
+- **E2E tests** with Playwright for critical user flows
 
 ## 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
+- `.cursor/rules/` - Development guidelines and best practices

Makefile

@@ -0,0 +1,48 @@
+DOCKER_NETWORK=twenty_network
+
+ensure-docker-network:
+	docker network inspect $(DOCKER_NETWORK) >/dev/null 2>&1 || docker network create $(DOCKER_NETWORK)
+
+postgres-on-docker: ensure-docker-network
+	docker run -d --network $(DOCKER_NETWORK) \
+	--name twenty_pg \
+	-e POSTGRES_USER=postgres \
+	-e POSTGRES_PASSWORD=postgres \
+	-e ALLOW_NOSSL=true \
+	-v twenty_db_data:/var/lib/postgresql/data \
+	-p 5432:5432 \
+	postgres:16
+	@echo "Waiting for PostgreSQL to be ready..."
+	@until docker exec twenty_pg psql -U postgres -d postgres \
+		-c 'SELECT pg_is_in_recovery();' 2>/dev/null | grep -q 'f'; do \
+		sleep 1; \
+	done
+	docker exec twenty_pg psql -U postgres -d postgres \
+		-c "CREATE DATABASE \"default\" WITH OWNER postgres;" \
+		-c "CREATE DATABASE \"test\" WITH OWNER postgres;"
+
+redis-on-docker: ensure-docker-network
+	docker run -d --network $(DOCKER_NETWORK) --name twenty_redis -p 6379:6379 redis/redis-stack-server:latest
+
+clickhouse-on-docker: ensure-docker-network
+	docker run -d --network $(DOCKER_NETWORK) --name twenty_clickhouse -p 8123:8123 -p 9000:9000 -e CLICKHOUSE_PASSWORD=devPassword clickhouse/clickhouse-server:latest \
+
+grafana-on-docker: ensure-docker-network
+	docker run -d --network $(DOCKER_NETWORK) \
+	--name twenty_grafana \
+	-p 4000:3000 \
+	-e GF_SECURITY_ADMIN_USER=admin \
+	-e GF_SECURITY_ADMIN_PASSWORD=admin \
+	-e GF_INSTALL_PLUGINS=grafana-clickhouse-datasource \
+	-v $(PWD)/packages/twenty-docker/grafana/provisioning/datasources:/etc/grafana/provisioning/datasources \
+	grafana/grafana-oss:latest
+
+opentelemetry-collector-on-docker: ensure-docker-network
+	docker run -d --network $(DOCKER_NETWORK) \
+	--name twenty_otlp_collector \
+	-p 4317:4317 \
+	-p 4318:4318 \
+	-p 13133:13133 \
+	-v $(PWD)/packages/twenty-docker/otel-collector/otel-collector-config.yaml:/etc/otel-collector-config.yaml \
+	otel/opentelemetry-collector-contrib:latest \
+	--config /etc/otel-collector-config.yaml

README.md

@@ -28,7 +28,7 @@ See:
 🚀 [Self-hosting](https://docs.twenty.com/developers/self-hosting/docker-compose)
 🖥️ [Local Setup](https://docs.twenty.com/developers/local-setup)
 
-# Why Twenty
+# Does the world need another CRM?
 
 We built Twenty for three reasons:
 
@@ -109,7 +109,7 @@ Below are a few features we have implemented to date:
 - [TypeScript](https://www.typescriptlang.org/)
 - [Nx](https://nx.dev/)
 - [NestJS](https://nestjs.com/), with [BullMQ](https://bullmq.io/), [PostgreSQL](https://www.postgresql.org/), [Redis](https://redis.io/)
-- [React](https://reactjs.org/), with [Jotai](https://jotai.org/), [Linaria](https://linaria.dev/) and [Lingui](https://lingui.dev/)
+- [React](https://reactjs.org/), with [Recoil](https://recoiljs.org/), [Emotion](https://emotion.sh/) and [Lingui](https://lingui.dev/)
 
 
 
@@ -120,7 +120,6 @@ Below are a few features we have implemented to date:
   <a href="https://greptile.com"><img src="./packages/twenty-website/public/images/readme/greptile.png" height="30" alt="Greptile" /></a>
   <a href="https://sentry.io/"><img src="./packages/twenty-website/public/images/readme/sentry.png" height="30" alt="Sentry" /></a>
   <a href="https://crowdin.com/"><img src="./packages/twenty-website/public/images/readme/crowdin.png" height="30" alt="Crowdin" /></a>
-  <a href="https://e2b.dev/"><img src="./packages/twenty-website/public/images/readme/e2b.svg" height="30" alt="E2B" /></a>
 </p>
 
   Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).

crowdin.yml

@@ -0,0 +1,31 @@
+#
+# Basic Crowdin CLI configuration
+# See https://crowdin.github.io/crowdin-cli/configuration for more information
+# See https://support.crowdin.com/developer/configuration-file/ for all available options
+#
+
+#
+# Defines whether to preserve the original directory structure in the Crowdin project
+# Recommended to set to true
+#
+"preserve_hierarchy": true
+
+#
+# Files configuration.
+# See https://support.crowdin.com/developer/configuration-file/ for all available options
+#
+files: [
+  {
+    #
+    # Source files filter
+    # e.g. "/resources/en/*.json"
+    #
+    "source": "**/en.po",
+
+    #
+    # Translation files filter
+    # e.g. "/resources/%two_letters_code%/%original_file_name%"
+    #
+    "translation": "%original_path%/%locale%.po",
+  }
+]

eslint.config.mjs

@@ -4,17 +4,12 @@ import typescriptEslint from '@typescript-eslint/eslint-plugin';
 import typescriptParser from '@typescript-eslint/parser';
 import importPlugin from 'eslint-plugin-import';
 import linguiPlugin from 'eslint-plugin-lingui';
-import * as mdxPlugin from 'eslint-plugin-mdx';
 import preferArrowPlugin from 'eslint-plugin-prefer-arrow';
 import prettierPlugin from 'eslint-plugin-prettier';
 import unicornPlugin from 'eslint-plugin-unicorn';
 import unusedImportsPlugin from 'eslint-plugin-unused-imports';
 import jsoncParser from 'jsonc-eslint-parser';
 
-const twentyRules = await nxPlugin.loadWorkspaceRules(
-  'packages/twenty-eslint-rules',
-);
-
 export default [
   // Base JavaScript configuration
   js.configs.recommended,
@@ -65,11 +60,7 @@ export default [
             },
             {
               sourceTag: 'scope:sdk',
-              onlyDependOnLibsWithTags: ['scope:sdk', 'scope:shared'],
-            },
-            {
-              sourceTag: 'scope:create-app',
-              onlyDependOnLibsWithTags: ['scope:create-app', 'scope:shared'],
+              onlyDependOnLibsWithTags: ['scope:sdk'],
             },
             {
               sourceTag: 'scope:shared',
@@ -85,7 +76,7 @@ export default [
             },
             {
               sourceTag: 'scope:zapier',
-              onlyDependOnLibsWithTags: ['scope:shared', 'scope:zapier'],
+              onlyDependOnLibsWithTags: ['scope:shared'],
             },
           ],
         },
@@ -149,10 +140,10 @@ export default [
       '@typescript-eslint/explicit-function-return-type': 'off',
       '@typescript-eslint/explicit-module-boundary-types': 'off',
       '@typescript-eslint/interface-name-prefix': 'off',
-      '@typescript-eslint/no-empty-object-type': [
+      '@typescript-eslint/no-empty-interface': [
         'error',
         {
-          allowInterfaces: 'with-single-extends',
+          allowSingleExtends: true,
         },
       ],
       '@typescript-eslint/no-explicit-any': 'off',
@@ -200,27 +191,4 @@ export default [
       parser: jsoncParser,
     },
   },
-
-  // MDX files
-  {
-    ...mdxPlugin.flat,
-    plugins: {
-      ...mdxPlugin.flat.plugins,
-      '@nx': nxPlugin,
-      twenty: { rules: twentyRules },
-    },
-  },
-  mdxPlugin.flatCodeBlocks,
-  {
-    files: ['**/*.mdx'],
-    rules: {
-      'no-unused-vars': 'off',
-      'unused-imports/no-unused-imports': 'off',
-      'unused-imports/no-unused-vars': 'off',
-      // Enforce JSX tags on separate lines to prevent Crowdin translation issues
-      'twenty/mdx-component-newlines': 'error',
-      // Disallow angle bracket placeholders to prevent Crowdin translation errors
-      'twenty/no-angle-bracket-placeholders': 'error',
-    },
-  },
 ];

eslint.config.react.mjs

@@ -0,0 +1,302 @@
+import js from '@eslint/js';
+import nxPlugin from '@nx/eslint-plugin';
+import typescriptEslint from '@typescript-eslint/eslint-plugin';
+import typescriptParser from '@typescript-eslint/parser';
+import importPlugin from 'eslint-plugin-import';
+import linguiPlugin from 'eslint-plugin-lingui';
+import preferArrowPlugin from 'eslint-plugin-prefer-arrow';
+import prettierPlugin from 'eslint-plugin-prettier';
+import reactPlugin from 'eslint-plugin-react';
+import reactHooksPlugin from 'eslint-plugin-react-hooks';
+import reactRefreshPlugin from 'eslint-plugin-react-refresh';
+import unicornPlugin from 'eslint-plugin-unicorn';
+import unusedImportsPlugin from 'eslint-plugin-unused-imports';
+import jsoncParser from 'jsonc-eslint-parser';
+
+export default [
+  // Base JavaScript configuration
+  js.configs.recommended,
+
+  // Lingui recommended rules
+  linguiPlugin.configs['flat/recommended'],
+
+  // Base configuration for all files
+  {
+    files: ['**/*.{js,jsx,ts,tsx}'],
+    plugins: {
+      'react': reactPlugin,
+      'react-hooks': reactHooksPlugin,
+      'react-refresh': reactRefreshPlugin,
+      'prettier': prettierPlugin,
+      'lingui': linguiPlugin,
+      '@nx': nxPlugin,
+      'prefer-arrow': preferArrowPlugin,
+      'import': importPlugin,
+      'unused-imports': unusedImportsPlugin,
+      'unicorn': unicornPlugin,
+    },
+    settings: {
+      react: {
+        version: 'detect',
+      },
+    },
+    rules: {
+      // General rules
+      'func-style': ['error', 'declaration', { allowArrowFunctions: true }],
+      'no-console': ['warn', { allow: ['group', 'groupCollapsed', 'groupEnd'] }],
+      'no-control-regex': 0,
+      'no-debugger': 'error',
+      'no-duplicate-imports': 'error',
+      'no-undef': 'off',
+      'no-unused-vars': 'off',
+      'prettier/prettier': 'error',
+
+      // Nx rules
+      '@nx/enforce-module-boundaries': [
+        'error',
+        {
+          enforceBuildableLibDependency: true,
+          allow: [],
+          depConstraints: [
+            {
+              sourceTag: 'scope:shared',
+              onlyDependOnLibsWithTags: ['scope:shared'],
+            },
+            {
+              sourceTag: 'scope:backend',
+              onlyDependOnLibsWithTags: ['scope:shared', 'scope:backend'],
+            },
+            {
+              sourceTag: 'scope:frontend',
+              onlyDependOnLibsWithTags: ['scope:shared', 'scope:frontend'],
+            },
+            {
+              sourceTag: 'scope:zapier',
+              onlyDependOnLibsWithTags: ['scope:shared'],
+            },
+          ],
+        },
+      ],
+
+      // Import rules
+      'import/no-relative-packages': 'error',
+      'import/no-useless-path-segments': 'error',
+      'import/no-duplicates': ['error', { considerQueryString: true }],
+
+      // Prefer arrow functions
+      'prefer-arrow/prefer-arrow-functions': [
+        'error',
+        {
+          disallowPrototype: true,
+          singleReturnOnly: false,
+          classPropertiesAllowed: false,
+        },
+      ],
+
+      // Unused imports
+      'unused-imports/no-unused-imports': 'warn',
+      'unused-imports/no-unused-vars': [
+        'warn',
+        {
+          vars: 'all',
+          varsIgnorePattern: '^_',
+          args: 'after-used',
+          argsIgnorePattern: '^_',
+        },
+      ],
+
+      // React rules
+      'react/no-unescaped-entities': 'off',
+      'react/prop-types': 'off',
+      'react/jsx-key': 'off',
+      'react/display-name': 'off',
+      'react/jsx-uses-react': 'off',
+      'react/react-in-jsx-scope': 'off',
+      'react/jsx-no-useless-fragment': 'off',
+      'react/jsx-props-no-spreading': [
+        'error',
+        {
+          explicitSpread: 'ignore',
+        },
+      ],
+
+      // React hooks rules
+      'react-hooks/rules-of-hooks': 'error',
+      'react-hooks/exhaustive-deps': [
+        'warn',
+        {
+          additionalHooks: 'useRecoilCallback',
+        },
+      ],
+    },
+  },
+
+  // TypeScript specific configuration
+  {
+    files: ['**/*.{ts,tsx}'],
+    languageOptions: {
+      parser: typescriptParser,
+      parserOptions: {
+        ecmaFeatures: {
+          jsx: true,
+        },
+        // Note: project path should be specified by each package individually
+      },
+    },
+    plugins: {
+      '@typescript-eslint': typescriptEslint,
+    },
+    rules: {
+      // Import restrictions
+      'no-restricted-imports': [
+        'error',
+        {
+          patterns: [
+            {
+              group: ['@tabler/icons-react'],
+              message: 'Please import icons from `twenty-ui`',
+            },
+            {
+              group: ['react-hotkeys-web-hook'],
+              importNames: ['useHotkeys'],
+              message: 'Please use the custom wrapper: `useScopedHotkeys` from `twenty-ui`',
+            },
+            {
+              group: ['lodash'],
+              message: "Please use the standalone lodash package (for instance: `import groupBy from 'lodash.groupby'` instead of `import { groupBy } from 'lodash'`)",
+            },
+          ],
+        },
+      ],
+
+      // TypeScript rules
+      'no-redeclare': 'off', // Turn off base rule for TypeScript
+      '@typescript-eslint/no-redeclare': 'error', // Use TypeScript-aware version
+      '@typescript-eslint/ban-ts-comment': 'error',
+      '@typescript-eslint/consistent-type-imports': [
+        'error',
+        { 
+          prefer: 'type-imports',
+          fixStyle: 'inline-type-imports'
+        },
+      ],
+      '@typescript-eslint/explicit-function-return-type': 'off',
+      '@typescript-eslint/explicit-module-boundary-types': 'off',
+      '@typescript-eslint/interface-name-prefix': 'off',
+      '@typescript-eslint/no-empty-interface': [
+        'error',
+        {
+          allowSingleExtends: true,
+        },
+      ],
+      '@typescript-eslint/no-empty-function': 'off',
+      '@typescript-eslint/no-explicit-any': 'off',
+      '@typescript-eslint/no-unused-vars': 'off',
+
+      // Custom workspace rules
+      '@nx/workspace-effect-components': 'error',
+      '@nx/workspace-no-hardcoded-colors': 'error',
+      '@nx/workspace-matching-state-variable': 'error',
+      '@nx/workspace-sort-css-properties-alphabetically': 'error',
+      '@nx/workspace-styled-components-prefixed-with-styled': 'error',
+      '@nx/workspace-no-state-useref': 'error',
+      '@nx/workspace-component-props-naming': 'error',
+      '@nx/workspace-explicit-boolean-predicates-in-if': 'error',
+      '@nx/workspace-use-getLoadable-and-getValue-to-get-atoms': 'error',
+      '@nx/workspace-useRecoilCallback-has-dependency-array': 'error',
+      '@nx/workspace-no-navigate-prefer-link': 'error',
+    },
+  },
+
+  // Storybook files
+  {
+    files: ['*.stories.@(ts|tsx|js|jsx)'],
+    rules: {
+      '@typescript-eslint/no-non-null-assertion': 'off',
+    },
+  },
+
+  // JavaScript specific configuration
+  {
+    files: ['*.{js,jsx}'],
+    rules: {
+      // JavaScript-specific rules if needed
+    },
+  },
+
+  // Constants files
+  {
+    files: ['**/constants/*.ts', '**/*.constants.ts'],
+    rules: {
+      '@typescript-eslint/naming-convention': [
+        'error',
+        {
+          selector: 'variable',
+          format: ['UPPER_CASE'],
+        },
+      ],
+      'unicorn/filename-case': [
+        'warn',
+        {
+          cases: {
+            pascalCase: true,
+          },
+        },
+      ],
+      '@nx/workspace-max-consts-per-file': ['error', { max: 1 }],
+    },
+  },
+
+  // Test files
+  {
+    files: [
+      '*.test.@(ts|tsx|js|jsx)',
+    ],
+    languageOptions: {
+      globals: {
+        jest: true,
+        describe: true,
+        it: true,
+        expect: true,
+        beforeEach: true,
+        afterEach: true,
+        beforeAll: true,
+        afterAll: true,
+      },
+    },
+    rules: {
+      '@typescript-eslint/no-non-null-assertion': 'off',
+    },
+  },
+
+  // Constants files
+  {
+    files: ['**/*.constants.ts'],
+    rules: {
+      '@typescript-eslint/naming-convention': [
+        'error',
+        {
+          selector: 'variable',
+          format: ['UPPER_CASE'],
+        },
+      ],
+      'unicorn/filename-case': [
+        'warn',
+        {
+          cases: {
+            pascalCase: true,
+          },
+        },
+      ],
+      '@nx/workspace-max-consts-per-file': ['error', { max: 1 }],
+    },
+  },
+
+  // JSON files
+  {
+    files: ['**/*.json'],
+    languageOptions: {
+      parser: jsoncParser,
+    },
+  },
+];

jest.config.mjs

@@ -0,0 +1,5 @@
+import { getJestProjects } from '@nx/jest';
+
+export default {
+  projects: getJestProjects(),
+};

jest.preset.js

@@ -1,9 +1,3 @@
 const nxPreset = require('@nx/jest/preset').default;
 
-module.exports = {
-  ...nxPreset,
-  // Override the new testEnvironmentOptions added in @nx/jest 22.3.3
-  // which breaks Lingui's module resolution
-  testEnvironmentOptions: {},
-};
-
+module.exports = { ...nxPreset };

nx

@@ -0,0 +1,5 @@
+#!/bin/bash
+command -v node >/dev/null 2>&1 || { echo >&2 "Nx requires NodeJS to be available. To install NodeJS and NPM, see: https://nodejs.org/en/download/ ."; exit 1; }
+command -v npm >/dev/null 2>&1 || { echo >&2 "Nx requires npm to be available. To install NodeJS and NPM, see: https://nodejs.org/en/download/ ."; exit 1; }
+path_to_root=$(dirname $BASH_SOURCE)
+node $path_to_root/.nx/nxw.js $@