cf 0.11.0 → 0.12.0

package/dist/_meta/agent-context.json

@@ -49,7 +49,7 @@
 		"connector-telemetry-snapshots": "# connector-telemetry-snapshots — connector-telemetry-snapshots\n\n## Commands\n\n### Read Operations\n\n- `cf connector-telemetry-snapshots get <snapshot-t>` — Gets Magic WAN Connector Telemetry Snapshot\n- `cf connector-telemetry-snapshots list` — Lists Magic WAN Connector Telemetry Snapshots\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"connector-telemetry-snapshots-latest": "# connector-telemetry-snapshots-latest — connector-telemetry-snapshots-latest\n\n## Commands\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"connectors": "# connectors — connectors\n\n## Commands\n\n### Read Operations\n\n- `cf connectors get <connector-id>` — Gets a Magic WAN Connector.\n- `cf connectors list` — Lists Magic WAN Connectors.\n\n### Create Operations\n\n- `cf connectors create` — Creates a Magic WAN Connector. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf connectors edit <connector-id>` — Edits properties of a Magic WAN Connector. May be used to re-provision a license key. (supports --dry-run, --body)\n- `cf connectors update <connector-id>` — Updates properties of a Magic WAN Connector. May be used to re-provision a license key. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf connectors delete <connector-id>` — Deletes a Magic WAN Connector. (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
