@growthub/cli 0.3.53 → 0.3.55

package/assets/worker-kits/growthub-twenty-crm-v1/examples/crm-playbook-sample.md

@@ -0,0 +1,172 @@
+# CRM Playbook — Growthub (SAMPLE)
+
+**Date:** 2026-04-15  
+**Kit:** `growthub-twenty-crm-v1`  
+**Version:** v1
+
+> **Note:** This is a sample output. Adapt all procedures to the actual client context.
+
+---
+
+## ABOUT THIS PLAYBOOK
+
+This playbook is the operating manual for the Growthub Twenty CRM workspace. It defines roles, daily workflows, pipeline procedures, and data hygiene rules. All four team members with CRM access must read this before their first session.
+
+---
+
+## 1. TEAM ROLES AND PERMISSIONS
+
+| Role | Name | Access level | Responsibilities |
+|---|---|---|---|
+| CRM Admin | Antonio Romero | Full access | Object config, member management, integration maintenance, data hygiene |
+| Sales Rep | [Rep 1] | Create/edit own records | Lead creation, pipeline updates, notes |
+| Sales Rep | [Rep 2] | Create/edit own records | Lead creation, pipeline updates, notes |
+| CS Manager | [CS] | Read/edit post-close | Customer success tracking, renewal notes |
+
+**Onboarding new members:** CRM Admin creates the workspace member in Settings > Members, assigns the correct role, and shares this playbook.
+
+---
+
+## 2. DAILY WORKFLOW
+
+### Sales rep daily workflow (10–15 min)
+
+1. Log in to Twenty and open **Pipeline Board** view (pre-filtered: open opportunities, my records)
+2. Review new leads assigned to you in the LEAD stage — move any that are ICP-qualified to QUALIFIED
+3. For every call or email from today: add a Note on the Person record (what you discussed, next step, date)
+4. Check Tasks due today — complete each or reschedule with a Note explaining the delay
+5. End of day: every new contact from today's outreach must be in Twenty before logging off
+
+**Expected daily time investment:** 10–15 minutes
+
+### CRM Admin daily workflow (5–10 min)
+
+1. Check import error log if enrichment pipeline ran overnight
+2. Spot-check 3 records for data quality (no blank required fields, company linked, stage current)
+3. Check workflow logs (Settings > Workflows) for any automation failures
+
+---
+
+## 3. PIPELINE MANAGEMENT PROCEDURES
+
+### Creating a new Opportunity
+
+1. Navigate to Opportunities → click `+ New`
+2. Fill in: **Name** (e.g. "Acme Corp — Growthub Platform"), **Stage** (start at LEAD), **Amount**, **Close Date**
+3. Link **Point of Contact** (Person) and **Company**
+4. Set **Assignee** to yourself or the responsible rep
+5. Add a first Note: where did this lead come from, what is the hook?
+
+### Moving a stage
+
+1. Open the Opportunity → click the stage badge at the top
+2. Select the new stage
+3. Add a Note immediately explaining what happened and what the next step is
+4. If moving to **CLOSED_WON**: confirm Amount and Close Date are accurate before saving
+5. If moving to **CLOSED_LOST**: add a Note with the reason (e.g. "No budget Q2", "Chose competitor", "Ghosted after demo")
+
+**Pipeline stages and exit criteria:**
+
+| Stage | Exit criteria |
+|---|---|
+| LEAD | ICP fit confirmed + email opened or replied |
+| QUALIFIED | Discovery call complete, pain confirmed, budget range known |
+| DEMO | Product demo complete, specific use case validated |
+| PROPOSAL | Commercial terms sent or under negotiation |
+| CLOSED_WON | Contract signed, payment confirmed |
+| CLOSED_LOST | Explicitly lost or no response after 3 follow-ups past close date |
+
+### Weekly pipeline review (team — 30 min)
+
+**View:** Pipeline Board filtered to QUALIFIED + DEMO + PROPOSAL  
+**Sort:** Close Date ascending
+
+For each open opportunity in the top 10 by close date:
+- Is the stage accurate?
+- When was the last Note added? (if >7 days, flag as stale)
+- What is the next action and who owns it?
+- Is there a Task assigned for the next action?
+
+---
+
+## 4. ENRICHMENT CADENCE
+
+**Schedule:** Weekly on Monday at 6 AM (automated cron job)
+
+**What runs automatically:**
+- Apollo enrichment job pulls the latest saved search export and runs a merge import into Twenty
+- New Person records are created; existing records are updated with latest enrichment data
+
+**What to do if the enrichment job fails:**
+1. CRM Admin checks the error log file `enrichment-errors.csv` (stored in the enrichment job output)
+2. Review skipped records — most common reason is missing email
+3. Manually add missing contacts from Apollo if volume is small (< 20 records)
+4. Contact [developer] if the job fails to run at all (check cron logs)
+
+---
+
+## 5. REPORTING AND DASHBOARD INSTRUCTIONS
+
+### Pipeline health view (built in Twenty)
+
+**Filter:** Opportunities where stage IN [QUALIFIED, DEMO, PROPOSAL]  
+**Group by:** Stage  
+**Sort:** Close Date ascending
+
+**Reading the view:**
+- Count in each stage = pipeline coverage (healthy = more in LEAD/QUALIFIED than PROPOSAL)
+- Total amount in DEMO + PROPOSAL = near-term revenue signal
+- Opportunities with last Note > 14 days old = stale — review in weekly pipeline call
+
+### Weekly metrics to track (manual, 5 min)
+
+Count from Twenty each Friday:
+- New Opportunities created this week
+- Opportunities moved to CLOSED_WON this week
+- Opportunities moved to CLOSED_LOST this week + note the loss reasons
+- Opportunities moved to DEMO this week (pipeline velocity indicator)
+
+---
+
+## 6. ESCALATION AND HANDOFF PROTOCOLS
+
+### Record dispute (wrong data)
+
+1. Do **not** delete the record
+2. Add a Note: "Data quality issue — [describe problem]" and tag `@antonio`
+3. CRM Admin reviews and resolves within 2 business days
+
+### Integration failure
+
+1. Check Settings > Workflows for automation errors
+2. Check enrichment error log file
+3. If unresolved: email [developer contact] with the error message and timestamp
+4. CRM Admin documents the gap in a Note on the affected object if data is missing
+
+### Offboarding a team member
+
+1. CRM Admin reassigns all open Opportunities from the departing member to the remaining rep
+2. Reassigns all open Tasks
+3. Deactivates the workspace member (Settings > Members > Deactivate)
+4. Revokes any API tokens the member had access to
+
+---
+
+## 7. MAINTENANCE AND DATA HYGIENE CHECKLIST
+
+**Weekly (CRM Admin — 15 min):**
+- [ ] Review import error log — resolve skipped records
+- [ ] Check stale Opportunities (no update in 14 days) — flag for reps to update
+- [ ] Confirm all Closed Won / Closed Lost opportunities have a loss/win reason Note
+
+**Monthly (CRM Admin — 30 min):**
+- [ ] Search for duplicate Person records (same email) — merge duplicates
+- [ ] Search for Companies with no linked Persons — flag for review or archive
+- [ ] Review workflow logs for repeated failures — escalate to developer if pattern
+- [ ] Update this playbook if any procedures have changed
+
+**Quarterly (CRM Admin + head of sales — 60 min):**
+- [ ] Review pipeline stage definitions — do they still match how we sell?
+- [ ] Evaluate enrichment provider data quality — are enriched fields accurate?
+- [ ] Review custom field usage — archive any fields the team stopped using
+- [ ] Check if new automation opportunities exist based on team pain points

