docs(flaky-tests): publish the test collections pages

[TylerJang27]

Important

This is the launch switch — land it last, and only after the default test_collection_status enum is flipped. Merging this makes the test collections documentation publicly visible in the navigation.

Overview

PR 6, the last of the Test Collections docs stack: unhides the concept page and the migration guide and gives each a navigation entry.

Details

Stacked on #329 → #325 → #324 → #323. Everything below has to land first, or this publishes navigation entries pointing at pages whose supporting edits are not in yet.

Three files: the two pages lose hidden: true, and docs.json gains two nav entries plus three redirects.

Considerations

• The concept page goes first in Getting Started, not below the framework pages. The plan had it above Multiple Repositories and Forks, which would have buried it under roughly forty framework and CI-provider entries. It moved because docs(flaky-tests): make collections the default in the straggler copy #324 changed that group's own index to tell readers to verify uploads on their collection's Uploads tab and to open the collection's Monitors tab — so the page explaining what a collection is has to be reachable before the pages that assume it.
• Both collections pages sit together at the top of Getting Started — the concept page, then the migration guide, then the framework and CI-provider pages. The migration guide started in Overview on the reasoning that it targets existing organizations rather than new setup; grouping it with the concept page reads better, since the two are read together. Its file stays at the top level, which matches dashboard sitting at the top level inside the Overview group.
• No new redirects. An earlier revision added three for paths a reader might guess; they were removed, because nothing links to any of them and none has ever been a live path, so there was no link rot for them to prevent. /flaky-tests/test-collections already redirects to the concept page and that one is real — the page has lived there.
• Nothing else in the flaky-tests tree is hidden, so this publishes exactly these two pages and no unrelated drafts.

Testing

Verified against a local build rather than by inspection:

• mint validate (strict) passes; mint broken-links reports none across the whole stack.
• Confirmed both pages now appear in the built navigation by fetching a rendered page and finding their entries — the specific thing this PR exists to do, and the thing a passing build would not otherwise prove.
• Confirmed the pre-existing redirect still resolves: /flaky-tests/test-collections returns 307 to /flaky-tests/get-started/test-collections.

Follow-up Work

Outside this stack, and worth tracking:

• The webhook-emission control's label on the migration guide is written generically, because no UI reads testCollectionWebhooksEnabledDuringMigration yet. Tighten it once that ships.
• The v2 spec in docs(flaky-tests): publish the v2 API and split the reference by scope #329 is a copied file and will drift; automating the copy is a small job worth doing.
• mint dev / mint validate are not run in CI here. Mintlify's own check only builds PRs targeting main, so a stacked PR gets no preview — worth considering a workflow that runs the CLI on every PR regardless of base.

References

• docs(flaky-tests): add the collection id to every setup instruction #323, docs(flaky-tests): make collections the default in the straggler copy #324, docs(flaky-tests): replace the dashboard's landing page for collections #325, docs(flaky-tests): publish the v2 API and split the reference by scope #329 — the rest of the stack
• trunk-io/trunk2#5830 — the CLI flag contract these pages document

🤖 Generated with Claude Code