docs: Fix Broken Links (#137)

* docs: Fix Broken Links

* One More Fix

Author: mckaragoz

docs/content/auth-flows/overview.md

@@ -210,19 +210,19 @@ The following pages explain each operation in detail. This overview focuses on t
 
 | Flow | Purpose | Practical outcome | Guide |
 | --- | --- | --- | --- |
-| **Login** | Establish authenticated access from acceptable credentials. | Creates a valid authentication session in session-issuing modes; may issue tokens according to policy. | [Login Flow](./login-flow.md) |
-| **Refresh** | Continue an existing authentication relationship using renewal authority. | Maintains or renews access according to mode, validation, and configured refresh behavior. | [Refresh Flow](./refresh-flow.md) |
-| **Logout** | End access at the applicable session or device scope. | Terminates authentication access and handles configured client cleanup/navigation. | [Logout Flow](./logout-flow.md) |
+| **Login** | Establish authenticated access from acceptable credentials. | Creates a valid authentication session in session-issuing modes; may issue tokens according to policy. | [Login Flow](/docs/auth-flows/login-flow) |
+| **Refresh** | Continue an existing authentication relationship using renewal authority. | Maintains or renews access according to mode, validation, and configured refresh behavior. | [Refresh Flow](/docs/auth-flows/refresh-flow) |
+| **Logout** | End access at the applicable session or device scope. | Terminates authentication access and handles configured client cleanup/navigation. | [Logout Flow](/docs/auth-flows/logout-flow) |
 
 These flows are related but not interchangeable. Login establishes access; refresh continues it; logout terminates it. Revocation operations provide stronger invalidation controls for the relevant security scope.
 
 ## Concepts shared by the flows
 
 | Concept | What it contributes | Guide |
 | --- | --- | --- |
-| **Session lifecycle** | Root, chain, and session relationships; creation, continuity, expiry, and invalidation. | [Session Lifecycle](./session-lifecycle.md) |
-| **Token behavior** | Access and refresh credentials, validation, renewal, and mode-specific behavior. | [Token Behavior](./token-behavior.md) |
-| **Device management** | Device-associated chains, multi-device access, and targeted termination. | [Device Management](./device-management.md) |
+| **Session lifecycle** | Root, chain, and session relationships; creation, continuity, expiry, and invalidation. | [Session Lifecycle](/docs/sessions-devices/session-lifecycle) |
+| **Token behavior** | Access and refresh credentials, validation, renewal, and mode-specific behavior. | [Token Behavior](/docs/security/token-security) |
+| **Device management** | Device-associated chains, multi-device access, and targeted termination. | [Device Management](/docs/sessions-devices/device-management) |
 
 ## What this design enables in real applications
 
@@ -246,4 +246,4 @@ This is the larger goal of UltimateAuth's unified model—not to make every auth
 
 ## Next step
 
-Start with [Login Flow](/docs/auth-flows/login) to see how UltimateAuth turns validated credentials into controlled authenticated access.
+Start with [Login Flow](/docs/auth-flows/login-flow) to see how UltimateAuth turns validated credentials into controlled authenticated access.

docs/content/client-sdk/authentication.md

@@ -1263,7 +1263,7 @@ For application-specific workflows that cannot be expressed through the componen
 
 ## Next Steps
 
-- [Session Management](/docs/client/session-management) — Inspect and manage session and device information.
+- [Session Management](/docs/client-sdk/session-management) — Inspect and manage session and device information.
 - [Token Security](/docs/security/token-security) — Understand token validity, refresh behavior, and revocation.
 - [Refresh Rotation & Replay Protection](/docs/security/refresh-rotation) — Explore refresh concurrency and reuse security.
 - [Authentication Modes](/docs/fundamentals/auth-modes) — Compare authentication behavior across modes.

docs/content/client-sdk/authorization.md

@@ -1310,7 +1310,7 @@ if (result.IsSuccess)
 
 This pattern works well alongside `UAuthClient.Users` for building a unified user administration interface.
 
-See [User Management](/docs/client/user-management).
+See [User Management](/docs/client-sdk/user-management).
 
 ## 20. Authorization State Events
 
@@ -1373,7 +1373,7 @@ Revoking a session changes whether an authentication session remains valid.
 
 Applications may combine these operations when security policy requires immediate termination of access, but the concepts should remain separate.
 
-See [Session Management](/docs/client/session-management).
+See [Session Management](/docs/client-sdk/session-management).
 
 ## 22. Multi-Tenant Authorization
 
@@ -1544,8 +1544,8 @@ This allows applications to provide flexible administrative interfaces while kee
 
 ## Next Steps
 
-- [Policies & Access Control](/docs/plugin-domains/policies-access-control) — Understand application policies and access rules.
-- [Authorization Pipeline Internals](/docs/security/authorization-pipeline-internals) — Explore how authorization decisions are evaluated.
-- [User Management](/docs/client/user-management) — Manage user accounts and lifecycle.
-- [Session Management](/docs/client/session-management) — Manage authenticated sessions and devices.
+- [Policies & Access Control](/docs/plugin-domains/policies) — Understand application policies and access rules.
+- [Authorization Pipeline Internals](/docs/security/authorization-pipeline) — Explore how authorization decisions are evaluated.
+- [User Management](/docs/client-sdk/user-management) — Manage user accounts and lifecycle.
+- [Session Management](/docs/client-sdk/session-management) — Manage authenticated sessions and devices.
 - [Session Security Model](/docs/security/session-security) — Understand session validity and security boundaries.

docs/content/client-sdk/credentials.md

@@ -1095,9 +1095,7 @@ Use `UAuthPasswordClientValidator` to provide immediate feedback before submitti
 ```csharp
 using CodeBeam.UltimateAuth.Client;
 
-var errors = UAuthPasswordClientValidator.Validate(
-    password,
-    policy);
+var errors = UAuthPasswordClientValidator.Validate(password, policy);
 
 if (errors.Count == 0)
 {

docs/content/client-sdk/identifiers.md

@@ -50,7 +50,7 @@ Each identifier has its own value, type, verification state, and primary designa
 
 **Identifiers are not profiles.** A user profile contains information such as display name and biography, while identifiers represent managed identity-related values.
 
-For general profile management, see [User Management](/docs/client/user-management).
+For general profile management, see [User Management](/docs/client-sdk/user-management).
 
 ## 2. Accessing the Identifier Client
 
@@ -1070,8 +1070,8 @@ Applications should distinguish identifier management from session revocation an
 
 ## Next Steps
 
-- [User Management](/docs/client/user-management) — Manage user profiles, account status, and lifecycle.
-- [Credentials](/docs/client/credentials) — Manage passwords, credentials, and recovery workflows.
-- [Authentication](/docs/client/authentication) — Understand login and authentication flows.
+- [User Management](/docs/client-sdk/user-management) — Manage user profiles, account status, and lifecycle.
+- [Credentials](/docs/client-sdk/credentials) — Manage passwords, credentials, and recovery workflows.
+- [Authentication](/docs/client-sdk/authentication) — Understand login and authentication flows.
 - [Users](/docs/plugin-domains/users) — Explore the user domain architecture.
 - [Session Security Model](/docs/security/session-security) — Understand authentication security boundaries.

docs/content/client-sdk/session-management.md

@@ -439,7 +439,7 @@ var result = await UAuthClient.Flows.LogoutMyDeviceAsync(
 
 Pass a `SessionChainId`, not an individual `AuthSessionId`.
 
-For complete logout examples, see [Authentication](/docs/client/authentication).
+For complete logout examples, see [Authentication](/docs/client-sdk/authentication).
 
 ## 11. Build a Device Management Page
 
@@ -792,7 +792,7 @@ These operations should be protected by appropriate permissions and, where requi
 
 ## Next Steps
 
-- [Authentication](/docs/client/authentication) — Login, logout, refresh, and authentication state validation.
+- [Authentication](/docs/client-sdk/authentication) — Login, logout, refresh, and authentication state validation.
 - [Session Model & Lifecycle](/docs/sessions-devices/session-lifecycle) — Session roots, chains, lifecycle, and expiration.
 - [Device Management](/docs/sessions-devices/device-management) — Device-associated authentication contexts.
 - [Session Security Model](/docs/security/session-security) — Revocation and session security boundaries.

docs/content/client-sdk/user-management.md

@@ -16,7 +16,7 @@ A user has a stable identity and may have multiple profiles. Account status cont
 
 This guide covers the public `IUserClient` API, including self-service and administrative operations, structured results, pagination, multi-profile support, and important update semantics.
 
-For email addresses, usernames, phone numbers, and identifier verification, see [Identifiers](/docs/client/identifiers).
+For email addresses, usernames, phone numbers, and identifier verification, see [Identifiers](/docs/client-sdk/identifiers).
 
 ## 1. Accessing the User Client
 
@@ -420,7 +420,7 @@ Verification flags must not be treated as client-controlled proof of identifier
 
 The server is responsible for enforcing verification requirements and determining whether a caller is authorized to establish verified identifier state.
 
-For identifier-specific operations and verification workflows, see [Identifiers](/docs/client/identifiers).
+For identifier-specific operations and verification workflows, see [Identifiers](/docs/client-sdk/identifiers).
 
 ### UserCreateResult
 
@@ -1339,8 +1339,8 @@ Applications should consider retention, recovery, audit requirements, and depend
 
 ## Next Steps
 
-- [Identifiers](/docs/client/identifiers) — Manage usernames, email addresses, phone numbers, and verification.
-- [Authentication](/docs/client/authentication) — Login, refresh, logout, and authentication state.
-- [Session Management](/docs/client/session-management) — Inspect and revoke sessions across devices.
+- [Identifiers](/docs/client-sdk/identifiers) — Manage usernames, email addresses, phone numbers, and verification.
+- [Authentication](/docs/client-sdk/authentication) — Login, refresh, logout, and authentication state.
+- [Session Management](/docs/client-sdk/session-management) — Inspect and revoke sessions across devices.
 - [Users](/docs/plugin-domains/users) — Understand the user domain and lifecycle architecture.
 - [Policies & Access Control](/docs/plugin-domains/policies) — Understand authorization enforcement for user operations.

docs/content/configuration/overview.md

@@ -490,7 +490,7 @@ builder.Services.AddUltimateAuthServer(options =>
 
 Do not enable an unsupported mode merely because it exists in the enum.
 
-For supported modes and their behavior, see [Authentication Modes](/docs/fundamentals/authentication-modes).
+For supported modes and their behavior, see [Authentication Modes](/docs/fundamentals/auth-modes).
 
 ## 10. Configure Credential Session Policies
 
@@ -836,7 +836,6 @@ The Core-only registration exists for infrastructure scenarios that explicitly c
 ## Next Steps
 
 - [Configuration Overview](/docs/configuration/configuration-overview) — Understand the overall configuration model.
-- [Core Options](/docs/configuration/core-options) — Explore the reusable option definitions composed into server configuration.
 - [Server Options](/docs/configuration/server-options) — Configure authentication and security behavior.
 - [Client Options](/docs/configuration/client-options) — Configure client profiles, flows, and SDK behavior.
 - [Advanced Configuration](/docs/configuration/advanced-configuration) — Customize integration, multi-tenancy, and runtime extension points.

docs/content/fundamentals/flow-based-auth.md

@@ -234,7 +234,7 @@ Separating these responsibilities prevents transport behavior from becoming auth
 
 For example, whether an access token is delivered through a cookie or header should not change the security requirements used to issue it.
 
-The technical components and request pipeline implementing these responsibilities are documented in [Auth Flows](../auth-flows/).
+The technical components and request pipeline implementing these responsibilities are documented in [Auth Flows](/docs/auth-flows/overview).
 
 ## Flows across client runtimes
 

docs/content/plugin-domains/credentials.md

@@ -306,6 +306,6 @@ The current password implementation provides the operational foundation. The bro
 
 - [Users](/docs/plugin-domains/users) — Understand identity ownership, identifiers, and account lifecycle.
 - [Authorization](/docs/plugin-domains/authorization) — Explore how authenticated identities are evaluated against access policies.
-- [Plugin Domains](/docs/plugin-domains) — Review the architecture and responsibilities of Plugin Domains.
+- [Plugin Domains](/docs/plugin-domains/overview) — Review the architecture and responsibilities of Plugin Domains.
 
-For the authentication flow that consumes credential verification results, see [Flow-Based Authentication](/docs/fundamentals/flow-based-authentication).
+For the authentication flow that consumes credential verification results, see [Flow-Based Authentication](/docs/fundamentals/flow-based-auth).