## Scope The same affordance on the manifests table for `docker` and `oci`, addressing a manifest by digest. The design disables Delete manifest on a manifest a parent index references; S14 already assigns that rule to the AR delete contract, so this step renders what the endpoint specifies rather than reproducing the rule as a client-side precondition. See [Spec row actions](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs/monolith/S14-version-list.md#row-actions-and-the-pull-command-drawer). The design's manifest row menu reads `View pull command`, `Copy digest`, `Manage tags`, `Download manifest`, `Delete manifest` ([Figma](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AR-concepting?node-id=3549-18014)). Only the delete item is this step's: `Manage tags` is Step 15 (#627405) and the rest are out of scope or already built. The confirmation copy differs by manifest kind, so this step supplies it per row rather than letting the modal derive it, the index variant at [3613-20029](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AR-concepting?node-id=3613-20029) and the signature variant at [3791-39878](https://www.figma.com/design/b5gaaEDjfxZbphoRQ3jVGv/AR-concepting?node-id=3791-39878), both quoted in Step 11 (#627401). **Refetch, not cache eviction** (decided 2026-09-09). The plan's Approach mandates eviction and forbids a refetch; that rule is dropped, for the reasons Step 11 (#627401) records. Copy `repositories/detail/artifacts_table.vue`: `refetchQueries` plus `awaitRefetchQueries: true`, a toast saying **scheduled for deletion** rather than deleted, and a per-row pending guard so a slow apply cannot be double-submitted. The mutation goes through the generalized helper in `graphql/utils/delete_artifact.js` that Step 11 provides. Nothing in `cache_update.js` changes. **This step threads two props that Step 12 does not have to.** `ArtifactRegistryManifestDelete` (**merged**, [!253536](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/253536), 2026-09-08) takes `name`, `imageId`, and `digest`. `manifests_table.vue` declares only `manifests`, `hiddenColumns`, `sort`, and `isLoading`, and `versions_section.vue` passes it neither the repository name nor the image id, though it already passes both to `versions_table.vue` as `name` and `artifact`. So this step widens the manifests table's props and the `versions_section.vue` call site, which Step 12 (#627402) does not touch. That is the one place these two otherwise-parallel steps differ in size, and it is worth knowing before the step is estimated as a copy of Step 12. **First slice.** Ships with the four surviving single deletes. - **Depends on:** Step 7 (Manifest and container tag delete mutations, **merged**), Step 11 (Shared artifact delete confirmation and cache eviction) - **Feature flag:** `artifact_registry_ui`, **dark**. - **Commit type:** `type::feature` ## Files - `ee/app/assets/javascripts/packages_and_registries/artifact_registry/repositories/versions/versions_section.vue` (Modify - pass the repository name and the image id through) - `ee/app/assets/javascripts/packages_and_registries/artifact_registry/repositories/versions/manifests_table.vue` (Modify - the row-menu delete item, and the two new props) - `ee/app/assets/javascripts/packages_and_registries/artifact_registry/graphql/mutations/delete_manifest.mutation.graphql` (Create) (No `cache_update.js` change: see the refetch decision above.) ## Shared seams `manifests_table.vue` is also touched by Step 14 (selection state) and Step 15 (the manage-tags entry point), each in its own region of the template. `cache_update.js` as Step 11. ## Acceptance As Step 12 (#627402), addressing the row by digest, and a referenced child manifest surfaces the `409` as an error on the row, naming the blocking digests it carried, rather than being pre-empted client-side or reported as a bare failure. A `409` shows no success toast and triggers no refetch, because nothing was deleted. ## Tests Jest spec update for `manifests_table.vue`. ## i18n / changelog The delete menu item label and its confirmation copy go to `locale/gitlab.pot`. No changelog, dark. ## Gating The plan MR, [artifact-registry!2201](https://gitlab.com/gitlab-org/ops/artifact-registry/-/merge_requests/2201), **merged on 2026-09-03**, so this gate is satisfied. Step MRs no longer open as Drafts on its account. Blocked on a **spec promotion MR**, which has no MR of its own yet. Both [monolith/S14](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs/monolith/S14-version-list.md) and [monolith/S06](https://gitlab.com/gitlab-org/ops/artifact-registry/-/blob/main/docs/specs/monolith/S06-version-detail.md) still carry Phase 1 prohibitions on rendering any delete affordance, and neither specifies a GraphQL surface, client rows, UX, or positive acceptance criteria for the deletes. The plan's Dependencies section lists what that MR must add, split by slice. S14's prohibition is the one covering this step. --- Step 13 of 19 in the monolith artifact delete surface plan, at `docs/plans/monolith/2026-09-01-artifact-delete-surface.md` on `main` in `gitlab-org/ops/artifact-registry`. **This issue is ahead of the plan file as of 2026-09-09.** A props gap on `manifests_table.vue` is recorded, which Step 12 does not have. The plan has not been amended, so where the two disagree, this issue is current. **Plan-level correction owed.** The plan file's `## Approach` still mandates cache eviction and forbids a refetch, and its Step 11 still specifies a node-eviction primitive. Neither has been amended. Until it is, these issues are the current source for the refetch decision. Parent: gitlab-org/gitlab#627172