@contractspec/example.crm-pipeline 1.48.0 → 1.48.1

package/.turbo/turbo-build$colon$bundle.log

@@ -15,10 +15,10 @@ $ tsdown
 ℹ dist/index.js                                        4.75 kB │ gzip: 1.15 kB
 ℹ dist/handlers/mock-data.js                           4.50 kB │ gzip: 1.09 kB
 ℹ dist/ui/renderers/pipeline.markdown.js               4.48 kB │ gzip: 1.34 kB
+ℹ dist/docs/crm-pipeline.docblock.js                   4.36 kB │ gzip: 1.75 kB
 ℹ dist/ui/CrmPipelineBoard.js                          3.88 kB │ gzip: 1.39 kB
 ℹ dist/events/deal.event.js                            3.77 kB │ gzip: 0.67 kB
 ℹ dist/handlers/deal.handlers.js                       3.73 kB │ gzip: 1.06 kB
-ℹ dist/docs/crm-pipeline.docblock.js                   3.60 kB │ gzip: 1.44 kB
 ℹ dist/entities/deal.entity.js                         3.56 kB │ gzip: 1.05 kB
 ℹ dist/ui/hooks/useDealMutations.js                    3.49 kB │ gzip: 0.80 kB
 ℹ dist/entities/task.entity.js                         3.41 kB │ gzip: 0.98 kB
@@ -44,7 +44,6 @@ $ tsdown
 ℹ dist/deal/deal.enum.js                               0.44 kB │ gzip: 0.24 kB
 ℹ dist/presentations/index.js                          0.40 kB │ gzip: 0.15 kB
 ℹ dist/events/index.js                                 0.32 kB │ gzip: 0.14 kB
-src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning: Could not resolve '@contractspec/example.crm-pipeline/handlers' in src/ui/renderers/pipeline.markdown.ts
 ℹ dist/ui/renderers/index.js                           0.26 kB │ gzip: 0.12 kB
 ℹ dist/ui/hooks/index.js                               0.16 kB │ gzip: 0.10 kB
 ℹ dist/ui/modals/index.js                              0.16 kB │ gzip: 0.09 kB
@@ -53,32 +52,23 @@ src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning:[
 ℹ dist/shared/overlay-types.js                         0.00 kB │ gzip: 0.02 kB
 ℹ dist/ui/modals/DealActionsModal.js.map              17.99 kB │ gzip: 4.12 kB
 ℹ dist/handlers/crm.handlers.js.map                   13.46 kB │ gzip: 3.36 kB
-    ╭─[ src/ui/renderers/pipeline.markdown.ts:10:8 ]
-    │
 ℹ dist/ui/CrmDashboard.js.map                         13.33 kB │ gzip: 3.99 kB
 ℹ dist/ui/modals/CreateDealModal.js.map                9.71 kB │ gzip: 3.02 kB
 ℹ dist/deal/deal.operation.js.map                      9.58 kB │ gzip: 2.06 kB
- 10 │ } from '@contractspec/example.crm-pipeline/handlers';
 ℹ dist/deal/deal.schema.js.map                         8.70 kB │ gzip: 1.25 kB
-    │        ──────────────────────┬──────────────────────  
 ℹ dist/ui/renderers/pipeline.markdown.js.map           8.68 kB │ gzip: 2.47 kB
 ℹ dist/handlers/deal.handlers.js.map                   7.82 kB │ gzip: 2.05 kB
 ℹ dist/handlers/mock-data.js.map                       7.43 kB │ gzip: 1.54 kB
-    │                              ╰──────────────────────── Module not found, treating it as an external dependency
-    │ 
 ℹ dist/ui/CrmPipelineBoard.js.map                      6.91 kB │ gzip: 2.34 kB
-    │ Help: The "main" field here was ignored. Main fields must be configured explicitly when using the "neutral" platform.
 ℹ dist/ui/hooks/useDealMutations.js.map                6.85 kB │ gzip: 1.65 kB
 ℹ dist/entities/deal.entity.js.map                     6.68 kB │ gzip: 1.76 kB
 ℹ dist/entities/task.entity.js.map                     6.10 kB │ gzip: 1.56 kB
 ℹ dist/events/deal.event.js.map                        5.88 kB │ gzip: 1.02 kB
