Part of epic &22453 (Repository detail, monolith/S05). Covers Steps 1 to 8 of the virtual plan, `docs/plans/monolith/2026-09-10-repository-detail-virtual.md` in the artifact-registry repo, which lands in its own plan MR before any step MR opens. The virtual repository detail page, across all four MVP formats (`maven`, `npm`, `docker`, `oci`). Steps 1 to 3 are the Ruby client read and the GraphQL field that `monolith/S07` Phase 3 declares and no S07 Phase 3 plan builds, so this plan carries them and names the ownership deviation. Steps 4 to 7 are the Vue work that turns the shipped hosted and remote detail page into one that also serves a virtual repository, built over the local Apollo layer so they run parallel with the schema. Step 8 connects the view to the schema. 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/`, Ruby under `ee/lib/artifact_registry/` and `ee/app/graphql/`, with specs under `ee/spec/`. <details> <summary>Implementation details</summary> **Step 1: Client upstream-list read** (`type::feature`, no predecessor) - `ee/lib/artifact_registry/client.rb` (Modify): `upstream_repositories(slug:, repository_name:, format:)` issuing `GET .../repositories/:name/:format/upstream_repositories` and returning the whole ordered array, not a page object, because the route is unpaginated by contract. A `404` resolves `nil` through `nil_on_missing`. - `ee/lib/artifact_registry/upstream_repository_association.rb` and `upstream_repository_summary.rb` (Create): value objects for the association (`id`, `position`, `upstream_repository`) and the summary (`id`, `name`, `format`, `kind`). - Specs: `client_spec.rb` (Modify), the two value-object specs (Create), one positive case per format. **Step 2: Kind gate on the artifact connections** (`type::feature`, no predecessor) - `ee/lib/artifact_registry/repository.rb` (Modify): `hosted?`, `remote?`, `virtual?`. - `ee/app/graphql/resolvers/artifact_registry/packages_resolver.rb` and `images_resolver.rb` (Modify): return nil on `virtual?` before the client is acquired. Today the gate is format-only, so a virtual Maven repository calls AR. - Specs (Modify): the repository, resolver, and packages and images request specs, one virtual case per format asserting no client call. **Step 3: Upstream list field and types** (`type::feature`, after Steps 1 and 2) - `ee/app/graphql/types/artifact_registry/upstream_repository_kind_enum.rb`, `upstream_repository_summary_type.rb`, `upstream_repository_association_type.rb` (Create); `resolvers/artifact_registry/upstream_repositories_resolver.rb` (Create); `types/artifact_registry/repository_details_type.rb` (Modify): the `upstreamRepositories` plain-list field, `null: true`, `FieldCallCount` limit 1, null on hosted and remote without an AR call. - The summary's `kind` is a two-value enum (`HOSTED`, `REMOTE`), the contract's own narrowing; a value outside it nulls the field with a top-level error. - The four regenerated `graphql-verify` artifacts. Specs: three type specs, the resolver spec, and `artifact_registry_repository_upstream_repositories_spec.rb` (Create); `repository_details_type_spec.rb` (Modify, the exact field list). **Step 4: Virtual main region and the upstream table** (`type::feature`, no predecessor) - `constants.js` (Modify): `REPOSITORY_KIND_VIRTUAL`, the table fields, the typename, strings. - `graphql/queries/get_repository_upstream_repositories.query.graphql` (Create, `@client`), `graphql/typedefs.graphql` and `graphql/mock_resolvers.js` (Modify), `graphql/mock_upstream_repositories.js` (Create), `graphql/cache_config.js` (Modify): the association keyed on `id`, the summary embedded. - `repositories/detail/repository_detail.vue` (Modify): a third smart query skipped unless the repository is virtual, no artifact connection on virtual, kind-aware loading, emptiness, and not-found, the upstream table in the main region and no pager. - `repositories/detail/upstream_repositories_table.vue` (Create): Order, Repository, Type; the Order header's keyboard-operable help affordance; no sort, filter, reorder, or row link; format renders nowhere. - Stories, `locale/gitlab.pot`, and specs: `repository_detail_spec.js`, `upstream_repositories_table_spec.js` (Create), `mock_resolvers_spec.js`, `cache_config_spec.js`, `queries_spec.js`, `mock_data.js`. **Step 5: Virtual sidebar stats** (`type::feature`, after Step 4) - `repositories/detail/repository_sidebar.vue` (Modify): an upstream-count input; on virtual the stats block renders Repositories alone, from the list's length, and nothing when the list failed. `repository_detail.vue` (Modify): pass the count. Constants, pot, stories, `repository_sidebar_spec.js`, `repository_detail_spec.js`. **Step 6: Virtual empty state and the setup entry** (`type::feature`, after Step 4) - `repositories/detail/upstream_repositories_empty_state.vue` (Create): illustration, heading, support text, documentation link, and an empty action slot named for the S07 Phase 3 Add repository affordance. `repository_detail.vue` (Modify): render it on an empty list. - Asserts the Setup instructions button hides on the empty virtual page, and that the populated virtual header renders the Virtual badge, no upstream URL, and an Install-only drawer with the tool set per format. Constants, pot, stories, specs. **Step 7: Upstream row actions** (`type::feature`, after Step 4) - `repositories/detail/upstream_repository_actions.vue` (Create): Edit repository on every row (a router link to the shipped edit route with the upstream's name), Clear cache on a remote-source row only, issuing the shipped `clearRepositoryCacheMutation` with the upstream's name, toasting acceptance without a count, evicting the upstream's own details entry through `evictUpdatedRepositoryDetails`, alerting on rejection. No confirmation, matching the shipped remote affordances; the spec is amended to match in the plan MR. Remove repository is not mounted; its position is named. - `upstream_repositories_table.vue` (Modify): the actions column. Constants, pot, stories, specs including `repository_actions_spec.js` asserting the virtual page kebab carries Copy repository URL and Delete repository only. **Step 8: Connect the virtual detail view to the schema** (`type::feature`, after Steps 3, 5, 6, 7) - Drop `@client` from the upstream document; remove the upstream entries from `typedefs.graphql` and `mock_resolvers.js`; delete `mock_upstream_repositories.js`. - `ee/spec/frontend/fixtures/artifact_registry/repository_upstream_repositories.rb` (Create); re-point the Jest specs at the fixture; `ee/spec/features/artifact_registry/repositories_spec.rb` (Modify): a `:js` example rendering a virtual repository's upstream table over stubbed AR reads, with the automated accessibility assertion. </details> ## Acceptance Step 1: the method issues its route with slug, name, and format encoded for each of the four formats; returns the array in AR's order with no cursors; `404` returns `nil`; `401`/`403` raise the authorization error; `5xx` raises the unavailable error; a non-array body raises. Step 2: on a virtual repository of each format the matching connection resolves null and the client receives no list call; hosted and remote are unchanged. Step 3: on a virtual repository the field returns the whole array ordered by `position` with each element's fields, per format; a 20-upstream list issues exactly one AR call; the field resolves null on hosted and remote without a client call; a `404` resolves null; a `5xx` renders the service-unavailable error with the repository still rendered; with the flag off it resolves null without a client call. Step 4: the virtual page issues the upstream query and no artifact query and renders the table with no pager; hosted and remote issue no upstream query; the table renders Order, Repository, and Type in AR's order, a kind badge per row, no format on a mixed `docker` and `oci` list, no row link, no sort, filter, or reorder control; the Order help affordance is keyboard operable and states the resolution-order text; a null list renders not-found; a failed list keeps the header and sidebar with the alert in the main region. Step 5: the virtual stats block renders Repositories alone, equal to the list's length, whatever `sizeBytes`, `downloadsCount`, and `artifactsCount` say; it renders nothing when the list failed; Connection and Caching period render on remote alone. Step 6: an empty list renders the empty state with no table and no Setup instructions button, the stats block hidden, and an empty action slot; the populated header renders the Virtual badge, no URL, and an Install-only drawer with the format's tool set. Step 7: a hosted-source row carries Edit repository alone; a remote-source row adds Clear cache; no row carries Remove repository; Clear cache issues the mutation once with the upstream's name, toasts acceptance without a count, and alerts on rejection; the item's accessible name carries the upstream; the virtual page kebab carries Copy repository URL and Delete repository only. Step 8: the document validates in `graphql-verify`; the connected specs pass over the fixture; the `:js` example renders the upstream table and passes the automated accessibility check. ## Dependencies - Steps 1, 2, and 4 have no predecessor and can open once the plan MR merges. Step 3 depends on Steps 1 and 2. Steps 5, 6, and 7 depend on Step 4. Step 8 depends on Steps 3, 5, 6, and 7. - **No step waits on AR.** Every step merges against WebMock stubs, mock resolvers, or a client double behind the disabled flag. What waits on AR is the live path: while AR's create route answers `kind=virtual` with `422` and no handler serves `listUpstreamRepositories`, no virtual repository exists through the API and no upstream list can be read; once the S17 Phase 6 plan's steps 36 to 42 land, the page renders against a real virtual repository. The Status table of `docs/plans/2026-08-13-s17-phase6-virtual-remote-repositories.md` is the live view. - Open MRs touching the same files, each an append or sibling edit that the second to land rebases: `constants.js` (nine open MRs), `typedefs.graphql` and `mock_resolvers.js` (the S06 steps and the manifest detail page), `repository_details_type.rb` (S06 steps), `client.rb` (four open MRs), `repository_detail.vue` (!254630 and !254345, the DetailLayout adoption, which reshapes the template Step 4 branches). ## Not in scope - **Add repository and Remove repository.** `monolith/S07` Phase 3 writes with no plan and no mutation behind them; Steps 6 and 7 name their mount points and assert them empty. - **Clear all caches.** No route in `api/openapi/v1.yaml` clears a virtual repository's upstream caches; the item renders nowhere until one is contracted and served. - **A confirmation on the upstream row's Clear cache.** Follows the shipped remote affordances, which confirm nothing; the plan MR amends the spec to match. - **Per-row URL, health, visibility, and Size; the filter bar; the Size and Downloads figures; the Virtual repository associations section; tabs.** Spec deferrals and omissions. - **Kind gates on the single `package` and `image` reads.** `monolith/S14` and `monolith/S06` own those fields.