refactor(frontend): remove enableRpcnTiles flag and serverless get-started wizard

[eblairmckee]

Summary

• removes the enableRpcnTiles feature flag and every branch it gated, plus the ./connect-tiles federated module exposure
• removes the serverless get-started API wizard (/get-started/api route, APIConnectWizard, api-wizard-store, onboarding code-snippet query) — its only entry point was Cloud UI's serverless onboarding wizard, deleted in the companion cloudv2 PR (redpanda-data/cloudv2#28773)
• removes the /rp-connect/wizard route entirely — pipeline creation always lands on /rp-connect/create now

Why

enableRpcnTiles was the tiles-based create flow embedded in the legacy layout — it's been superseded since the new connect UI (enablePipelineDiagrams tier, #2285) shipped at the end of March, and that tier has proven stable since. The flag is now off in LaunchDarkly, so every isFeatureFlagEnabled('enableRpcnTiles') && isEmbedded() branch was dead code.

The ./connect-tiles federated exposure goes with it: its only consumer was Cloud UI's serverless onboarding wizard, which is deleted in the companion cloudv2 PR (redpanda-data/cloudv2#28773).

The /rp-connect/wizard route is retired with it. Tier 1 already redirected wizard → create, and every "create pipeline" entry point now goes straight to /rp-connect/create — the wizard was an extra hop that no longer earned its place. That takes ConnectOnboardingWizard, ConnectTiles/ConnectTile, the wizard-only stepper constants, and the yaml-regeneration helpers with it. AddTopicStep/AddUserStep and rpcn-wizard-store stay — PipelinePage uses them.

What changed

• constants.ts — dropped enableRpcnTiles from FEATURE_FLAGS (also swept the dead enableServerlessOnboardingWizard default, which nothing reads)
• pipelines-create.tsx / pipelines-edit.tsx / pipelines-details.tsx / connect/overview.tsx — removed the flag-gated PipelinePage / PipelineListPage early returns; tier-1 routing via enablePipelineDiagrams is unchanged
• header.tsx — useShouldHideHeader now checks enablePipelineDiagrams only
• module-federation.config.ts — removed the ./connect-tiles expose
• console-app.test.tsx — flag passthrough tests now use enablePipelineDiagrams
• Deleted: routes/get-started/api.tsx, api-connect-wizard.tsx, state/api-wizard-store.ts, react-query/api/onboarding.tsx; header.tsx dropped its /get-started/api route match; routeTree.gen.ts regenerated
• Deleted: routes/rp-connect/wizard.tsx, onboarding-wizard.tsx, connect-tiles.tsx, connect-tile.tsx; pipeline/list.tsx create button navigates to /rp-connect/create; header.tsx dropped its wizard route match; pruned the orphaned WizardStepper constants and handleStepResult/regenerateYamlForTopicUserComponents helpers

Test coverage

• console-app.test.tsx + topic/user step suites — 44 tests pass
• type-check clean for touched files (remaining errors are pre-existing in redpanda-ui registry components on master)

[github-actions]

🚨 Registry drift detected

App: frontend · Scope: diff vs origin/master · Files: 16

	Count
⚠️ Outdated registry components	2
🛠 Locally-modified components	0
❓ Unknown to registry	0
🎨 Off-token palette colours	0
🔢 Ad-hoc utility classes	0

Components needing attention

Status	Component	Uses	Detail
⚠️ outdated	data-table	1×	installed 2.4.0 → latest 2.4.1
⚠️ outdated	tabs	1×	installed 2.4.0 → latest 2.4.1

Refresh command:

bunx shadcn@latest add @redpanda/data-table @redpanda/tabs --overwrite

Generated by lookout audit-changes.

[eblairmckee]

are there any risks while cloud UI is promoted to production but console will not be until next wednesday?

1. Old wizard route still exists in prod console all week. Console won't pick up the deletion until Wednesday's release, so /rp-connect/wizard keeps resolving.
2. Old console already has a redirect built in — the wizard route's beforeLoad throws redirect({ to: '/rp-connect/create' }) when enablePipelineDiagrams is on and it's embedded. So on prod clusters with the new connect UI, anyone landing on the wizard URL bounces to create automatically, today, with zero code change.
3. If any cluster has enablePipelineDiagrams off, the old wizard renders and still works — all its code ships in the old console build.
4. Cloud-ui deleting its wizard route stub doesn't 404 either — those stubs are only for typed links/search validation; at runtime the cluster dashboard hands any non-cloud-ui subpath to the embedded console (/* catch-all).
5. The removed feature flags are also safe: old console falls back to its own false defaults when cloud-ui stops passing them — identical to the LaunchDarkly flags you already turned off.

The only 404 risk starts AFTER Wednesday's console release: stale bookmarks/browser history pointing at /rp-connect/wizard will hit console's not-found page, because we deleted the route and nothing in the new build redirects it. Real exposure is small (in-product links are all retargeted; the URL only ever existed behind onboarding flows).

[SpicyPete]

always good to see code cleaned up 👍