Part of epic &22453 (Repository detail, monolith/S05). Covers Steps 10 to 14 of the remote plan, `docs/plans/monolith/2026-08-20-repository-detail-remote.md` in the artifact-registry repo. The remote detail page's cache-eviction write surface, its schema connect, and two sidebar presentation rules. Steps 10 to 13 form one chain: the clear-cache flow, its failure paths, the per-row delete that reuses both, then the join that drops the `@client` directives. Step 14 is unrelated to eviction and rides here because it is presentation-only on the same page. Every step is dark behind `artifact_registry_ui`; no changelog, since that entry rides the flag-default-on merge request. Application paths sit under `ee/app/assets/javascripts/packages_and_registries/artifact_registry/`, with Jest specs under `ee/spec/frontend/packages_and_registries/artifact_registry/`. <details> <summary>Implementation details</summary> **Step 10: Clear cache** (`type::feature`) - `repositories/detail/cache_eviction_modal.vue` (Create): the scope-parameterized confirmation, its three statements, its cancel path, and its focus handling. It is parameterized from the start, because Step 12 mounts it with a different scope, and its accessible name carries that scope. - `repositories/detail/repository_actions.vue` (Modify): the Clear cache item, remote only, in the position the spec's kebab table fixes, and the mutation it issues. - `graphql/mutations/clear_repository_cache.mutation.graphql` (Create): wholly `@client`, with its own operation name, which `@graphql-eslint/unique-operation-name` enforces app-wide. - `graphql/mock_resolvers.js` (Modify): a `Mutation` resolver answering the accepted outcome. `graphql/utils/cache_update.js` (Modify): a helper dropping the details entry's artifact connection fields, beside the two that already maintain that entry by hand. - `constants.js` (Modify) and `locale/gitlab.pot` (repository root, regenerated). `repositories/detail/repository_detail.stories.js` (Modify): confirmation and accepted stories. - Specs: `repositories/detail/cache_eviction_modal_spec.js` (Create); `repository_actions_spec.js`, `graphql/cache_update_spec.js`, `graphql/mock_resolvers_spec.js`, `graphql/mutations_spec.js` (Modify). - The confirmation says the two things the contract makes true and a user would otherwise assume away: the upstream is untouched and a later pull re-caches the coordinate, and the clear is applied after acceptance rather than instantly. The images bulk route's own description states both, so the copy has contract backing. - **No pending marker, no polling, and no refetch control.** The spec states the race outright: the refetch can beat the apply, a `202` carries no handle to poll, and rows still present contradict a message that claimed only acceptance. A user who wants to see the result reloads the page. - The document declares nothing in `typedefs.graphql` and keeps the mounted field, input, and payload names from the start, following the merged `packages` precedent. **The first task is to confirm that** the enabled `@graphql-eslint` rules include no schema-existence check. That is read off the rule list in `eslint.config.mjs` rather than observed, so if one fires, the field takes a `local` prefix and Step 13 renames it. **Step 11: Eviction failure handling** (`type::feature`) - `repositories/detail/cache_eviction_modal.vue` and `repository_actions.vue` (Modify): the rejected branch, the alert, and the retry. - `graphql/mock_resolvers.js` (Modify): the rejected and `503` outcomes, so both are drivable in a browser. `constants.js`, `locale/gitlab.pot`, and `repository_detail.stories.js` (Modify). - Specs (Modify): `cache_eviction_modal_spec.js`, `repository_actions_spec.js`, `graphql/mock_resolvers_spec.js`. - A rejected eviction changes nothing on the page and renders an alert naming the failure, because no eviction was accepted. The retry is offered on a `503` from either collection's bulk route, both of which declare one, and on no other failure. That is safe because AR recorded no job and deleted nothing. - **Each alert states its `captureError` rather than inheriting one.** The merged sibling `connection_section.vue` sets `captureError: true`, so the tree has a convention the plans never named, and the right answer differs by path. A payload rejection is AR refusing a request it understood, so it captures nothing. A transport failure or a `5xx` captures. The `503` retry path sits with the first, since the retry is the response to it. **Step 12: Delete cache entry on a remote row** (`type::feature`) - `repositories/detail/artifacts_table.vue` (Modify): the row kebab on a remote row, and its actions column. - `graphql/mutations/delete_cached_artifact.mutation.graphql` (Create): wholly `@client`, with its own operation name. `graphql/mock_resolvers.js` (Modify): a resolver answering the accepted and already-gone outcomes. `graphql/utils/cache_update.js` (Modify): reuse the Step 10 helper for the row's subject. - `constants.js`, `locale/gitlab.pot`, and `repository_detail.stories.js` (Modify). Specs (Modify): `artifacts_table_spec.js`, `cache_eviction_modal_spec.js`, `graphql/mock_resolvers_spec.js`. - A hosted row carries no actions, so the row kebab renders on a remote row alone. The hosted row's Delete package is a hosted artifact write rather than an eviction and stays out of scope. - This route differs from the bulk one on a missing target: AR answers `404` rather than a no-op `202`. So the rejected path covers a target already gone, and it offers no retry, the `503` being the bulk route's alone. **Step 13: Connect the remote eviction path to the schema** (`type::feature`) - `graphql/mutations/clear_repository_cache.mutation.graphql` and `delete_cached_artifact.mutation.graphql` (Modify): drop `@client`, which puts both documents under `graphql-verify`. - `graphql/mock_resolvers.js` (Modify): drop the two `Mutation` resolvers. The remaining local entries stay while their backends are unmerged. - `ee/spec/frontend/fixtures/artifact_registry/repository_cache_eviction.rb` (Create). - Specs (Modify): `cache_eviction_modal_spec.js`, `repository_actions_spec.js`, `artifacts_table_spec.js`, `graphql/mock_resolvers_spec.js`, each re-pointed at the schema over the real fixture. - `ee/spec/features/artifact_registry/repositories_spec.rb` (Modify): a `:js` example clearing a remote repository's cache over an `ArtifactRegistry::Client` double, carrying the automated accessibility assertion over the rendered confirmation. - Because the documents declared nothing and kept the mounted names, dropping the directives is the whole change, unless Step 10's check found a schema-existence rule firing. - The step carries `type::feature` rather than `type::maintenance`, matching the merged hosted plan's own connect step on this page, and the rule that dark scaffolding with no user-visible effect is still feature work. **Step 14: Withheld Downloads and the stacked sidebar** (`type::feature`) - `repositories/detail/repository_sidebar.vue` (Modify): withhold Downloads by format and drop the not-authoritative qualifier. `repositories/detail/repository_detail.vue` (Modify): the responsive grid. - `constants.js` (Modify): remove any not-authoritative copy the sidebar carried. `locale/gitlab.pot` (regenerated). `repository_detail.stories.js` (Modify): a narrow-viewport story. Spec (Modify): `repository_sidebar_spec.js`. - **Downloads renders on Maven only, on hosted and remote alike.** The figure was previously rendered everywhere and qualified as not authoritative. The spec now withholds it where nothing writes it, on the grounds that a zero the user cannot distinguish from real traffic is worse than no figure. - **The sidebar stacks below the main column at narrow viewports**, following the monolith's standard detail-page layout. No criterion asserts it; it is in the spec's layout section. - The two ride together because neither is large enough for a step of its own and both are presentation-only on one page. They are not folded into plan Step 7, whose merge request is under review. </details> ## Acceptance Step 10: - Clear cache renders in the remote page kebab and in no hosted one. - Choosing it opens the confirmation, which names the scope, says the upstream is untouched and the coordinate re-caches on the next pull, and says the clear is applied after acceptance. - Canceling closes it, issues nothing, and returns focus to the item. Confirming issues the mutation once. - A resolved mutation reports acceptance rather than completion, reports no count, evicts the details entry's artifact connection, and refetches the connection and the repository once. A row still present after the refetch renders no error and no pending affordance anywhere on the page. - The acceptance announces through a live region. The modal's accessible name carries its scope. Step 11: - A rejected mutation leaves the page unchanged and renders an alert. - The alert offers a retry on a `503` from either collection's bulk route and not on other failures. - The rejection announces through the live region. Step 12: - Delete cache entry renders on each remote artifact row and on no hosted row. - Choosing it opens the confirmation naming that one package or image, and canceling sends nothing. - A resolved mutation reports acceptance without a count and refetches the connection. - An already-gone target renders the alert with no retry offered. Step 13: - With the directives gone, both documents validate in `graphql-verify`. - Each affordance issues its mounted mutation with the repository's slug and name, and the single-artifact one additionally with the artifact's id. - The accepted, rejected, and `503`-retry behaviors are unchanged from the mocked path. - The `:js` example clears a remote repository's cache in a browser and passes the automated accessibility check. Step 14: - The stats block renders Downloads on a `maven` repository and renders no Downloads figure on `npm`, `docker`, or `oci`, on hosted and on remote alike, whatever `downloadsCount` the stubbed response carries. - The sidebar stacks below the main column at narrow viewports. ## Dependencies - Step 10 and Step 14 have no predecessor, in plan or external. Both can open at once. - Step 11 depends on Step 10. Step 12 depends on Step 11 and on plan Step 6, whose merge request !251515 has merged. - Step 13 depends on Steps 3, 11, and 12. Step 3's mutations were mounted by !252723, which has merged, so the schema half of that dependency is discharged. - Step 4 removes the kebab item that Steps 10 and 11 add a sibling to, in `repository_actions.vue` and in its spec. It is tracked in #627312. Whichever lands second rebases. - Steps 10 to 12 all touch `cache_eviction_modal.vue`, `repository_actions.vue`, `mock_resolvers.js`, `constants.js`, and `locale/gitlab.pot`. They are a strict chain, so each rebases on the one before it rather than in parallel. - Against a running AR, Step 12 sits behind the per-format remote read stores, and Step 13's `:js` example behind the eviction handler arms and the remote bulk passes. The Status table of `docs/plans/2026-08-13-s17-phase6-virtual-remote-repositories.md` is the live view of both. No gate holds a merge request here: the Jest specs run over the local Apollo layer, the RSpec example doubles the client, and the flag is disabled. ## Not in scope - **A pending marker, polling, or a refetch control on an accepted eviction.** The spec rules all three out; the `202` carries no handle to poll. - **Clear all caches.** No declared path in `api/openapi/v1.yaml` clears a virtual repository's upstream caches. - **The upstream row's Clear cache.** It calls the same mutation Step 10's item calls, with the upstream as its subject, and it is drawn on the virtual repository's table. Plan Step 3 mounted a mutation that already takes a repository name and asserts the other-repository subject, so the virtual plan needs no new mutation, only the affordance and the confirmation naming the upstream. - **The hosted row's Delete package.** It is a hosted artifact write rather than a cache eviction. - **Pre-gating an eviction on an ability.** AR checks `delete_artifact`, an artifact ability on a repository page, so the affordance's gating follows neither the Edit button beside it nor the read that got the viewer here. The mechanism waits on monolith/S07, so an unauthorized eviction fails after the user selects it.