Part of epic &22453 (Repository detail, monolith/S05). Covers Steps 4 and 9 of the remote plan, `docs/plans/monolith/2026-08-20-repository-detail-remote.md` in the artifact-registry repo. Two page-shell changes the remote detail page needs: the setup drawer's entry point moves out of the kebab into a persistent header button with per-kind tabs, and the remote artifact list gets its own empty state. Dark behind `artifact_registry_ui`; no changelog. 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 4: Setup instructions entry point and per-kind tabs** (`type::feature`) - `repositories/detail/repository_header.vue` (Modify): the persistent Setup instructions button beside Edit, and the drawer it now owns. - `repositories/detail/repository_actions.vue` (Modify): drop the kebab item and the drawer. - `repositories/detail/setup_instructions/setup_drawer.vue` (Modify): a `kind` prop. The Publish tab renders on hosted only, so a remote repository carries an Install tab alone. - `constants.js` (Modify): the button's label. `locale/gitlab.pot` (repository root, regenerated). - `repositories/detail/repository_detail.stories.js` (Modify): an open-drawer story on a remote repository, for the `test-storybook` axe run. - Specs (Modify): `repositories/detail/repository_header_spec.js`, `repository_actions_spec.js`, `setup_instructions/setup_drawer_spec.js`. - **This step edits a shipped hosted surface from a remote slice, which the plan names as an accepted trade.** A remote-only button would leave the hosted page carrying both a kebab item and a button for identical content. - Two conditions the button keeps. The shipped kebab item rendered only when the injected client base URL was present, and the button keeps that condition, so "persistent" means "not behind a menu" rather than "unconditional". And the spec holds the entry out of a virtual repository whose upstream list is empty; that input arrives with virtual detail, so this step renders the button on hosted and remote and leaves the carve-out to the plan that has a list to be empty. - The empty state's inline steps are unchanged, so `artifacts_empty_state.vue` is untouched by this step. **Step 9: Remote empty state** (`type::feature`) - `repositories/detail/artifacts_section.vue` (Modify): on remote, render the table with its nothing-cached row in place of `artifacts_empty_state.vue`. - `repositories/detail/artifacts_table.vue` (Modify): the empty body row. - `constants.js` (Modify): the nothing-cached copy. `locale/gitlab.pot` (repository root, regenerated). - `repositories/detail/repository_detail.stories.js` (Modify): a remote empty story. - Specs (Modify): `repositories/detail/artifacts_section_spec.js`, `artifacts_table_spec.js`, `repository_sidebar_spec.js`. - A remote repository fills on its first pull rather than on a publish, so there is no onboarding action to offer inline. The header's Setup instructions button stays, which is why this step sits beside Step 4. - The trigger is the artifact connection's first page, never the buffered `artifactsCount`. - The sidebar hides its stats block through the existing `hideStats` prop, and Last updated falls away under the existing null rule rather than a rule of this step's. </details> ## Acceptance Step 4: - The header renders a persistent Setup instructions button on a hosted and on a remote repository, and neither kebab carries a setup item. - The button is absent when no client base URL is injected, the condition the kebab item already carried. - The drawer has Install and Publish tabs on hosted and an Install tab alone on remote, with the tool set following the format and the repository's own URL in every snippet. - The drawer traps focus and returns it to the button on close. Step 9: - An empty first page on a remote repository renders the column headers plus the nothing-cached message, with no illustration and no inline setup steps. - It keeps the header's Setup instructions button and hides the stats block, regardless of the `artifactsCount` value. - A hosted repository's empty state is unchanged. ## Dependencies - The remote plan's merge request must merge before any merge request here opens. - Step 4 has no predecessor, in plan or external. The drawer's content is built client-side and makes no AR call. - Step 9 depends on plan Step 6 (the remote artifact table), which is not in this issue. Its merge request opens after that step lands. - Step 4 removes the kebab item that the plan's cache-eviction steps add a sibling to, in the component and in its spec. Whichever lands second rebases. - Against a running AR, Step 9 sits behind the per-format remote read stores, tracked in the Status table of `docs/plans/2026-08-13-s17-phase6-virtual-remote-repositories.md`. No gate holds either merge request: the Jest specs run over the local Apollo layer and the flag is disabled. ## Not in scope - **The virtual carve-out on the setup entry point.** The spec holds the button out of a virtual repository whose upstream list is empty. There is no upstream list on this page yet, so the assertion belongs to the virtual detail plan. - **The hosted empty state.** It ships and is asserted here only as a regression case.