Add diagrams to artifact and run deletion documentation (#1560)

- Added a comprehensive diagram illustrating the artifact garbage
collection process, clarifying the soft-delete mechanism and subsequent
file deletion.
- Introduced a new section detailing the run deletion workflow,
including options for deleting associated artifacts and handling Model
Registry links.

Resolves DOCS-1005

<!-- preview-links-comment -->
📄 **[View preview links for changed
pages](#1560 (comment)

Author: johndmulhausen

content/en/guides/core/artifacts/manage-data/delete-artifacts.md

@@ -10,14 +10,54 @@ title: Delete an artifact
 
 Delete artifacts interactively with the App UI or programmatically with the W&B SDK. When you delete an artifact, W&B marks that artifact as a *soft-delete*. In other words, the artifact is marked for deletion but files are not immediately deleted from storage. 
 
-The contents of the artifact remain as a soft-delete, or pending deletion state, until a regularly run garbage collection process reviews all artifacts marked for deletion. The garbage collection process deletes associated files from storage if the artifact and its associated files are not used by a previous or subsequent artifact versions. 
+The contents of the artifact remain as a soft-delete, or pending deletion state, until a regularly run garbage collection process reviews all artifacts marked for deletion. The garbage collection process deletes associated files from storage if the artifact and its associated files are not used by a previous or subsequent artifact versions.
+
+## Artifact garbage collection workflow
+
+The following diagram illustrates the complete artifact garbage collection process:
+
+```mermaid
+graph TB
+    Start([Artifact Deletion Initiated]) --> DeleteMethod{Deletion Method}
+    
+    DeleteMethod -->|UI| UIDelete[Delete via W&B App UI]
+    DeleteMethod -->|SDK| SDKDelete[Delete via W&B SDK]
+    DeleteMethod -->|TTL| TTLDelete[TTL Policy Expires]
+    
+    UIDelete --> SoftDelete[Artifact Marked as<br/>'Soft Delete']
+    SDKDelete --> SoftDelete
+    TTLDelete --> SoftDelete
+    
+    SoftDelete --> GCWait[(Wait for<br/>Garbage Collection<br/>Process)]
+    
+    GCWait --> GCRun[Garbage Collection<br/>Process Runs<br/><br/>- Reviews all soft-deleted artifacts<br/>- Checks file dependencies]
+    
+    GCRun --> CheckUsage{Are files used by<br/>other artifact versions?}
+    
+    CheckUsage -->|Yes| KeepFiles[Files Kept in Storage<br/><br/>- Artifact marked deleted<br/>- Files remain for other versions]
+    CheckUsage -->|No| DeleteFiles[Files Deleted from Storage<br/><br/>- Artifact fully removed<br/>- Storage space reclaimed]
+    
+    KeepFiles --> End([End])
+    DeleteFiles --> End
+    
+    style Start fill:#e1f5fe,stroke:#333,stroke-width:2px,color:#000
+    style SoftDelete fill:#fff3e0,stroke:#333,stroke-width:2px,color:#000
+    style GCRun fill:#f3e5f5,stroke:#333,stroke-width:2px,color:#000
+    style KeepFiles fill:#e8f5e9,stroke:#333,stroke-width:2px,color:#000
+    style DeleteFiles fill:#ffebee,stroke:#333,stroke-width:2px,color:#000
+    style End fill:#e0e0e0,stroke:#333,stroke-width:2px,color:#000
+``` 
 
 The sections in this page describe how to delete specific artifact versions, how to delete an artifact collection, how to delete artifacts with and without aliases, and more. You can schedule when artifacts are deleted from W&B with TTL policies. For more information, see [Manage data retention with Artifact TTL policy]({{< relref "./ttl.md" >}}).
 
 {{% alert %}}
 Artifacts that are scheduled for deletion with a TTL policy, deleted with the W&B SDK, or deleted with the W&B App UI are first soft-deleted. Artifacts that are soft deleted undergo garbage collection before they are hard-deleted.
 {{% /alert %}}
 
+{{% alert %}}
+Deleting an entity, project, or artifact collection will also trigger the artifact deletion process described on this page. When deleting a run, if you choose to delete associated artifacts, those artifacts will follow the same soft-delete and garbage collection workflow.
+{{% /alert %}}
+
 ### Delete an artifact version
 
 To delete an artifact version:
@@ -27,7 +67,7 @@ To delete an artifact version:
 3. On the right hand side of the workspace, select the kebab dropdown.
 4. Choose Delete.
 
-An artifact version can also be deleted programatically via the [delete()]({{< relref "/ref/python/sdk/classes/artifact.md#delete" >}}) method. See the examples below. 
+An artifact version can also be deleted programmatically via the [delete()]({{< relref "/ref/python/sdk/classes/artifact.md#delete" >}}) method. See the examples below. 
 
 ### Delete multiple artifact versions with aliases
 
@@ -71,6 +111,18 @@ for artifact_version in runs.logged_artifacts():
         artifact.delete(delete_aliases=True)
 ```
 
+### Protected aliases and deletion permissions
+
+Artifacts with protected aliases have special deletion restrictions. [Protected aliases]({{< relref "/guides/core/registry/model_registry/access_controls.md" >}}) are aliases in the Model Registry that registry admins can set to prevent unauthorized deletion.
+
+{{% alert %}}
+**Important considerations for protected aliases:**
+- Artifacts with protected aliases cannot be deleted by non-registry admins
+- Within a registry, registry admins can unlink protected artifact versions and delete collections/registries that contain protected aliases
+- For source artifacts: if a source artifact is linked to a registry with a protected alias, it cannot be deleted by any user
+- Registry admins can remove the protected aliases from source artifacts and then delete them
+{{% /alert %}}
+
 ### Delete all versions of an artifact that do not have an alias
 
 The following code snippet demonstrates how to delete all versions of an artifact that do not have an alias. Provide the name of the project and entity for the `project` and `entity` keys in `wandb.Api`, respectively. Replace the `<>` with the name of your artifact:

content/en/guides/models/track/runs/_index.md

@@ -536,6 +536,46 @@ Once a run with a specific ID is deleted, its ID may not be used again. Trying t
 For projects that contain a large number of runs, you can use either the search bar to filter runs you want to delete using Regex or the filter button to filter runs based on their status, tags, or other properties. 
 {{% /alert %}}
 
+### Run deletion workflow
+
+The following diagram illustrates the complete run deletion process, including the handling of associated artifacts and Model Registry links:
+
+```mermaid
+graph TB
+    Start([User Initiates<br/>Run Deletion]) --> RunSelect[Select Runs<br/>to Delete]
+    
+    RunSelect --> DeletePrompt{Delete Associated<br/>Artifacts?}
+    
+    DeletePrompt -->|No| DeleteRunOnly[Delete Run Only<br/><br/>- Run metadata removed<br/>- Artifacts remain available<br/>- Can still access artifacts]
+    
+    DeletePrompt -->|Yes| CheckArtifacts[Check for<br/>Associated Artifacts]
+    
+    CheckArtifacts --> HasRegistry{Artifacts Linked to<br/>Model Registry?}
+    
+    HasRegistry -->|Yes| RegistryWarning[⚠️ Warning<br/><br/>Registry models will be deleted<br/>Production aliases affected]
+    HasRegistry -->|No| DirectDelete
+    
+    RegistryWarning --> ConfirmRegistry{Confirm Registry<br/>Model Deletion?}
+    
+    ConfirmRegistry -->|No| DeleteRunOnly
+    ConfirmRegistry -->|Yes| DirectDelete[Delete Run + Artifacts<br/><br/>- Run metadata removed<br/>- Artifacts permanently deleted<br/>- Registry links removed<br/>- Cannot be recovered]
+    
+    DeleteRunOnly --> PartialEnd([Run Deleted<br/>Artifacts Preserved])
+    DirectDelete --> FullEnd([Run + Artifacts<br/>Permanently Deleted])
+    
+    style Start fill:#e1f5fe,stroke:#333,stroke-width:2px,color:#000
+    style DeletePrompt fill:#fff3e0,stroke:#333,stroke-width:2px,color:#000
+    style RegistryWarning fill:#ffecb3,stroke:#333,stroke-width:2px,color:#000
+    style DirectDelete fill:#ffebee,stroke:#333,stroke-width:2px,color:#000
+    style DeleteRunOnly fill:#e8f5e9,stroke:#333,stroke-width:2px,color:#000
+    style PartialEnd fill:#c8e6c9,stroke:#333,stroke-width:2px,color:#000
+    style FullEnd fill:#ffcdd2,stroke:#333,stroke-width:2px,color:#000
+```
+
+{{% alert title="Important" %}}
+When you delete a run and choose to delete associated artifacts, the artifacts are permanently removed and can't be recovered, even if the run is restored later. This includes models linked to the Model Registry.
+{{% /alert %}}
+
 ## Organize runs 
 
 This section provides instructions on how to organize runs using groups and job types. By assigning runs to groups (for example, experiment names) and specifying job types (for example, preprocessing, training, evaluation, debugging), you can streamline your workflow and improve model comparison.
@@ -547,7 +587,7 @@ Each run in W&B can be categorized by **group** and a **job type**:
 - **Group**: a broad category for the experiment, used to organize and filter runs.
 - **Job type**: the function of the run, such as `preprocessing`, `training`, or `evaluation`.
 
-The proceeding [example workspace](https://wandb.ai/stacey/model_iterz?workspace=user-stacey), trains a baseline model using increasing amounts of data from the Fashion-MNIST dataset. The workspace uses colorts to represent the amount of data used:
+The proceeding [example workspace](https://wandb.ai/stacey/model_iterz?workspace=user-stacey), trains a baseline model using increasing amounts of data from the Fashion-MNIST dataset. The workspace uses colors to represent the amount of data used:
 
 - **Yellow to dark green** indicate increasing amounts of data for the baseline model.
 - **Light blue to violet to magenta** indicate amounts of data for a more complex "double" model with additional parameters.