Move Quarkus extension to Quarkiverse

[t1]

Sub-issue of #9. Depends on the extension being stable.

Apply for Quarkiverse onboarding and move the extension modules to a new repo.

See design spec: docs/superpowers/specs/2026-04-09-quarkus-dev-mode-design.md — sub-issue 4.

Scope:

• Extension Proposal issue in quarkusio/quarkus
• New repo github.com/quarkiverse/quarkus-openapi-ui
• Coordinate change to io.quarkiverse.openapiui
• Quarkiverse parent POM, release workflow, Antora docs
• Register in extension catalog and ecosystem CI

[t1]

Question from agent

Context: Phase 1 (Load & Assess) — checking sub-issue dependencies
Assessment: This issue depends on #27 (demo app update) and #26 (build extension), which are blocked on #25 (model migration).
Impact: Cannot move the extension to Quarkiverse until it is built and verified.

Marking this issue as blocked until #27 is resolved.

[t1]

Agent: starting work

Type: Feature (infrastructure migration)
Summary: Move the Quarkus extension from this repository to the Quarkiverse ecosystem. This completes the Quarkus dev-mode integration by placing the extension in its proper long-term home where it can be maintained and released independently.

Design decisions:

• Extension is stable and tested (issues Migrate core from Swagger model to MicroProfile OpenAPI model #25, Build Quarkus extension for OpenAPI UI #26, Update demo app to use Quarkus extension #27 complete)
• Quarkiverse onboarding follows standard process: proposal → repo creation → code migration
• New coordinates: io.quarkiverse.openapiui:quarkus-openapi-ui
• Extension stays compatible with current users via deprecation period for old coordinates

Acceptance criteria:

• Extension Proposal issue created in quarkusio/quarkus
• Code migrated to quarkiverse/quarkus-openapi-ui (once repo is created)
• Extension catalog registration
• This repo updated to deprecate local extension and point to Quarkiverse

Files: Will create proposal issue first, then coordinate code migration with Quarkiverse team

Autonomous mode limitation: This issue requires external coordination with the Quarkus team for repository creation and permissions. The agent can prepare the proposal and mark specific coordination steps as blocked, but cannot complete the full migration autonomously.

[t1]

Question from agent

Context: Phase 4 (Implement) — preparing Quarkiverse migration
Assessment: This issue requires external coordination that cannot be completed autonomously:

1. Extension Proposal — I can draft a proposal issue for quarkusio/quarkus, but the maintainer must review and submit it
2. Quarkiverse repo creation — Requires Quarkiverse team approval; cannot proceed until repo exists
3. Code migration — Requires write access to the new Quarkiverse repository
4. Infrastructure setup — Requires Quarkiverse repository and permissions

Question: Should I:

• (A) Draft the extension proposal as a document in this repo, commit it, and mark the issue blocked for maintainer review/submission?
• (B) Attempt to create the proposal issue directly in quarkusio/quarkus (if the agent has permissions)?
• (C) Something else?

Options:

• Option A keeps the proposal under version control for review, but adds a manual step
• Option B is more direct but may not have permissions, and bypasses review

Impact: The Quarkiverse migration is blocked until the proposal is submitted and the repo is created by the Quarkiverse team.

[t1]

Agent: blocked status confirmed

Assessment: Issue #28 is still blocked awaiting owner response.

Last question: Posted at 2026-04-09T08:18:35Z asking whether to:

• (A) Draft extension proposal as a document in this repo for review
• (B) Create proposal issue directly in quarkusio/quarkus
• (C) Something else

Status: No owner response found after the question. Issue remains blocked.

Next step: Once the owner answers, the agent can resume work on the Quarkiverse migration.

[t1]

create subtasks so we can tackle them one-by-one

[t1]

Agent: resuming work

Found answer from owner. Continuing from where the previous agent left off.

Owner instruction: Create subtasks for the Quarkiverse migration to tackle them one-by-one.

Next step: Break down the migration into discrete sub-issues that can be completed independently.