-		"containers": "# containers — Deploy and manage Containers applications on Cloudflare's global network\n\n## Commands\n\n### Read Operations\n\n- `cf containers applications get <application-id>` — Returns a single application by id.\n- `cf containers applications instances get <instance-id>` — Returns a container instance belonging to an application.\n- `cf containers applications instances list` — Lists container instances belonging to an application.\n- `cf containers applications list` — Lists all the applications that are associated with your account.\n- `cf containers applications versions list` — Returns all versions for a scheduler-backed application with `scheduling_policy: \"default\"`. Versions and rollouts do not apply to applications with `scheduling_policy: \"durable_object\"`.\n- `cf containers registries list` — Get the list of configured registries in the account.\n\n### Create Operations\n\n- `cf containers applications create` — Create a Containers application. Use `scheduling_policy: \"default\"` for a scheduler-backed application. The Containers scheduler maintains the requested instance count and manages deployment configuration, placement, scaling, versions, and rollouts. Use `scheduling_policy: \"durable_object\"` for a Durable Object-managed application. Each Durable Object creates and manages the lifecycle of its container instance. This request accepts only `name`, `scheduling_policy`, and `durable_objects`. Application-level configuration, scaling, constraints, versions, and rollouts do not apply. (supports --dry-run, --body)\n- `cf containers applications rollouts create <application-id>` — Creates a rollout to update the application's configuration across instances with minimal downtime. Rollouts apply only to scheduler-backed applications with `scheduling_policy: \"default\"`. Versions and rollouts do not apply to applications with `scheduling_policy: \"durable_object\"`. (supports --dry-run, --body)\n- `cf containers registries create` — Registers credentials for a supported private external image registry so Containers can pull images from it. This endpoint does not create a registry or upload an image. Public Docker Hub images and images in the Cloudflare managed registry do not require this configuration. Refer to [Image management](https://developers.cloudflare.com/containers/platform-details/image-management/) for supported registries and instructions for storing registry credentials. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf containers applications edit <application-id>` — Modifies a single application by id. Changes that replace instance deployment configuration, including the image, must be applied with a rollout. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf containers applications delete <application-id>` — Deletes a single application by id. (supports --dry-run)\n- `cf containers registries delete <domain>` — Delete a registry from the account, this will prevent Containers from pulling images from the registry. (supports --dry-run)\n\n### Other Operations\n\n- `cf containers images prepare` — Idempotently starts or observes preparation of the runtime artifacts required to run one digest-pinned managed container image on Cloudflare's network. Returns 202 while durable preparation continues and 200 when the image is ready or preparation has reached a terminal error. (supports --dry-run, --body)\n- `cf containers registries credentials generate <domain>` — Generates credentials for accessing a configured container image registry. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
+		"containers": "# containers — Deploy and manage Containers applications on Cloudflare's global network\n\n## Commands\n\n### Read Operations\n\n- `cf containers applications get <application-id>` — Returns a single application by id.\n- `cf containers applications instances get <instance-id>` — Returns a container instance belonging to an application.\n- `cf containers applications instances list` — Lists container instances belonging to an application.\n- `cf containers applications list` — Lists all the applications that are associated with your account.\n- `cf containers applications versions list` — Returns all versions for a scheduler-backed application with `scheduling_policy: \"default\"`. Versions and rollouts do not apply to applications with `scheduling_policy: \"durable_object\"`.\n- `cf containers images list` — List images in the Cloudflare managed registry.\n- `cf containers registries list` — Get the list of configured registries in the account.\n\n### Create Operations\n\n- `cf containers applications create` — Create a Containers application. Use `scheduling_policy: \"default\"` for a scheduler-backed application. The Containers scheduler maintains the requested instance count and manages deployment configuration, placement, scaling, versions, and rollouts. Use `scheduling_policy: \"durable_object\"` for a Durable Object-managed application. Each Durable Object creates and manages the lifecycle of its container instance. This request accepts only `name`, `scheduling_policy`, and `durable_objects`. Application-level configuration, scaling, constraints, versions, and rollouts do not apply. (supports --dry-run, --body)\n- `cf containers applications rollouts create <application-id>` — Creates a rollout to update the application's configuration across instances with minimal downtime. Rollouts apply only to scheduler-backed applications with `scheduling_policy: \"default\"`. Versions and rollouts do not apply to applications with `scheduling_policy: \"durable_object\"`. (supports --dry-run, --body)\n- `cf containers registries create` — Registers credentials for a supported private external image registry so Containers can pull images from it. This endpoint does not create a registry or upload an image. Public Docker Hub images and images in the Cloudflare managed registry do not require this configuration. Refer to [Image management](https://developers.cloudflare.com/containers/platform-details/image-management/) for supported registries and instructions for storing registry credentials. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf containers applications edit <application-id>` — Modifies a single application by id. Changes that replace instance deployment configuration, including the image, must be applied with a rollout. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf containers applications delete <application-id>` — Deletes a single application by id. (supports --dry-run)\n- `cf containers images delete <image>` — Delete an image tag in the Cloudflare managed registry.\n- `cf containers registries delete <domain>` — Delete a registry from the account, this will prevent Containers from pulling images from the registry. (supports --dry-run)\n\n### Other Operations\n\n- `cf containers build <path>` — Build a Container image from a Dockerfile.\n- `cf containers images prepare` — Idempotently starts or observes preparation of the runtime artifacts required to run one digest-pinned managed container image on Cloudflare's network. Returns 202 while durable preparation continues and 200 when the image is ready or preparation has reached a terminal error. (supports --dry-run, --body)\n- `cf containers push` — Push an existing local Docker image to Cloudflare's managed registry.\n- `cf containers registries credentials generate <domain>` — Generates credentials for accessing a configured container image registry. (supports --dry-run, --body)\n- `cf containers ssh <id> [ssh-command]` — SSH into a container.\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"content-scan": "# content-scan — Malicious uploads detection, scan uploaded content in HTTP requests for malware and malicious payloads\n\n## Commands\n\n### Read Operations\n\n- `cf content-scan expressions list` — List the Content Scanning custom expressions configured for the zone, each with its own identifier. A custom expression tells the scanner how to reach content objects in a request it cannot parse on its own, such as files Base64-encoded inside a JSON body.\n- `cf content-scan get` — Get the current Content Scanning status for the zone, together with the date the status was last modified.\n\n### Create Operations\n\n- `cf content-scan expressions create` — Create one or more Content Scanning custom expressions, appending them to the existing list of the zone, and return the updated list. Each expression reaches content objects the scanner cannot find automatically, for example `lookup_json_string(http.request.body.raw, \"file\")`. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf content-scan expressions update <expression-id>` — Update the Content Scanning custom expression with the given identifier and return the updated list of expressions. (supports --dry-run, --body)\n- `cf content-scan update` — Update the Content Scanning status by setting the status value to `enabled` or `disabled`. This is equivalent to calling the dedicated enable and disable endpoints. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf content-scan expressions delete <expression-id>` — Delete the Content Scanning custom expression with the given identifier and return the expressions that remain. Content objects reached only by the deleted expression are no longer scanned. (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"csamScanner": "# csamScanner — csamScanner\n\n## Commands\n\n### Read Operations\n\n- `cf csamScanner get` — Retrieve the current CSAM Scanner configuration for a zone. The notification email is masked by default in responses.\n\n### Update Operations\n\n- `cf csamScanner edit` — Update the CSAM Scanner configuration for a zone. Allows enabling or disabling CSAM scanning, updating the notification email, and configuring scanning sources. When a new email is provided, email verification is triggered automatically. The `enabled` field is a toggle; the server may adjust it based on whether the notification email is verified. Returns 403 if the zone or account is locked by Trust & Safety. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"ct-alerting": "# ct-alerting — ct-alerting\n\n## Commands\n\n### Read Operations\n\n- `cf ct-alerting get` — Retrieve the Certificate Transparency alerting subscription settings for a zone. Returns whether CT monitoring is enabled and the list of email addresses that receive alerts, if any have been configured.\n\n### Update Operations\n\n- `cf ct-alerting update` — Create or update the Certificate Transparency alerting subscription for a zone. Enables or disables email notifications when certificates are issued for the zone's domains. The `enabled` field is required on every request and controls whether the subscription is active. The `emails` field is optional and, when provided, replaces the stored recipient list for the zone. When `emails` is omitted, the stored recipient list is preserved and only the enabled state is toggled. A maximum of 100 email addresses may be configured per zone. Requests that omit `enabled` are rejected with error code 1008. Subscribe and unsubscribe notification emails are only sent for recipients whose effective subscription state changes. Idempotent requests (no state change) send no notification email. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
@@ -181,7 +181,7 @@
 		"waiting-rooms": "# waiting-rooms — Virtual queues that throttle traffic to your site during peak demand with customizable waiting pages\n\n## Commands\n\n### Read Operations\n\n- `cf waiting-rooms account-waiting-rooms list` — Lists waiting rooms for account or zone.\n- `cf waiting-rooms events details get <event-id>` — Previews an event's configuration as if it was active. Inherited fields from the waiting room will be displayed with their current values.\n- `cf waiting-rooms events get <event-id>` — Fetches a single configured event for a waiting room.\n- `cf waiting-rooms events list` — Lists events for a waiting room.\n- `cf waiting-rooms get <waiting-room-id>` — Fetches a single configured waiting room.\n- `cf waiting-rooms rules get <waiting-room-id>` — Lists rules for a waiting room.\n- `cf waiting-rooms settings get` — Get zone-level Waiting Room settings.\n- `cf waiting-rooms statuses get <waiting-room-id>` — Fetches the status of a configured waiting room. Response fields include: 1. `status`: String indicating the status of the waiting room. The possible status are: - **not_queueing** indicates that the configured thresholds have not been met and all users are going through to the origin. - **queueing** indicates that the thresholds have been met and some users are held in the waiting room. - **event_prequeueing** indicates that an event is active and is currently prequeueing users before it starts. - **suspended** indicates that the room is suspended. 2. `event_id`: String of the current event's `id` if an event is active, otherwise an empty string. 3. `estimated_queued_users`: Integer of the estimated number of users currently waiting in the queue. 4. `estimated_total_active_users`: Integer of the estimated number of users currently active on the origin. 5. `max_estimated_time_minutes`: Integer of the maximum estimated time currently presented to the users.\n\n### Create Operations\n\n- `cf waiting-rooms create` — Creates a new waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms events create <waiting-room-id>` — Only available for the Waiting Room Advanced subscription. Creates an event for a waiting room. An event takes place during a specified period of time, temporarily changing the behavior of a waiting room. While the event is active, some of the properties in the event's configuration may either override or inherit from the waiting room's configuration. Note that events cannot overlap with each other, so only one event can be active at a time. (supports --dry-run, --body)\n- `cf waiting-rooms rules create <waiting-room-id>` — Only available for the Waiting Room Advanced subscription. Creates a rule for a waiting room. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf waiting-rooms edit <waiting-room-id>` — Patches a configured waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms events edit <event-id>` — Patches a configured event for a waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms events update <event-id>` — Updates a configured event for a waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms rules edit <rule-id>` — Patches a rule for a waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms rules update <waiting-room-id>` — Only available for the Waiting Room Advanced subscription. Replaces all rules for a waiting room. (supports --dry-run, --body)\n- `cf waiting-rooms settings edit` — Patch zone-level Waiting Room settings. (supports --dry-run, --body)\n- `cf waiting-rooms settings update` — Replace zone-level Waiting Room settings. (supports --dry-run, --body)\n- `cf waiting-rooms update <waiting-room-id>` — Updates a configured waiting room. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf waiting-rooms delete <waiting-room-id>` — Deletes a waiting room. (supports --dry-run)\n- `cf waiting-rooms events delete <event-id>` — Deletes an event for a waiting room. (supports --dry-run)\n- `cf waiting-rooms rules delete <rule-id>` — Deletes a rule for a waiting room. (supports --dry-run)\n\n### Other Operations\n\n- `cf waiting-rooms page preview` — Creates a waiting room page preview. Upload a custom waiting room page for preview. You will receive a preview URL in the form `http://waitingrooms.dev/preview/<uuid>`. You can use the following query parameters to change the state of the preview: 1. `force_queue`: Boolean indicating if all users will be queued in the waiting room and no one will be let into the origin website (also known as queueAll). 2. `queue_is_full`: Boolean indicating if the waiting room's queue is currently full and not accepting new users at the moment. 3. `queueing_method`: The queueing method currently used by the waiting room. - **fifo** indicates a FIFO queue. - **random** indicates a Random queue. - **passthrough** indicates a Passthrough queue. Keep in mind that the waiting room page will only be displayed if `force_queue=true` or `event=prequeueing` — for other cases the request will pass through to the origin. For our preview, this will be a fake origin website returning \\\"Welcome\\\". - **reject** indicates a Reject queue. 4. `event`: Used to preview a waiting room event. - **none** indicates no event is occurring. - **prequeueing** indicates that an event is prequeueing (between `prequeue_start_time` and `event_start_time`). - **started** indicates that an event has started (between `event_start_time` and `event_end_time`). 5. `shuffle_at_event_start`: Boolean indicating if the event will shuffle users in the prequeue when it starts. This can only be set to **true** if an event is active (`event` is not **none**). For example, you can make a request to `http://waitingrooms.dev/preview/<uuid>?force_queue=false&queue_is_full=false&queueing_method=random&event=started&shuffle_at_event_start=true` 6. `waitTime`: Non-zero, positive integer indicating the estimated wait time in minutes. The default value is 10 minutes. For example, you can make a request to `http://waitingrooms.dev/preview/<uuid>?waitTime=50` to configure the estimated wait time as 50 minutes. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"web-assets": "# web-assets — web-assets\n\n## Commands\n\n### Read Operations\n\n- `cf web-assets discovery get` — Returns the latest API operations discovered from zone traffic, rendered as OpenAPI schemas.\n- `cf web-assets discovery operations get <discovery-id>` — Returns a discovered web or API operation by discovery ID.\n- `cf web-assets discovery operations list` — Returns the latest web and API operations discovered from zone traffic.\n- `cf web-assets labels list` — Returns all managed and user-defined labels available for web and API operations in the zone.\n- `cf web-assets labels managed get <name>` — Returns a managed label and the web and API operations associated with it.\n- `cf web-assets labels user get <name>` — Returns a user-defined label and the web and API operations associated with it.\n- `cf web-assets operations get <operation-id>` — Returns a web or API operation, including its schema validation settings and requested feature data.\n- `cf web-assets operations list` — Lists web and API operations tracked for the zone, including each operation's method, path, and feature configuration.\n- `cf web-assets schemas list` — Returns tracked web and API operations and their feature configuration rendered as OpenAPI schemas.\n\n### Create Operations\n\n- `cf web-assets operations create` — Creates one web or API operation. The host, method, and path are normalized; an existing matching operation is returned instead of duplicated. (supports --dry-run, --body)\n- `cf web-assets operations labels create <operation-id>` — Attaches one or more labels to a web or API operation. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf web-assets discovery operations edit <discovery-id>` — Updates the state of a discovered web or API operation. (supports --dry-run, --body)\n- `cf web-assets labels managed operations update <name>` — Replaces the complete set of web and API operations attached to the managed label. (supports --dry-run, --body)\n- `cf web-assets labels user edit <name>` — Updates only the supplied fields on a user-defined label. (supports --dry-run, --body)\n- `cf web-assets labels user operations update <name>` — Replaces the complete set of web and API operations attached to the user-defined label. (supports --dry-run, --body)\n- `cf web-assets labels user update <name>` — Replaces all editable fields on a user-defined label. (supports --dry-run, --body)\n- `cf web-assets operations labels update <operation-id>` — Replaces the complete label set on a web or API operation. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf web-assets labels user delete <name>` — Deletes a user-defined label and removes its associations with web and API operations. (supports --dry-run)\n- `cf web-assets operations delete <operation-id>` — Deletes a web or API operation from endpoint management so its feature configuration is no longer tracked. (supports --dry-run)\n- `cf web-assets operations labels delete <operation-id>` — Removes one or more labels from a web or API operation. (supports --dry-run, --body)\n\n### Other Operations\n\n- `cf web-assets discovery operations bulk-edit` — Updates the state of one or more discovered web and API operations. (supports --dry-run, --body)\n- `cf web-assets labels user bulk-create` — Creates one or more user-defined labels for classifying web and API operations. (supports --dry-run, --body)\n- `cf web-assets labels user bulk-delete` — Deletes one or more user-defined labels and removes their associations with web and API operations. (supports --dry-run, --body)\n- `cf web-assets operations bulk-create` — Creates one or more web or API operations. Hosts, methods, and paths are normalized; an existing matching operation is returned instead of duplicated. (supports --dry-run, --body)\n- `cf web-assets operations bulk-delete` — Deletes multiple web or API operations from endpoint management in one request. (supports --dry-run, --body)\n- `cf web-assets operations labels bulk-create` — Attaches labels to multiple web or API operations in one request. (supports --dry-run, --body)\n- `cf web-assets operations labels bulk-delete` — Removes labels from multiple web or API operations in one request. (supports --dry-run, --body)\n- `cf web-assets operations labels bulk-update` — Replaces the complete label sets on multiple web or API operations in one request. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"web3": "# web3 — web3\n\n## Commands\n\n### Read Operations\n\n- `cf web3 hostnames get <identifier>` — Web3 Hostname Details\n- `cf web3 hostnames ipfs-universal-paths content-lists entries get <content-list-entry-identifier>` — IPFS Universal Path Gateway Content List Entry Details\n- `cf web3 hostnames ipfs-universal-paths content-lists entries list` — List IPFS Universal Path Gateway Content List Entries\n- `cf web3 hostnames ipfs-universal-paths content-lists get <identifier>` — IPFS Universal Path Gateway Content List Details\n- `cf web3 hostnames list` — List Web3 Hostnames\n\n### Create Operations\n\n- `cf web3 hostnames create` — Create Web3 Hostname (supports --dry-run, --body)\n- `cf web3 hostnames ipfs-universal-paths content-lists entries create <identifier>` — Create IPFS Universal Path Gateway Content List Entry (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf web3 hostnames edit <identifier>` — Edit Web3 Hostname (supports --dry-run, --body)\n- `cf web3 hostnames ipfs-universal-paths content-lists entries update <content-list-entry-identifier>` — Edit IPFS Universal Path Gateway Content List Entry (supports --dry-run, --body)\n- `cf web3 hostnames ipfs-universal-paths content-lists update <identifier>` — Update IPFS Universal Path Gateway Content List (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf web3 hostnames delete <identifier>` — Delete Web3 Hostname (supports --dry-run)\n- `cf web3 hostnames ipfs-universal-paths content-lists entries delete <content-list-entry-identifier>` — Delete IPFS Universal Path Gateway Content List Entry (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
