fix: fix more broken links

Really Him · Really Him · commit 7a68d7f35a21 · 2025-05-30T08:04:30.000-04:00
diff --git a/docs/specification/2024-11-05/server/index.mdx b/docs/specification/2024-11-05/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/2024-11-05/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/2024-11-05/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/2024-11-05/server/tools" />
 </CardGroup>
diff --git a/docs/specification/2024-11-05/server/prompts.mdx b/docs/specification/2024-11-05/server/prompts.mdx
@@ -20,7 +20,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/2024-11-05/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/2024-11-05/server/resources.mdx b/docs/specification/2024-11-05/server/resources.mdx
@@ -23,7 +23,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/2024-11-05/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
diff --git a/docs/specification/2025-03-26/server/index.mdx b/docs/specification/2025-03-26/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/2025-03-26/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/2025-03-26/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/2025-03-26/server/tools" />
 </CardGroup>
diff --git a/docs/specification/2025-03-26/server/prompts.mdx b/docs/specification/2025-03-26/server/prompts.mdx
@@ -19,7 +19,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/2025-03-26/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/2025-03-26/server/resources.mdx b/docs/specification/2025-03-26/server/resources.mdx
@@ -21,7 +21,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/2025-03-26/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
diff --git a/docs/specification/draft/server/index.mdx b/docs/specification/draft/server/index.mdx
@@ -25,7 +25,7 @@ Each primitive can be summarized in the following control hierarchy:
 Explore these key primitives in more detail below:
 
 <CardGroup cols={3}>
-  <Card title="Prompts" icon="message" href="prompts" />
-  <Card title="Resources" icon="file-lines" href="resources" />
-  <Card title="Tools" icon="wrench" href="tools" />
+  <Card title="Prompts" icon="message" href="/specification/draft/server/prompts" />
+  <Card title="Resources" icon="file-lines" href="/specification/draft/server/resources" />
+  <Card title="Tools" icon="wrench" href="/specification/draft/server/tools" />
 </CardGroup>
diff --git a/docs/specification/draft/server/prompts.mdx b/docs/specification/draft/server/prompts.mdx
@@ -19,7 +19,7 @@ interface, which allows users to naturally discover and invoke available prompts
 
 For example, as slash commands:
 
-![Example of prompt exposed as slash command](slash-command.png)
+![Example of prompt exposed as slash command](/specification/draft/server/slash-command.png)
 
 However, implementors are free to expose prompts through any interface pattern that suits
 their needs&mdash;the protocol itself does not mandate any specific user interaction
diff --git a/docs/specification/draft/server/resources.mdx b/docs/specification/draft/server/resources.mdx
@@ -21,7 +21,7 @@ For example, applications could:
 - Allow the user to search through and filter available resources
 - Implement automatic context inclusion, based on heuristics or the AI model's selection
 
-![Example of resource context picker](resource-picker.png)
+![Example of resource context picker](/specification/draft/server/resource-picker.png)
 
 However, implementations are free to expose resources through any interface pattern that
 suits their needs&mdash;the protocol itself does not mandate any specific user
