# (NEW!) Delete Metadata Cascade

Permanently remove a metadata cascade. Deletion is blocked if the cascade is featured, and blocked if it is still referenced by a table (and, transitively, any template that reaches it through that table).

Business Rules:
- Checks run in this order: not found, then featured, then in-use.

The user submitting the request must have the Metadata Template Management admin privilege.

Endpoint: DELETE /metadata/cascades/{id}
Version: 1.5
Security: ApiKeyAuth, BasicAuth

## Header parameters:

  - `Authorization` (string, required)
    Provided by Authentication Token creation operation.

## Path parameters:

  - `id` (string, required)
    The unique ID of the cascade to delete.
    Example: "b7e41f2a-6c9d-4a17-8f3b-2d5c8a0e3f61"

## Response 400 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)

## Response 401 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)

## Response 403 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)

## Response 404 fields (application/json):

  - `status` (string)
    Example: "error"

  - `message` (string)

## Response 409 fields (application/json):

  - `message` (string)

  - `usedIn` (object)
    Present only for the in-use conflict.

  - `usedIn.metadataTables` (array)

  - `usedIn.metadataTables.id` (string)

  - `usedIn.metadataTables.name` (string)

  - `usedIn.metadataTemplates` (array)


## Response 204 fields