docs: apply review suggestions

Author: macarie

docs/.vitepress/components.d.ts

@@ -7,6 +7,7 @@ export {}
 /* prettier-ignore */
 declare module 'vue' {
   export interface GlobalComponents {
+    Advanced: typeof import('./components/Advanced.vue')['default']
     ArrowDown: typeof import('./components/ArrowDown.vue')['default']
     BlogIndex: typeof import('./components/BlogIndex.vue')['default']
     Box: typeof import('./components/Box.vue')['default']

docs/.vitepress/components/Advanced.vue

@@ -0,0 +1,5 @@
+<template>
+  <Badge type="danger" title="This is an advanced API intended for library authors and framework integrations. Most users should not need this." class="cursor-help">
+    advanced
+  </Badge>
+</template>

docs/.vitepress/config.ts

@@ -994,7 +994,7 @@ export default ({ mode }: { mode: string }) => {
                 link: '/api/advanced/metadata',
               },
               {
-                text: 'Artifacts',
+                text: 'TestArtifact',
                 link: '/api/advanced/artifacts',
               },
             ],

docs/api/advanced/artifacts.md

@@ -3,7 +3,7 @@ outline: deep
 title: Test Artifacts
 ---
 
-# Test Artifacts <Badge type="danger">advanced</Badge> <Badge type="warning">experimental</Badge>
+# Test Artifacts <Advanced /> <Version type="experimental">4.0.9</Version> <Experimental />
 
 ::: warning
 This is an advanced API. As a user, you most likely want to use [test annotations](/guide/test-annotations) to add notes or context to your tests instead. This is primarily used internally and by library authors.
@@ -25,7 +25,7 @@ Vitest automatically manages attachment serialization (files are copied to [`att
 
 ## API
 
-### `recordArtifact` <Badge type="warning">experimental</Badge> {#recordartifact}
+### `recordArtifact` <Experimental /> {#recordartifact}
 
 ::: warning
 `recordArtifact` is an experimental API. Breaking changes might not follow SemVer, please pin Vitest's version when using it.
@@ -49,7 +49,7 @@ Note: annotations, [even though they're built on top of this feature](#relations
 
 The `TestArtifact` type is a union containing all artifacts Vitest can produce, including custom ones. All artifacts extend from [`TestArtifactBase`](#testartifactbase)
 
-### `TestArtifactBase` <Badge type="warning">experimental</Badge> {#testartifactbase}
+### `TestArtifactBase` <Experimental /> {#testartifactbase}
 
 ```ts
 export interface TestArtifactBase {

docs/api/advanced/reporters.md

@@ -16,7 +16,7 @@ Vitest has its own test run lifecycle. These are represented by reporter's metho
       - [`onHookEnd(beforeAll)`](#onhookend)
         - [`onTestCaseReady`](#ontestcaseready)
           - [`onTestAnnotate`](#ontestannotate) <Version>3.2.0</Version>
-          - [`onTestCaseArtifactRecord`](#ontestcaseartifactrecord) <Version>4.0.9</Version>
+          - [`onTestCaseArtifactRecord`](#ontestcaseartifactrecord) <Version type="experimental">4.0.9</Version>
           - [`onHookStart(beforeEach)`](#onhookstart)
           - [`onHookEnd(beforeEach)`](#onhookend)
           - [`onHookStart(afterEach)`](#onhookstart)
@@ -334,7 +334,7 @@ The `onTestAnnotate` hook is associated with the [`context.annotate`](/guide/tes
 
 If the path is specified, Vitest stores it in a separate directory (configured by [`attachmentsDir`](/config/#attachmentsdir)) and modifies the `path` property to reference it.
 
-## onTestCaseArtifactRecord <Version>4.0.9</Version> {#ontestcaseartifactrecord}
+## onTestCaseArtifactRecord <Version type="experimental">4.0.9</Version> {#ontestcaseartifactrecord}
 
 ```ts
 function onTestCaseArtifactRecord(
@@ -346,3 +346,5 @@ function onTestCaseArtifactRecord(
 The `onTestCaseArtifactRecord` hook is associated with the [`recordArtifact`](/api/advanced/artifacts#recordartifact) utility. When `recordArtifact` is invoked, Vitest serialises it and sends the same attachment to the main thread where reporter can interact with it.
 
 If the path is specified, Vitest stores it in a separate directory (configured by [`attachmentsDir`](/config/#attachmentsdir)) and modifies the `path` property to reference it.
+
+Note: annotations, [even though they're built on top of this feature](/api/advanced/artifacts#relationship-with-annotations), won't hit this hook and won't appear in the `task.artifacts` array for backwards compatibility reasons until the next major version.