@crossdelta/platform-sdk 0.7.5 → 0.7.7

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

@@ -206,7 +206,8 @@ Bun.serve({ port, fetch: app.fetch })
 - ✅ Use `handleEvent()` for each event type
 - ❌ Usually NO REST endpoints (except /health)
 
-**Example index.ts:**
+**⚠️ CRITICAL: Event Consumer index.ts Template - COPY THIS EXACTLY:**
+
 ```ts
 import '@crossdelta/telemetry'
 
@@ -234,12 +235,19 @@ consumeJetStreamEvents({
 })
 ```
 
-**CRITICAL:** 
-- MUST call `ensureJetStreamStream()` BEFORE `consumeJetStreamEvents()` 
-- MUST use top-level await (Bun supports this)
-- `ensureJetStreamStream()` uses `subjects` parameter (stream-level: what goes INTO the stream)
-- `consumeJetStreamEvents()` uses `filterSubjects` parameter (consumer-level: what THIS consumer reads)
-- Do NOT confuse `subjects` (stream) with `filterSubjects` (consumer)
+**⚠️ MANDATORY CHECKLIST - Event Consumer index.ts MUST INCLUDE:**
+- [ ] `import { consumeJetStreamEvents, ensureJetStreamStream } from '@crossdelta/cloudevents'`
+- [ ] `await ensureJetStreamStream({ stream: 'ORDERS', subjects: ['orders.>'] })`
+- [ ] `consumeJetStreamEvents({ stream: 'ORDERS', consumer: 'service-name', discover: './src/events/**/*.event.ts' })`
+- [ ] Top-level await (Bun supports this natively)
+- [ ] `ensureJetStreamStream()` called BEFORE `consumeJetStreamEvents()`
+
+**CRITICAL ERRORS TO AVOID:**
+- ❌ Missing `ensureJetStreamStream()` → Stream won't exist, events won't be consumed
+- ❌ Missing `consumeJetStreamEvents()` → Service won't listen to events
+- ❌ Wrong import order → Telemetry must be first
+- ❌ Using `filterSubjects` in `ensureJetStreamStream()` → Use `subjects` parameter
+- ❌ Using `subjects` in `consumeJetStreamEvents()` → Use `filterSubjects` parameter if needed
 
 ### � HTTP CloudEvent Receiver (Receives CloudEvents via HTTP POST)
 

package/bin/templates/workspace/.github/copilot-instructions.md.hbs

@@ -54,3 +54,18 @@ Always generate **minimal diffs**, never full rewrites.
 - Use relative paths.
 - Keep comments minimal.
 - Do not generate abstractions not already present.
+
+## Service-Specific Guidelines
+
+When working with specific service types or packages, refer to these detailed guidelines:
+
+### Service Generation & Architecture
+- [Service Architecture Guidelines](../docs/generators/services/architecture-guidelines.md) - General patterns for all services
+- [Hono Microservice Guidelines](../docs/generators/services/hono-micro-guidelines.md) - Event-driven Hono patterns
+
+### Key Packages
+- [@crossdelta/cloudevents](../packages/cloudevents/README.md) - Event handling with NATS and CloudEvents
+- [@crossdelta/telemetry](../packages/telemetry/README.md) - OpenTelemetry instrumentation
+- [@crossdelta/infrastructure](../packages/infrastructure/README.md) - Pulumi/K8s configuration
+
+**When generating services**: Always check the appropriate guidelines above to ensure correct patterns, especially for event-driven architectures.

package/bin/templates/workspace/packages/contracts/src/index.ts

@@ -1,8 +1 @@
 // Export your event contracts and schemas here
-// Example:
-// export * from './events/order-created.schema'
-// export * from './events/order-created.contract'
-
-export * from './events/order-created'
-export * from './events/user-updated'
-export * from './events/order'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crossdelta/platform-sdk",
-  "version": "0.7.5",
+  "version": "0.7.7",
   "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",