package/assets/worker-kits/growthub-twenty-crm-v1/examples/crm-setup-sample.md

@@ -0,0 +1,100 @@
+# CRM Setup Brief — Growthub (SAMPLE)
+
+**Date:** 2026-04-15  
+**Operator:** `twenty-crm-operator`  
+**Kit:** `growthub-twenty-crm-v1`  
+**Mode:** `cloud`
+
+> **Note:** This is a sample output illustrating the quality and format expected from this kit. Adapt all values to the actual client context.
+
+---
+
+## 1. CLIENT CONTEXT AND CRM OBJECTIVE
+
+**Client:** Growthub  
+**Industry:** B2B SaaS / Growth Platform  
+**Company size:** 12 employees  
+**CRM objective:** Build a structured outbound sales pipeline with automated lead enrichment from Apollo, Stripe event capture, and Intercom conversation logging.
+
+**Why Twenty:**
+- Open-source, MIT license — no vendor lock-in risk for a growing platform company
+- TypeScript/React/NestJS stack matches Growthub's existing codebase — easier to self-host and extend
+- REST and GraphQL APIs make it straightforward to build custom enrichment pipelines
+- Custom object support handles the non-standard Growthub product-led-growth workflow
+
+---
+
+## 2. DEPLOYMENT MODE
+
+**Selected mode:** `cloud`  
+**API URL:** `https://api.twenty.com`  
+**Environment:** production
+
+**Prerequisites confirmed:**
+- [x] Twenty workspace created at app.twenty.com
+- [x] API token generated: `growthub-production` token (stored in `.env`)
+- [x] `node setup/verify-env.mjs` exits 0 — connected to workspace "Growthub" (id: abc123)
+
+---
+
+## 3. TEAM SIZE AND USER ROLES
+
+| Role | User | Permissions |
+|---|---|---|
+| CRM Admin | Antonio Romero | Full access |
+| Sales Rep | [Sales Rep 1] | Create/edit Opportunities and Persons |
+| Sales Rep | [Sales Rep 2] | Create/edit Opportunities and Persons |
+| CS Manager | [CS Manager] | Read/edit Opportunities post-close |
+
+**Total workspace members:** 4
+
+---
+
+## 4. DATA SOURCES AND VOLUME ESTIMATES
+
+| Source | Object type | Estimated volume | Import method |
+|---|---|---|---|
+| Apollo CSV export | Person + Company | ~1,200 contacts, ~400 companies | CSV import |
+| Stripe | Company + Note | ~50 new customers/month | Webhook (customer.created) |
+| Intercom | Note | ~150 conversations/month | Webhook (conversation.created) |
+
+---
+
+## 5. INTEGRATION SCOPE
+
+| Integration | Direction | Priority |
+|---|---|---|
+| Apollo | Inbound enrichment | High |
+| Stripe | Inbound webhook | High |
+| Intercom | Inbound webhook | Medium |
+| Slack | Outbound notification (Closed Won) | Low |
+
+---
+
+## 6. GO-LIVE TIMELINE AND MILESTONES
+
+| Milestone | Target date | Owner |
+|---|---|---|
+| Data model finalized | 2026-04-18 | Antonio (CRM Admin) |
+| Initial Apollo import complete | 2026-04-20 | Antonio |
+| Stripe webhook live | 2026-04-22 | Developer |
+| Intercom webhook live | 2026-04-25 | Developer |
+| Stage automations active | 2026-04-25 | Developer |
+| Team onboarded | 2026-04-28 | Antonio |
+
+---
+
+## 7. SUCCESS CRITERIA
+
+- [x] All 1,200 contacts imported and deduplicated against email
+- [x] Pipeline visible with 6 stages (Lead → Closed Won/Lost)
+- [x] 3 automations active (stage change → task creation, Closed Won → Slack notify, Intercom → Note)
+- [x] Stripe enrichment running on customer.created event
+- [x] All 4 team members onboarded and logging daily activity in the CRM
+
+---
+
+## OPEN QUESTIONS
+
+- [ ] Does the head of sales want round-robin assignment or territory-based routing?
+- [ ] Should Intercom conversations be logged as Notes on Person or as a custom Activity object?

