@crossdelta/platform-sdk 0.7.8 → 0.7.9

package/README.md

@@ -167,12 +167,8 @@ my-platform/
 │   └── nats/         # NATS message broker (auto-scaffolded)
 ├── apps/             # Frontend apps (optional: Qwik, Next.js, etc.)
 ├── packages/         # Shared libraries
-│   ├── contracts/    # Event contracts (Schema Registry)
+│   ├── contracts/    # Event contracts (Schema Registry - created when generating Event Consumers)
 │   │   └── src/
-│   │       ├── events/        # Event schemas with Zod validation
-│   │       │   ├── order-created.ts
-│   │       │   ├── order-created.mock.json
-│   │       │   └── payment-processed.ts
 │   │       └── index.ts       # Export all contracts
 │   ├── cloudevents/  # Event publishing/consuming toolkit
 │   ├── telemetry/    # OpenTelemetry setup
@@ -188,6 +184,8 @@ my-platform/
 └── .env.local        # Auto-generated from infra configs
 ```
 
+> **Note:** The `packages/contracts` package starts with just an `index.ts`. Event contract files (e.g., `events/order-created.ts`) are automatically generated when you create **Event Consumer** services with `pf new hono-micro --ai`.
+
 ### Key Architectural Decisions
 
 1. **NATS + JetStream baseline** — Event-driven communication is built-in, not bolted on
@@ -200,7 +198,7 @@ my-platform/
 
 ### Event-Driven Mental Model
 
-Services communicate via **CloudEvents** over **NATS JetStream** with **type-safe contracts**:
+Services communicate via **CloudEvents** over **NATS JetStream** using the **Schema Registry** as single source of truth:
 
 ```typescript
 // packages/contracts/src/events/order-created.ts (Schema Registry)
@@ -222,20 +220,20 @@ export type OrderCreatedData = z.infer<typeof OrderCreatedContract.schema>
 import { publish } from '@crossdelta/cloudevents'
 import { OrderCreatedContract } from '@my-platform/contracts'
 
-await publish(OrderCreatedContract, { 
-  orderId: '123', 
+await publish(OrderCreatedContract, {
+  orderId: '123',
   customerId: 'cust-456',
-  total: 99.99 
+  total: 99.99
 })
 
 // Service B auto-discovers and handles it (Event Consumer)
 // File: services/notifications/src/events/order-created.event.ts
 import { handleEvent } from '@crossdelta/cloudevents'
 import { OrderCreatedContract, type OrderCreatedData } from '@my-platform/contracts'
-export default handleEvent(
-  { schema: OrderCreatedSchema, type: 'orders.created' },
-  async (data) => { await sendNotification(data) }
-)
+
+export default handleEvent(OrderCreatedContract, async (data: OrderCreatedData) => {
+  await sendNotification(data)
+})
 ```
 
 No manual NATS subscriptions. No boilerplate. Just **convention over configuration**.

package/bin/services/ai/instructions/ai-instructions.md

@@ -697,7 +697,7 @@ Step 3: CREATE event handler that uses those fields:
   services/order-notifications/src/events/order-created.event.ts:
     import { OrderCreatedContract, type OrderCreatedData } from '@scope/contracts'
     export default handleEvent(OrderCreatedContract, async (data) => {
-      await sendNotification({ 
+      await sendNotification({
         orderId: data.orderId,       // ✅ Field exists in contract
         customerId: data.customerId, // ✅ Field exists in contract
         total: data.total,           // ✅ Field exists in contract
@@ -742,7 +742,7 @@ export const OrderCreatedContract = createContract({
     orderId: z.string(),
     customerId: z.string(),
     total: z.number(),
-    
+
     // OPTIONAL: Additional context fields
     items: z.array(z.object({
       productId: z.string(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossdelta/platform-sdk",
-  "version": "0.7.8",
+  "version": "0.7.9",
   "description": "Your AI-powered platform engineer. Scaffold complete Turborepo workspaces, generate microservice boilerplate with natural language, and deploy to the cloud — all from one CLI",
   "keywords": [
     "cli",