@autonoma-ai/planner 0.1.8 → 0.1.10

package/dist/index.js

@@ -2160,25 +2160,6 @@ function resolveEntityOrder(models, importanceRank) {
   }
   return result;
 }
-function getEntityDependencyChain(entityName, models, entityOrder) {
-  const modelMap = new Map(models.map((m) => [m.name, m]));
-  const visited = /* @__PURE__ */ new Set();
-  const chain = [];
-  function walk(name) {
-    if (visited.has(name)) return;
-    visited.add(name);
-    const model = modelMap.get(name);
-    if (!model) return;
-    for (const dep of model.created_by) {
-      if (entityOrder.includes(dep.owner)) {
-        walk(dep.owner);
-      }
-    }
-    chain.push(name);
-  }
-  walk(entityName);
-  return chain;
-}
 var createdBySchema, auditedModelSchema, frontmatterSchema;
 var init_entity_order = __esm({
   "src/agents/04-recipe-builder/entity-order.ts"() {
@@ -3475,15 +3456,44 @@ var init_highlight = __esm({
 // src/agents/04-recipe-builder/recipe.ts
 import { readFile as readFile15, writeFile as writeFile7 } from "fs/promises";
 import { join as join22 } from "path";
+function collectRefs(value, out) {
+  if (Array.isArray(value)) {
+    for (const v of value) collectRefs(v, out);
+  } else if (value !== null && typeof value === "object") {
+    const obj = value;
+    if (typeof obj._ref === "string") out.add(obj._ref);
+    for (const v of Object.values(obj)) collectRefs(v, out);
+  }
+}
 function buildSingleEntityRecipe(entityName, models, entityOrder, allEntities) {
-  const chain = getEntityDependencyChain(entityName, models, entityOrder);
-  const recipe = {};
-  for (const name of chain) {
-    const entity = allEntities[name];
-    if (entity?.recipeData && entity.recipeData.length > 0) {
-      recipe[name] = entity.recipeData;
+  const modelMap = new Map(models.map((m) => [m.name, m]));
+  const aliasOwner = /* @__PURE__ */ new Map();
+  for (const [name, entity] of Object.entries(allEntities)) {
+    for (const rec of entity?.recipeData ?? []) {
+      if (typeof rec._alias === "string") aliasOwner.set(rec._alias, name);
     }
   }
+  const recipe = {};
+  const done = /* @__PURE__ */ new Set();
+  const onStack = /* @__PURE__ */ new Set();
+  function include(name) {
+    if (done.has(name) || onStack.has(name)) return;
+    onStack.add(name);
+    const records = allEntities[name]?.recipeData ?? [];
+    for (const dep of modelMap.get(name)?.created_by ?? []) {
+      if (entityOrder.includes(dep.owner)) include(dep.owner);
+    }
+    const refs = /* @__PURE__ */ new Set();
+    collectRefs(records, refs);
+    for (const alias of refs) {
+      const owner = aliasOwner.get(alias);
+      if (owner && owner !== name) include(owner);
+    }
+    onStack.delete(name);
+    done.add(name);
+    if (records.length > 0) recipe[name] = records;
+  }
+  include(entityName);
   return recipe;
 }
 function buildFullRecipe(entityOrder, allEntities) {
@@ -3525,7 +3535,6 @@ var init_recipe = __esm({
   "src/agents/04-recipe-builder/recipe.ts"() {
     "use strict";
     init_esm_shims();
-    init_entity_order();
     RECIPE_FILE = "recipe.json";
   }
 });
@@ -3585,7 +3594,7 @@ function buildClassifierPrompt(args) {
   const statusLine = args.httpStatus != null ? `HTTP status: ${args.httpStatus}. (A 5xx usually means the handler threw; a 4xx is more often a rejected payload, but use the error text \u2014 status alone is not decisive.)` : `No HTTP status (the request threw before a response \u2014 often a network/server-process problem, lean implementation or unclear).`;
   return `${PRIMER}
 
-- RECIPE DATA is wrong \u2014 the JSON the tool sent doesn't fit the developer's (correct) schema. Examples of the *kind* of problem (not an exhaustive list): a _ref points at an alias that does not exist among the valid targets listed below, a field holds a value the backend rejects, a required field is missing or an unknown field was sent, or a value has the wrong type. These are fixable by regenerating the data \u2014 the developer's code is fine.
+- RECIPE DATA is wrong \u2014 the JSON the tool sent doesn't fit the developer's (correct) schema. Examples of the *kind* of problem (not an exhaustive list): the request body references an alias (_ref) that no record in THIS SAME request declares with an _alias, a field holds a value the backend rejects, a required field is missing or an unknown field was sent, or a value has the wrong type. These are fixable by regenerating the data \u2014 the developer's code is fine. NOTE: an error like "references unknown alias(es): X" is recipe-side whenever X is not declared by an _alias in the test data shown below \u2014 the SDK resolves _refs WITHIN the request body, so it does not matter whether X appears in the "valid targets" list (that list is historical context about other entities' own runs, NOT the contents of this request).
 - IMPLEMENTATION is wrong \u2014 the developer's own handler/factory code is broken. Examples of the *kind* of problem: the factory for this entity is not registered, the handler references a column or table that does not exist (even though the recipe never mentioned it), the insert/delete logic has a bug, or the server threw an unhandled exception. No change to the test data can fix this; the developer must edit code.
 
 ## How to decide
@@ -3595,7 +3604,7 @@ Ask: "Would sending DIFFERENT, corrected test data \u2014 still matching the int
 - If the data shown below looks valid and the error points at the server's own logic, a missing factory, or a column/table the recipe never referenced \u2192 **implementation**.
 - If you genuinely cannot tell from the evidence \u2192 **unclear**. Prefer "unclear" over a confident guess; a wrong confident answer is worse than admitting uncertainty.
 
-Cross-check the error against the actual data below before deciding \u2014 e.g. only call a _ref invalid if its target really is absent from the valid targets list.
+Cross-check the error against the actual data sent below before deciding. For an "unknown alias" error, look at whether a record in the test data declares that alias with an _alias \u2014 NOT at the valid-targets list. If the alias the error names is missing from (or spelled differently in) the data we sent, it is recipe-side, even when that alias appears in the valid-targets list.
 
 ## Evidence
 
@@ -3740,6 +3749,7 @@ ${completedAliases}
 Rules:
 - _alias fields must be unique identifiers (e.g., "card_1", "transaction_1")
 - _ref fields must reference an alias that ALREADY EXISTS on a parent entity \u2014 see the list of valid targets below. Never invent a _ref to an alias that isn't listed.
+- If the error says "references unknown alias(es): X", a _ref points at "X" but nothing being created declares it. Correct that _ref to one of the valid targets listed below (it's usually a typo, e.g. "users_1" vs "user_1"), or drop the reference if the field is optional. Do NOT leave a _ref pointing at an alias that isn't in the valid targets list.
 - Read scenarios.md to verify you're using correct alias names from parent entities
 - Field names must match the entity's schema from entity-audit.md`,
       model,
@@ -3906,8 +3916,7 @@ function seedFeedbackFromError(errorContext, reason) {
 async function promptOnFailure(entityName, errorBody, ctx, phase, httpStatus) {
   notify("Autonoma", `${entityName} \u2014 failed, action needed`);
   const errorContext = formatErrorContext(errorBody);
-  const budgetLeft = ctx.budget.attempts < MAX_AUTOFIX_ATTEMPTS;
-  const { side, reason } = await classifyFailure(ctx.model, {
+  const { reason } = await classifyFailure(ctx.model, {
     entityName,
     phase,
     httpStatus,
@@ -3916,31 +3925,25 @@ async function promptOnFailure(entityName, errorBody, ctx, phase, httpStatus) {
     validRefAliases: ctx.validRefAliases,
     entityAudit: ctx.entityAudit
   });
-  if (side === "recipe" && budgetLeft) {
+  if (ctx.budget.attempts < MAX_AUTOFIX_ATTEMPTS) {
     ctx.budget.attempts++;
+    p5.log.info(`Triage: ${reason}`);
     p5.log.info(
-      `Triaged as a recipe-data issue \u2014 fixing automatically (attempt ${ctx.budget.attempts}/${MAX_AUTOFIX_ATTEMPTS}): ${reason}`
+      `Handing the failure to the agent to fix from the error (attempt ${ctx.budget.attempts}/${MAX_AUTOFIX_ATTEMPTS})...`
     );
     return seedFeedbackFromError(errorContext, reason);
   }
-  const offerAutofix = side !== "implementation" && budgetLeft;
-  if (side === "implementation") {
-    p5.log.warn(`This looks like a handler/code issue, not the test data: ${reason}`);
-  } else if (side === "recipe" && !budgetLeft) {
-    p5.log.warn(`Autofix ran ${MAX_AUTOFIX_ATTEMPTS}\xD7 without resolving it \u2014 over to you. Latest read: ${reason}`);
-  }
+  p5.log.warn(`The agent tried ${MAX_AUTOFIX_ATTEMPTS}\xD7 without resolving it. Latest triage: ${reason}`);
   const action = await p5.select({
     message: "What would you like to do?",
     options: [
       { value: "retry", label: "Yes, retry \u2014 I fixed my handler code", hint: "Send the same request again" },
-      ...offerAutofix ? [
-        {
-          value: "autofix",
-          label: "Yes, let the agent fix it from the error",
-          hint: "The error explains itself \u2014 hand it to the agent, no typing"
-        }
-      ] : [],
-      { value: "feedback", label: "Yes, fix the recipe data \u2014 I'll explain what's wrong", hint: "The request data is wrong and I'll describe the change" },
+      {
+        value: "autofix",
+        label: "Let the agent try again from the error",
+        hint: "Hand the raw error back to the agent, no typing"
+      },
+      { value: "feedback", label: "Let me explain what's wrong", hint: "Describe the change and the agent will apply it" },
       { value: "skip", label: "No, skip this entity", hint: "Move on to the next entity" }
     ]
   });
@@ -3949,7 +3952,7 @@ async function promptOnFailure(entityName, errorBody, ctx, phase, httpStatus) {
   if (action === "retry") return "retry";
   if (action === "autofix") {
     ctx.budget.attempts++;
-    return seedFeedbackFromError(errorContext);
+    return seedFeedbackFromError(errorContext, reason);
   }
   const fb = await p5.text({
     message: "What's wrong with the recipe data?",