@aventurevc/api-schemas 0.8.68 → 0.8.69

package/dist/agent/help-question.js

@@ -6,7 +6,7 @@ const AgentHelpQuestionSchemaDefinition = z.object({
     model: z.string().nullish(),
     /** The question to answer, in natural language. */
     question: z.string().max(2000),
-    /** True resolves the question to one runnable operation instead of answering it: the response carries a resolution (operation advice, clarify, or abstain) and no generated answer. Resolving calls no chat model, ignores model, and draws on its own per-caller limit instead of the answer quota. */
+    /** True selects a catalog task or recommends an operation instead of composing an answer. Outcomes are TASK_PLAN, OPERATION_ADVICE, CLARIFY, or ABSTAIN. Resolve uses retrieval and a model decision, ignores model, and draws on its own per-caller limit instead of the answer quota. */
     resolve: z.boolean().optional(),
     /** Optional scope restricting which operations the answer may recommend; null means all. */
     scope: HelpScopeSchema.nullish(),

package/dist/agent/help.js

@@ -10,7 +10,7 @@ const AgentHelpSchemaDefinition = z.object({
     citation: z.array(HelpCitationSchema),
     /** Confidence the answer is fully supported by the cited corpus. LOW signals an abstention. */
     confidence: ConfidenceSchema,
-    /** The resolved operation when the question asked to resolve; absent for a generated answer. */
+    /** The task or operation resolution when the question asked to resolve; absent for a generated answer. */
     resolution: HelpResolutionSchema.nullish(),
 });
 /**

package/dist/help/resolution.d.ts

@@ -1,6 +1,6 @@
 import { z } from "zod/v4";
 /**
- * Resolution of a request to one operation: advice naming it, a clarification between candidates, or an abstention.
+ * Resolution of a request to a catalog task or an operation, clarification between candidates, or an abstention.
  *
  * @openapiSchema HelpResolution
  * @endpoint POST /v1/agents/help

package/dist/help/resolution.js

@@ -3,7 +3,7 @@ import { z } from "zod/v4";
 import { HelpCitationSchema } from "./citation.js";
 import { HelpResolutionOutcomeSchema } from "./resolution-outcome.js";
 /**
- * Resolution of a request to one operation: advice naming it, a clarification between candidates, or an abstention.
+ * Resolution of a request to a catalog task or an operation, clarification between candidates, or an abstention.
  *
  * @openapiSchema HelpResolution
  * @endpoint POST /v1/agents/help
@@ -21,7 +21,7 @@ export const HelpResolutionSchema = z.object({
     outcome: HelpResolutionOutcomeSchema,
     /** Probability the decision model gave the chosen option (an operation, or none). */
     probability: z.number().nullish(),
-    /** The chosen catalog task; present only for TASK_PLAN. getHarnessTaskPlan reads its plan. */
+    /** The chosen catalog task for TASK_PLAN, or the task leading a CLARIFY; getHarnessTaskPlan reads its plan. */
     taskKey: z.string().nullish(),
 });
 //# sourceMappingURL=resolution.js.map

package/dist/natural/search.js