package/assets/worker-kits/growthub-twenty-crm-v1/examples/lead-enrichment-sample.md

@@ -0,0 +1,117 @@
+# Lead Enrichment Pipeline — Growthub (SAMPLE)
+
+**Date:** 2026-04-15  
+**Kit:** `growthub-twenty-crm-v1`  
+**Mode:** `cloud`
+
+> **Note:** This is a sample output. Adapt all values to the actual client context.
+
+---
+
+## 1. ENRICHMENT PROVIDER(S)
+
+| Provider | Auth mechanism | Data tier | Primary use |
+|---|---|---|---|
+| Apollo | Bearer token | Person + Company | Outbound lead source |
+| Clay | API key | Person + Company | Enrichment waterfall (email verification + firmographic) |
+
+---
+
+## 2. SOURCE FIELDS PROVIDED
+
+### Apollo — Person fields
+
+| Provider field | Data type | Example value |
+|---|---|---|
+| `first_name` | string | `Jane` |
+| `last_name` | string | `Doe` |
+| `email` | string | `jane@acme.com` |
+| `title` | string | `Head of Growth` |
+| `seniority` | string | `director` |
+| `linkedin_url` | string | `https://linkedin.com/in/janedoe` |
+| `city` | string | `San Francisco` |
+| `organization.name` | string | `Acme Corp` |
+| `organization.website_url` | string | `https://acme.com` |
+| `organization.estimated_num_employees` | integer | `250` |
+
+---
+
+## 3. DEDUPLICATION STRATEGY
+
+**Person dedup key:** `emails.primaryEmail`  
+**Company dedup key:** `domain`  
+**Secondary person key (when email unavailable):** `linkedInLink.url`
+
+**Dedup behavior:**
+- Match found → **merge** (update existing record with enriched fields, preserve existing data)
+- No match found → **insert** (create new record)
+- If both email and LinkedIn are absent → **skip and log** for manual review
+
+---
+
+## 4. IMPORT MODE
+
+**Selected mode:** `merge-with-insert-fallback`
+
+**Rationale:** Growthub has existing contacts from previous manual spreadsheet work. Merging ensures enrichment data layers on top without creating duplicates.
+
+---
+
+## 5. IMPORT METHOD
+
+**Method:** CSV import via Twenty UI (first batch), then GraphQL mutation batch (ongoing enrichment)
+
+**Import sequence:**
+1. Export Apollo contact list as CSV with all available fields selected
+2. Clean CSV: lowercase all emails, strip `https://` and trailing slashes from domain field
+3. Import Company records first (Settings > Companies > Import)
+4. Import Person records second with company linking enabled
+5. Run post-import audit
+
+**Batch size recommendation:** 500 records per batch
+
+---
+
+## 6. FIELD MAPPING (SUMMARY)
+
+| Source field | → | Twenty object | Twenty field | Transformation |
+|---|---|---|---|---|
+| `email` | → | `Person` | `emails.primaryEmail` | lowercase, trim |
+| `first_name` | → | `Person` | `name.firstName` | none |
+| `last_name` | → | `Person` | `name.lastName` | none |
+| `title` | → | `Person` | `position` | none |
+| `linkedin_url` | → | `Person` | `linkedInLink.url` | none |
+| `city` | → | `Person` | `city` | none |
+| `organization.name` | → | `Company` | `name` | none |
+| `organization.website_url` | → | `Company` | `domain` | strip `https://` and trailing `/` |
+| `organization.estimated_num_employees` | → | `Company` | `employees` | integer cast |
+
+---
+
+## 7. POST-IMPORT VALIDATION
+
+| Check | Expected result | Actual result |
+|---|---|---|
+| Total Person records imported | ~1,200 | [fill after import] |
+| Total Company records imported | ~400 | [fill after import] |
+| Duplicate email check | 0 duplicates | [fill after import] |
+| Company linkage rate | ≥ 90% | [fill after import] |
+| Skipped records (no email) | < 5% | [fill after import] |
+
+---
+
+## 8. ERROR AND FAILURE HANDLING
+
+| Error type | Behavior | Resolution |
+|---|---|---|
+| Invalid email format | Skip record, log to `enrichment-errors.csv` | Manual review and clean |
+| Duplicate email (post-dedup) | Merge into existing record | Review merged record for accuracy |
+| Missing company domain | Create Company with name only; flag for manual domain entry | Review flagged companies weekly |
+| API rate limit hit | Pause 30 seconds, retry with smaller batch | Reduce to 250 records/batch |
+
+---
+
+## 9. UPDATE FREQUENCY
+
+**Enrichment cadence:** Weekly on Monday mornings  
+**Trigger:** Apollo saves a new export on Sundays; enrichment job runs at 6 AM Monday via cron

