@shipeasy/openapi 3.2.0 → 3.3.0

package/dist/schemas.js

@@ -11,13 +11,29 @@ import {
   zAddToGateWhitelistRequest,
   zAddToGateWhitelistResponse,
   zAlertApiRow,
+  zAlertCompositeSpec,
+  zAnswerOpsQuestionBody,
+  zAnswerOpsQuestionHeaders,
+  zAnswerOpsQuestionPath,
+  zAnswerOpsQuestionRequest,
+  zAnswerOpsQuestionResponse,
   zApproveEventBody,
   zApproveEventHeaders,
   zApproveEventPath,
   zApproveEventRequest,
   zApproveEventResponse,
   zApproveEventResponse2,
+  zAskOpsQuestionInput,
+  zAskOpsQuestionsBody,
+  zAskOpsQuestionsHeaders,
+  zAskOpsQuestionsPath,
+  zAskOpsQuestionsRequest,
+  zAskOpsQuestionsResponse,
+  zAskOpsQuestionsResponse2,
   zAttributeType,
+  zCancelOpsQuestionHeaders,
+  zCancelOpsQuestionPath,
+  zCancelOpsQuestionResponse,
   zClaudeTriggerConfig,
   zConfigName,
   zConnectorData,
@@ -25,6 +41,7 @@ import {
   zConnectorProvider,
   zConnectorRecord,
   zCopilotTriggerConfig,
+  zCopilotTriggerRepo,
   zCreateAlertRuleBody,
   zCreateAlertRuleHeaders,
   zCreateAlertRuleRequest,
@@ -137,6 +154,7 @@ import {
   zCreateUniverseResponse,
   zCreateUniverseResponse2,
   zCursorTriggerConfig,
+  zCursorTriggerRepo,
   zDeleteAlertRuleHeaders,
   zDeleteAlertRulePath,
   zDeleteAlertRuleResponse,
@@ -209,6 +227,7 @@ import {
   zEnableGatePath,
   zEnableGateResponse,
   zEnableGateResponse2,
+  zEntityTagsResponse,
   zEnv,
   zError,
   zErrorCode,
@@ -253,6 +272,9 @@ import {
   zGetCurrentProjectHeaders,
   zGetCurrentProjectResponse,
   zGetCurrentProjectResponse2,
+  zGetEntityTagsHeaders,
+  zGetEntityTagsPath,
+  zGetEntityTagsResponse,
   zGetErrorHeaders,
   zGetErrorPath,
   zGetErrorResponse,
@@ -421,9 +443,18 @@ import {
   zListOpsItemsQuery,
   zListOpsItemsResponse,
   zListOpsItemsResponse2,
+  zListOpsQuestionsHeaders,
+  zListOpsQuestionsPath,
+  zListOpsQuestionsQuery,
+  zListOpsQuestionsResponse,
+  zListOpsQuestionsResponse2,
   zListSlackChannelsHeaders,
   zListSlackChannelsResponse,
   zListSlackChannelsResponse2,
+  zListTagsHeaders,
+  zListTagsQuery,
+  zListTagsResponse,
+  zListTagsResponse2,
   zListUniversesHeaders,
   zListUniversesQuery,
   zListUniversesResponse,
@@ -432,6 +463,8 @@ import {
   zMeasurePlanStep,
   zMetricDefaultMinEffectOfInterest,
   zMetricDirection,
+  zMetricDisplayConfig,
+  zMetricDisplayName,
   zMetricDisplayUnit,
   zMetricEventName,
   zMetricName,
@@ -463,6 +496,11 @@ import {
   zOpsItemRelated,
   zOpsItemStatus,
   zOpsMeasurePlanContext,
+  zOpsQuestion,
+  zOpsQuestionAnswer,
+  zOpsQuestionDelivery,
+  zOpsQuestionOption,
+  zOpsQuestionStatus,
   zOpsRun,
   zOpsRunAction,
   zOpsRunActionOrNull,
@@ -516,6 +554,11 @@ import {
   zSearchResourcesQuery,
   zSearchResourcesResponse,
   zSearchResponse,
+  zSetEntityTagsBody,
+  zSetEntityTagsHeaders,
+  zSetEntityTagsPath,
+  zSetEntityTagsRequest,
+  zSetEntityTagsResponse,
   zSetExperimentMetricsBody,
   zSetExperimentMetricsHeaders,
   zSetExperimentMetricsPath,
@@ -551,6 +594,9 @@ import {
   zSetKillswitchValueResponse,
   zSetKillswitchValueResponse2,
   zSlackConnectorData,
+  zTag,
+  zTagName,
+  zTaggableEntityType,
   zTestConnectorHeaders,
   zTestConnectorPath,
   zTestConnectorResponse,
@@ -612,6 +658,11 @@ import {
   zUpdateConnectorResponse2,
   zUpdateCopilotTriggerRequest,
   zUpdateCursorTriggerRequest,
+  zUpdateEntityTagsBody,
+  zUpdateEntityTagsHeaders,
+  zUpdateEntityTagsPath,
+  zUpdateEntityTagsRequest,
+  zUpdateEntityTagsResponse,
   zUpdateErrorStatusBody,
   zUpdateErrorStatusHeaders,
   zUpdateErrorStatusPath,
@@ -654,6 +705,11 @@ import {
   zUpdateI18nKeyResponse,
   zUpdateI18nKeyResponse2,
   zUpdateJulesTriggerRequest,
+  zUpdateKeyBody,
+  zUpdateKeyHeaders,
+  zUpdateKeyPath,
+  zUpdateKeyRequest,
+  zUpdateKeyResponse,
   zUpdateKillswitchBody,
   zUpdateKillswitchHeaders,
   zUpdateKillswitchPath,
@@ -711,7 +767,7 @@ import {
   zUpsertProjectRequest,
   zUpsertProjectResponse,
   zUpsertProjectResponse2
-} from "./chunk-DW33MG4B.js";
+} from "./chunk-ZYK74ZIW.js";
 export {
   zAckOpsItemBody,
   zAckOpsItemHeaders,
@@ -725,13 +781,29 @@ export {
   zAddToGateWhitelistRequest,
   zAddToGateWhitelistResponse,
   zAlertApiRow,
+  zAlertCompositeSpec,
+  zAnswerOpsQuestionBody,
+  zAnswerOpsQuestionHeaders,
+  zAnswerOpsQuestionPath,
+  zAnswerOpsQuestionRequest,
+  zAnswerOpsQuestionResponse,
   zApproveEventBody,
   zApproveEventHeaders,
   zApproveEventPath,
   zApproveEventRequest,
   zApproveEventResponse,
   zApproveEventResponse2,
+  zAskOpsQuestionInput,
+  zAskOpsQuestionsBody,
+  zAskOpsQuestionsHeaders,
+  zAskOpsQuestionsPath,
+  zAskOpsQuestionsRequest,
+  zAskOpsQuestionsResponse,
+  zAskOpsQuestionsResponse2,
   zAttributeType,
+  zCancelOpsQuestionHeaders,
+  zCancelOpsQuestionPath,
+  zCancelOpsQuestionResponse,
   zClaudeTriggerConfig,
   zConfigName,
   zConnectorData,
@@ -739,6 +811,7 @@ export {
   zConnectorProvider,
   zConnectorRecord,
   zCopilotTriggerConfig,
+  zCopilotTriggerRepo,
   zCreateAlertRuleBody,
   zCreateAlertRuleHeaders,
   zCreateAlertRuleRequest,
@@ -851,6 +924,7 @@ export {
   zCreateUniverseResponse,
   zCreateUniverseResponse2,
   zCursorTriggerConfig,
+  zCursorTriggerRepo,
   zDeleteAlertRuleHeaders,
   zDeleteAlertRulePath,
   zDeleteAlertRuleResponse,
@@ -923,6 +997,7 @@ export {
   zEnableGatePath,
   zEnableGateResponse,
   zEnableGateResponse2,
+  zEntityTagsResponse,
   zEnv,
   zError,
   zErrorCode,
@@ -967,6 +1042,9 @@ export {
   zGetCurrentProjectHeaders,
   zGetCurrentProjectResponse,
   zGetCurrentProjectResponse2,
+  zGetEntityTagsHeaders,
+  zGetEntityTagsPath,
+  zGetEntityTagsResponse,
   zGetErrorHeaders,
   zGetErrorPath,
   zGetErrorResponse,
@@ -1135,9 +1213,18 @@ export {
   zListOpsItemsQuery,
   zListOpsItemsResponse,
   zListOpsItemsResponse2,
+  zListOpsQuestionsHeaders,
+  zListOpsQuestionsPath,
+  zListOpsQuestionsQuery,
+  zListOpsQuestionsResponse,
+  zListOpsQuestionsResponse2,
   zListSlackChannelsHeaders,
   zListSlackChannelsResponse,
   zListSlackChannelsResponse2,
+  zListTagsHeaders,
+  zListTagsQuery,
+  zListTagsResponse,
+  zListTagsResponse2,
   zListUniversesHeaders,
   zListUniversesQuery,
   zListUniversesResponse,
@@ -1146,6 +1233,8 @@ export {
   zMeasurePlanStep,
   zMetricDefaultMinEffectOfInterest,
   zMetricDirection,
+  zMetricDisplayConfig,
+  zMetricDisplayName,
   zMetricDisplayUnit,
   zMetricEventName,
   zMetricName,
@@ -1177,6 +1266,11 @@ export {
   zOpsItemRelated,
   zOpsItemStatus,
   zOpsMeasurePlanContext,
+  zOpsQuestion,
+  zOpsQuestionAnswer,
+  zOpsQuestionDelivery,
+  zOpsQuestionOption,
+  zOpsQuestionStatus,
   zOpsRun,
   zOpsRunAction,
   zOpsRunActionOrNull,
@@ -1230,6 +1324,11 @@ export {
   zSearchResourcesQuery,
   zSearchResourcesResponse,
   zSearchResponse,
+  zSetEntityTagsBody,
+  zSetEntityTagsHeaders,
+  zSetEntityTagsPath,
+  zSetEntityTagsRequest,
+  zSetEntityTagsResponse,
   zSetExperimentMetricsBody,
   zSetExperimentMetricsHeaders,
   zSetExperimentMetricsPath,
@@ -1265,6 +1364,9 @@ export {
   zSetKillswitchValueResponse,
   zSetKillswitchValueResponse2,
   zSlackConnectorData,
+  zTag,
+  zTagName,
+  zTaggableEntityType,
   zTestConnectorHeaders,
   zTestConnectorPath,
   zTestConnectorResponse,
@@ -1326,6 +1428,11 @@ export {
   zUpdateConnectorResponse2,
   zUpdateCopilotTriggerRequest,
   zUpdateCursorTriggerRequest,
+  zUpdateEntityTagsBody,
+  zUpdateEntityTagsHeaders,
+  zUpdateEntityTagsPath,
+  zUpdateEntityTagsRequest,
+  zUpdateEntityTagsResponse,
   zUpdateErrorStatusBody,
   zUpdateErrorStatusHeaders,
   zUpdateErrorStatusPath,
@@ -1368,6 +1475,11 @@ export {
   zUpdateI18nKeyResponse,
   zUpdateI18nKeyResponse2,
   zUpdateJulesTriggerRequest,
+  zUpdateKeyBody,
+  zUpdateKeyHeaders,
+  zUpdateKeyPath,
+  zUpdateKeyRequest,
+  zUpdateKeyResponse,
   zUpdateKillswitchBody,
   zUpdateKillswitchHeaders,
   zUpdateKillswitchPath,

package/openapi-sdk.json

@@ -47,7 +47,7 @@
       "post": {
         "operationId": "createPublicBug",
         "summary": "File a bug",
-        "description": "Files one bug onto a project's queue, awaiting human approval. This is the **public** intake: it authenticates with a *client* SDK key rather than an admin key, so it can be called from a CLI, an installer script, a devtools overlay, or any shipped code — the same places a client key already lives.\n\nThree gates decide whether a ticket is filed, and nothing else the caller sends can widen them:\n\n1. the key is a `client` key carrying the `tickets:public_create` scope,\n2. the key's project has public ticket creation enabled, and\n3. the item is filed as `pending_approval` — parked out of the work queue until a human promotes it in the dashboard.\n\nThe project is the key's own project; there is no `X-Project-Id` to pass and no way to file into someone else's queue. Repeat submissions of the same title dedupe against the open ticket already tracking it, which returns `200` with `deduped: true` instead of filing again.\n\nThis endpoint is served by the Shipeasy **edge worker** (`api.shipeasy.ai`), not the admin API — see `servers` below.\n\n**Use case:** `shipeasy setup` fails on a customer's machine and self-reports the failure with the user's consent — `{ \"title\": \"Setup failed at Feature installs\", \"stepsToReproduce\": \"…\", \"actualResult\": \"…\" }`.",
+        "description": "Files one bug onto a project's queue, awaiting human approval. This is the **public** intake: it authenticates with a *client* SDK key rather than an admin key, so it can be called from a CLI, an installer script, a devtools overlay, or any shipped code — the same places a client key already lives.\n\nThree gates decide whether a ticket is filed, and nothing else the caller sends can widen them:\n\n1. the key is a `client` key carrying the `tickets:public_create` scope,\n2. the key's project has public ticket creation enabled, and\n3. the item is filed as `pending_approval` — parked out of the work queue until a human promotes it in the dashboard.\n\nThe project is the key's own project; there is no `X-Project-Id` to pass and no way to file into someone else's queue. Repeat submissions of the same title dedupe against the open ticket already tracking it, which returns `200` with `deduped: true` instead of filing again.\n\nSend a `dedupKey` to own that grain yourself — the same key from a monitor, a job, or a retried install re-triggers its open ticket: the ticket's fields are refreshed from the new payload and a \"re-triggered\" comment is appended (`200` with `deduped: true, updated: true`), so one recurring failure stays one ticket with its history intact.\n\nThis endpoint is served by the Shipeasy **edge worker** (`api.shipeasy.ai`), not the admin API — see `servers` below.\n\n**Use case:** `shipeasy setup` fails on a customer's machine and self-reports the failure with the user's consent — `{ \"title\": \"Setup failed at Feature installs\", \"stepsToReproduce\": \"…\", \"actualResult\": \"…\" }`.",
         "tags": [
           "Ops"
         ],
@@ -160,7 +160,7 @@
       "post": {
         "operationId": "createPublicFeatureRequest",
         "summary": "File a feature request",
-        "description": "Files one feature request onto a project's queue, awaiting human approval. The feature-request counterpart to `POST /ops/bug`, with the same three gates: a `client` key carrying `tickets:public_create`, a project that has opted in, and a `pending_approval` state forced server-side.\n\nThe project is the key's own project; there is no `X-Project-Id` to pass. Repeat submissions of the same title dedupe against the open ticket already tracking it, which returns `200` with `deduped: true` instead of filing again.\n\nThis endpoint is served by the Shipeasy **edge worker** (`api.shipeasy.ai`), not the admin API — see `servers` below.\n\n**Use case:** An in-product \"request a feature\" form posts what the user asked for — `{ \"title\": \"Dark mode\", \"useCase\": \"Reduce eye strain at night\" }`.",
+        "description": "Files one feature request onto a project's queue, awaiting human approval. The feature-request counterpart to `POST /ops/bug`, with the same three gates: a `client` key carrying `tickets:public_create`, a project that has opted in, and a `pending_approval` state forced server-side.\n\nThe project is the key's own project; there is no `X-Project-Id` to pass. Repeat submissions of the same title dedupe against the open ticket already tracking it, which returns `200` with `deduped: true` instead of filing again. A `dedupKey` works exactly as on `POST /ops/bug`: a repeat carrying the same key refreshes the open ticket and comments that it was re-triggered.\n\nThis endpoint is served by the Shipeasy **edge worker** (`api.shipeasy.ai`), not the admin API — see `servers` below.\n\n**Use case:** An in-product \"request a feature\" form posts what the user asked for — `{ \"title\": \"Dark mode\", \"useCase\": \"Reduce eye strain at night\" }`.",
         "tags": [
           "Ops"
         ],
@@ -816,6 +816,12 @@
         ],
         "description": "Lifecycle status of a queue item. The working flow is `open` → `in_progress` → `ready_for_qa` → `resolved` (or `wont_fix`, terminal from any earlier stage). `blocked` marks an item that can't progress until an external dependency clears — a working state a human sets and clears. `ready_for_qa` is what a developer sets once a fix lands; `resolved` is the QA sign-off, normally flipped in the dashboard after verification — set it directly from code only when the fix has been verified end-to-end. `investigating_by_ai` is a system-owned display state — set when the AI agent (Jarvis) picks an item up to investigate, never chosen by a human — so it is shown but not offered as a manual choice. `pending_approval` is the one human-gated holding state: it parks an item OUT of the work queue until a human promotes it to `open` in the dashboard, so `GET /api/admin/ops` excludes it under `status=all`/default and returns it only when requested as an exact `status`. It covers untriaged inbound that must never be auto-implemented — connector requests filed from a customer's connectors panel, and questions funnelled in from the \"Stuck in onboarding?\" assistant — where approving means flipping the status to `open`. Two earlier values were removed in favour of this single gate: `triage` (the onboarding-help bucket, now `pending_approval`) and `triaged` (a redundant \"looked at but not started\" step, now plain `open`)."
       },
+      "TagName": {
+        "type": "string",
+        "minLength": 1,
+        "maxLength": 64,
+        "description": "A tag name. Trimmed; matched case-insensitively against the project's existing tags."
+      },
       "NotificationTarget": {
         "anyOf": [
           {
@@ -935,11 +941,12 @@
           },
           "tags": {
             "type": "array",
+            "maxItems": 50,
             "items": {
-              "type": "string"
+              "$ref": "#/components/schemas/TagName"
             },
             "default": [],
-            "description": "Tag names to attach at creation (get-or-created by name, deduped case-insensitively)."
+            "description": "Tag names to label the item with, e.g. `[\"ios\", \"checkout\"]`. Each name is matched case-insensitively against the project's existing tags and reuses that tag (keeping its stored casing) when one matches; a name with no match creates a new project tag. Here the tags only label the ticket: the project's tag rules (owner/status/agent routing) are not applied to a public report while it awaits approval."
           },
           "reporterEmail": {
             "anyOf": [
@@ -1001,6 +1008,11 @@
             ],
             "description": "Arbitrary capture context, or `null`."
           },
+          "dedupKey": {
+            "type": "string",
+            "maxLength": 200,
+            "description": "Caller-chosen dedupe identity for this report, stored on the ticket. A repeat submission carrying the same key does NOT file a second ticket: the open ticket already holding that key is refreshed from this payload (title and the report fields overwritten, a \"re-triggered\" comment appended) and returned with `deduped: true` and `updated: true`. Triage state a human owns — status, priority, assignee, tags — is left untouched, and a `resolved`/`wont_fix` ticket no longer holds the key, so a failure that comes back after being closed files a fresh ticket. Omit it to fall back to the derived (title + `context.step`) dedupe, whose repeats return the existing ticket unchanged."
+          },
           "notify": {
             "anyOf": [
               {
@@ -1017,7 +1029,7 @@
           "title"
         ],
         "additionalProperties": false,
-        "description": "Body for `POST /ops/bug`. The same bug fields as `CreateBugRequest`, minus the `type` discriminator — the path already says what is being filed."
+        "description": "Body for `POST /ops/bug`. The same bug fields as `CreateBugRequest`, minus the `type` discriminator — the path already says what is being filed, plus the public intake's own `dedupKey`."
       },
       "CreatePublicTicketResponse": {
         "type": "object",
@@ -1033,13 +1045,17 @@
           "deduped": {
             "type": "boolean",
             "description": "`true` when an open ticket already tracked this report and nothing was filed (HTTP 200). Absent on a fresh file (HTTP 201)."
+          },
+          "updated": {
+            "type": "boolean",
+            "description": "`true` when the deduped ticket was REFRESHED from this payload and got a \"re-triggered\" comment — only ever set alongside `deduped` on a submission that carried a `dedupKey`. Absent when the existing ticket was returned untouched."
           }
         },
         "required": [
           "number"
         ],
         "additionalProperties": false,
-        "description": "Response for the public ticket intake. A fresh file returns `201` with `id` + `number`; a repeat of a report already tracked by an open ticket returns `200` with that ticket's `number` and `deduped: true`."
+        "description": "Response for the public ticket intake. A fresh file returns `201` with `id` + `number`; a repeat of a report already tracked by an open ticket returns `200` with that ticket's `number` and `deduped: true` — plus `updated: true` when a `dedupKey` re-triggered it and its fields were refreshed."
       },
       "ErrorCode": {
         "type": "string",
@@ -1199,11 +1215,12 @@
           },
           "tags": {
             "type": "array",
+            "maxItems": 50,
             "items": {
-              "type": "string"
+              "$ref": "#/components/schemas/TagName"
             },
             "default": [],
-            "description": "Tag names to attach at creation (get-or-created by name, deduped case-insensitively)."
+            "description": "Tag names to label the item with, e.g. `[\"ios\", \"checkout\"]`. Each name is matched case-insensitively against the project's existing tags and reuses that tag (keeping its stored casing) when one matches; a name with no match creates a new project tag. Here the tags only label the ticket: the project's tag rules (owner/status/agent routing) are not applied to a public report while it awaits approval."
           },
           "reporterEmail": {
             "anyOf": [
@@ -1253,6 +1270,11 @@
             ],
             "description": "Arbitrary capture context, or `null`."
           },
+          "dedupKey": {
+            "type": "string",
+            "maxLength": 200,
+            "description": "Caller-chosen dedupe identity for this request, stored on the ticket. Behaves exactly as on `POST /ops/bug`: a repeat carrying the same key refreshes the open ticket already holding it (fields overwritten, a \"re-triggered\" comment appended) and returns `deduped: true` with `updated: true`, instead of filing a second one."
+          },
           "notify": {
             "anyOf": [
               {
@@ -1269,7 +1291,7 @@
           "title"
         ],
         "additionalProperties": false,
-        "description": "Body for `POST /ops/feature-request`. The same feature-request fields as `CreateFeatureRequestRequest`, minus the `type` discriminator — the path already says what is being filed."
+        "description": "Body for `POST /ops/feature-request`. The same feature-request fields as `CreateFeatureRequestRequest`, minus the `type` discriminator — the path already says what is being filed, plus the public intake's own `dedupKey`."
       },
       "ResourceId": {
         "type": "string",