@principal-ai/principal-view-cli 0.4.2 → 0.4.4

package/dist/commands/formats.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"formats.d.ts","sourceRoot":"","sources":["../../src/commands/formats.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAufpC,wBAAgB,oBAAoB,IAAI,OAAO,CA6B9C"}
+{"version":3,"file":"formats.d.ts","sourceRoot":"","sources":["../../src/commands/formats.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AA8fpC,wBAAgB,oBAAoB,IAAI,OAAO,CA6B9C"}

package/dist/commands/formats.js

@@ -186,7 +186,14 @@ ${chalk.cyan('3. Template syntax (Handlebars):')}
    - eq, ne, lt, gt, lte, gte, and, or, not
    - Example: {{#if (gt count 10)}}Many{{/if}}
 
-${chalk.cyan('4. Template style:')}
+${chalk.cyan('4. Template requirements:')}
+   ${chalk.bold('IMPORTANT:')} The ${chalk.yellow('"events"')} field is ${chalk.bold('REQUIRED')} in all templates
+   - Must be a non-empty object mapping event names to templates
+   - All event names must exist in the canvas
+   - Use to customize how each event type is displayed
+   - Example: { "event.name": "Template with {{variables}}" }
+
+${chalk.cyan('5. Template style:')}
    - Clear, concise summary line
    - 3-5 detail steps showing workflow
    - Use emojis for visual scanning (✅ ❌ 📋)

package/dist/index.cjs

@@ -241935,6 +241935,40 @@ var NarrativeValidator = class {
     const violations = [];
     const validFields = ["introduction", "events", "logs", "flow", "summary", "span", "children"];
     const templateKeys = Object.keys(template);
+    if (!template.events) {
+      violations.push({
+        ruleId: "narrative-template-structure",
+        severity: "error",
+        file,
+        path: `scenarios[${scenarioIdx}].template`,
+        message: 'Template is missing required "events" field',
+        impact: "Template must specify how to render each event type",
+        suggestion: 'Add "events: { eventName: template }" to map event names to templates',
+        fixable: false
+      });
+    } else if (typeof template.events !== "object" || Array.isArray(template.events)) {
+      violations.push({
+        ruleId: "narrative-template-structure",
+        severity: "error",
+        file,
+        path: `scenarios[${scenarioIdx}].template.events`,
+        message: 'Template "events" field must be an object',
+        impact: "Events will not render correctly",
+        suggestion: 'Use object format: { "event.name": "template string" }',
+        fixable: false
+      });
+    } else if (Object.keys(template.events).length === 0) {
+      violations.push({
+        ruleId: "narrative-template-structure",
+        severity: "error",
+        file,
+        path: `scenarios[${scenarioIdx}].template.events`,
+        message: 'Template "events" field must not be empty',
+        impact: "No events will be rendered in this scenario",
+        suggestion: 'Add at least one event template: { "event.name": "template string" }',
+        fixable: false
+      });
+    }
     for (const key of templateKeys) {
       if (!validFields.includes(key)) {
         if (key === "steps") {
@@ -247777,7 +247811,14 @@ ${source_default.cyan("3. Template syntax (Handlebars):")}
    - eq, ne, lt, gt, lte, gte, and, or, not
    - Example: {{#if (gt count 10)}}Many{{/if}}
 
-${source_default.cyan("4. Template style:")}
+${source_default.cyan("4. Template requirements:")}
+   ${source_default.bold("IMPORTANT:")} The ${source_default.yellow('"events"')} field is ${source_default.bold("REQUIRED")} in all templates
+   - Must be a non-empty object mapping event names to templates
+   - All event names must exist in the canvas
+   - Use to customize how each event type is displayed
+   - Example: { "event.name": "Template with {{variables}}" }
+
+${source_default.cyan("5. Template style:")}
    - Clear, concise summary line
    - 3-5 detail steps showing workflow
    - Use emojis for visual scanning (\u2705 \u274C \u{1F4CB})