package/assets/worker-kits/growthub-twenty-crm-v1/examples/pipeline-automation-sample.md

@@ -0,0 +1,132 @@
+# Pipeline Automation Brief — Growthub (SAMPLE)
+
+**Date:** 2026-04-15  
+**Kit:** `growthub-twenty-crm-v1`  
+**Mode:** `cloud`
+
+> **Note:** This is a sample output. Adapt all values to the actual client context.
+
+---
+
+## AUTOMATION INVENTORY
+
+| # | Automation name | Trigger | Action | Status |
+|---|---|---|---|---|
+| 1 | Lead Qualified — Assign Rep + Create Follow-Up Task | Stage changes to QUALIFIED | Assign owner, create Task | planned |
+| 2 | Demo Scheduled — Notify Slack | Stage changes to DEMO | Send outbound webhook to Slack | planned |
+| 3 | Closed Won — Create Customer Onboarding Task | Stage changes to CLOSED_WON | Create Task, update field | planned |
+
+---
+
+## AUTOMATION 1 — LEAD QUALIFIED: ASSIGN REP AND CREATE FOLLOW-UP TASK
+
+**Purpose:** When a lead's stage changes to QUALIFIED, assign the opportunity to the next available sales rep (round-robin, two reps) and create a follow-up task due in 24 hours.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | any (except QUALIFIED) |
+| New value | `QUALIFIED` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `assign_owner` | `Opportunity` | Round-robin between [Sales Rep 1 ID] and [Sales Rep 2 ID] |
+| 2 | `create_task` | `Person` (pointOfContact) | `title: "Follow up with [Person name]", dueAt: +24h, assignee: opportunity.assignee` |
+| 3 | `update_field` | `Opportunity` | `qualifiedAt: now()` (custom date field) |
+
+### Failure behavior
+
+**If step 1 fails (assignment):** Assign to CRM Admin as fallback  
+**If step 2 fails (task creation):** Retry once after 60 seconds; if still failing, send in-app notification to CRM Admin  
+**If step 3 fails (field update):** Log error; non-critical, do not halt
+
+### Monitoring
+
+Check the automation execution log in Twenty > Settings > Workflows weekly. Expected volume: 5–15 triggers per week.
+
+---
+
+## AUTOMATION 2 — DEMO SCHEDULED: NOTIFY SLACK
+
+**Purpose:** When a deal enters the DEMO stage, post a message to the #sales-pipeline Slack channel so the full team sees demo activity in real time.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | `QUALIFIED` |
+| New value | `DEMO` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `send_webhook` | Slack Incoming Webhook URL | See payload below |
+
+**Slack payload:**
+
+```json
+{
+  "text": "🎯 Demo stage reached: *{{opportunity.name}}* — assigned to {{opportunity.assignee.name}}. Close date: {{opportunity.closeDate}}",
+  "channel": "#sales-pipeline"
+}
+```
+
+### Failure behavior
+
+**If webhook fails:** Retry 3× (5s, 15s, 45s). If all retries fail: log error and send in-app notification to CRM Admin. Non-critical — pipeline is not blocked.
+
+---
+
+## AUTOMATION 3 — CLOSED WON: CREATE ONBOARDING TASK
+
+**Purpose:** When a deal is marked as CLOSED_WON, automatically create a customer onboarding task assigned to the CS Manager.
+
+### Trigger
+
+| Property | Value |
+|---|---|
+| Trigger type | `on_field_change` |
+| Target object | `Opportunity` |
+| Field | `stage` |
+| Previous value | any |
+| New value | `CLOSED_WON` |
+
+### Action sequence
+
+| Step | Action type | Target | Parameters |
+|---|---|---|---|
+| 1 | `create_task` | `Person` (pointOfContact) | `title: "Onboard [Person name] — [Company name]", dueAt: +3 days, assignee: [CS Manager ID]` |
+| 2 | `update_field` | `Opportunity` | `closedAt: now()` (custom date field) |
+| 3 | `send_webhook` | Slack Incoming Webhook | Post to #customer-success: "New customer: [Company name]" |
+
+### Failure behavior
+
+**If task creation fails:** Retry once; then send email notification to CS Manager directly  
+**If Slack webhook fails:** Retry 3×; if all fail, log — non-critical
+
+---
+
+## AUTOMATION DESIGN DECISIONS
+
+| Decision | Choice | Rationale |
+|---|---|---|
+| Assignment method | Round-robin (2 reps) | Equal load distribution; no territory segmentation needed at current team size |
+| Slack notification trigger | Stage change to DEMO (not QUALIFIED) | QUALIFIED happens frequently (5–15/week); only DEMO warrants team visibility |
+| Onboarding task assignee | CS Manager (fixed) | Single CS contact at current team size; revisit when team grows |
+
+---
+
+## OPEN QUESTIONS
+
+- [ ] Should the Closed Won Slack notification include the deal amount? (confirm with head of sales)
+- [ ] What is the round-robin assignment rule when one rep is on leave — assign to the other rep only, or default to CRM Admin?

