Add rpk registry context reference pages

[micheleRP]

Summary

Adds three wrapper pages in cloud-docs for rpk registry context, rpk registry context list, and rpk registry context delete, following the established include::ROOT:reference:...[tag=single-source] pattern used by the other rpk-registry pages. Also adds the corresponding nav entries between compatibility-level and mode.

Why this fix is needed

@Feediver1 — your recent PR redpanda-data/docs#1690 (DOC-1790: Schema Registry Metadata Properties) added these xrefs inside the single-sourced section of modules/manage/pages/schema-reg/schema-reg-contexts.adoc (the page that single-sources into cloud-docs):

* xref:reference:rpk/rpk-registry/rpk-registry-context-list.adoc[]
* xref:reference:rpk/rpk-registry/rpk-registry-context-delete.adoc[]

Cloud-docs didn't have wrapper pages for the rpk registry context list/delete commands, so when the docs-repo content was included into cloud-docs the xrefs failed to resolve (in Antora, xrefs inside included content resolve in the including page's component, not the source component).

The rpk registry context commands work against any Schema Registry, including cloud, so the right fix is to add the missing wrappers here. Companion docs-repo fix (for a third broken xref to release-notes/redpanda.adoc which is genuinely self-managed-only): redpanda-data/docs#1707.

Preview pages

• rpk registry context (new)
• rpk registry context list (new)
• rpk registry context delete (new)

Test plan

• Cloud-docs local build with the companion docs branch confirms all three Schema Registry contexts xref errors are gone.
• Once both PRs land, cloud-docs CI build is clean for modules/manage/pages/schema-reg/schema-reg-contexts.adoc.

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for rp-cloud ready!

Name	Link
🔨 Latest commit	bc06cd3
🔍 Latest deploy log	https://app.netlify.com/projects/rp-cloud/deploys/6a0a79d306670700084f068a
😎 Deploy Preview	https://deploy-preview-588--rp-cloud.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds documentation infrastructure for the rpk registry context command family. Three new AsciiDoc pages are introduced—one parent page for the context command and two subcommand pages for list and delete operations—each containing a title and an include:: directive that pulls content from a shared single-source reference. Navigation entries are added to modules/ROOT/nav.adoc to expose these new pages in the table of contents under the rpk-registry command reference section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• Feediver1
• JakeSCahill
• mattschumpert

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding three wrapper pages for rpk registry context commands to the reference documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description check	✅ Passed	The pull request description is comprehensive and well-structured, covering the summary, motivation, preview links, and test plan.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-rpk-registry-context-pages

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Feediver1]

From Claude:
For the fix in xref:reference:rpk/rpk-profile.adoc:

xref: xref:reference:rpk/rpk-profile.adoc (in all 3)
Resolves in cloud-docs?: ✅
How: Resolves via :page-aliases: reference:rpk/rpk-profile.adoc on the actual page at
modules/reference/pages/rpk/rpk-profile/rpk-profile.adoc

Something that is worth knowing about for the future: the file lives at a nested path but a page-aliases directive makes the short xref work. That's the same trick available if you ever need the inverse — a self-managed-only target that needs to resolve in cloud-docs — though ifndef::env-cloud[] is usually cleaner.

[Feediver1]

Thank you!