@wix/auto_sdk_restaurants_menus 1.0.78 → 1.0.80

package/build/cjs/schemas.js

@@ -59,7 +59,7 @@ module.exports = __toCommonJS(schemas_exports);
 
 // src/restaurants-menus-v1-menu-menus.schemas.ts
 var z = __toESM(require("zod"));
-var CreateMenuRequest = z.object({
+var CreateMenuRequest = /* @__PURE__ */ z.object({
   menu: z.object({
     _id: z.string().describe("Menu ID.").regex(
       /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
@@ -86,7 +86,7 @@ var CreateMenuRequest = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -98,7 +98,7 @@ var CreateMenuRequest = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -130,7 +130,7 @@ var CreateMenuRequest = z.object({
     ).optional().nullable()
   }).describe("Menu details.")
 });
-var CreateMenuResponse = z.object({
+var CreateMenuResponse = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
@@ -156,7 +156,7 @@ var CreateMenuResponse = z.object({
     tags: z.array(
       z.object({
         type: z.string().describe(
-          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
         ).optional(),
         props: z.record(z.string(), z.any()).describe(
           'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -168,7 +168,7 @@ var CreateMenuResponse = z.object({
           "SEO tag inner content. For example, `<title> inner content </title>`."
         ).optional(),
         custom: z.boolean().describe(
-          'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+          "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
         ).optional(),
         disabled: z.boolean().describe(
           "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -197,7 +197,7 @@ var CreateMenuResponse = z.object({
     "Must be a valid GUID"
   ).optional().nullable()
 });
-var BulkCreateMenusRequest = z.object({
+var BulkCreateMenusRequest = /* @__PURE__ */ z.object({
   menus: z.array(
     z.object({
       _id: z.string().describe("Menu ID.").regex(
@@ -225,7 +225,7 @@ var BulkCreateMenusRequest = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -237,7 +237,7 @@ var BulkCreateMenusRequest = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -273,7 +273,7 @@ var BulkCreateMenusRequest = z.object({
     returnEntity: z.boolean().describe("Whether to receive the created menus in the response.").optional()
   }).optional()
 });
-var BulkCreateMenusResponse = z.object({
+var BulkCreateMenusResponse = /* @__PURE__ */ z.object({
   results: z.array(
     z.object({
       menuMetadata: z.object({
@@ -318,7 +318,7 @@ var BulkCreateMenusResponse = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -330,7 +330,7 @@ var BulkCreateMenusResponse = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -371,13 +371,13 @@ var BulkCreateMenusResponse = z.object({
     ).optional()
   }).describe("Metadata for the API call.").optional()
 });
-var GetMenuRequest = z.object({
+var GetMenuRequest = /* @__PURE__ */ z.object({
   menuId: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
   )
 });
-var GetMenuResponse = z.object({
+var GetMenuResponse = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
@@ -403,7 +403,7 @@ var GetMenuResponse = z.object({
     tags: z.array(
       z.object({
         type: z.string().describe(
-          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
         ).optional(),
         props: z.record(z.string(), z.any()).describe(
           'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -415,7 +415,7 @@ var GetMenuResponse = z.object({
           "SEO tag inner content. For example, `<title> inner content </title>`."
         ).optional(),
         custom: z.boolean().describe(
-          'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+          "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
         ).optional(),
         disabled: z.boolean().describe(
           "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -444,7 +444,7 @@ var GetMenuResponse = z.object({
     "Must be a valid GUID"
   ).optional().nullable()
 });
-var ListMenusRequest = z.object({
+var ListMenusRequest = /* @__PURE__ */ z.object({
   options: z.object({
     menuIds: z.array(z.string()).max(500).optional(),
     paging: z.object({
@@ -458,7 +458,7 @@ var ListMenusRequest = z.object({
     ).optional().nullable()
   }).optional()
 });
-var ListMenusResponse = z.object({
+var ListMenusResponse = /* @__PURE__ */ z.object({
   menus: z.array(
     z.object({
       _id: z.string().describe("Menu ID.").regex(
@@ -486,7 +486,7 @@ var ListMenusResponse = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -498,7 +498,7 @@ var ListMenusResponse = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -543,7 +543,7 @@ var ListMenusResponse = z.object({
     ).optional().nullable()
   }).describe("The metadata of the paginated results.").optional()
 });
-var QueryMenusRequest = z.object({
+var QueryMenusRequest = /* @__PURE__ */ z.object({
   query: z.object({
     filter: z.object({
       _id: z.object({
@@ -609,7 +609,7 @@ var QueryMenusRequest = z.object({
     ).optional()
   }).catchall(z.any()).describe("Query options.")
 });
-var QueryMenusResponse = z.object({
+var QueryMenusResponse = /* @__PURE__ */ z.object({
   menus: z.array(
     z.object({
       _id: z.string().describe("Menu ID.").regex(
@@ -637,7 +637,7 @@ var QueryMenusResponse = z.object({
         tags: z.array(
           z.object({
             type: z.string().describe(
-              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+              "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
             ).optional(),
             props: z.record(z.string(), z.any()).describe(
               'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -649,7 +649,7 @@ var QueryMenusResponse = z.object({
               "SEO tag inner content. For example, `<title> inner content </title>`."
             ).optional(),
             custom: z.boolean().describe(
-              'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+              "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
             ).optional(),
             disabled: z.boolean().describe(
               "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -694,7 +694,7 @@ var QueryMenusResponse = z.object({
     ).optional().nullable()
   }).describe("The metadata of the paginated results.").optional()
 });
-var UpdateMenuRequest = z.object({
+var UpdateMenuRequest = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
@@ -725,7 +725,7 @@ var UpdateMenuRequest = z.object({
       tags: z.array(
         z.object({
           type: z.string().describe(
-            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+            "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
           ).optional(),
           props: z.record(z.string(), z.any()).describe(
             'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -737,7 +737,7 @@ var UpdateMenuRequest = z.object({
             "SEO tag inner content. For example, `<title> inner content </title>`."
           ).optional(),
           custom: z.boolean().describe(
-            'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+            "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
           ).optional(),
           disabled: z.boolean().describe(
             "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -769,7 +769,7 @@ var UpdateMenuRequest = z.object({
     ).optional().nullable()
   }).describe("Menu to update.")
 });
-var UpdateMenuResponse = z.object({
+var UpdateMenuResponse = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
@@ -795,7 +795,7 @@ var UpdateMenuResponse = z.object({
     tags: z.array(
       z.object({
         type: z.string().describe(
-          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+          "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
         ).optional(),
         props: z.record(z.string(), z.any()).describe(
           'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -807,7 +807,7 @@ var UpdateMenuResponse = z.object({
           "SEO tag inner content. For example, `<title> inner content </title>`."
         ).optional(),
         custom: z.boolean().describe(
-          'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+          "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
         ).optional(),
         disabled: z.boolean().describe(
           "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -836,7 +836,7 @@ var UpdateMenuResponse = z.object({
     "Must be a valid GUID"
   ).optional().nullable()
 });
-var BulkUpdateMenuRequest = z.object({
+var BulkUpdateMenuRequest = /* @__PURE__ */ z.object({
   menus: z.array(
     z.object({
       menu: z.object({
@@ -865,7 +865,7 @@ var BulkUpdateMenuRequest = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -877,7 +877,7 @@ var BulkUpdateMenuRequest = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -915,7 +915,7 @@ var BulkUpdateMenuRequest = z.object({
     returnEntity: z.boolean().describe("Whether to receive the entity in the response.").optional()
   }).optional()
 });
-var BulkUpdateMenuResponse = z.object({
+var BulkUpdateMenuResponse = /* @__PURE__ */ z.object({
   results: z.array(
     z.object({
       menuMetadata: z.object({
@@ -960,7 +960,7 @@ var BulkUpdateMenuResponse = z.object({
           tags: z.array(
             z.object({
               type: z.string().describe(
-                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`."
+                "SEO tag type.\n\n\nSupported values: `title`, `meta`, `script`, `link`.\n\nWhich of these an API actually accepts depends on where the tag is being set: this\nlist is not a blanket guarantee across every API that reuses this message. Site SEO\nTags in particular accepts only `meta` (see `SiteSeoTags.tags`) and rejects\n`title`/`script`/`link` with a validation error even though they appear here \u2014\ncheck the field description of the specific `tags`-typed field you're writing to\nfor the types it actually supports and the error it returns.\n\nLimitation: `title` and `script` (e.g. a `script` tag with `props.type`\n`\"application/ld+json\"` carrying structured data) are supported only when\n`custom` is unset or `false`. Setting `custom: true` on a `title` or `script`\ntag is rejected with `TAG_TYPE_NOT_ALLOWED`, because `custom: true` routes the\nwrite through the site's Advanced/Custom Tags list. To write structured data,\nomit `custom` (or set it to `false`)."
               ).optional(),
               props: z.record(z.string(), z.any()).describe(
                 'A `{"key": "value"}` pair object where each SEO tag property (`"name"`, `"content"`, `"rel"`, `"href"`) contains a value.\nFor example: `{"name": "description", "content": "the description itself"}`.'
@@ -972,7 +972,7 @@ var BulkUpdateMenuResponse = z.object({
                 "SEO tag inner content. For example, `<title> inner content </title>`."
               ).optional(),
               custom: z.boolean().describe(
-                'Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages).\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so custom tags saved on those pages are missing from the response entirely. For\nthose pages `false` therefore does not mean "not a custom tag" \u2014 it means this API could not tell.\nPass `seoData` explicitly to resolve against a known set of tags.'
+                "Whether the tag is a [custom tag](https://support.wix.com/en/article/adding-additional-meta-tags-to-your-sites-pages) \u2014\ni.e. an entry from the site's Advanced/Custom Tags list.\n\nSetting this to `true` on a write restricts which `type` values are accepted\n\u2014 the same restriction the Advanced/Custom Tags UI enforces. `title` and\n`script` tags (including JSON-LD structured data) must be sent with `custom`\nomitted or `false`; sending them with `custom: true` is rejected with\n`TAG_TYPE_NOT_ALLOWED`.\n\nNote this is a separate restriction from Site SEO Tags' own type restriction on\n`SiteSeoTags.tags`: even with `custom` unset, Site SEO Tags rejects `script` (e.g.\nfor site-wide structured data) unconditionally. There is currently no way to set\nsite-wide, every-page structured data through any of these APIs \u2014 write a per-page\n`script` tag through the Item SEO Tags API instead.\n\nThis flag is scoped to that feature only. It is NOT an indicator of whether a standard tag\n(`title`, `description`, Open Graph, etc.) reflects a manually configured value versus a computed\ndefault/pattern \u2014 standard tags always resolve with `custom: false`, even when their content comes\nfrom a page's manually saved SEO title/description override. Don't use this field to verify whether\na live page reflects a manual per-page SEO edit.\n\nLimitation: when `ResolveStaticPageSeoTags` is called without `seoData`, the per-page SEO data is read\nonly from the Vibe/Wix-managed-headless override store. That store holds nothing for classic Wix Editor\nor Wix Studio pages, so even genuine Advanced/Custom Tags saved on those pages are missing from the\nresponse entirely \u2014 there, `false` means this API could not tell, not that no custom tag exists.\nPass `seoData` explicitly to resolve against a known set of tags."
               ).optional(),
               disabled: z.boolean().describe(
                 "Whether the tag is disabled. If the tag is disabled, people can't find your page when searching for this phrase in search engines."
@@ -1015,7 +1015,7 @@ var BulkUpdateMenuResponse = z.object({
     ).optional()
   }).describe("Metadata for the API call.").optional()
 });
-var UpdateExtendedFieldsRequest = z.object({
+var UpdateExtendedFieldsRequest = /* @__PURE__ */ z.object({
   _id: z.string().describe("ID of the entity to update."),
   namespace: z.string().describe(
     "Identifier for the app whose extended fields are being updated."
@@ -1026,18 +1026,18 @@ var UpdateExtendedFieldsRequest = z.object({
     )
   })
 });
-var UpdateExtendedFieldsResponse = z.object({
+var UpdateExtendedFieldsResponse = /* @__PURE__ */ z.object({
   namespace: z.string().describe("Namespace of the app.").optional(),
   namespaceData: z.record(z.string(), z.any()).describe("Updated extended fields data.").optional().nullable()
 });
-var DeleteMenuRequest = z.object({
+var DeleteMenuRequest = /* @__PURE__ */ z.object({
   menuId: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
   )
 });
-var DeleteMenuResponse = z.object({});
-var DuplicateMenuRequest = z.object({
+var DeleteMenuResponse = /* @__PURE__ */ z.object({});
+var DuplicateMenuRequest = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu id to be duplicated.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
@@ -1050,21 +1050,21 @@ var DuplicateMenuRequest = z.object({
     menuName: z.string().describe("The new name of the duplicated menu.").max(500).optional().nullable()
   }).optional()
 });
-var DuplicateMenuResponse = z.object({
+var DuplicateMenuResponse = /* @__PURE__ */ z.object({
   menuIds: z.array(z.string()).optional()
 });
-var GetMenuSiteUrlRequest = z.object({
+var GetMenuSiteUrlRequest = /* @__PURE__ */ z.object({
   _id: z.string().describe("Menu ID.").regex(
     /^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$/,
     "Must be a valid GUID"
   )
 });
-var GetMenuSiteUrlResponse = z.object({
+var GetMenuSiteUrlResponse = /* @__PURE__ */ z.object({
   menuSiteUrl: z.object({
     path: z.string().describe("Path URL.").min(1).max(1e3).optional()
   }).describe("Retrieved menuInfo with path url.").optional()
 });
-var QueryMenusSiteUrlRequest = z.object({
+var QueryMenusSiteUrlRequest = /* @__PURE__ */ z.object({
   options: z.object({
     query: z.intersection(
       z.object({
@@ -1100,7 +1100,7 @@ var QueryMenusSiteUrlRequest = z.object({
     ).describe("Query options").optional()
   }).optional()
 });
-var QueryMenusSiteUrlResponse = z.object({
+var QueryMenusSiteUrlResponse = /* @__PURE__ */ z.object({
   menuSiteUrls: z.array(
     z.object({
       path: z.string().describe("Path URL.").min(1).max(1e3).optional()