package/assets/worker-kits/growthub-twenty-crm-v1/growthub-meta/README.md

@@ -0,0 +1,114 @@
+# Growthub Agent Worker Kit — Twenty CRM v1
+
+**Kit ID:** `growthub-twenty-crm-v1`  
+**Version:** `1.0.0`  
+**Type:** `worker`  
+**Execution mode:** `export`
+
+---
+
+## What this kit does
+
+This kit gives an agent a self-contained environment for implementing, configuring, and operating Twenty CRM — the open-source Salesforce/Apollo alternative — as a growth stack foundation.
+
+It packages:
+- agent operating instructions
+- a locked CRM methodology
+- runtime and deployment assumptions
+- API, webhook, and data model reference docs
+- CRM implementation templates (12 templates)
+- example output artifacts (4 complete samples)
+- brand kit system
+- output standards
+- setup scripts for local-fork and cloud modes
+- contributor metadata
+
+The intended operator is a growth engineer, CRM consultant, or AI agent responsible for implementing Twenty CRM for a B2B team and building enrichment pipelines, pipeline automations, and integration handoffs on top of it.
+
+---
+
+## Folder structure
+
+```text
+growthub-twenty-crm-v1/
+├── kit.json
+├── bundles/
+├── workers/
+│   └── twenty-crm-operator/
+│       └── CLAUDE.md
+├── brands/
+│   ├── _template/brand-kit.md
+│   ├── growthub/brand-kit.md
+│   └── NEW-CLIENT.md
+├── setup/
+│   ├── clone-fork.sh
+│   ├── verify-env.mjs
+│   └── check-deps.sh
+├── templates/
+│   ├── crm-setup-brief.md
+│   ├── data-model-design.md
+│   ├── lead-enrichment-pipeline.md
+│   ├── pipeline-automation-brief.md
+│   ├── webhook-integration-spec.md
+│   ├── api-query-plan.md
+│   ├── crm-playbook.md
+│   ├── custom-object-design.md
+│   ├── import-mapping.md
+│   ├── workspace-config-checklist.md
+│   ├── integration-handoff.md
+│   └── enrichment-field-map.md
+├── examples/
+│   ├── crm-setup-sample.md
+│   ├── lead-enrichment-sample.md
+│   ├── pipeline-automation-sample.md
+│   └── crm-playbook-sample.md
+├── docs/
+│   ├── twenty-fork-integration.md
+│   ├── api-and-webhooks.md
+│   └── data-model-layer.md
+├── output/
+│   └── README.md
+├── growthub-meta/
+│   ├── README.md
+│   └── kit-standard.md
+├── skills.md
+├── output-standards.md
+├── runtime-assumptions.md
+├── validation-checklist.md
+├── QUICKSTART.md
+└── .env.example
+```
+
+---
+
+## Activation
+
+1. Export the kit via `growthub kit download growthub-twenty-crm-v1`.
+2. Point the agent working directory at the expanded folder.
+3. The agent reads `workers/twenty-crm-operator/CLAUDE.md`.
+4. `skills.md` provides the working method for every session.
+
+---
+
+## Supported output categories
+
+- CRM setup brief
+- data model design
+- lead enrichment pipeline
+- pipeline automation brief
+- webhook integration spec
+- API query plan
+- custom object design
+- import mapping
+- workspace config checklist
+- integration handoff
+- enrichment field map
+- CRM playbook
+
+---
+
+## Source repository
+
+Twenty CRM: [github.com/twentyhq/twenty](https://github.com/twentyhq/twenty)  
+License: MIT  
+Stack: TypeScript / React / NestJS / PostgreSQL / Redis

package/assets/worker-kits/growthub-twenty-crm-v1/growthub-meta/kit-standard.md

@@ -0,0 +1,61 @@
+# Kit Standard — Twenty CRM v1
+
+This document defines the locked contract for this kit.
+
+---
+
+## Required files contract
+
+Every path in `kit.json -> frozenAssetPaths` must exist in every valid release.
+
+---
+
+## Bundle contract
+
+The bundle manifest must remain aligned with `kit.json`:
+- `bundle.kitId` matches `kit.id`
+- `bundle.workerId` matches `entrypoint.workerId`
+- `requiredFrozenAssets` stays a subset of `frozenAssetPaths`
+
+---
+
+## Agent operating rules
+
+The entrypoint file is the operating law. `skills.md` is the methodology.
+
+Required invariants:
+- strict workflow order (Steps 0–10)
+- environment gate passes before any planning work
+- data model is defined before automation or enrichment pipelines
+- deployment mode is always labeled in every output
+- deduplication key is named in every enrichment or import artifact
+- every automation trigger-action pair has a documented failure path
+- no secrets are stored in any kit file or output artifact
+- outputs are operational artifacts, not ideation-only text
+
+---
+
+## Runtime rules
+
+- no secrets stored in kit files
+- agent-only mode is always a valid fallback — no live CRM required for planning work
+- cloud, self-hosted, and local-fork modes are all first-class
+- outputs are Markdown only
+- field names use Twenty's naming conventions (camelCase for fields, PascalCase for objects)
+- SELECT option values use SCREAMING_SNAKE_CASE
+
+---
+
+## Versioning rules
+
+Additive template/docs changes are minor-version work. Entrypoint path changes, export name changes, or fundamental workflow changes require a major version bump.
+
+---
+
+## Scope rules
+
+This kit is scoped to Twenty CRM implementation planning and operator documentation. It does not:
+- provide a live CRM dashboard
+- write application code (it produces specs and handoffs for developers)
+- manage infrastructure directly
+- store client data in kit files