docs: route data owners through ingestion before use-case creation

[saadqbal]

Summary

• Reworks the data-owner bullet in the setup-guide's "What's Next" section so it routes through ingestion first, then into use-case creation.
• Replaces "select datasets" with "pick from prepared datasets" to match the homepage wording from docs: add "Bring your data" step to homepage journey #29.

Found by a broader audit of the docs site after #29 merged. Same inversion class — the data owner who finished the client install was sent straight to "create a use case" with no mention of ingesting data first.

-**Data owners:** [Create a use case](/create-use-case/prerequisites) — select datasets, define evaluation metrics, and invite contributors to submit models.
+**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.

Closes #30.

Audit status

Grep across origin/develop for select datasets|define datasets|active use case:

• Homepage: clean (fixed in docs: add "Bring your data" step to homepage journey #29)
• This page: was the last remaining hit — fixed here
• join-use-case/overview.mdx:16 "Browse active use cases": benign (different meaning of "active")

No further occurrences of the inversion pattern on develop. main still has the homepage hits because develop hasn't synced — separate operational concern.

Test plan

• Visual review of the "What's Next" section in setup-guide.mdx
• Both inline links (/create-use-case/prepare-dataset and /create-use-case/prerequisites) render correctly

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk documentation-only change that updates navigation links and wording, with the main risk being broken/incorrect doc links or guidance.

Overview
Updates the Setup Guide "What's Next" guidance for data owners to direct them to dataset ingestion first (/create-use-case/prepare-dataset) and only then to use-case creation (/create-use-case/prerequisites).

Also refreshes the wording from "select datasets" to "pick from prepared datasets" to align terminology with the rest of the docs.

^{Reviewed by Cursor Bugbot for commit ea6f74e. Bugbot is set up for automated code reviews on this repo. Configure here.}

[LukasWodka]

👋 Heads-up — Code review queue is at 9 / 8

Above the WIP limit. The team convention is to review existing PRs before opening new work.

Open PRs currently in Code review (oldest first):

• backend#642 — Bump django from 3.0.10 to 4.2.30 · author: @dependabot · no reviewer assigned
• backend#643 — Bump gitpython from 3.1.27 to 3.1.50 · author: @dependabot · no reviewer assigned
• data-ingestors#68 — fix: add Visibility schema to keypoint template, fix sample data sizes · author: @shujaatTracebloc · reviewer: @divyasinghds
• data-ingestors#74 — docs: add per-template READMEs for the 6 templates missing one · author: @saadqbal · no reviewer assigned
• docs#14 — docs: migrate join-use-case API examples to snake_case (0.7.0) · author: @divyasinghds · no reviewer assigned
• docs#26 — docs: add "How training works" page · author: @divyasinghds · no reviewer assigned
• docs#27 — docs: add automated upstream sync workflow · author: @divyasinghds · reviewer: @saadqbal
• tracebloc-client#254 — Fix keypoint detection bbox clamp and annotation column case · author: @shujaatTracebloc · no reviewer assigned

Pull from review before opening new work. (This is a nudge from the kanban WIP check, not a block.)