@aventurevc/api-schemas 0.8.203 → 0.8.205

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -60,6 +60,7 @@ declare const AgentHelpSchemaDefinition: z.ZodObject<{
60
60
  step: {
61
61
  instruction: string;
62
62
  operationId: string;
63
+ planTaskKey?: string[] | undefined;
63
64
  stepKey?: string | undefined;
64
65
  };
65
66
  writeGuidance?: {
@@ -76,6 +77,7 @@ declare const AgentHelpSchemaDefinition: z.ZodObject<{
76
77
  step: {
77
78
  instruction: string;
78
79
  operationId: string;
80
+ planTaskKey?: string[] | undefined;
79
81
  stepKey?: string | undefined;
80
82
  };
81
83
  writeGuidance?: {
@@ -5,10 +5,12 @@ declare const HarnessTaskPlanStepSchemaDefinition: z.ZodObject<{
5
5
  step: z.ZodType<{
6
6
  instruction: string;
7
7
  operationId: string;
8
+ planTaskKey?: string[] | undefined;
8
9
  stepKey?: string | undefined;
9
10
  }, import("./task-step.ts").HarnessTaskStepSchemaInput, z.core.$ZodTypeInternals<{
10
11
  instruction: string;
11
12
  operationId: string;
13
+ planTaskKey?: string[] | undefined;
12
14
  stepKey?: string | undefined;
13
15
  }, import("./task-step.ts").HarnessTaskStepSchemaInput>>;
14
16
  writeGuidance: z.ZodOptional<z.ZodNullable<z.ZodObject<{
@@ -31,6 +31,7 @@ export declare const HarnessTaskPlanSchema: z.ZodObject<{
31
31
  step: {
32
32
  instruction: string;
33
33
  operationId: string;
34
+ planTaskKey?: string[] | undefined;
34
35
  stepKey?: string | undefined;
35
36
  };
36
37
  writeGuidance?: {
@@ -47,6 +48,7 @@ export declare const HarnessTaskPlanSchema: z.ZodObject<{
47
48
  step: {
48
49
  instruction: string;
49
50
  operationId: string;
51
+ planTaskKey?: string[] | undefined;
50
52
  stepKey?: string | undefined;
51
53
  };
52
54
  writeGuidance?: {
@@ -2,13 +2,14 @@ import { z } from "zod/v4";
2
2
  declare const HarnessTaskStepSchemaDefinition: z.ZodObject<{
3
3
  instruction: z.ZodString;
4
4
  operationId: z.ZodString;
5
+ planTaskKey: z.ZodOptional<z.ZodArray<z.ZodString>>;
5
6
  stepKey: z.ZodOptional<z.ZodString>;
6
7
  }, z.core.$strip>;
7
8
  type HarnessTaskStepDefinition = z.infer<typeof HarnessTaskStepSchemaDefinition>;
8
9
  export interface HarnessTaskStepSchemaInput extends z.input<typeof HarnessTaskStepSchemaDefinition> {
9
10
  }
10
11
  /**
11
- * One ordered task step: its key, instruction, and the operation that runs it.
12
+ * One ordered task step: its key, instruction, the operation that runs it, and the delegated plans it follows.
12
13
  *
13
14
  * @openapiSchema HarnessTaskStep
14
15
  * @endpoint POST /v1/agents/help
@@ -5,11 +5,13 @@ const HarnessTaskStepSchemaDefinition = z.object({
5
5
  instruction: z.string(),
6
6
  /** OpenAPI operationId this step calls; it must be in the task's operation list. */
7
7
  operationId: z.string(),
8
+ /** Agent-task keys whose plans this step follows instead of restating their steps: the task then owns each named plan's steps, so a write one of them commits counts for this task too. Each must name another planned task; a key may appear once per task and delegations must not loop. */
9
+ planTaskKey: z.array(z.string()).optional(),
8
10
  /** Step key, unique within its task. */
9
11
  stepKey: z.string().optional(),
10
12
  });
11
13
  /**
12
- * One ordered task step: its key, instruction, and the operation that runs it.
14
+ * One ordered task step: its key, instruction, the operation that runs it, and the delegated plans it follows.
13
15
  *
14
16
  * @openapiSchema HarnessTaskStep
15
17
  * @endpoint POST /v1/agents/help
@@ -52,6 +52,7 @@ export declare const HelpResolutionSchema: z.ZodObject<{
52
52
  step: {
53
53
  instruction: string;
54
54
  operationId: string;
55
+ planTaskKey?: string[] | undefined;
55
56
  stepKey?: string | undefined;
56
57
  };
57
58
  writeGuidance?: {
@@ -68,6 +69,7 @@ export declare const HelpResolutionSchema: z.ZodObject<{
68
69
  step: {
69
70
  instruction: string;
70
71
  operationId: string;
72
+ planTaskKey?: string[] | undefined;
71
73
  stepKey?: string | undefined;
72
74
  };
73
75
  writeGuidance?: {
@@ -66,6 +66,7 @@ declare const ProblemDetailSchemaDefinition: z.ZodObject<{
66
66
  origin_detail_shutdown: "origin_detail_shutdown";
67
67
  primary_website_missing: "primary_website_missing";
68
68
  prose_rejected: "prose_rejected";
69
+ query_deadline_shed: "query_deadline_shed";
69
70
  r2_delete_failed: "r2_delete_failed";
70
71
  r2_fetch_failed: "r2_fetch_failed";
71
72
  r2_upload_failed: "r2_upload_failed";
@@ -41,6 +41,8 @@ const ProblemDetailSchemaDefinition = z.object({
41
41
  "origin_detail_capacity",
42
42
  /** Detail-origin cold-miss scheduler rejected work because this instance is shutting down for a redeploy. Agent action: retry shortly; the platform routes the retry to a healthy instance. This is deploy-window noise, not a capacity defect — do not treat it as backend saturation. */
43
43
  "origin_detail_shutdown",
44
+ /** A read overran its database query budget and was shed before it could answer, so nothing was read and the identical request can be replayed. Agent action: retry after a short backoff; this service records the shed WARN-only without an incident, so a consumer that reports it files the only incident for an expected condition. */
45
+ "query_deadline_shed",
44
46
  /** Request prose looks shell-mangled around a money phrase: either shell expansion stripped a leading dollar sign ('50 million' where '$50 million' was meant) or an escape character survived into the text ('\$50 million', standalone '/$50 million'). Agent action: write '$' literally and re-send the JSON body from a file or stdin, or quote it so the shell does not expand '$'; use allowSuspectedShellStrip only when the value is intentional. */
45
47
  "suspectedShellStrip",
46
48
  /** Request prose looks shell-mangled around a money phrase: either shell expansion stripped a leading dollar sign ('50 million' where '$50 million' was meant) or an escape character survived into the text ('\$50 million', standalone '/$50 million'). Agent action: write '$' literally and re-send the JSON body from a file or stdin, or quote it so the shell does not expand '$'; use allowSuspectedShellStrip only when the value is intentional. */
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aventurevc/api-schemas",
3
- "version": "0.8.203",
3
+ "version": "0.8.205",
4
4
  "private": false,
5
5
  "description": "Zod v4 schemas and TypeScript types for the aVenture API.",
6
6
  "license": "Apache-2.0",