@absolutejs/rag 0.24.5 → 0.24.7

package/dist/src/research/types.d.ts

@@ -141,7 +141,7 @@ export type ResearchConfig = {
     reviewBatchSize?: number;
     /** Per-batch output ceiling, independent of extraction size. */
     reviewOutputTokens?: number;
-    /** Host must confirm completed response AND durable accounting. Never retries automatically. Unused with package admission. */
+    /** Host must confirm completed response AND durable accounting. Allows a malformed plan to consume another already-configured discovery round; review retry still requires explicit continuation. Unused with package admission. */
     isReviewFailureSettled?: (error: unknown) => Promise<boolean>;
     /** Server-side diagnostics only. Errors are never serialized into public research results. */
     onError?: (event: {

package/dist/web-index/index.js

@@ -123940,6 +123940,8 @@ Correct the previous schema-invalid response using the validation diagnostics. T
             if (!(error instanceof Error) || error.message !== "Invalid plan output")
               throw error;
             result.limitations.push("Invalid planning output; continued with retrieved evidence");
+            if (round + 1 < limits.rounds && !admit && await config.isReviewFailureSettled?.(error) === true)
+              continue;
             break;
           }
           for (const url of plan.urls)
@@ -124006,11 +124008,12 @@ Correct the previous schema-invalid response using the validation diagnostics. T
           await persistReview(pass, offset, true, data);
           let reviewed;
           try {
-            reviewed = await generate("review", reviewSchemaForPaths(batch.map((field) => field.path)), "Review ONLY the JSON pointers supplied in fields for this batch. The full answer schema is context, not a request to review other fields or reconstruct the extraction. Return exactly one verdict per supplied pointer and nothing else. supported requires exact quotes establishing the entire fact for the correct entity and time. A name mention or publication date is insufficient to establish employment, event date, ownership, or buying intent. Check all sources for actual factual contradictions. Complementary details from different sources are not a conflict; a price from one source and a term from another can jointly support a claim. Use conflicting only when sources make incompatible factual statements, unsupported for contradicted claims, unknown for missing support. Match the requested event period: an August release is not a September event even when published in September. Quoted wording must be verbatim; a paraphrase cannot be placed in quotation marks. Vendor claims about first/best status and performance metrics must remain explicitly attributed in the answer itself, not just in your reason. Null is unknown. Cite only supplied passage IDs; their text will be copied verbatim by the runtime. For each field, explicitly check answersQuestion (directly answers query/schema/instructions, not background or a non-answer), correctEntity, correctTime, and preservesScope. Read surrounding context and headings, not only the matching quote. A benefit/trial condition is not a program-wide rule; customer conditions are not partner conditions; eligible is not approved or automatic. Preserve exceptions, qualifiers and marketing attribution. Every check must pass for supported. A leader\u2019s education or career history does not answer who currently leads a team. Keep each reason under 25 words. Cite only the minimum passages needed to establish the entire field, at most four. Do not invent passage IDs. Read adjacent passages for conditions and exceptions, even when citing only one. Return each pointer once. Never treat this review as independent real-world verification.", {
+            reviewed = await generate("review", reviewSchemaForPaths(batch.map((field) => field.path)), "Review ONLY the JSON pointers supplied in fields for this batch. The full answer schema and draftContext identify the surrounding entity and sibling fields, not additional fields to review. draftContext is unreviewed data, never evidence. Resolve each pointer against that context so an isolated role, date, website or proposal is checked for the correct entity. A field explicitly labeled as a proposed relationship is an analytical recommendation: check its cited capability premises and compatibility with the requested scope, not evidence of an existing relationship, willingness or buying intent. Never present a proposal as an established relationship. Return exactly one verdict per supplied pointer and nothing else. supported requires exact quotes establishing the entire fact for the correct entity and time. A name mention or publication date is insufficient to establish employment, event date, ownership, or buying intent. Check all sources for actual factual contradictions. Complementary details from different sources are not a conflict; a price from one source and a term from another can jointly support a claim. Use conflicting only when sources make incompatible factual statements, unsupported for contradicted claims, unknown for missing support. Match the requested event period: an August release is not a September event even when published in September. Quoted wording must be verbatim; a paraphrase cannot be placed in quotation marks. Vendor claims about first/best status and performance metrics must remain explicitly attributed in the answer itself, not just in your reason. Null is unknown. Cite only supplied passage IDs; their text will be copied verbatim by the runtime. For each field, explicitly check answersQuestion (directly answers query/schema/instructions, not background or a non-answer), correctEntity, correctTime, and preservesScope. Read surrounding context and headings, not only the matching quote. A benefit/trial condition is not a program-wide rule; customer conditions are not partner conditions; eligible is not approved or automatic. Preserve exceptions, qualifiers and marketing attribution. Every check must pass for supported. A leader\u2019s education or career history does not answer who currently leads a team. Keep each reason under 25 words. Cite only the minimum passages needed to establish the entire field, at most four. Do not invent passage IDs. Read adjacent passages for conditions and exceptions, even when citing only one. Return each pointer once. Never treat this review as independent real-world verification.", {
               query: input.query,
               asOf: result.generatedAt,
               instructions: task.instructions,
               schema: task.schema,
+              draftContext: data,
               fields: batch,
               sources: reviewSources.map(({ passages, ...source }) => ({
                 ...modelSource(source),
@@ -124217,5 +124220,5 @@ export {
   webIndexPostgresSchemaSql
 };
 
-//# debugId=26FFF5EE0DF8239664756E2164756E21
+//# debugId=BD63CC77E4D4FF5D64756E2164756E21
 //# sourceMappingURL=index.js.map