@@ -2,7 +2,7 @@
 import { z } from "zod/v4";
 import { SearchModeSchema } from "../search/mode.js";
 const NaturalSearchSchemaDefinition = z.object({
-    /** Search strategy to run. Defaults to `auto`: the fast name layer runs first (a single-token query as keyword search, a multiword query as an exact normalized name) and the language-model planner runs only on a miss, so name lookups never pay for planning. Any other value forces exactly that strategy: `exact` and `keyword` skip planner model resolution and its rate limit. Entity and person natural-search take every value; news and federated search accept only `auto` and `keyword`; content search accepts `auto`, `keyword`, and `semantic` (`semantic` only for one entity's or person's content). */
+    /** Search strategy to run. Defaults to `auto`: the fast name layer runs first (a single-token query as keyword search, a multiword query as an exact normalized name) and the language-model planner runs only on a miss, so name lookups never pay for planning. Any other value forces exactly that strategy: `exact` and `keyword` skip planner model resolution and its rate limit. Entity and person natural-search take every value but `hybrid`; news and federated search accept only `auto` and `keyword`; content search accepts `auto`, `keyword`, `semantic`, and `hybrid` (`semantic` and `hybrid` only for one entity's or person's content). */
     mode: SearchModeSchema.default("auto").optional(),
     /** Optional chat model for planning; null uses the configured natural-search default. A caller without admin authority may only choose an allowlisted model; admin callers are unrestricted. */
     model: z.string().nullish(),

package/dist/search/mode.d.ts

@@ -2,13 +2,14 @@ import { z } from "zod/v4";
 declare const SearchModeSchemaDefinition: z.ZodUnion<readonly [z.ZodEnum<{
     auto: "auto";
     exact: "exact";
+    hybrid: "hybrid";
     keyword: "keyword";
     natural: "natural";
     semantic: "semantic";
 }>, z.ZodString]>;
 type SearchModeDefinition = z.infer<typeof SearchModeSchemaDefinition>;
 /**
- * Search strategy for a natural-language search request. `auto` keeps the server pipeline (exact-name shortcut first, planner otherwise); `exact` matches entity or person names exactly with no planner and no embedding; `keyword` runs full-text search; `semantic` runs vector similarity; `natural` always runs the language-model planner. Entity and person natural-search support every mode; news and federated search accept only `auto` and `keyword`; content search accepts `auto` (topic, type, relation, and year words become filters and any other words rank by full text), `keyword` (the full text of articles, posts, and fetched pages), and `semantic` (one entity's or person's library pages by vector similarity of their fetched bodies).
+ * Search strategy for a natural-language search request. `auto` keeps the server pipeline (exact-name shortcut first, planner otherwise); `exact` matches entity or person names exactly with no planner and no embedding; `keyword` runs full-text search; `semantic` runs vector similarity; `natural` always runs the language-model planner; `hybrid` fuses keyword and semantic rankings by reciprocal rank. Entity and person natural-search support every mode but `hybrid`; news and federated search accept only `auto` and `keyword`; content search accepts `auto` (topic, type, relation, and year words become filters and any other words rank by full text), `keyword` (the full text of articles, posts, and fetched pages), `semantic` (one entity's or person's library pages by vector similarity of their fetched bodies), and `hybrid` (that owner's keyword and semantic rankings fused).
  *
  * @openapiSchema SearchMode
  * @endpoint GET /v1/search/link

package/dist/search/mode.js

@@ -1,11 +1,11 @@
 // LLM AGENTS MAY NOT EDIT THIS FILE UNDER ANY CIRCUMSTANCES. DO NOT EDIT - generated from Kotlin data classes via OpenAPI. Edit the backend owner and run: make docs-openapi && make docs-zod
 import { z } from "zod/v4";
 const SearchModeSchemaDefinition = z.union([
-    z.enum(["auto", "exact", "keyword", "semantic", "natural"]),
+    z.enum(["auto", "exact", "keyword", "semantic", "natural", "hybrid"]),
     z.string(),
 ]);
 /**
- * Search strategy for a natural-language search request. `auto` keeps the server pipeline (exact-name shortcut first, planner otherwise); `exact` matches entity or person names exactly with no planner and no embedding; `keyword` runs full-text search; `semantic` runs vector similarity; `natural` always runs the language-model planner. Entity and person natural-search support every mode; news and federated search accept only `auto` and `keyword`; content search accepts `auto` (topic, type, relation, and year words become filters and any other words rank by full text), `keyword` (the full text of articles, posts, and fetched pages), and `semantic` (one entity's or person's library pages by vector similarity of their fetched bodies).
+ * Search strategy for a natural-language search request. `auto` keeps the server pipeline (exact-name shortcut first, planner otherwise); `exact` matches entity or person names exactly with no planner and no embedding; `keyword` runs full-text search; `semantic` runs vector similarity; `natural` always runs the language-model planner; `hybrid` fuses keyword and semantic rankings by reciprocal rank. Entity and person natural-search support every mode but `hybrid`; news and federated search accept only `auto` and `keyword`; content search accepts `auto` (topic, type, relation, and year words become filters and any other words rank by full text), `keyword` (the full text of articles, posts, and fetched pages), `semantic` (one entity's or person's library pages by vector similarity of their fetched bodies), and `hybrid` (that owner's keyword and semantic rankings fused).
  *
  * @openapiSchema SearchMode
  * @endpoint GET /v1/search/link

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aventurevc/api-schemas",
-  "version": "0.8.68",
+  "version": "0.8.69",
   "private": false,
   "description": "Zod v4 schemas and TypeScript types for the aVenture API.",
   "license": "Apache-2.0",