+ℹ dist/docs/crm-pipeline.docblock.js.map               5.26 kB │ gzip: 1.97 kB
 ℹ dist/ui/hooks/useDealList.js.map                     4.93 kB │ gzip: 1.83 kB
 ℹ dist/presentations/pipeline.presentation.js.map      4.69 kB │ gzip: 1.22 kB
-ℹ dist/docs/crm-pipeline.docblock.js.map               4.46 kB │ gzip: 1.65 kB
 ℹ dist/crm-pipeline.feature.js.map                     4.43 kB │ gzip: 1.20 kB
-────╯
 ℹ dist/entities/contact.entity.js.map                  4.32 kB │ gzip: 1.37 kB
-
 ℹ dist/entities/company.entity.js.map                  3.58 kB │ gzip: 1.17 kB
 ℹ dist/ui/CrmDealCard.js.map                           3.37 kB │ gzip: 1.49 kB
 ℹ dist/presentations/dashboard.presentation.js.map     2.40 kB │ gzip: 0.86 kB
@@ -168,5 +158,15 @@ src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning:[
 ℹ dist/ui/overlays/index.d.ts                          0.14 kB │ gzip: 0.09 kB
 ℹ dist/docs/crm-pipeline.docblock.d.ts                 0.01 kB │ gzip: 0.03 kB
 ℹ dist/docs/index.d.ts                                 0.01 kB │ gzip: 0.03 kB
-ℹ 152 files, total: 371.73 kB
-✔ Build complete in 31915ms
+ℹ 152 files, total: 373.29 kB
+src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning: Could not resolve '@contractspec/example.crm-pipeline/handlers' in src/ui/renderers/pipeline.markdown.ts
+    ╭─[ src/ui/renderers/pipeline.markdown.ts:10:8 ]
+    │
+ 10 │ } from '@contractspec/example.crm-pipeline/handlers';
+    │        ──────────────────────┬──────────────────────  
+    │                              ╰──────────────────────── Module not found, treating it as an external dependency
+    │ 
+    │ Help: The "main" field here was ignored. Main fields must be configured explicitly when using the "neutral" platform.
+────╯
+
+✔ Build complete in 31714ms

package/.turbo/turbo-build.log

@@ -16,10 +16,10 @@ $ tsdown
 ℹ dist/index.js                                        4.75 kB │ gzip: 1.15 kB
 ℹ dist/handlers/mock-data.js                           4.50 kB │ gzip: 1.09 kB
 ℹ dist/ui/renderers/pipeline.markdown.js               4.48 kB │ gzip: 1.34 kB
+ℹ dist/docs/crm-pipeline.docblock.js                   4.36 kB │ gzip: 1.75 kB
 ℹ dist/ui/CrmPipelineBoard.js                          3.88 kB │ gzip: 1.39 kB
 ℹ dist/events/deal.event.js                            3.77 kB │ gzip: 0.67 kB
 ℹ dist/handlers/deal.handlers.js                       3.73 kB │ gzip: 1.06 kB
-ℹ dist/docs/crm-pipeline.docblock.js                   3.60 kB │ gzip: 1.44 kB
 ℹ dist/entities/deal.entity.js                         3.56 kB │ gzip: 1.05 kB
 ℹ dist/ui/hooks/useDealMutations.js                    3.49 kB │ gzip: 0.80 kB
 ℹ dist/entities/task.entity.js                         3.41 kB │ gzip: 0.98 kB
@@ -65,9 +65,9 @@ $ tsdown
 ℹ dist/entities/deal.entity.js.map                     6.68 kB │ gzip: 1.76 kB
 ℹ dist/entities/task.entity.js.map                     6.10 kB │ gzip: 1.56 kB
 ℹ dist/events/deal.event.js.map                        5.88 kB │ gzip: 1.02 kB
+ℹ dist/docs/crm-pipeline.docblock.js.map               5.26 kB │ gzip: 1.97 kB
 ℹ dist/ui/hooks/useDealList.js.map                     4.93 kB │ gzip: 1.83 kB
 ℹ dist/presentations/pipeline.presentation.js.map      4.69 kB │ gzip: 1.22 kB