-		"workers": "# workers — workers\n\n## Commands\n\n### Read Operations\n\n- `cf workers account-settings get` — Fetches Worker account settings for an account.\n- `cf workers beta workers get <worker-id>` — Get details about a specific Worker.\n- `cf workers beta workers list` — List all Workers for an account.\n- `cf workers beta workers versions get <version-id>` — Get details about a specific version.\n- `cf workers beta workers versions list` — List all versions for a Worker.\n- `cf workers deployments get <deployment-id>` — Get information about a Worker Deployment.\n- `cf workers deployments list` — List of Worker Deployments. The first deployment in the list is the latest deployment actively serving traffic.\n- `cf workers domains get <domain-id>` — Gets information about a domain.\n- `cf workers domains list` — Lists all domains for an account.\n- `cf workers placement regions list` — Returns a list of available placement regions organized by cloud provider. These regions can be used to configure Smart Placement for Workers.\n- `cf workers routes get <route-id>` — Returns information about a route, including URL pattern and Worker.\n- `cf workers routes list` — Returns routes for a zone.\n- `cf workers scripts content get` — Fetch script content only.\n- `cf workers scripts get` — Fetch raw script content for your worker. Note this is the original script content, not JSON encoded.\n- `cf workers scripts list` — Fetch a list of uploaded workers.\n- `cf workers scripts schedules get` — Fetches Cron Triggers for a Worker.\n- `cf workers scripts script-and-version-settings get` — Get metadata and config, such as bindings or usage model.\n- `cf workers scripts settings get` — Get script-level settings when using [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions). Includes Logpush and Tail Consumers.\n- `cf workers scripts subdomain get` — Get if the Worker is available on the workers.dev subdomain.\n- `cf workers scripts tail get` — Get list of tails currently deployed on a Worker.\n- `cf workers scripts usage-model get` — Fetches the Usage Model for a given Worker.\n- `cf workers secrets get <secret-name>` — Get a given secret binding (value omitted) on a script.\n- `cf workers secrets list` — List secrets bound to a script.\n- `cf workers services environments content get <environment-name>` — Get script content from a worker with an environment.\n- `cf workers services environments settings get <environment-name>` — Get script settings from a worker with an environment.\n- `cf workers subdomains get` — Returns a Workers subdomain for an account.\n- `cf workers versions get <version-id>` — Retrieves detailed information about a specific version of a Workers script.\n- `cf workers versions list` — List of Worker Versions. The first version in the list is the latest version.\n\n### Create Operations\n\n- `cf workers assets upload create` — Upload assets ahead of creating a Worker version. To learn more about the direct uploads of assets, see https://developers.cloudflare.com/workers/static-assets/direct-upload/. (supports --dry-run, --body)\n- `cf workers beta workers create` — Create a new Worker. (supports --dry-run, --body)\n- `cf workers beta workers versions create <worker-id>` — Create a new version. (supports --dry-run, --body)\n- `cf workers deployments create` — Deployments configure how [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions) are deployed to traffic. A deployment can consist of one or two versions of a Worker. (supports --dry-run, --body)\n- `cf workers routes create` — Creates a route that maps a URL pattern to a Worker. (supports --dry-run, --body)\n- `cf workers scripts assets upload create` — Start uploading a collection of assets for use in a Worker version. To learn more about the direct uploads of assets, see https://developers.cloudflare.com/workers/static-assets/direct-upload/. (supports --dry-run, --body)\n- `cf workers scripts subdomain create` — Enable or disable the Worker on the workers.dev subdomain. (supports --dry-run, --body)\n- `cf workers scripts tail create` — Starts a tail that receives logs and exception from a Worker. (supports --dry-run)\n- `cf workers versions create` — Upload a new Worker Version without deploying it (supports --dry-run)\n\n### Update Operations\n\n- `cf workers account-settings update` — Creates Worker account settings for an account. (supports --dry-run, --body)\n- `cf workers beta workers edit <worker-id>` — Perform a partial update on a Worker, where omitted properties are left unchanged from their current values. (supports --dry-run, --body)\n- `cf workers beta workers update <worker-id>` — Perform a complete replacement of a Worker, where omitted properties are set to their default values. This is the exact same as the Create Worker endpoint, but operates on an existing Worker. To perform a partial update instead, use the Edit Worker endpoint. (supports --dry-run, --body)\n- `cf workers beta workers versions edit <worker-id>` — Only `/versions/latest` is supported. Creates a new version by applying a JSON Merge Patch (RFC 7396) to the latest version. Patching a specific version ID is not supported. Omitted fields are inherited from the latest version. (supports --dry-run, --body)\n- `cf workers domains update` — Attaches a domain that routes traffic to a Worker. (supports --dry-run, --body)\n- `cf workers routes update <route-id>` — Updates the URL pattern or Worker associated with a route. (supports --dry-run, --body)\n- `cf workers scripts content update` — Put script content without touching config or metadata. (supports --dry-run, --body)\n- `cf workers scripts schedules update` — Updates Cron Triggers for a Worker. (supports --dry-run, --body)\n- `cf workers scripts script-and-version-settings edit` — Patch metadata or config, such as bindings or usage model. (supports --dry-run, --body)\n- `cf workers scripts settings edit` — Patch script-level settings when using [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions). Including but not limited to Logpush and Tail Consumers. (supports --dry-run, --body)\n- `cf workers scripts update` — Upload a worker module. You can find more about the multipart metadata on our docs: https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/. (supports --dry-run, --body)\n- `cf workers scripts usage-model update` — Updates the Usage Model for a given Worker. Requires a Workers Paid subscription. (supports --dry-run, --body)\n- `cf workers secrets update <name>` — Add a secret to a script. (supports --dry-run, --body)\n- `cf workers services environments content update <environment-name>` — Put script content from a worker with an environment. (supports --dry-run, --body)\n- `cf workers services environments settings edit <environment-name>` — Patch script metadata, such as bindings. (supports --dry-run, --body)\n- `cf workers subdomains update` — Creates a Workers subdomain for an account. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf workers beta workers delete <worker-id>` — Delete a Worker and all its associated resources (versions, deployments, etc.). (supports --dry-run)\n- `cf workers beta workers versions delete <version-id>` — Delete a version. (supports --dry-run)\n- `cf workers deployments delete <deployment-id>` — Delete a Worker Deployment. The latest deployment, which is actively serving traffic, cannot be deleted. All other deployments can be deleted. (supports --dry-run)\n- `cf workers domains delete <domain-id>` — Detaches a domain from a Worker. Both the Worker and all of its previews are no longer routable using this domain. (supports --dry-run)\n- `cf workers routes delete <route-id>` — Deletes a route. (supports --dry-run)\n- `cf workers scripts delete` — Delete your worker. This call has no response body on a successful delete. (supports --dry-run)\n- `cf workers scripts subdomain delete` — Disable all workers.dev subdomains for a Worker. (supports --dry-run)\n- `cf workers scripts tail delete <id>` — Deletes a tail from a Worker. (supports --dry-run)\n- `cf workers secrets delete <secret-name>` — Remove a secret from a script. (supports --dry-run)\n- `cf workers subdomains delete` — Deletes a Workers subdomain for an account. (supports --dry-run)\n\n### Other Operations\n\n- `cf workers check` — Profile a Worker's startup performance locally using Build Output API files.\n- `cf workers scripts search` — Search for Workers in an account. (supports --dry-run)\n- `cf workers secrets bulk-edit` — Create, update, or delete multiple secrets on a script in a single operation using JSON Merge Patch (RFC 7396). Usage: - To create or update a secret, set its value to a secret object. - To delete a secret, set its value to `null`. - Secrets not included in the request are left unchanged. (supports --dry-run, --body)\n- `cf workers triggers deploy` — Apply triggers (Routes, Workflows, Cron triggers etc.) (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
+		"workers": "# workers — workers\n\n## Commands\n\n### Read Operations\n\n- `cf workers account-settings get` — Fetches Worker account settings for an account.\n- `cf workers beta workers get <worker-id>` — Get details about a specific Worker.\n- `cf workers beta workers list` — List all Workers for an account.\n- `cf workers beta workers versions get <version-id>` — Get details about a specific version.\n- `cf workers beta workers versions list` — List all versions for a Worker.\n- `cf workers deployments get <deployment-id>` — Get information about a Worker Deployment.\n- `cf workers deployments list` — List of Worker Deployments. The first deployment in the list is the latest deployment actively serving traffic.\n- `cf workers domains get <domain-id>` — Gets information about a domain.\n- `cf workers domains list` — Lists all domains for an account.\n- `cf workers placement regions list` — Returns a list of available placement regions organized by cloud provider. These regions can be used to configure Smart Placement for Workers.\n- `cf workers routes get <route-id>` — Returns information about a route, including URL pattern and Worker.\n- `cf workers routes list` — Returns routes for a zone.\n- `cf workers scripts content get` — Fetch script content only.\n- `cf workers scripts get` — Fetch raw script content for your worker. Note this is the original script content, not JSON encoded.\n- `cf workers scripts list` — Fetch a list of uploaded workers.\n- `cf workers scripts schedules get` — Fetches Cron Triggers for a Worker.\n- `cf workers scripts script-and-version-settings get` — Get metadata and config, such as bindings or usage model.\n- `cf workers scripts settings get` — Get script-level settings when using [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions). Includes Logpush and Tail Consumers.\n- `cf workers scripts subdomain get` — Get if the Worker is available on the workers.dev subdomain.\n- `cf workers scripts tail get` — Get list of tails currently deployed on a Worker.\n- `cf workers scripts usage-model get` — Fetches the Usage Model for a given Worker.\n- `cf workers secrets get <secret-name>` — Get a given secret binding (value omitted) on a script.\n- `cf workers secrets list` — List secrets bound to a script.\n- `cf workers services environments content get <environment-name>` — Get script content from a worker with an environment.\n- `cf workers services environments settings get <environment-name>` — Get script settings from a worker with an environment.\n- `cf workers subdomains get` — Returns a Workers subdomain for an account.\n- `cf workers versions get <version-id>` — Retrieves detailed information about a specific version of a Workers script.\n- `cf workers versions list` — List of Worker Versions. The first version in the list is the latest version.\n\n### Create Operations\n\n- `cf workers assets upload create` — Upload assets ahead of creating a Worker version. To learn more about the direct uploads of assets, see https://developers.cloudflare.com/workers/static-assets/direct-upload/. (supports --dry-run, --body)\n- `cf workers beta workers create` — Create a new Worker. (supports --dry-run, --body)\n- `cf workers beta workers versions create <worker-id>` — Create a new version. (supports --dry-run, --body)\n- `cf workers deployments create` — Deployments configure how [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions) are deployed to traffic. A deployment can consist of one or two versions of a Worker. (supports --dry-run, --body)\n- `cf workers routes create` — Creates a route that maps a URL pattern to a Worker. (supports --dry-run, --body)\n- `cf workers scripts assets upload create` — Start uploading a collection of assets for use in a Worker version. To learn more about the direct uploads of assets, see https://developers.cloudflare.com/workers/static-assets/direct-upload/. (supports --dry-run, --body)\n- `cf workers scripts subdomain create` — Enable or disable the Worker on the workers.dev subdomain. (supports --dry-run, --body)\n- `cf workers scripts tail create` — Starts a tail that receives logs and exception from a Worker. (supports --dry-run)\n- `cf workers versions create` — Upload a new Worker Version without deploying it (supports --dry-run)\n\n### Update Operations\n\n- `cf workers account-settings update` — Creates Worker account settings for an account. (supports --dry-run, --body)\n- `cf workers beta workers edit <worker-id>` — Perform a partial update on a Worker, where omitted properties are left unchanged from their current values. (supports --dry-run, --body)\n- `cf workers beta workers update <worker-id>` — Perform a complete replacement of a Worker, where omitted properties are set to their default values. This is the exact same as the Create Worker endpoint, but operates on an existing Worker. To perform a partial update instead, use the Edit Worker endpoint. (supports --dry-run, --body)\n- `cf workers beta workers versions edit <worker-id>` — Only `/versions/latest` is supported. Creates a new version by applying a JSON Merge Patch (RFC 7396) to the latest version. Patching a specific version ID is not supported. Omitted fields are inherited from the latest version. (supports --dry-run, --body)\n- `cf workers domains update` — Attaches a domain that routes traffic to a Worker. (supports --dry-run, --body)\n- `cf workers routes update <route-id>` — Updates the URL pattern or Worker associated with a route. (supports --dry-run, --body)\n- `cf workers scripts content update` — Put script content without touching config or metadata. (supports --dry-run, --body)\n- `cf workers scripts schedules update` — Updates Cron Triggers for a Worker. (supports --dry-run, --body)\n- `cf workers scripts script-and-version-settings edit` — Patch metadata or config, such as bindings or usage model. (supports --dry-run, --body)\n- `cf workers scripts settings edit` — Patch script-level settings when using [Worker Versions](https://developers.cloudflare.com/api/operations/worker-versions-list-versions). Including but not limited to Logpush and Tail Consumers. (supports --dry-run, --body)\n- `cf workers scripts update` — Upload a worker module. You can find more about the multipart metadata on our docs: https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/. (supports --dry-run, --body)\n- `cf workers scripts usage-model update` — Updates the Usage Model for a given Worker. Requires a Workers Paid subscription. (supports --dry-run, --body)\n- `cf workers secrets update <name>` — Add a secret to a script. (supports --dry-run, --body)\n- `cf workers services environments content update <environment-name>` — Put script content from a worker with an environment. (supports --dry-run, --body)\n- `cf workers services environments settings edit <environment-name>` — Patch script metadata, such as bindings. (supports --dry-run, --body)\n- `cf workers subdomains update` — Creates a Workers subdomain for an account. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf workers beta workers delete <worker-id>` — Delete a Worker and all its associated resources (versions, deployments, etc.). (supports --dry-run)\n- `cf workers beta workers versions delete <version-id>` — Delete a version. (supports --dry-run)\n- `cf workers deployments delete <deployment-id>` — Delete a Worker Deployment. The latest deployment, which is actively serving traffic, cannot be deleted. All other deployments can be deleted. (supports --dry-run)\n- `cf workers domains delete <domain-id>` — Detaches a domain from a Worker. Both the Worker and all of its previews are no longer routable using this domain. (supports --dry-run)\n- `cf workers routes delete <route-id>` — Deletes a route. (supports --dry-run)\n- `cf workers scripts delete` — Delete your worker. This call has no response body on a successful delete. (supports --dry-run)\n- `cf workers scripts subdomain delete` — Disable all workers.dev subdomains for a Worker. (supports --dry-run)\n- `cf workers scripts tail delete <id>` — Deletes a tail from a Worker. (supports --dry-run)\n- `cf workers secrets delete <secret-name>` — Remove a secret from a script. (supports --dry-run)\n- `cf workers subdomains delete` — Deletes a Workers subdomain for an account. (supports --dry-run)\n\n### Other Operations\n\n- `cf workers check` — Profile a Worker's startup performance locally using Build Output Specification files.\n- `cf workers scripts search` — Search for Workers in an account. (supports --dry-run)\n- `cf workers secrets bulk-edit` — Create, update, or delete multiple secrets on a script in a single operation using JSON Merge Patch (RFC 7396). Usage: - To create or update a secret, set its value to a secret object. - To delete a secret, set its value to `null`. - Secrets not included in the request are left unchanged. (supports --dry-run, --body)\n- `cf workers triggers deploy` — Apply triggers (Routes, Workflows, Cron triggers etc.) (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"workers-builds": "# workers-builds — Automated build and deployment pipeline for Workers — track builds, logs, and repo connections\n\n## Commands\n\n### Read Operations\n\n- `cf workers-builds builds get <build-uuid>` — Retrieve detailed information about a specific build\n- `cf workers-builds builds list` — Get all builds for a specific worker script with pagination\n- `cf workers-builds builds logs get <build-uuid>` — Retrieve logs for a specific build with cursor-based pagination\n- `cf workers-builds deploy-hooks get <deploy-hook-uuid>` — Get details of a specific deploy hook.\n- `cf workers-builds deploy-hooks list` — Get all deploy hooks for a specific worker script.\n- `cf workers-builds repos config-autofill get <repo-id>` — Analyze repository for automatic configuration detection\n- `cf workers-builds tokens list` — Get all build tokens with pagination\n- `cf workers-builds triggers environment-variables list` — Get all environment variables for a trigger\n- `cf workers-builds triggers list` — Get all triggers for a specific worker script\n- `cf workers-builds workers get <script-tag>` — Retrieve the build configuration for a specific Worker script, including git repository details and production settings.\n\n### Create Operations\n\n- `cf workers-builds deploy-hooks create <script-name>` — Create a new deploy hook for a worker script. (supports --dry-run, --body)\n- `cf workers-builds tokens create` — Create a new build authentication token (supports --dry-run, --body)\n- `cf workers-builds triggers create` — Create a new CI/CD trigger (supports --dry-run, --body)\n- `cf workers-builds workers create` — Create a new build configuration for a Worker script, linking it to a git repository with CI/CD triggers. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf workers-builds deploy-hooks update <deploy-hook-uuid>` — Update an existing deploy hook. (supports --dry-run, --body)\n- `cf workers-builds triggers update <trigger-uuid>` — Update an existing CI/CD trigger (supports --dry-run, --body)\n- `cf workers-builds workers edit <script-tag>` — Update the build configuration for a Worker script. Supports partial updates to git repository settings and production build settings. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf workers-builds deploy-hooks delete <deploy-hook-uuid>` — Delete a deploy hook. (supports --dry-run)\n- `cf workers-builds repos connections delete <repo-connection-uuid>` — Remove a repository connection (supports --dry-run)\n- `cf workers-builds tokens delete <build-token-uuid>` — Remove a build authentication token (supports --dry-run)\n- `cf workers-builds triggers delete <trigger-uuid>` — Remove a CI/CD trigger (supports --dry-run)\n- `cf workers-builds triggers environment-variables delete <environment-variable-key>` — Remove a specific environment variable from a trigger (supports --dry-run)\n- `cf workers-builds workers delete <script-tag>` — Delete the build configuration for a Worker script. (supports --dry-run)\n\n### Other Operations\n\n- `cf workers-builds builds cancel <build-uuid>` — Cancel a running or queued build (supports --dry-run)\n- `cf workers-builds deploy-hooks trigger <deploy-hook-uuid>` — Trigger a build using a deploy hook. This endpoint does not require authentication - the deploy_hook_uuid acts as a secret token. (supports --dry-run)\n- `cf workers-builds get-account-limits` — Retrieve account limits and usage information (supports --dry-run)\n- `cf workers-builds get-builds-by-version` — Retrieve builds for specific version IDs (supports --dry-run)\n- `cf workers-builds get-latest-builds` — Retrieve the most recent builds for multiple worker scripts (supports --dry-run)\n- `cf workers-builds repos connections upsert` — Upsert a repository connection for CI/CD integration (supports --dry-run, --body)\n- `cf workers-builds triggers create-build <trigger-uuid>` — Trigger a manual build for a specific trigger (supports --dry-run, --body)\n- `cf workers-builds triggers environment-variables upsert <trigger-uuid>` — Create or update environment variables for a trigger (supports --dry-run, --body)\n- `cf workers-builds triggers purge-cache <trigger-uuid>` — Clear the build cache for a specific trigger (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"workflows": "# workflows — Durable, multi-step workflows that run on Workers with automatic retries and state persistence\n\n## Commands\n\n### Read Operations\n\n- `cf workflows get <workflow-name>` — Retrieves configuration and metadata for a specific workflow.\n- `cf workflows instances get <instance-id>` — Retrieves logs and execution status for a specific workflow instance.\n- `cf workflows instances list` — Lists all instances of a workflow with their execution status.\n- `cf workflows instances step get <instance-id>` — Retrieves the full, untruncated output for a specific step on a workflow instance. Returns a flat status-shaped JSON body with step `status` ('running' | 'waiting' | 'complete' | 'errored'), `error` (nullable), and `output` (the step value, or null while running/waiting/errored). When the step returned a ReadableStream from step.do, the response is served as 'application/octet-stream' with the raw bytes as the body instead of JSON. A `status='running'` response with non-null `error` indicates the step is currently retrying after a prior attempt failed.\n- `cf workflows list` — Lists all workflows configured for the account.\n- `cf workflows settings get` — Retrieves account-level Workflows settings, such as the default instance retention.\n- `cf workflows versions get <version-id>` — Retrieves details for a specific deployed workflow version.\n- `cf workflows versions list` — Lists all deployed versions of a workflow.\n\n### Create Operations\n\n- `cf workflows instances batch create <workflow-name>` — Creates multiple workflow instances in a single batch operation. (supports --dry-run, --body)\n- `cf workflows instances create <workflow-name>` — Creates a new instance of a workflow, starting its execution. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf workflows settings edit` — Updates only the account-level Workflows settings fields present in the request body. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf workflows delete <workflow-name>` — Deletes a Workflow. This only deletes the Workflow and does not delete or modify any Worker associated to this Workflow or bounded to it. (supports --dry-run)\n- `cf workflows instances delete <instance-id>` — Deletes a workflow instance and its stored state. (supports --dry-run)\n\n### Other Operations\n\n- `cf workflows instances events send <event-type>` — Sends an event to a running workflow instance to trigger state transitions. (supports --dry-run)\n- `cf workflows instances pause <instance-id>` — Changes the execution status of a workflow instance (e.g., pause, resume, terminate). (supports --dry-run, --body)\n- `cf workflows instances restart <instance-id>` — Changes the execution status of a workflow instance (e.g., pause, resume, terminate). (supports --dry-run, --body)\n- `cf workflows instances resume <instance-id>` — Changes the execution status of a workflow instance (e.g., pause, resume, terminate). (supports --dry-run, --body)\n- `cf workflows instances terminate <instance-id>` — Changes the execution status of a workflow instance (e.g., pause, resume, terminate). (supports --dry-run, --body)\n- `cf workflows versions graph <version-id>` — Retrieves the graph visualization of a workflow version. (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"zaraz": "# zaraz — Server-side tag manager — load third-party tools (analytics, pixels, etc.) from Cloudflare's edge without client-side JS\n\n## Commands\n\n### Read Operations\n\n- `cf zaraz config get` — Gets latest Zaraz configuration for a zone. It can be preview or published configuration, whichever was the last updated. Secret variables values will not be included.\n- `cf zaraz default get` — Gets default Zaraz configuration for a zone.\n- `cf zaraz export get` — Exports full current published Zaraz configuration for a zone, secret variables included.\n- `cf zaraz history configs get` — Gets a history of published Zaraz configurations by ID(s) for a zone.\n- `cf zaraz history list` — Lists a history of published Zaraz configuration records for a zone.\n- `cf zaraz workflow get` — Gets Zaraz workflow for a zone.\n\n### Create Operations\n\n- `cf zaraz publish create` — Publish current Zaraz preview configuration for a zone. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf zaraz config update` — Updates Zaraz configuration for a zone. (supports --dry-run, --body)\n- `cf zaraz history update` — Restores a historical published Zaraz configuration by ID for a zone. (supports --dry-run, --body)\n- `cf zaraz workflow update` — Updates Zaraz workflow for a zone. (supports --dry-run, --body)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
@@ -189,5 +189,5 @@
 		"zone": "# zone — zone\n\n## Commands\n\n### Other Operations\n\n- `cf zone activate` — Triggeres a new activation check for a PENDING Zone. This can be triggered every 5 min for paygo/ent customers, every hour for FREE Zones. (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n",
 		"zones": "# zones — Zones are domains on Cloudflare — list, create, and configure domain settings\n\n## Commands\n\n### Read Operations\n\n- `cf zones aegis get` — Aegis provides dedicated egress IPs (from Cloudflare to your origin) for your layer 7 WAF and CDN services. The egress IPs are reserved exclusively for your account so that you can increase your origin security by only allowing traffic from a small list of IP addresses.\n- `cf zones fonts get` — Enhance your website's font delivery with Cloudflare Fonts. Deliver Google Hosted fonts from your own domain, boost performance, and enhance user privacy. Refer to the Cloudflare Fonts documentation for more information.\n- `cf zones get` — Retrieves detailed information about a specific zone identified by its zone ID. Returns zone configuration, status, nameservers, and associated metadata.\n- `cf zones holds get` — Retrieve whether the zone is subject to a zone hold, and metadata about the hold.\n- `cf zones list` — Lists, searches, sorts, and filters your zones. Listing zones across more than 500 accounts is currently not allowed.\n- `cf zones origin-h2-max-streams get` — Origin H2 Max Streams configures the max number of concurrent requests that Cloudflare will send within the same connection when communicating with the origin server, if the origin supports it. Note that if your origin does not support H2 multiplexing, 5xx errors may be observed, particularly 520s. Also note that the default value is `100` for all plan types except Enterprise where it is `1`. `1` means that H2 multiplexing is disabled.\n- `cf zones origin-max-http-version get` — Origin Max HTTP Setting Version sets the highest HTTP version Cloudflare will attempt to use with your origin. This setting allows Cloudflare to make HTTP/2 requests to your origin. (Refer to [Enable HTTP/2 to Origin](https://developers.cloudflare.com/cache/how-to/enable-http2-to-origin/), for more information.). The default value is \"2\" for all plan types except Enterprise where it is \"1\".\n- `cf zones plans get <plan-identifier>` — Details of the available plan that the zone can subscribe to.\n- `cf zones plans list` — Lists available plans the zone can subscribe to.\n- `cf zones rate-plans get` — Lists all rate plans the zone can subscribe to.\n- `cf zones rum get` — Retrieves RUM status for a zone.\n- `cf zones settings get <setting-id>` — Fetch a single zone setting by name\n- `cf zones speed-brain get` — Speed Brain lets compatible browsers speculate on content which can be prefetched or preloaded, making website navigation faster. Refer to the Cloudflare Speed Brain documentation for more information.\n- `cf zones subscriptions get` — Lists zone subscription details.\n\n### Create Operations\n\n- `cf zones create` — Creates a new zone (domain) in your Cloudflare account. The zone is created in a pending state and must be activated by updating your domain's nameservers to point to Cloudflare, or by completing the verification process for partial (CNAME) setups. (supports --dry-run, --body)\n- `cf zones holds create` — Enforce a zone hold on the zone, blocking the creation and activation of zones with this zone's hostname. Zone holds cannot be enabled on CDN-only zones. (supports --dry-run)\n- `cf zones subscriptions create` — Create a zone subscription, either plan or add-ons. (supports --dry-run, --body)\n\n### Update Operations\n\n- `cf zones aegis edit` — Aegis provides dedicated egress IPs (from Cloudflare to your origin) for your layer 7 WAF and CDN services. The egress IPs are reserved exclusively for your account so that you can increase your origin security by only allowing traffic from a small list of IP addresses. (supports --dry-run, --body)\n- `cf zones edit` — Edits a zone. Only one zone property can be changed at a time. (supports --dry-run, --body)\n- `cf zones fonts edit` — Enhance your website's font delivery with Cloudflare Fonts. Deliver Google Hosted fonts from your own domain, boost performance, and enhance user privacy. Refer to the Cloudflare Fonts documentation for more information. (supports --dry-run, --body)\n- `cf zones holds edit` — Update the `hold_after` and/or `include_subdomains` values on an existing zone hold. The hold is enabled if the `hold_after` date-time value is in the past. Existing zone holds can be removed from CDN-only zones by setting `hold_after` to `null`. Other zone hold updates cannot be made on CDN-only zones. Active holds are automatically disabled when a zone transitions to CDN-only mode. (supports --dry-run, --body)\n- `cf zones origin-h2-max-streams edit` — Origin H2 Max Streams configures the max number of concurrent requests that Cloudflare will send within the same connection when communicating with the origin server, if the origin supports it. Note that if your origin does not support H2 multiplexing, 5xx errors may be observed, particularly 520s. Also note that the default value is `100` for all plan types except Enterprise where it is `1`. `1` means that H2 multiplexing is disabled. (supports --dry-run, --body)\n- `cf zones origin-max-http-version edit` — Origin Max HTTP Setting Version sets the highest HTTP version Cloudflare will attempt to use with your origin. This setting allows Cloudflare to make HTTP/2 requests to your origin. (Refer to [Enable HTTP/2 to Origin](https://developers.cloudflare.com/cache/how-to/enable-http2-to-origin/), for more information.). The default value is \"2\" for all plan types except Enterprise where it is \"1\". (supports --dry-run, --body)\n- `cf zones rum edit` — Toggles RUM on/off for an existing zone. (supports --dry-run, --body)\n- `cf zones settings edit <setting-id>` — Updates a single zone setting by the identifier (supports --dry-run, --body)\n- `cf zones speed-brain edit` — Speed Brain lets compatible browsers speculate on content which can be prefetched or preloaded, making website navigation faster. Refer to the Cloudflare Speed Brain documentation for more information. (supports --dry-run, --body)\n- `cf zones subscriptions update` — Updates zone subscriptions, either plan or add-ons. (supports --dry-run, --body)\n\n### Delete Operations\n\n- `cf zones delete` — Deletes an existing zone. (supports --dry-run)\n- `cf zones holds delete` — Stop enforcement of a zone hold on the zone, permanently or temporarily, allowing the creation and activation of zones with this zone's hostname. Existing zone holds can be removed from CDN-only zones when `hold_after` is not provided. Active holds are automatically disabled when a zone transitions to CDN-only mode. (supports --dry-run)\n- `cf zones subscriptions delete` — Deletes a zone's subscription. (supports --dry-run)\n\n## Safety Guidelines\n\n- Always use `--dry-run` before destructive operations (delete, update)\n"
 	},
