Fix cross-ref links (for pages under Services) (#333)

* Fix cross-ref links (for pages under Services)

* Add sandbox env var info

Author: parteeksingh24

content/Agents/ai-gateway.mdx

@@ -174,4 +174,4 @@ We recommend using the AI Gateway for most projects.
 
 - [Using the AI SDK](/Agents/ai-sdk-integration): Structured output, tool calling, and multi-turn conversations
 - [Returning Streaming Responses](/Agents/streaming-responses): Real-time chat UIs and progress indicators
-- [Logging](/Observability/logging): Debug requests and track LLM performance
+- [Logging](/Services/Observability/logging): Debug requests and track LLM performance

content/Agents/events-lifecycle.mdx

@@ -251,5 +251,5 @@ Use events for observability. Use [evaluations](/Agents/evaluations) for output
 - [Evaluations](/Agents/evaluations): Automated quality testing for agent outputs
 - [State Management](/Agents/state-management): Thread and session state patterns
 - [Calling Other Agents](/Agents/calling-other-agents): Multi-agent coordination
-- [Logging](/Observability/logging): Structured logging for debugging events
-- [Tracing](/Observability/tracing): Track timing across event handlers
+- [Logging](/Services/Observability/logging): Structured logging for debugging events
+- [Tracing](/Services/Observability/tracing): Track timing across event handlers

content/Agents/state-management.mdx

@@ -200,7 +200,7 @@ Both `ctx.state` and `ctx.session.state` are request-scoped and reset after each
 For most use cases, use `ctx.state`. Use `ctx.session.state` only when you need data in session completion events. See [Events & Lifecycle](/Agents/events-lifecycle) for more on event handlers.
 
 <Callout type="info" title="Persistent Data">
-Neither `ctx.state` nor `ctx.session.state` persist across requests. For data that should survive across requests, use `ctx.thread.state` (up to 1 hour) or [KV storage](/Storage/key-value) (durable).
+Neither `ctx.state` nor `ctx.session.state` persist across requests. For data that should survive across requests, use `ctx.thread.state` (up to 1 hour) or [KV storage](/Services/Storage/key-value) (durable).
 </Callout>
 
 ## Persisting to Storage
@@ -436,7 +436,7 @@ Thread and session state are limited to **1MB** after JSON serialization. Values
 </Callout>
 
 To stay within limits:
-- Store large data in [KV storage](/Storage/key-value) instead of state
+- Store large data in [KV storage](/Services/Storage/key-value) instead of state
 - Keep only recent messages (e.g., last 20-50)
 - Store IDs or references rather than full objects
 
@@ -467,6 +467,6 @@ if (messages.length > 50) {
 
 ## Next Steps
 
-- [Key-Value Storage](/Storage/key-value): Durable data persistence with namespaces and TTL
+- [Key-Value Storage](/Services/Storage/key-value): Durable data persistence with namespaces and TTL
 - [Calling Other Agents](/Agents/calling-other-agents): Share state between agents in workflows
 - [Events & Lifecycle](/Agents/events-lifecycle): Monitor agent execution and cleanup

content/Agents/streaming-responses.mdx

@@ -40,7 +40,7 @@ await stream.write('data');
 await stream.close();
 ```
 
-This page focuses on ephemeral streaming with the AI SDK. For persistent streaming patterns, see the [Storage documentation](/Storage/durable-streams).
+This page focuses on ephemeral streaming with the AI SDK. For persistent streaming patterns, see the [Storage documentation](/Services/Storage/durable-streams).
 
 <Callout type="info" title="Two Parts to Streaming">
 Streaming requires both: `schema.stream: true` in your agent (so the handler returns a stream) and `stream()` middleware in your route (so the response is streamed to the client).

content/Learn/Cookbook/Patterns/background-tasks.mdx

@@ -161,5 +161,5 @@ const agent = createAgent('BatchProcessor', {
 
 ## See Also
 
-- [Durable Streams](/Storage/durable-streams) for stream creation and management
+- [Durable Streams](/Services/Storage/durable-streams) for stream creation and management
 - [Webhook Handler](/Learn/Cookbook/Patterns/webhook-handler) for another `waitUntil` example

content/Learn/Cookbook/Patterns/cron-with-storage.mdx

@@ -162,4 +162,4 @@ curl http://localhost:3500/api/hn/stories
 ## See Also
 
 - [Cron Routes](/Routes/cron) for schedule expressions and patterns
-- [Key-Value Storage](/Storage/key-value) for KV operations and TTL options
+- [Key-Value Storage](/Services/Storage/key-value) for KV operations and TTL options

content/Learn/Cookbook/Patterns/product-search.mdx

@@ -422,6 +422,6 @@ curl "http://localhost:3500/products/search?q=laptop&category=electronics&maxPri
 
 ## See Also
 
-- [Vector Storage](/Storage/vector) for all vector operations
+- [Vector Storage](/Services/Storage/vector) for all vector operations
 - [Build a RAG Agent](/Learn/Cookbook/Tutorials/rag-agent) for question-answering
 - [AI SDK Integration](/Agents/ai-sdk-integration) for `generateObject` patterns

content/Learn/Cookbook/Tutorials/rag-agent.mdx

@@ -18,7 +18,7 @@ A question-answering agent that:
 ## Prerequisites
 
 - An Agentuity project ([Quickstart](/Get-Started/quickstart) if you need one)
-- Basic familiarity with [Vector Storage](/Storage/vector)
+- Basic familiarity with [Vector Storage](/Services/Storage/vector)
 
 ## Project Structure
 
@@ -380,4 +380,4 @@ createRoot(document.getElementById('root')!).render(
 - Add an [evaluation](/Agents/evaluations) to check answer quality
 - Implement [streaming](/Agents/streaming-responses) for longer responses
 - Add metadata filtering to search specific categories
-- See the [Vector Storage](/Storage/vector) guide for advanced search options
+- See the [Vector Storage](/Services/Storage/vector) guide for advanced search options

content/Reference/CLI/debugging.mdx

@@ -290,4 +290,4 @@ agentuity --json cloud thread list --count=100 | \
 
 - [Managing Cloud Data](/Reference/CLI/data-management): Inspect storage, env vars, and secrets
 - [Deploying to the Cloud](/Reference/CLI/deployment): Deploy and manage projects
-- [Logging](/Observability/logging): Configure logging in your agents
+- [Logging](/Services/Observability/logging): Configure logging in your agents

content/Reference/CLI/deployment.mdx

@@ -415,5 +415,5 @@ Pre-created deployments are typically provisioned by external systems like GitHu
 ## Next Steps
 
 - [Debugging Deployments](/Reference/CLI/debugging): SSH access and debugging tools
-- [Logging](/Observability/logging): Configure logging in your agents
-- [Key-Value Storage](/Storage/key-value): Store persistent data
+- [Logging](/Services/Observability/logging): Configure logging in your agents
+- [Key-Value Storage](/Services/Storage/key-value): Store persistent data