@eventop/sdk 1.2.14 → 1.2.15

package/dist/core.cjs

@@ -486,13 +486,7 @@ function buildSystemPrompt(config) {
     var _f$screen;
     return (_f$screen = f.screen) === null || _f$screen === void 0 ? void 0 : _f$screen.id;
   }).map(f => f.screen.id))];
-
-  // Split features into live (current page) and ghost (other pages).
-  // This lets the AI understand what's immediately available vs reachable
-  // via navigation, and craft the right message when something isn't found.
-  const liveFeatures = (config.features || []).filter(f => !f._ghost);
-  const ghostFeatures = (config.features || []).filter(f => f._ghost);
-  const summarise = f => {
+  const featureSummary = (config.features || []).map(f => {
     var _f$screen2, _f$flow;
     const entry = {
       id: f.id,
@@ -507,18 +501,15 @@ function buildSystemPrompt(config) {
       entry.note = `This feature has ${f.flow.length} sequential sub-steps. Include ONE step per flow entry.`;
     }
     return entry;
-  };
-  const liveSection = liveFeatures.length ? `CURRENT PAGE FEATURES (user is here now):\n${JSON.stringify(liveFeatures.map(summarise), null, 2)}` : `CURRENT PAGE FEATURES: none registered yet.`;
-  const ghostSection = ghostFeatures.length ? `OTHER PAGE FEATURES (reachable via navigation — SDK handles it automatically):\n${JSON.stringify(ghostFeatures.map(summarise), null, 2)}` : '';
+  });
   return `
 You are an in-app assistant called "${config.assistantName || 'AI Guide'}" for "${config.appName}".
 Your ONLY job: guide users step-by-step through tasks using the feature map below.
 
-${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. The SDK navigates automatically — just pick the right feature id.` : ''}
-
-${liveSection}
+${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. Features are screen-specific. The SDK handles navigation — just pick the right features.` : ''}
 
-${ghostSection}
+FEATURE MAP (only reference IDs from this list):
+${JSON.stringify(featureSummary, null, 2)}
 
 RESPOND ONLY with this exact JSON — no markdown, no extra text:
 {
@@ -535,26 +526,16 @@ RESPOND ONLY with this exact JSON — no markdown, no extra text:
 }
 
 RULES:
-1. The step "id" MUST match a feature id from the current page or other page features above.
+1. The step "id" MUST match a feature id from the feature map.
 2. Only use selectors and IDs from the feature map. Never invent them.
-3. position values: top | bottom | left | right | auto only.
-4. Order steps logically. For multi-step flows, order as the user encounters them.
-5. For forms: ALWAYS include a step for the form section or first input BEFORE the
+3. No matching feature → steps: [], explain kindly in message.
+4. position values: top | bottom | left | right | auto only.
+5. Order steps logically. For multi-step flows, order as the user encounters them.
+6. For forms: ALWAYS include a step for the form section or first input BEFORE the
    continue/submit button. The button step must always be LAST in its section.
-6. If a feature has a flow, include one step per flow entry using the same feature id —
+7. If a feature has a flow, include one step per flow entry using the same feature id —
    the SDK expands them automatically.
-7. Never skip features in a required sequence. Include every step end-to-end.
-
-WHEN THE USER'S REQUEST DOESN'T MATCH ANY FEATURE:
-- If it partially matches something (e.g. they said "create template" and there's a
-  "template-gallery" feature): guide them to the closest matching feature and explain
-  what it does. Don't say you can't help.
-- If it matches a feature on another page (ghost): include that feature's steps normally.
-  The SDK will navigate there automatically. Do NOT tell the user to navigate manually.
-- If there is genuinely no match anywhere in the feature map: set steps to [] and say
-  something like "That doesn't seem to be a feature in ${config.appName} yet. Here's
-  what I can help you with:" then list 2-3 relevant features from the map by name.
-  Never say you "can only guide through available features" — always offer alternatives.
+8. Never skip features in a required sequence. Include every step end-to-end.
 `.trim();
 }
 

package/dist/core.js