-	"universal": "# cf CLI Agent Guide\n\n## Authentication\n- Preferred: Set CLOUDFLARE_API_TOKEN environment variable\n- Alternative: `cf auth login` for OAuth flow\n- Verify: `cf auth whoami`\n\n## Output\n- All output is JSON; pipe through `jq` for transforms\n\n## Safety\n- Always use `--dry-run` before create/update/delete operations\n- Use `--body '{...}'` for complex request payloads\n- Verify zone resolution with `--quiet` disabled\n\n## Context Resolution\n\nAccount ID priority (highest to lowest):\n1. `CLOUDFLARE_ACCOUNT_ID` environment variable\n2. The named `settings` export in `cloudflare.config.ts`\n3. Cached or interactive account selection\n\nZone priority (highest to lowest):\n1. `--zone` / `-z` flag\n2. `CLOUDFLARE_ZONE_ID` environment variable\n\n## Introspection\n- `cf schema --list` — list all available API schemas\n- `cf schema dns records create` — get full request/response schema for a command\n- `cf agent-context [product]` — load agent skill files\n- `cf agent-context auth` — load auth command guidance\n- `cf tools` — get MCP tool definitions\n\n## Error Handling\n- Non-zero exit codes indicate errors\n- Error details are in stderr\n- Check `cf auth whoami` if you get 401 errors\n"
+	"universal": "# cf CLI Agent Guide\n\n## Authentication\n- Preferred: Set CLOUDFLARE_API_TOKEN environment variable\n- Alternative: `cf auth login` for OAuth flow\n- Verify: `cf auth whoami`\n\n## Output\n- All output is JSON; pipe through `jq` for transforms\n\n## Safety\n- Always use `--dry-run` before create/update/delete operations\n- Use `--body '{...}'` for complex request payloads\n- Verify zone resolution with `--quiet` disabled\n\n## Context Resolution\n\nAccount ID priority (highest to lowest):\n1. `CLOUDFLARE_ACCOUNT_ID` environment variable\n2. The account settings in `cloudflare.config.ts`'s default export\n3. Cached or interactive account selection\n\nZone priority (highest to lowest):\n1. `--zone` / `-z` flag\n2. `CLOUDFLARE_ZONE_ID` environment variable\n\n## Introspection\n- `cf schema --list` — list all available API schemas\n- `cf schema dns records create` — get full request/response schema for a command\n- `cf agent-context [product]` — load agent skill files\n- `cf agent-context auth` — load auth command guidance\n- `cf tools` — get MCP tool definitions\n\n## Error Handling\n- Non-zero exit codes indicate errors\n- Error details are in stderr\n- Check `cf auth whoami` if you get 401 errors\n"
 }