-ℹ dist/docs/crm-pipeline.docblock.js.map               4.46 kB │ gzip: 1.65 kB
 ℹ dist/crm-pipeline.feature.js.map                     4.43 kB │ gzip: 1.20 kB
 ℹ dist/entities/contact.entity.js.map                  4.32 kB │ gzip: 1.37 kB
 ℹ dist/entities/company.entity.js.map                  3.58 kB │ gzip: 1.17 kB
@@ -97,7 +97,7 @@ $ tsdown
 ℹ dist/entities/task.entity.d.ts.map                   0.43 kB │ gzip: 0.26 kB
 ℹ dist/handlers/mock-data.d.ts.map                     0.42 kB │ gzip: 0.26 kB
 ℹ dist/ui/hooks/useDealList.d.ts.map                   0.34 kB │ gzip: 0.22 kB
-ℹ dist/presentations/pipeline.presentation.d.ts.map    0.31 kB │ gzip: 0.19 kB
+ℹ dist/presentations/pipeline.presentation.d.ts.map    0.31 kB │ gzip: 0.20 kB
 ℹ dist/ui/CrmDealCard.d.ts.map                         0.31 kB │ gzip: 0.21 kB
 ℹ dist/entities/contact.entity.d.ts.map                0.27 kB │ gzip: 0.19 kB
 ℹ dist/entities/company.entity.d.ts.map                0.26 kB │ gzip: 0.19 kB
@@ -115,11 +115,11 @@ $ tsdown
 ℹ dist/seeders/index.d.ts.map                          0.16 kB │ gzip: 0.14 kB
 ℹ dist/entities/index.d.ts.map                         0.15 kB │ gzip: 0.13 kB
 ℹ dist/example.d.ts.map                                0.14 kB │ gzip: 0.13 kB
-ℹ dist/deal/deal.operation.d.ts                       14.27 kB │ gzip: 0.97 kB
-ℹ dist/deal/deal.schema.d.ts                           8.12 kB │ gzip: 0.84 kB
+ℹ dist/deal/deal.operation.d.ts                       14.01 kB │ gzip: 0.97 kB
+ℹ dist/deal/deal.schema.d.ts                           8.27 kB │ gzip: 0.84 kB
 ℹ dist/index.d.ts                                      4.79 kB │ gzip: 1.16 kB
-ℹ dist/entities/deal.entity.d.ts                       3.54 kB │ gzip: 0.55 kB
-ℹ dist/events/deal.event.d.ts                          3.28 kB │ gzip: 0.43 kB
+ℹ dist/entities/deal.entity.d.ts                       3.54 kB │ gzip: 0.56 kB
+ℹ dist/events/deal.event.d.ts                          3.31 kB │ gzip: 0.43 kB
 ℹ dist/entities/task.entity.d.ts                       2.99 kB │ gzip: 0.51 kB
 ℹ dist/handlers/deal.handlers.d.ts                     2.40 kB │ gzip: 0.69 kB
 ℹ dist/handlers/crm.handlers.d.ts                      2.18 kB │ gzip: 0.69 kB
@@ -131,7 +131,7 @@ $ tsdown
 ℹ dist/shared/overlay-types.d.ts                       1.00 kB │ gzip: 0.40 kB
 ℹ dist/ui/hooks/useDealList.d.ts                       0.98 kB │ gzip: 0.47 kB
 ℹ dist/ui/hooks/useDealMutations.d.ts                  0.96 kB │ gzip: 0.38 kB
-ℹ dist/events/contact.event.d.ts                       0.93 kB │ gzip: 0.31 kB
+ℹ dist/events/contact.event.d.ts                       0.94 kB │ gzip: 0.31 kB
 ℹ dist/events/task.event.d.ts                          0.93 kB │ gzip: 0.30 kB
 ℹ dist/handlers/index.d.ts                             0.91 kB │ gzip: 0.28 kB
 ℹ dist/entities/index.d.ts                             0.85 kB │ gzip: 0.32 kB