@@ -484,13 +484,7 @@ function buildSystemPrompt(config) {
     var _f$screen;
     return (_f$screen = f.screen) === null || _f$screen === void 0 ? void 0 : _f$screen.id;
   }).map(f => f.screen.id))];
-
-  // Split features into live (current page) and ghost (other pages).
-  // This lets the AI understand what's immediately available vs reachable
-  // via navigation, and craft the right message when something isn't found.
-  const liveFeatures = (config.features || []).filter(f => !f._ghost);
-  const ghostFeatures = (config.features || []).filter(f => f._ghost);
-  const summarise = f => {
+  const featureSummary = (config.features || []).map(f => {
     var _f$screen2, _f$flow;
     const entry = {
       id: f.id,
@@ -505,18 +499,15 @@ function buildSystemPrompt(config) {
       entry.note = `This feature has ${f.flow.length} sequential sub-steps. Include ONE step per flow entry.`;
     }
     return entry;
-  };
-  const liveSection = liveFeatures.length ? `CURRENT PAGE FEATURES (user is here now):\n${JSON.stringify(liveFeatures.map(summarise), null, 2)}` : `CURRENT PAGE FEATURES: none registered yet.`;
-  const ghostSection = ghostFeatures.length ? `OTHER PAGE FEATURES (reachable via navigation — SDK handles it automatically):\n${JSON.stringify(ghostFeatures.map(summarise), null, 2)}` : '';
+  });
   return `
 You are an in-app assistant called "${config.assistantName || 'AI Guide'}" for "${config.appName}".
 Your ONLY job: guide users step-by-step through tasks using the feature map below.
 
-${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. The SDK navigates automatically — just pick the right feature id.` : ''}
-
-${liveSection}
+${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. Features are screen-specific. The SDK handles navigation — just pick the right features.` : ''}
 
-${ghostSection}
+FEATURE MAP (only reference IDs from this list):
+${JSON.stringify(featureSummary, null, 2)}
 
 RESPOND ONLY with this exact JSON — no markdown, no extra text:
 {
@@ -533,26 +524,16 @@ RESPOND ONLY with this exact JSON — no markdown, no extra text:
 }
 
 RULES:
-1. The step "id" MUST match a feature id from the current page or other page features above.
+1. The step "id" MUST match a feature id from the feature map.
 2. Only use selectors and IDs from the feature map. Never invent them.
-3. position values: top | bottom | left | right | auto only.
-4. Order steps logically. For multi-step flows, order as the user encounters them.
-5. For forms: ALWAYS include a step for the form section or first input BEFORE the
+3. No matching feature → steps: [], explain kindly in message.
+4. position values: top | bottom | left | right | auto only.
+5. Order steps logically. For multi-step flows, order as the user encounters them.
+6. For forms: ALWAYS include a step for the form section or first input BEFORE the
    continue/submit button. The button step must always be LAST in its section.
-6. If a feature has a flow, include one step per flow entry using the same feature id —
+7. If a feature has a flow, include one step per flow entry using the same feature id —
    the SDK expands them automatically.
-7. Never skip features in a required sequence. Include every step end-to-end.
-
-WHEN THE USER'S REQUEST DOESN'T MATCH ANY FEATURE:
-- If it partially matches something (e.g. they said "create template" and there's a
-  "template-gallery" feature): guide them to the closest matching feature and explain
-  what it does. Don't say you can't help.
-- If it matches a feature on another page (ghost): include that feature's steps normally.
-  The SDK will navigate there automatically. Do NOT tell the user to navigate manually.
-- If there is genuinely no match anywhere in the feature map: set steps to [] and say
-  something like "That doesn't seem to be a feature in ${config.appName} yet. Here's
-  what I can help you with:" then list 2-3 relevant features from the map by name.
-  Never say you "can only guide through available features" — always offer alternatives.
+8. Never skip features in a required sequence. Include every step end-to-end.
 `.trim();
 }
 

package/dist/react/core.cjs

