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

docs.json

@@ -174,13 +174,15 @@
                 "group": "Overview",
                 "root": "flaky-tests/overview",
                 "pages": [
+                  "flaky-tests/test-collections",
                   "flaky-tests/dashboard"
                 ]
               },
               {
                 "group": "Getting Started",
                 "root": "flaky-tests/get-started/index",
                 "pages": [
+                  "flaky-tests/get-started/migrate-to-test-collections",
                   {
                     "group": "Test frameworks",
                     "root": "flaky-tests/get-started/frameworks/index",
@@ -2164,10 +2166,6 @@
       "source": "/flaky-tests/quarantine-service-availability",
       "destination": "/flaky-tests/quarantining/quarantine-service-availability"
     },
-    {
-      "source": "/flaky-tests/test-collections",
-      "destination": "/flaky-tests/get-started/test-collections"
-    },
     {
       "source": "/flaky-tests/test-labels",
       "destination": "/flaky-tests/management/test-labels"

flaky-tests/dashboard.mdx

@@ -11,7 +11,7 @@ Press <kbd>⌘</kbd> <kbd>K</kbd> (macOS) or <kbd>Ctrl</kbd> <kbd>K</kbd> (Windo
 
 ## Collections overview
 
-When you navigate to `/<your-org>/flaky-tests`, you land on your [test collections](./get-started/test-collections). The page exists to answer two questions — what collections have flaky tests, and which are not finished being set up.
+When you navigate to `/<your-org>/flaky-tests`, you land on your [test collections](./test-collections). The page exists to answer two questions — what collections have flaky tests, and which are not finished being set up.
 
 <Frame caption="The collections list. Setup shows how far each collection got; the shield marks quarantining.">
   <img className="block dark:hidden" src="/assets/flaky-tests/collections-list-light.png" alt="A list of five test collections, each with its Collection ID, repository count, setup progress, test counts, flaky and broken trends, and a runs-per-day chart." />
@@ -20,7 +20,7 @@ When you navigate to `/<your-org>/flaky-tests`, you land on your [test collectio
 
 | Column | Description |
 |--------|-------------|
-| **ID** | The [Collection ID](./get-started/test-collections#the-collection-id), with a button to copy it. This is the value CI passes to route uploads here. |
+| **ID** | The [Collection ID](./test-collections#the-collection-id), with a button to copy it. This is the value CI passes to route uploads here. |
 | **Repos** | How many repositories have uploaded to this collection |
 | **Setup** | How many of the collection's setup steps are complete |
 | **Tests** | Total tracked test cases in the collection (60-day window) |
@@ -41,7 +41,7 @@ A quarantine status icon appears next to a collection's name when quarantining i
 
 While you are migrating, the repository view stays available behind **Legacy view** on this page. It carries the same columns and the same quarantine icons, per repository rather than per collection.
 
-Active repositories (those with test data in the last 30 days) appear at the top of the list. Repositories with no recent data are collapsed under an **Inactive Repositories** section you can expand. See the [migration guide](./migrate-to-test-collections) for how the two views relate, and [Quarantining](./quarantining/) to configure quarantine settings.
+Active repositories (those with test data in the last 30 days) appear at the top of the list. Repositories with no recent data are collapsed under an **Inactive Repositories** section you can expand. See the [migration guide](./get-started/migrate-to-test-collections) for how the two views relate, and [Quarantining](./quarantining/) to configure quarantine settings.
 
 ## Collection dashboard
 

flaky-tests/detection/pass-on-retry-monitor.mdx

@@ -49,7 +49,7 @@ You can create more than one pass-on-retry monitor for the same repository. Each
 
 A common pattern is to run one monitor scoped to stable branches (like `main`) with a shorter recovery period for fast feedback, and a second monitor scoped to `release/*` branches with a longer recovery period for builds where intermittent failures are more expensive to re-investigate.
 
-To add a monitor, open the **Monitors** tab — on a [test collection](/flaky-tests/get-started/test-collections) or on a repository — and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
+To add a monitor, open the **Monitors** tab — on a [test collection](/flaky-tests/test-collections) or on a repository — and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
 
 <Frame caption="The Monitors tab lists each monitor as its own row, grouped into Health classification and Lifecycle & performance. Add Monitor creates an additional monitor in the same repository.">
 <img className="block dark:hidden" src="/assets/flaky-tests/detection/repo-monitors-tab-light.png" alt="The repository Monitors tab showing a pass-on-retry monitor, two failure-rate monitors, and lifecycle monitors, each as a separate row with an Add Monitor control." />

flaky-tests/get-started/ci-providers/otherci.mdx

@@ -40,7 +40,7 @@ You can find your token under **Settings** → **Organization** → **General**,
 
 Store the Trunk slug and API token obtained in the previous step in your CI provider as a secret, environment variable, or an equivalent concept and name them `TRUNK_ORG_URL_SLUG` and `TRUNK_API_TOKEN` respectively.
 
-Set `TRUNK_TEST_COLLECTION_ID` as well, to the ID of the [test collection](/flaky-tests/get-started/test-collections) the results belong to. It is not a secret, and it is per job rather than per organization — a job that uploads to a different collection sets a different value.
+Set `TRUNK_TEST_COLLECTION_ID` as well, to the ID of the [test collection](/flaky-tests/test-collections) the results belong to. It is not a secret, and it is per job rather than per organization — a job that uploads to a different collection sets a different value.
 
 ## Upload to Trunk
 

flaky-tests/get-started/frameworks/behave.mdx

@@ -100,7 +100,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/cypress.mdx

@@ -138,7 +138,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/gotestsum.mdx

@@ -119,7 +119,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/gradle.mdx

@@ -111,7 +111,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/jasmine.mdx

@@ -124,7 +124,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/jest.mdx

@@ -137,7 +137,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/karma.mdx

@@ -111,7 +111,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/kotest.mdx

@@ -181,7 +181,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/maven.mdx

@@ -126,7 +126,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/minitest.mdx

@@ -109,7 +109,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />

flaky-tests/get-started/frameworks/mocha.mdx

@@ -113,7 +113,7 @@ You make an upload to Trunk using the following command:
     --token <TRUNK_ORG_TOKEN>
 ```
 
-You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/get-started/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
+You can find your Trunk organization slug and token in the settings or by following these [instructions](/flaky-tests/get-started/ci-providers/otherci#id-1.-store-a-trunk_token-secret-in-your-ci-system). The collection ID identifies the [test collection](/flaky-tests/test-collections) the results belong to, and you copy it from that collection in the Trunk app. After your upload, you can verify that Trunk has received and processed it successfully in the **Uploads** tab. Warnings will be displayed if the report has issues.
 
 <Frame>
 <img className="block dark:hidden" src="/assets/_shared/data-uploads-light.png" alt="" />