Setup-guide 'What's Next' omits ingestion for data owners — same journey-order bug class as #28

[saadqbal]

Bug

environment-setup/setup-guide.mdx:153 routes data owners directly from "client is running" to "create a use case", with "select datasets, define evaluation metrics, and invite contributors" framed as sub-actions of use-case creation. Same inversion pattern as #28 (which fixed the homepage), found by a broader audit of the docs site.

Current line:

**Data owners:** [Create a use case](/create-use-case/prerequisites) — select datasets, define evaluation metrics, and invite contributors to submit models.

A data owner who finishes the client install and follows this signpost lands on /create-use-case/prerequisites expecting to "select datasets" — but they haven't ingested any yet. Same dead-end the homepage bug produced.

Audit context

Grep across origin/develop (with #29 already merged) turned up exactly this one remaining instance of the inversion pattern. origin/main still has the homepage hits too, but those resolve when develop next merges to main (separate operational concern, not new doc bugs). One other hit — join-use-case/overview.mdx:16 "Browse active use cases" — is benign (different meaning of "active").

Suggested fix

Reword to include ingestion as a step in the data-owner path:

**Data owners:** [Ingest your dataset](/create-use-case/prepare-dataset), then [create a use case](/create-use-case/prerequisites) — pick from prepared datasets, define evaluation metrics, and invite contributors to submit models.

Two links, one bullet, accurate ordering.

Acceptance

• The setup-guide's "What's Next" section reflects ingestion-before-use-case ordering for the data-owner path.
• "Select datasets" no longer reads as a UI action performed during use-case creation.
• Grep select datasets|define datasets across all .mdx files on develop returns no further hits (homepage fix from docs: add "Bring your data" step to homepage journey #29 + this).

Refs

• Homepage 'How It Works' inverts journey order — drops the ingestion step, says datasets are selected during use-case definition #28 — homepage journey inversion (parent audit context, closed by docs: add "Bring your data" step to homepage journey #29)