package/dist/_meta/commands.json

@@ -38221,6 +38221,88 @@
 			"operationId": "listApplicationVersions",
 			"hideCommand": false
 		},
+		{
+			"command": "cf containers build",
+			"name": "build",
+			"fullPath": ["containers", "build"],
+			"category": "action",
+			"description": "Build a Container image from a Dockerfile.",
+			"usage": "cf containers build <path> --tag <name:tag> [--push]",
+			"arguments": [
+				{
+					"name": "path",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "Directory containing the Dockerfile to build"
+				}
+			],
+			"options": [
+				{
+					"name": "tag",
+					"type": "string",
+					"required": true,
+					"description": "Name and optional tag for the built image"
+				},
+				{
+					"name": "push",
+					"type": "boolean",
+					"required": false,
+					"description": "Push the built image to Cloudflare's managed registry",
+					"default": false
+				},
+				{
+					"name": "path-to-docker",
+					"type": "string",
+					"required": false,
+					"description": "Path to the Docker binary if it is not on PATH"
+				}
+			]
+		},
+		{
+			"command": "cf containers images delete",
+			"name": "delete",
+			"fullPath": ["containers", "images", "delete"],
+			"category": "delete",
+			"description": "Delete an image tag in the Cloudflare managed registry.",
+			"usage": "cf containers images delete <image:tag> [--force]",
+			"arguments": [
+				{
+					"name": "image",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "Image and tag to delete, of the form IMAGE:TAG"
+				}
+			],
+			"options": [
+				{
+					"name": "force",
+					"alias": "f",
+					"type": "boolean",
+					"required": false,
+					"default": false,
+					"description": "Skip the deletion confirmation prompt"
+				}
+			]
+		},
+		{
+			"command": "cf containers images list",
+			"name": "list",
+			"fullPath": ["containers", "images", "list"],
+			"category": "read",
+			"description": "List images in the Cloudflare managed registry.",
+			"usage": "cf containers images list [--filter <regex>]",
+			"arguments": [],
+			"options": [
+				{
+					"name": "filter",
+					"type": "string",
+					"required": false,
+					"description": "Regex to filter repository names"
+				}
+			]
+		},
 		{
 			"command": "cf containers images prepare",
 			"name": "prepare",
@@ -38256,6 +38338,29 @@
 			"operationId": "prepareContainerImage",
 			"hideCommand": false
 		},
