docs: update links in GitHub OAuth and Quick Start documentation for consistency and clarity

Author: Lasim

docs/development/backend/api-security.mdx

@@ -179,7 +179,7 @@ fastify.get('/dual-auth-endpoint', {
 });
 ```
 
-For detailed OAuth2 implementation, see the [OAuth Implementation Guide](./oauth.mdx) and [Security Policy](./security.mdx#oauth2-server-security).
+For detailed OAuth2 implementation, see the [Backend OAuth Implementation Guide](/development/backend/oauth) and [Backend Security Policy](/development/backend/security#oauth2-server-security).
 
 ### Team-Aware Permission System
 
@@ -485,5 +485,5 @@ Before deploying any protected endpoint, verify:
 ## Related Documentation
 
 - [API Documentation Generation](/development/backend/api) - General API development patterns
-- [Authentication System](deploystack/auth) - User authentication implementation
+- [Authentication System](/development/backend/auth) - User authentication implementation
 - [Role-Based Access Control](/development/backend/roles) - Permission system details

docs/development/backend/api.mdx

@@ -17,7 +17,7 @@ The DeployStack Backend uses Fastify with Swagger plugins to automatically gener
 
 ## 🔒 Security First
 
-**IMPORTANT**: Before developing any protected API endpoints, read the [API Security Best Practices](./api-security.mdx) documentation. It covers critical security patterns including:
+**IMPORTANT**: Before developing any protected API endpoints, read the [API Security Best Practices](/development/backend/api-security) documentation. It covers critical security patterns including:
 
 - **Authorization Before Validation**: Why `preValidation` must be used instead of `preHandler` for authorization
 - **Proper Error Responses**: Ensuring unauthorized users get 403 Forbidden, not validation errors

docs/development/backend/auth.mdx

@@ -0,0 +1,6 @@
+---
+title: Authentication System
+description: Complete guide to implementing user authentication in DeployStack Backend.
+---
+
+# DeployStack Authentication System

docs/development/backend/global-settings.mdx

@@ -930,7 +930,7 @@ Key points for plugin-contributed settings:
 - **Declaration**: Plugins declare global settings via a `globalSettingsExtension` property in their main class.
 - **Initialization**: The `PluginManager` processes these definitions at startup, creating new groups and settings if they don't already exist.
 - **Precedence**: Core global settings always take precedence. If a plugin tries to define a setting with a key that already exists (either from core or another plugin), the plugin's definition for that specific key is ignored.
-- **Documentation**: For details on how plugins can define global settings, refer to the [PLUGINS.MD](PLUGINS.MD) document.
+- **Documentation**: For details on how plugins can define global settings, refer to the [Backend Plugins Docs](/development/backend/plugins) document.
 
 ## Helper Methods API Reference
 

docs/development/backend/oauth.mdx

@@ -28,7 +28,7 @@ For programmatic API access by CLI tools and applications:
 
 The OAuth2 server enables CLI tools and applications to access DeployStack APIs securely using Bearer tokens.
 
-For OAuth2 security details including PKCE, token security, authorization flow security, and Bearer token authentication, see the [Security Policy](./security.mdx#oauth2-server-security).
+For OAuth2 security details including PKCE, token security, authorization flow security, and Bearer token authentication, see the [Security Policy](/development/backend/security#oauth2-server-security).
 
 ### Database Schema
 

docs/development/backend/roles.mdx

@@ -106,7 +106,7 @@ fastify.post('/teams/:teamId/resources', {
 }, handler);
 ```
 
-See [API Security Best Practices](./api-security.mdx) for detailed information about team-aware permissions and security patterns.
+See [API Security Best Practices](/development/backend/api-security) for detailed information about team-aware permissions and security patterns.
 
 ### Programmatic Checks
 

docs/development/backend/security.mdx

@@ -105,7 +105,7 @@ The OAuth2 server implementation follows RFC 6749 and RFC 7636 security standard
 - **Scope Enforcement:** Middleware validates required scopes per endpoint
 - **Dual Authentication:** Seamless support for both cookies and Bearer tokens
 
-For implementation details, see the [OAuth Implementation Guide](./oauth.mdx).
+For implementation details, see the [Backend OAuth Implementation Guide](/development/backend/oauth).
 
 ## Dependencies
 

docs/development/backend/test.mdx

@@ -133,7 +133,7 @@ console.log('User created:', user);
 server.log.info('User created', { userId: user.id });
 ```
 
-See the [Backend Logging Guide](./logging.mdx) for complete logging best practices.
+See the [Backend Logging Guide](/development/backend/logging) for complete logging best practices.
 
 ## Writing New Tests
 

docs/development/gateway/caching-system.mdx

@@ -96,7 +96,7 @@ Tool discovery is automatically triggered during:
 The discovery workflow follows these steps:
 
 1. **Server Enumeration**: Identify all MCP servers configured for the team
-2. **Process Communication**: Connect to already-running MCP server processes as described in [Process Management](./process-management)
+2. **Process Communication**: Connect to already-running MCP server processes as described in [Gateway Process Management](/development/gateway/process-management)
 3. **Tool Interrogation**: Query each running server for its available tools using MCP protocol
 4. **Schema Extraction**: Extract complete tool schemas including parameters and descriptions
 5. **Namespacing**: Apply server-specific namespacing to prevent tool name conflicts
@@ -175,9 +175,9 @@ The caching system ensures data privacy by:
 
 The caching system integrates seamlessly with other Gateway components:
 
-- **[MCP Configuration Management](./mcp)**: Uses team configurations to determine which servers to discover
-- **[Process Management](./process-management)**: Coordinates with process spawning for tool discovery
-- **[Project Structure](./structure)**: Implements the centralized architecture through the utils layer
+- **[MCP Configuration Management](/development/gateway/mcp)**: Uses team configurations to determine which servers to discover
+- **[Gateway Process Management](/development/gateway/process-management)**: Coordinates with process spawning for tool discovery
+- **[Gateway Project Structure](/development/gateway/structure)**: Implements the centralized architecture through the utils layer
 - **HTTP Proxy Server**: Provides cached tool information for immediate client responses
 
 ## Cache Management Operations

docs/development/gateway/index.mdx

@@ -165,11 +165,11 @@ The Gateway works with MCP server configurations in this format:
 3. **Persistent Process Startup**: Starts all configured MCP servers as background processes when gateway launches
 4. **HTTP Server**: Starts local HTTP server with SSE endpoints immediately available (default: `localhost:9095/sse`)
 5. **Request Handling**: Receives MCP requests from development tools and routes to already-running processes
-6. **Process Management**: Maintains persistent background processes as described in [Process Management](./process-management)
+6. **Process Management**: Maintains persistent background processes as described in [Gateway Process Management](/development/gateway/process-management).
 7. **Credential Injection**: Securely injects environment variables into running processes at startup
 8. **Tool Routing**: Routes namespaced tool calls to persistent MCP servers via stdio transport
 
-For detailed information about the caching system, see [Caching System](./caching-system).
+For detailed information about the caching system, see [Gateway Caching System](/development/gateway/caching-system).
 
 ## Language Support
 
@@ -227,5 +227,3 @@ The Gateway is actively under development. Key areas for contribution:
 - **Phase 3**: Support for remote MCP servers (HTTP transport)
 - **Phase 4**: Advanced monitoring and analytics
 - **Future**: Plugin system for custom MCP server types
-
-For detailed contribution guidelines, see [CONTRIBUTING.md](../../../CONTRIBUTING.md).