docs: Remove legacy device management documentation and update related links for clarity

Author: Lasim

docs/development/backend/gateway-client-config.mdx

@@ -72,7 +72,6 @@ PKCE provides security for public clients (like CLI tools and MCP clients):
 Manages the authorization flow:
 
 #### Client Validation
-- Validates static clients against whitelist (`deploystack-gateway-cli`)
 - Validates dynamic clients against database (`dynamic_oauth_clients` table)
 - Supports both pre-registered and dynamically registered clients
 - Extensible for additional client types
@@ -262,17 +261,6 @@ Scopes are enforced at the endpoint level:
 
 ## Client Types and Configuration
 
-### Static Clients (Pre-registered)
-
-**DeployStack Gateway CLI:**
-- **Client ID**: `deploystack-gateway-cli`
-- **Client Type**: Public (no secret)
-- **Redirect URIs**: 
-  - `http://localhost:8976/oauth/callback`
-  - `http://127.0.0.1:8976/oauth/callback`
-- **Required**: PKCE with SHA256
-- **Token Lifetime**: 1-hour access, 30-day refresh
-
 ### Dynamic Clients (RFC 7591)
 
 **VS Code MCP Extension:**
@@ -457,7 +445,6 @@ The backend validates OAuth scopes to control API access. Scope configuration mu
 
 For the current list of supported scopes, check the source code at:
 - **Backend validation**: `services/backend/src/services/oauth/authorizationService.ts` in the `validateScope()` method
-- **Gateway requests**: `services/gateway/src/utils/auth-config.ts` in the `scopes` array
 
 ### Adding New Scopes
 