+		{
+			"command": "cf containers push",
+			"name": "push",
+			"fullPath": ["containers", "push"],
+			"category": "action",
+			"description": "Push an existing local Docker image to Cloudflare's managed registry.",
+			"usage": "cf containers push --tag <name:tag>",
+			"arguments": [],
+			"options": [
+				{
+					"name": "tag",
+					"type": "string",
+					"required": true,
+					"description": "Tag of the local image to push"
+				},
+				{
+					"name": "path-to-docker",
+					"type": "string",
+					"required": false,
+					"description": "Path to the Docker binary if it is not on PATH"
+				}
+			]
+		},
 		{
 			"command": "cf containers registries create",
 			"name": "create",
@@ -38418,6 +38523,38 @@
 			"operationId": "listImageRegistries",
 			"hideCommand": false
 		},
+		{
+			"command": "cf containers ssh",
+			"name": "ssh",
+			"fullPath": ["containers", "ssh"],
+			"category": "action",
+			"description": "SSH into a container.",
+			"usage": "cf containers ssh <id> [--stdio] [-- <command...>]",
+			"arguments": [
+				{
+					"name": "id",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "ID of the container instance"
+				},
+				{
+					"name": "ssh-command",
+					"position": 1,
+					"type": "string",
+					"required": false,
+					"description": "Command and arguments to run in the container"
+				}
+			],
+			"options": [
+				{
+					"name": "stdio",
+					"type": "boolean",
+					"required": false,
+					"description": "Proxy SSH traffic over stdin/stdout"
+				}
+			]
+		},
 		{
 			"command": "cf content-scan expressions create",
 			"name": "create",
@@ -43095,7 +43232,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Deploy existing Build Output API files without building",
+					"description": "Deploy existing Build Output Specification files without building",
 					"default": false
 				},
 				{
@@ -43128,6 +43265,13 @@
 					"type": "string",
 					"required": false,
 					"description": "Name of a dispatch namespace to deploy the Worker to (Workers for Platforms)"
+				},
+				{
+					"name": "containers-rollout",
+					"type": "string",
+					"required": false,
+					"description": "Rollout strategy for Container changes. Immediate rolls out to all instances in one step; none leaves deployed Containers unchanged.",
+					"enum": ["immediate", "gradual", "none"]
 				}
 			]
 		},