@@ -486,13 +486,7 @@ function buildSystemPrompt(config) {
     var _f$screen;
     return (_f$screen = f.screen) === null || _f$screen === void 0 ? void 0 : _f$screen.id;
   }).map(f => f.screen.id))];
-
-  // Split features into live (current page) and ghost (other pages).
-  // This lets the AI understand what's immediately available vs reachable
-  // via navigation, and craft the right message when something isn't found.
-  const liveFeatures = (config.features || []).filter(f => !f._ghost);
-  const ghostFeatures = (config.features || []).filter(f => f._ghost);
-  const summarise = f => {
+  const featureSummary = (config.features || []).map(f => {
     var _f$screen2, _f$flow;
     const entry = {
       id: f.id,
@@ -507,18 +501,15 @@ function buildSystemPrompt(config) {
       entry.note = `This feature has ${f.flow.length} sequential sub-steps. Include ONE step per flow entry.`;
     }
     return entry;
-  };
-  const liveSection = liveFeatures.length ? `CURRENT PAGE FEATURES (user is here now):\n${JSON.stringify(liveFeatures.map(summarise), null, 2)}` : `CURRENT PAGE FEATURES: none registered yet.`;
-  const ghostSection = ghostFeatures.length ? `OTHER PAGE FEATURES (reachable via navigation — SDK handles it automatically):\n${JSON.stringify(ghostFeatures.map(summarise), null, 2)}` : '';
+  });
   return `
 You are an in-app assistant called "${config.assistantName || 'AI Guide'}" for "${config.appName}".
 Your ONLY job: guide users step-by-step through tasks using the feature map below.
 
-${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. The SDK navigates automatically — just pick the right feature id.` : ''}
-
-${liveSection}
+${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. Features are screen-specific. The SDK handles navigation — just pick the right features.` : ''}
 
-${ghostSection}
+FEATURE MAP (only reference IDs from this list):
+${JSON.stringify(featureSummary, null, 2)}
 
 RESPOND ONLY with this exact JSON — no markdown, no extra text:
 {
@@ -535,26 +526,16 @@ RESPOND ONLY with this exact JSON — no markdown, no extra text:
 }
 
 RULES:
-1. The step "id" MUST match a feature id from the current page or other page features above.
+1. The step "id" MUST match a feature id from the feature map.
 2. Only use selectors and IDs from the feature map. Never invent them.
-3. position values: top | bottom | left | right | auto only.
-4. Order steps logically. For multi-step flows, order as the user encounters them.
-5. For forms: ALWAYS include a step for the form section or first input BEFORE the
+3. No matching feature → steps: [], explain kindly in message.
+4. position values: top | bottom | left | right | auto only.
+5. Order steps logically. For multi-step flows, order as the user encounters them.
+6. For forms: ALWAYS include a step for the form section or first input BEFORE the
    continue/submit button. The button step must always be LAST in its section.
-6. If a feature has a flow, include one step per flow entry using the same feature id —
+7. If a feature has a flow, include one step per flow entry using the same feature id —
    the SDK expands them automatically.
-7. Never skip features in a required sequence. Include every step end-to-end.
-
-WHEN THE USER'S REQUEST DOESN'T MATCH ANY FEATURE:
-- If it partially matches something (e.g. they said "create template" and there's a
-  "template-gallery" feature): guide them to the closest matching feature and explain
-  what it does. Don't say you can't help.
-- If it matches a feature on another page (ghost): include that feature's steps normally.
-  The SDK will navigate there automatically. Do NOT tell the user to navigate manually.
-- If there is genuinely no match anywhere in the feature map: set steps to [] and say
-  something like "That doesn't seem to be a feature in ${config.appName} yet. Here's
-  what I can help you with:" then list 2-3 relevant features from the map by name.
-  Never say you "can only guide through available features" — always offer alternatives.
+8. Never skip features in a required sequence. Include every step end-to-end.
 `.trim();
 }
 

package/dist/react/core.js

@@ -484,13 +484,7 @@ function buildSystemPrompt(config) {
     var _f$screen;
     return (_f$screen = f.screen) === null || _f$screen === void 0 ? void 0 : _f$screen.id;
   }).map(f => f.screen.id))];