@@ -519,18 +506,6 @@ server.get('/api/another-endpoint', {
 
 Always coordinate scope changes between backend and client implementations.
 
-## Gateway Integration
-
-The OAuth2 server integrates with the DeployStack Gateway:
-
-### Gateway OAuth Client
-
-See [Gateway OAuth Implementation](/development/gateway/oauth) for:
-- Client-side PKCE generation
-- Browser integration
-- Callback server
-- Token storage
-- Automatic refresh
 
 ## MCP Client Integration
 
@@ -576,7 +551,6 @@ The OAuth2 server supports MCP clients through dynamic registration:
 ## Related Documentation
 
 - [Backend Authentication System](/development/backend/auth) - Core authentication
-- [Gateway OAuth Implementation](/development/gateway/oauth) - Client-side OAuth
 - [Satellite OAuth Authentication](/development/satellite/oauth-authentication) - MCP client authentication
 - [Security Policy](/development/backend/security) - Security details
 - [API Documentation](/development/backend/api) - API reference

docs/development/backend/oauth2-server.mdx

@@ -444,7 +444,7 @@ class MyPlugin implements Plugin {
 }
 ```
 
-For complete event documentation, see the [Global Event Bus](./events) guide.
+For complete event documentation, see the [Global Event Bus](/development/backend/events) guide.
 
 ### Access to Core Services
 

docs/development/backend/plugins.mdx

@@ -475,7 +475,7 @@ sqlite3 services/backend/persistent_data/database/deploystack.db
 
 ## API Documentation
 
-For detailed API endpoints, request/response formats, and authentication patterns, see the [API Specification](../../api-spec) generated from the backend OpenAPI schema.
+For detailed API endpoints, request/response formats, and authentication patterns, see the [API Specification](/development/backend/api) generated from the backend OpenAPI schema.
 
 ## Related Documentation
 

docs/development/backend/satellite-communication.mdx

@@ -113,7 +113,7 @@ MCP Client                    Satellite
 - `resources/templates/list` - List resource templates (returns empty array)
 - `prompts/list` - List available prompts (returns empty array)
 
-For detailed information about tool discovery and execution, see [Tool Discovery Implementation](./tool-discovery).
+For detailed information about tool discovery and execution, see [Tool Discovery Implementation](/development/satellite/tool-discovery).
 
 **Error Handling:**
 - JSON-RPC 2.0 compliant error responses
@@ -286,7 +286,7 @@ Satellite                    Backend
 - **Error Recovery**: Exponential backoff with maximum 5-minute intervals
 - **3-Second Response Time**: Immediate priority commands enable near real-time responses
 
-For complete implementation details, see [Backend Polling Implementation](./polling).
+For complete implementation details, see [Backend Polling Implementation](/development/satellite/polling).
 
 ## Security Architecture
 
@@ -375,7 +375,7 @@ Configuration → Spawn → Monitor → Health Check → Restart/Terminate
 - **Status Reporting**: Real-time metrics and health
 - **Command Processing**: Execute Backend commands
 
-For detailed information about the polling implementation, see [Backend Polling Implementation](./polling).
+For detailed information about the polling implementation, see [Backend Polling Implementation](/development/satellite/polling).
 
 ### Phase 5: Enterprise Features
 - **OAuth 2.1 Authentication**: Full authentication server

docs/development/satellite/architecture.mdx

@@ -126,7 +126,7 @@ data: {"timestamp": "2025-01-09T13:30:00.000Z"}
 - `tools/list` - List available tools from remote MCP servers
 - `tools/call` - Execute tools on remote MCP servers
 
-For detailed information about tool discovery and execution, see [Tool Discovery Implementation](./tool-discovery).
+For detailed information about tool discovery and execution, see [Tool Discovery Implementation](/development/satellite/tool-discovery).
 
 ### Resources
 - `resources/list` - List available resources (returns empty array)
@@ -246,4 +246,4 @@ All transport protocols generate structured logs with:
 - Error conditions
 - Performance metrics
 
-See [Logging Documentation](./logging) for detailed log format specifications.
+See [Logging Documentation](/development/satellite/logging) for detailed log format specifications.

docs/development/satellite/mcp-transport.mdx

@@ -58,7 +58,7 @@ MCP Client                    Satellite                    Backend
 - Team-aware `tools/call` - validates team access before execution
 - Integrates with existing tool discovery and configuration systems
 
-For detailed team isolation implementation, see [Team Isolation Implementation](./team-isolation).
+For detailed team isolation implementation, see [Team Isolation Implementation](/development/satellite/team-isolation).
 
 **Dynamic Client Support:**
 - Supports RFC 7591 dynamically registered clients

docs/development/satellite/oauth-authentication.mdx

@@ -10,7 +10,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
 
 DeployStack Satellite implements OAuth 2.1 Resource Server-based team isolation to provide secure multi-tenant access to MCP servers. This system ensures complete separation of team resources while maintaining a unified MCP client interface.
 
-For OAuth authentication details, see [OAuth Authentication Implementation](./oauth-authentication). For tool discovery mechanics, see [Tool Discovery Implementation](./tool-discovery).
+For OAuth authentication details, see [OAuth Authentication Implementation](/development/satellite/oauth-authentication). For tool discovery mechanics, see [Tool Discovery Implementation](/development/satellite/tool-discovery).
 
 ## Technical Architecture
 
@@ -279,8 +279,8 @@ Team isolation maintains full MCP client compatibility:
 
 ## Related Documentation
 
-- [OAuth Authentication Implementation](./oauth-authentication) - OAuth 2.1 Resource Server details
-- [Tool Discovery Implementation](./tool-discovery) - Tool caching and namespacing mechanics
-- [Satellite Architecture Design](./architecture) - Overall satellite architecture
-- [Backend Communication](./backend-communication) - Backend integration patterns
+- [OAuth Authentication Implementation](/development/satellite/oauth-authentication) - OAuth 2.1 Resource Server details
+- [Tool Discovery Implementation](/development/satellite/tool-discovery) - Tool caching and namespacing mechanics
+- [Satellite Architecture Design](/development/satellite/architecture) - Overall satellite architecture
+- [Backend Communication](/development/satellite/backend-communication) - Backend integration patterns
 - [Backend OAuth2 Server Implementation](/development/backend/oauth2-server) - OAuth server implementation

docs/development/satellite/team-isolation.mdx

@@ -10,7 +10,7 @@ import { Callout } from 'fumadocs-ui/components/callout';
 
 DeployStack Satellite implements automatic tool discovery from remote HTTP MCP servers, providing dynamic tool availability without manual configuration. This system enables MCP clients to discover and execute tools from external MCP servers through the satellite's proxy layer.
 
-For information about the overall satellite architecture, see [Satellite Architecture Design](./architecture). For details about the MCP transport protocols that expose discovered tools, see [MCP Transport Protocols](./mcp-transport).
+For information about the overall satellite architecture, see [Satellite Architecture Design](/development/satellite/architecture). For details about the MCP transport protocols that expose discovered tools, see [MCP Transport Protocols](/development/satellite/mcp-transport).
 
 ## Technical Overview
 
@@ -170,7 +170,7 @@ Internal Server: "context7-john-R36no6FGoMFEZO9nWJJLT"
 - **Internal Routing**: Uses full server name for team isolation
 - **Uniqueness**: Guaranteed unique names across all servers
 
-For team-based server resolution, see [Team Isolation Implementation](./team-isolation).
+For team-based server resolution, see [Team Isolation Implementation](/development/satellite/team-isolation).
 
 ## SSE Response Processing