@@ -131591,7 +131735,7 @@
 			"name": "check",
 			"fullPath": ["workers", "check"],
 			"category": "action",
-			"description": "Profile a Worker's startup performance locally using Build Output API files.",
+			"description": "Profile a Worker's startup performance locally using Build Output Specification files.",
 			"usage": "cf workers check [--outfile <path>] [--prebuilt]",
 			"arguments": [],
 			"options": [
@@ -131606,7 +131750,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Use existing Build Output API files without building",
+					"description": "Use existing Build Output Specification files without building",
 					"default": false
 				}
 			]
@@ -133624,7 +133768,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Use existing Build Output API files without building",
+					"description": "Use existing Build Output Specification files without building",
 					"default": false
 				},
 				{
@@ -133648,7 +133792,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Deploy existing Build Output API files without building",
+					"description": "Deploy existing Build Output Specification files without building",
 					"default": false
 				},
 				{

package/dist/_meta/hand-written-commands.json

@@ -328,6 +328,173 @@
 				"dir": "completions"
 			}
 		},
+		{
+			"command": "cf containers build",
+			"name": "build",
+			"fullPath": ["containers", "build"],
+			"category": "action",
+			"description": "Build a Container image from a Dockerfile.",
+			"usage": "cf containers build <path> --tag <name:tag> [--push]",
+			"arguments": [
+				{
+					"name": "path",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "Directory containing the Dockerfile to build"
+				}
+			],
+			"options": [
+				{
+					"name": "tag",
+					"type": "string",
+					"required": true,
+					"description": "Name and optional tag for the built image"
+				},
+				{
+					"name": "push",
+					"type": "boolean",
+					"required": false,
+					"description": "Push the built image to Cloudflare's managed registry",
+					"default": false
+				},
+				{
+					"name": "path-to-docker",
+					"type": "string",
+					"required": false,
+					"description": "Path to the Docker binary if it is not on PATH"
+				}
+			],
+			"handWritten": {
+				"kind": "leaf",
+				"overrides": false,
+				"dir": "containers/build",
+				"parent": "containers"
+			}
+		},
+		{
+			"command": "cf containers images delete",
+			"name": "delete",
+			"fullPath": ["containers", "images", "delete"],
+			"category": "delete",
+			"description": "Delete an image tag in the Cloudflare managed registry.",
+			"usage": "cf containers images delete <image:tag> [--force]",
+			"arguments": [
+				{
+					"name": "image",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "Image and tag to delete, of the form IMAGE:TAG"
+				}
+			],
+			"options": [
+				{
+					"name": "force",
+					"alias": "f",
+					"type": "boolean",
+					"required": false,
+					"default": false,
+					"description": "Skip the deletion confirmation prompt"
+				}
+			],
+			"handWritten": {
+				"kind": "leaf",
+				"overrides": false,
+				"dir": "containers/images/delete",
+				"parent": "containers/images"
+			}
+		},
+		{
+			"command": "cf containers images list",
+			"name": "list",
+			"fullPath": ["containers", "images", "list"],
+			"category": "read",
+			"description": "List images in the Cloudflare managed registry.",
+			"usage": "cf containers images list [--filter <regex>]",
+			"arguments": [],
+			"options": [
+				{
+					"name": "filter",
+					"type": "string",
+					"required": false,
+					"description": "Regex to filter repository names"
+				}
+			],
+			"handWritten": {
+				"kind": "leaf",
+				"overrides": false,
+				"dir": "containers/images/list",
+				"parent": "containers/images"
+			}
+		},
+		{
+			"command": "cf containers push",
+			"name": "push",
+			"fullPath": ["containers", "push"],
+			"category": "action",
+			"description": "Push an existing local Docker image to Cloudflare's managed registry.",
+			"usage": "cf containers push --tag <name:tag>",
+			"arguments": [],
+			"options": [
+				{
+					"name": "tag",
+					"type": "string",
+					"required": true,
+					"description": "Tag of the local image to push"
+				},
+				{
+					"name": "path-to-docker",
+					"type": "string",
+					"required": false,
+					"description": "Path to the Docker binary if it is not on PATH"
+				}
+			],
+			"handWritten": {
+				"kind": "leaf",
+				"overrides": false,
+				"dir": "containers/push",
+				"parent": "containers"
+			}
+		},
+		{
+			"command": "cf containers ssh",
+			"name": "ssh",
+			"fullPath": ["containers", "ssh"],
+			"category": "action",
+			"description": "SSH into a container.",
+			"usage": "cf containers ssh <id> [--stdio] [-- <command...>]",
+			"arguments": [
+				{
+					"name": "id",
+					"position": 0,
+					"type": "string",
+					"required": true,
+					"description": "ID of the container instance"
+				},
+				{
+					"name": "ssh-command",
+					"position": 1,
+					"type": "string",
+					"required": false,
+					"description": "Command and arguments to run in the container"
+				}
+			],
+			"options": [
+				{
+					"name": "stdio",
+					"type": "boolean",
+					"required": false,
+					"description": "Proxy SSH traffic over stdin/stdout"
+				}
+			],
+			"handWritten": {
+				"kind": "leaf",
+				"overrides": false,
+				"dir": "containers/ssh",
+				"parent": "containers"
+			}
+		},
 		{
 			"command": "cf d1 migrations apply",
 			"name": "apply",
@@ -464,7 +631,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Deploy existing Build Output API files without building",
+					"description": "Deploy existing Build Output Specification files without building",
 					"default": false
 				},
 				{
@@ -497,6 +664,13 @@
 					"type": "string",
 					"required": false,
 					"description": "Name of a dispatch namespace to deploy the Worker to (Workers for Platforms)"
+				},
+				{
+					"name": "containers-rollout",
+					"type": "string",
+					"required": false,
+					"description": "Rollout strategy for Container changes. Immediate rolls out to all instances in one step; none leaves deployed Containers unchanged.",
+					"enum": ["immediate", "gradual", "none"]
 				}
 			],
 			"handWritten": {
@@ -652,7 +826,7 @@
 			"name": "check",
 			"fullPath": ["workers", "check"],
 			"category": "action",
-			"description": "Profile a Worker's startup performance locally using Build Output API files.",
+			"description": "Profile a Worker's startup performance locally using Build Output Specification files.",
 			"usage": "cf workers check [--outfile <path>] [--prebuilt]",
 			"arguments": [],
 			"options": [
@@ -667,7 +841,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Use existing Build Output API files without building",
+					"description": "Use existing Build Output Specification files without building",
 					"default": false
 				}
 			],