-
-  // Split features into live (current page) and ghost (other pages).
-  // This lets the AI understand what's immediately available vs reachable
-  // via navigation, and craft the right message when something isn't found.
-  const liveFeatures = (config.features || []).filter(f => !f._ghost);
-  const ghostFeatures = (config.features || []).filter(f => f._ghost);
-  const summarise = f => {
+  const featureSummary = (config.features || []).map(f => {
     var _f$screen2, _f$flow;
     const entry = {
       id: f.id,
@@ -505,18 +499,15 @@ function buildSystemPrompt(config) {
       entry.note = `This feature has ${f.flow.length} sequential sub-steps. Include ONE step per flow entry.`;
     }
     return entry;
-  };
-  const liveSection = liveFeatures.length ? `CURRENT PAGE FEATURES (user is here now):\n${JSON.stringify(liveFeatures.map(summarise), null, 2)}` : `CURRENT PAGE FEATURES: none registered yet.`;
-  const ghostSection = ghostFeatures.length ? `OTHER PAGE FEATURES (reachable via navigation — SDK handles it automatically):\n${JSON.stringify(ghostFeatures.map(summarise), null, 2)}` : '';
+  });
   return `
 You are an in-app assistant called "${config.assistantName || 'AI Guide'}" for "${config.appName}".
 Your ONLY job: guide users step-by-step through tasks using the feature map below.
 
-${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. The SDK navigates automatically — just pick the right feature id.` : ''}
-
-${liveSection}
+${screens.length > 1 ? `SCREENS: This app has multiple screens: ${screens.join(', ')}. Features are screen-specific. The SDK handles navigation — just pick the right features.` : ''}
 
-${ghostSection}
+FEATURE MAP (only reference IDs from this list):
+${JSON.stringify(featureSummary, null, 2)}
 
 RESPOND ONLY with this exact JSON — no markdown, no extra text:
 {
@@ -533,26 +524,16 @@ RESPOND ONLY with this exact JSON — no markdown, no extra text:
 }
 
 RULES:
-1. The step "id" MUST match a feature id from the current page or other page features above.
+1. The step "id" MUST match a feature id from the feature map.
 2. Only use selectors and IDs from the feature map. Never invent them.
-3. position values: top | bottom | left | right | auto only.
-4. Order steps logically. For multi-step flows, order as the user encounters them.
-5. For forms: ALWAYS include a step for the form section or first input BEFORE the
+3. No matching feature → steps: [], explain kindly in message.
+4. position values: top | bottom | left | right | auto only.
+5. Order steps logically. For multi-step flows, order as the user encounters them.
+6. For forms: ALWAYS include a step for the form section or first input BEFORE the
    continue/submit button. The button step must always be LAST in its section.
-6. If a feature has a flow, include one step per flow entry using the same feature id —
+7. If a feature has a flow, include one step per flow entry using the same feature id —
    the SDK expands them automatically.
-7. Never skip features in a required sequence. Include every step end-to-end.
-
-WHEN THE USER'S REQUEST DOESN'T MATCH ANY FEATURE:
-- If it partially matches something (e.g. they said "create template" and there's a
-  "template-gallery" feature): guide them to the closest matching feature and explain
-  what it does. Don't say you can't help.
-- If it matches a feature on another page (ghost): include that feature's steps normally.
-  The SDK will navigate there automatically. Do NOT tell the user to navigate manually.
-- If there is genuinely no match anywhere in the feature map: set steps to [] and say
-  something like "That doesn't seem to be a feature in ${config.appName} yet. Here's
-  what I can help you with:" then list 2-3 relevant features from the map by name.
-  Never say you "can only guide through available features" — always offer alternatives.
+8. Never skip features in a required sequence. Include every step end-to-end.
 `.trim();
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eventop/sdk",
-  "version": "1.2.14",
+  "version": "1.2.15",
   "description": "AI-powered guided tours for any web app. Drop-in, themeable, provider-agnostic.",
   "keywords": [
     "onboarding",