@@ -159,7 +159,7 @@ $ tsdown
 ℹ dist/ui/overlays/index.d.ts                          0.14 kB │ gzip: 0.09 kB
 ℹ dist/docs/crm-pipeline.docblock.d.ts                 0.01 kB │ gzip: 0.03 kB
 ℹ dist/docs/index.d.ts                                 0.01 kB │ gzip: 0.03 kB
-ℹ 152 files, total: 371.70 kB
+ℹ 152 files, total: 373.19 kB
 src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning: Could not resolve '@contractspec/example.crm-pipeline/handlers' in src/ui/renderers/pipeline.markdown.ts
     ╭─[ src/ui/renderers/pipeline.markdown.ts:10:8 ]
     │
@@ -170,4 +170,4 @@ src/ui/renderers/pipeline.markdown.ts (10:7) [UNRESOLVED_IMPORT] Warning:[
     │ Help: The "main" field here was ignored. Main fields must be configured explicitly when using the "neutral" platform.
 ────╯
 
-✔ Build complete in 35255ms
+✔ Build complete in 31791ms

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @contractspec/example.crm-pipeline
 
+## 1.48.1
+
+### Patch Changes
+
+- Updated dependencies [c560ee7]
+- Updated dependencies [1536bf3]
+  - @contractspec/lib.design-system@1.48.1
+  - @contractspec/lib.contracts@1.48.1
+  - @contractspec/lib.example-shared-ui@1.2.1
+  - @contractspec/lib.identity-rbac@1.48.1
+  - @contractspec/module.audit-trail@1.48.1
+  - @contractspec/module.notifications@1.48.1
+
 ## 1.48.0
 
 ### Minor Changes

package/README.md

@@ -2,7 +2,6 @@
 
 Website: https://contractspec.io/
 
-
 A complete CRM (Customer Relationship Management) application demonstrating ContractSpec principles.
 
 ## What's Included
@@ -116,14 +115,14 @@ const StageEntity = defineEntity({
 
 ## Events
 
-| Event | Description |
-|-------|-------------|
-| contact.created | New contact added |
-| deal.created | New deal created |
-| deal.moved | Deal moved to new stage |
-| deal.won | Deal marked as won |
-| deal.lost | Deal marked as lost |
-| task.completed | Task marked complete |
+| Event           | Description             |
+| --------------- | ----------------------- |
+| contact.created | New contact added       |
+| deal.created    | New deal created        |
+| deal.moved      | Deal moved to new stage |
+| deal.won        | Deal marked as won      |
+| deal.lost       | Deal marked as lost     |
+| task.completed  | Task marked complete    |
 
 ## Usage
 
@@ -137,3 +136,24 @@ This example is registered as `crm-pipeline` in the ContractSpec Studio.
 npx degit lssm/contractspec/packages/examples/crm-pipeline my-crm-app
 ```
 
+## Adoption narrative
+
+### Before
+
+- A CRM app with hand-written data models and handler logic.
+- Pipeline stage rules live in code and drift across UI/API/events.
+- Regeneration is risky because specs and implementations are not aligned.
+
+### After
+
+- Contracts define deals, stages, and tasks as the source of truth.
+- Regeneration keeps UI/API/events in sync when stages change.
+- Compliance surfaces (audits, notifications) stay consistent with specs.
+
+### Minimal adoption steps
+
+1. Add ContractSpec CLI and core libraries.
+2. Define one operation (for example, `deal/create`).
+3. Run `contractspec build` to generate handlers and types.
+4. Wire the generated handler into your existing router.
+5. Expand to events and presentations as you add surface areas.

package/dist/docs/crm-pipeline.docblock.js

@@ -42,7 +42,27 @@ registerDocBlocks([
 ## Guardrails
 - Emit events for stage moves and task completions; log to Audit Trail.
 - Keep required fields enforced in contracts; avoid freeform state.
-- Redact contact PII in markdown/JSON outputs.`
+- Redact contact PII in markdown/JSON outputs.
+
+## Adoption narrative
+
+### Before
+- A CRM app with hand-written data models and handler logic.
+- Pipeline stage rules live in code and drift across UI/API/events.
+- Regeneration is risky because specs and implementations are not aligned.
+
+### After
+- Contracts define deals, stages, and tasks as the source of truth.
+- Regeneration keeps UI/API/events in sync when stages change.
+- Compliance surfaces (audits, notifications) stay consistent with specs.
+
+### Minimal adoption steps
+1) Add ContractSpec CLI and core libraries.
+2) Define one operation (for example, deal/create).
+3) Run contractspec build to generate handlers and types.
+4) Wire the generated handler into your existing router.
+5) Expand to events and presentations as you add surface areas.
+`
 	},
 	{
 		id: "docs.examples.crm-pipeline.reference",

package/dist/docs/crm-pipeline.docblock.js.map

@@ -1 +1 @@
-{"version":3,"file":"crm-pipeline.docblock.js","names":[],"sources":["../../src/docs/crm-pipeline.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@contractspec/lib.contracts/docs';\nimport { registerDocBlocks } from '@contractspec/lib.contracts/docs';\n\nconst crmPipelineDocBlocks: DocBlock[] = [\n  {\n    id: 'docs.examples.crm-pipeline.goal',\n    title: 'CRM Pipeline — Goal',\n    summary:\n      'Deals, stages, contacts, companies, and tasks with auditable stage movement.',\n    kind: 'goal',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline/goal',\n    tags: ['crm', 'goal'],\n    body: `## Why it matters\n- Regenerable CRM flow for deals/stages without code drift.\n- Ensures stage movement, tasks, and contacts stay aligned across surfaces.\n\n## Business/Product goal\n- Give sales teams a governed pipeline with auditable moves and notifications.\n- Allow experimentation (feature flags) on stage definitions and task flows.\n\n## Success criteria\n- Stage/state changes emit events and remain declarative in spec.\n- PII (contacts) is scoped/redacted in presentations.`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.usage',\n    title: 'CRM Pipeline — Usage',\n    summary: 'How to seed, extend, and regenerate the CRM pipeline.',\n    kind: 'usage',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline/usage',\n    tags: ['crm', 'usage'],\n    body: `## Setup\n1) Seed (if available) or create pipeline stages, deals, contacts, companies, tasks.\n2) Configure Notifications for stage changes/tasks; set policy.pii for contact data.\n\n## Extend & regenerate\n1) Adjust stage schema/order, deal fields, task fields in the spec.\n2) Regenerate to sync UI/API/events; ensure kanban/action buttons update.\n3) Use Feature Flags to trial new stages or SLA rules.\n\n## Guardrails\n- Emit events for stage moves and task completions; log to Audit Trail.\n- Keep required fields enforced in contracts; avoid freeform state.\n- Redact contact PII in markdown/JSON outputs.`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.reference',\n    title: 'CRM Pipeline — Reference',\n    summary:\n      'Entities, contracts, events, and presentations for the CRM template.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline',\n    tags: ['crm', 'reference'],\n    body: `## Entities\n- Contact, Company, Deal, Pipeline, Stage, Task.\n\n## Contracts\n- deal/create, stage/move, contact/company CRUD, task create/complete.\n\n## Events\n- deal.created, stage.moved, task.completed, contact.updated.\n\n## Presentations\n- Pipelines/kanban, deal detail, contact/company profiles, task lists.\n\n## Notes\n- Stage definitions should be declarative; enforce via spec and regeneration.\n- Use Notifications for deal/task updates; Audit Trail for state changes.`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.constraints',\n    title: 'CRM Pipeline — Constraints & Safety',\n    summary:\n      'Internal guardrails for stages, PII, and regeneration semantics in the CRM template.',\n    kind: 'reference',\n    visibility: 'internal',\n    route: '/docs/examples/crm-pipeline/constraints',\n    tags: ['crm', 'constraints', 'internal'],\n    body: `## Constraints\n- Stage definitions/order must remain declarative; no imperative overrides in code.\n- Events to emit: deal.created, stage.moved, task.completed, contact.updated (minimum).\n- Regeneration should not alter stage semantics without explicit spec change.\n\n## PII\n- Mark contact/company PII (emails, phones) for redaction in presentations.\n- Ensure MCP/web outputs avoid raw PII when not needed.\n\n## Verification\n- Add fixtures for stage move rules and SLA/task changes.\n- Ensure Audit/Notifications remain wired for stage and task events.\n- Use Feature Flags for experimental stages/SLAs; default safe/off.`,\n  },\n];\n\nregisterDocBlocks(crmPipelineDocBlocks);\n"],"mappings":";;;AAiGA,kBA9FyC;CACvC;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,OAAO;EACrB,MAAM;;;;;;;;;;;EAWP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SAAS;EACT,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,QAAQ;EACtB,MAAM;;;;;;;;;;;;;EAaP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,YAAY;EAC1B,MAAM;;;;;;;;;;;;;;;EAeP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAe;GAAW;EACxC,MAAM;;;;;;;;;;;;;EAaP;CACF,CAEsC"}
+{"version":3,"file":"crm-pipeline.docblock.js","names":[],"sources":["../../src/docs/crm-pipeline.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@contractspec/lib.contracts/docs';\nimport { registerDocBlocks } from '@contractspec/lib.contracts/docs';\n\nconst crmPipelineDocBlocks: DocBlock[] = [\n  {\n    id: 'docs.examples.crm-pipeline.goal',\n    title: 'CRM Pipeline — Goal',\n    summary:\n      'Deals, stages, contacts, companies, and tasks with auditable stage movement.',\n    kind: 'goal',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline/goal',\n    tags: ['crm', 'goal'],\n    body: `## Why it matters\n- Regenerable CRM flow for deals/stages without code drift.\n- Ensures stage movement, tasks, and contacts stay aligned across surfaces.\n\n## Business/Product goal\n- Give sales teams a governed pipeline with auditable moves and notifications.\n- Allow experimentation (feature flags) on stage definitions and task flows.\n\n## Success criteria\n- Stage/state changes emit events and remain declarative in spec.\n- PII (contacts) is scoped/redacted in presentations.`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.usage',\n    title: 'CRM Pipeline — Usage',\n    summary: 'How to seed, extend, and regenerate the CRM pipeline.',\n    kind: 'usage',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline/usage',\n    tags: ['crm', 'usage'],\n    body: `## Setup\n1) Seed (if available) or create pipeline stages, deals, contacts, companies, tasks.\n2) Configure Notifications for stage changes/tasks; set policy.pii for contact data.\n\n## Extend & regenerate\n1) Adjust stage schema/order, deal fields, task fields in the spec.\n2) Regenerate to sync UI/API/events; ensure kanban/action buttons update.\n3) Use Feature Flags to trial new stages or SLA rules.\n\n## Guardrails\n- Emit events for stage moves and task completions; log to Audit Trail.\n- Keep required fields enforced in contracts; avoid freeform state.\n- Redact contact PII in markdown/JSON outputs.\n\n## Adoption narrative\n\n### Before\n- A CRM app with hand-written data models and handler logic.\n- Pipeline stage rules live in code and drift across UI/API/events.\n- Regeneration is risky because specs and implementations are not aligned.\n\n### After\n- Contracts define deals, stages, and tasks as the source of truth.\n- Regeneration keeps UI/API/events in sync when stages change.\n- Compliance surfaces (audits, notifications) stay consistent with specs.\n\n### Minimal adoption steps\n1) Add ContractSpec CLI and core libraries.\n2) Define one operation (for example, deal/create).\n3) Run contractspec build to generate handlers and types.\n4) Wire the generated handler into your existing router.\n5) Expand to events and presentations as you add surface areas.\n`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.reference',\n    title: 'CRM Pipeline — Reference',\n    summary:\n      'Entities, contracts, events, and presentations for the CRM template.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/examples/crm-pipeline',\n    tags: ['crm', 'reference'],\n    body: `## Entities\n- Contact, Company, Deal, Pipeline, Stage, Task.\n\n## Contracts\n- deal/create, stage/move, contact/company CRUD, task create/complete.\n\n## Events\n- deal.created, stage.moved, task.completed, contact.updated.\n\n## Presentations\n- Pipelines/kanban, deal detail, contact/company profiles, task lists.\n\n## Notes\n- Stage definitions should be declarative; enforce via spec and regeneration.\n- Use Notifications for deal/task updates; Audit Trail for state changes.`,\n  },\n  {\n    id: 'docs.examples.crm-pipeline.constraints',\n    title: 'CRM Pipeline — Constraints & Safety',\n    summary:\n      'Internal guardrails for stages, PII, and regeneration semantics in the CRM template.',\n    kind: 'reference',\n    visibility: 'internal',\n    route: '/docs/examples/crm-pipeline/constraints',\n    tags: ['crm', 'constraints', 'internal'],\n    body: `## Constraints\n- Stage definitions/order must remain declarative; no imperative overrides in code.\n- Events to emit: deal.created, stage.moved, task.completed, contact.updated (minimum).\n- Regeneration should not alter stage semantics without explicit spec change.\n\n## PII\n- Mark contact/company PII (emails, phones) for redaction in presentations.\n- Ensure MCP/web outputs avoid raw PII when not needed.\n\n## Verification\n- Add fixtures for stage move rules and SLA/task changes.\n- Ensure Audit/Notifications remain wired for stage and task events.\n- Use Feature Flags for experimental stages/SLAs; default safe/off.`,\n  },\n];\n\nregisterDocBlocks(crmPipelineDocBlocks);\n"],"mappings":";;;AAqHA,kBAlHyC;CACvC;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,OAAO;EACrB,MAAM;;;;;;;;;;;EAWP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SAAS;EACT,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,QAAQ;EACtB,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAiCP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM,CAAC,OAAO,YAAY;EAC1B,MAAM;;;;;;;;;;;;;;;EAeP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAe;GAAW;EACxC,MAAM;;;;;;;;;;;;;EAaP;CACF,CAEsC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@contractspec/example.crm-pipeline",
-  "version": "1.48.0",
+  "version": "1.48.1",
   "description": "CRM Pipeline - Contacts, Companies, Deals, Tasks",
   "type": "module",
   "types": "./dist/index.d.ts",
@@ -62,18 +62,19 @@
     "lint": "bun lint:fix",
     "lint:fix": "eslint src --fix",
     "lint:check": "eslint src",
-    "test": "bun test"
+    "test": "bun test",
+    "validate": "contractspec validate"
   },
   "dependencies": {
-    "@contractspec/lib.contracts": "1.48.0",
-    "@contractspec/lib.design-system": "1.48.0",
-    "@contractspec/lib.example-shared-ui": "1.2.0",
-    "@contractspec/lib.identity-rbac": "1.48.0",
+    "@contractspec/lib.contracts": "1.48.1",
+    "@contractspec/lib.design-system": "1.48.1",
+    "@contractspec/lib.example-shared-ui": "1.2.1",
+    "@contractspec/lib.identity-rbac": "1.48.1",
     "@contractspec/lib.runtime-sandbox": "0.3.0",
     "@contractspec/lib.schema": "1.48.0",
     "@contractspec/lib.ui-kit-web": "1.48.0",
-    "@contractspec/module.audit-trail": "1.48.0",
-    "@contractspec/module.notifications": "1.48.0",
+    "@contractspec/module.audit-trail": "1.48.1",
+    "@contractspec/module.notifications": "1.48.1",
     "react": "19.2.3",
     "react-dom": "19.2.3"
   },

package/src/docs/crm-pipeline.docblock.ts

@@ -43,7 +43,27 @@ const crmPipelineDocBlocks: DocBlock[] = [
 ## Guardrails
 - Emit events for stage moves and task completions; log to Audit Trail.
 - Keep required fields enforced in contracts; avoid freeform state.
-- Redact contact PII in markdown/JSON outputs.`,
+- Redact contact PII in markdown/JSON outputs.
+
+## Adoption narrative
+
+### Before
+- A CRM app with hand-written data models and handler logic.
+- Pipeline stage rules live in code and drift across UI/API/events.
+- Regeneration is risky because specs and implementations are not aligned.
+
+### After
+- Contracts define deals, stages, and tasks as the source of truth.
+- Regeneration keeps UI/API/events in sync when stages change.
+- Compliance surfaces (audits, notifications) stay consistent with specs.
+
+### Minimal adoption steps
+1) Add ContractSpec CLI and core libraries.
+2) Define one operation (for example, deal/create).
+3) Run contractspec build to generate handlers and types.
+4) Wire the generated handler into your existing router.
+5) Expand to events and presentations as you add surface areas.
+`,
   },
   {
     id: 'docs.examples.crm-pipeline.reference',