@@ -691,7 +865,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Use existing Build Output API files without building",
+					"description": "Use existing Build Output Specification files without building",
 					"default": false
 				},
 				{
@@ -721,7 +895,7 @@
 					"name": "prebuilt",
 					"type": "boolean",
 					"required": false,
-					"description": "Deploy existing Build Output API files without building",
+					"description": "Deploy existing Build Output Specification files without building",
 					"default": false
 				},
 				{
@@ -772,6 +946,8 @@
 	],
 	"descriptions": {
 		"ai": "ai",
+		"containers": "Deploy and manage Containers applications on Cloudflare's global network",
+		"containers images": "Operations for images",
 		"d1": "D1 is Cloudflare's managed, serverless database with SQLite's SQL semantics, built-in disaster recovery, and Worker and HTTP API access.",
 		"d1 migrations": "Create, list, and apply D1 database migrations",
 		"registrar": "registrar",

package/dist/{abuse-reports-sDBTV0qZ.mjs → abuse-reports-D40QFl-y.mjs}

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import{t as e}from"./local-Be3lg_9E.mjs";import{f as t,g as n}from"./oauth-DuEONNgC.mjs";import{r}from"./auth-D3X9HYhD.mjs";import{t as i}from"./output-Ccqw2WOb.mjs";import{t as a}from"./dry-run-DL2V6yFm.mjs";import{t as o}from"./progress-BqQcF5QH.mjs";import{n as s,r as c,t as l}from"./body-parser-BshbixEq.mjs";import{n as u}from"./input-validation-QDIYu7Vb.mjs";import{a as d,i as f}from"./prompt-B0sWIs9c.mjs";import{t as p}from"./cli-types-DAYeL_Mj.mjs";function m(e){return e.positional(`report-id`,{type:`string`,description:`Abuse Report ID`,demandOption:!0}).option(`dry-run`,{type:`boolean`,description:`Validate and show what would happen without executing`,default:!1})}const h={command:`eligibility <report-id>`,describe:`Returns whether the report is currently appealable, along with the signals behind that decision: whether it already has an open appeal, how many appeals have been submitted against it, and whether it has at least one mitigation that an appeal could reverse.`,builder:m,handler:async s=>{if(s.dryRun){a({command:`cf abuse-reports appeals eligibility`,method:`GET`,url:`https://api.cloudflare.com/client/v4/accounts/${await n()??`<account-id>`}/abuse-reports/${s[`report-id`]==null?`<report-id>`:encodeURIComponent(String(s[`report-id`]))}/appeals/eligibility`,pathParams:{"report-id":String(s[`report-id`]??``)},bodyKind:`none`});return}let c=await r(s),l=s.local?e:await t();s.accountId=l,i(await o(`Loading`,async()=>c.abuseReports.appeals.eligibility({account_id:l,report_id:s[`report-id`]})),{successLabel:`Loaded`})}},g={command:`appeals`,describe:`Operations for appeals`,builder:e=>e.command(h).demandCommand(1,`Please specify a subcommand`),handler:()=>{}};function _(e){return e.positional(`report-param`,{type:`string`,description:`The report type to be submitted. Example: abuse_general`,demandOption:!0}).option(`act`,{type:`string`,description:`The act field`,choices:[`abuse_dmca`,`abuse_trademark`,`abuse_general`,`abuse_phishing`,`abuse_children`,`abuse_threat`,`abuse_registrar_whois`,`abuse_ncsei`]}).option(`comments`,{type:`string`,description:`Any additional comments about the infringement not exceeding 2000 characters`}).option(`company`,{type:`string`,description:`Text not exceeding 100 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`email`,{type:`string`,description:`A valid email of the abuse reporter. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`email2`,{type:`string`,description:"Should match the value provided in `email`"}).option(`name`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`reported-country`,{type:`string`,description:`Text containing 2 characters`}).option(`reported-user-agent`,{type:`string`,description:`Text not exceeding 255 characters`}).option(`tele`,{type:`string`,description:`Text not exceeding 20 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`title`,{type:`string`,description:`Text not exceeding 255 characters`}).option(`urls`,{type:`string`,description:`A list of valid URLs separated by ‘\\n’ (new line character). The list of the URLs should not exceed 250 URLs. All URLs should have the same hostname. Each URL should be unique. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`address1`,{type:`string`,description:`Text not exceeding 100 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`agent-name`,{type:`string`,description:`The name of the copyright holder. Text not exceeding 60 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`agree`,{type:`number`,description:"Can be `0` for false or `1` for true. Must be value: 1 for DMCA reports"}).option(`city`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`country`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).
+import{t as e}from"./local-DGiIS1uM.mjs";import{f as t,g as n}from"./oauth-DAa7SwkM.mjs";import{r}from"./auth-DY_Y2bXC.mjs";import{t as i}from"./output-BqDR9h74.mjs";import{t as a}from"./dry-run-ILZRVpnp.mjs";import{t as o}from"./progress-jYW64HY7.mjs";import{n as s,r as c,t as l}from"./body-parser-BGVbwPeM.mjs";import{n as u}from"./input-validation-1esLElok.mjs";import{a as d,i as f}from"./prompt-CyATfGUu.mjs";import{t as p}from"./cli-types-C3nVfpSG.mjs";function m(e){return e.positional(`report-id`,{type:`string`,description:`Abuse Report ID`,demandOption:!0}).option(`dry-run`,{type:`boolean`,description:`Validate and show what would happen without executing`,default:!1})}const h={command:`eligibility <report-id>`,describe:`Returns whether the report is currently appealable, along with the signals behind that decision: whether it already has an open appeal, how many appeals have been submitted against it, and whether it has at least one mitigation that an appeal could reverse.`,builder:m,handler:async s=>{if(s.dryRun){a({command:`cf abuse-reports appeals eligibility`,method:`GET`,url:`https://api.cloudflare.com/client/v4/accounts/${await n()??`<account-id>`}/abuse-reports/${s[`report-id`]==null?`<report-id>`:encodeURIComponent(String(s[`report-id`]))}/appeals/eligibility`,pathParams:{"report-id":String(s[`report-id`]??``)},bodyKind:`none`});return}let c=await r(s),l=s.local?e:await t();s.accountId=l,i(await o(`Loading`,async()=>c.abuseReports.appeals.eligibility({account_id:l,report_id:s[`report-id`]})),{successLabel:`Loaded`})}},g={command:`appeals`,describe:`Operations for appeals`,builder:e=>e.command(h).demandCommand(1,`Please specify a subcommand`),handler:()=>{}};function _(e){return e.positional(`report-param`,{type:`string`,description:`The report type to be submitted. Example: abuse_general`,demandOption:!0}).option(`act`,{type:`string`,description:`The act field`,choices:[`abuse_dmca`,`abuse_trademark`,`abuse_general`,`abuse_phishing`,`abuse_children`,`abuse_threat`,`abuse_registrar_whois`,`abuse_ncsei`]}).option(`comments`,{type:`string`,description:`Any additional comments about the infringement not exceeding 2000 characters`}).option(`company`,{type:`string`,description:`Text not exceeding 100 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`email`,{type:`string`,description:`A valid email of the abuse reporter. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`email2`,{type:`string`,description:"Should match the value provided in `email`"}).option(`name`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`reported-country`,{type:`string`,description:`Text containing 2 characters`}).option(`reported-user-agent`,{type:`string`,description:`Text not exceeding 255 characters`}).option(`tele`,{type:`string`,description:`Text not exceeding 20 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`title`,{type:`string`,description:`Text not exceeding 255 characters`}).option(`urls`,{type:`string`,description:`A list of valid URLs separated by ‘\\n’ (new line character). The list of the URLs should not exceed 250 URLs. All URLs should have the same hostname. Each URL should be unique. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`address1`,{type:`string`,description:`Text not exceeding 100 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`agent-name`,{type:`string`,description:`The name of the copyright holder. Text not exceeding 60 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`agree`,{type:`number`,description:"Can be `0` for false or `1` for true. Must be value: 1 for DMCA reports"}).option(`city`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).`}).option(`country`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).
 `}).option(`host-notification`,{type:`string`,description:`Notification type based on the abuse type. NOTE: Copyright (DMCA) and Trademark reports cannot be anonymous.
 `,choices:[`send`,`send-anon`]}).option(`original-work`,{type:`string`,description:`Text not exceeding 255 characters. This field may be released by Cloudflare to third parties such as the Lumen Database (https://lumendatabase.org/).
 `}).option(`owner-notification`,{type:`string`,description:`Notification type based on the abuse type. NOTE: Copyright (DMCA) and Trademark reports cannot be anonymous.