docs: fix 5 broken intra-repo links

docs/bulk-redirects.md

@@ -84,5 +84,5 @@ can audit.
 
 ## See also
 
-- [configuration.md](configuration.md#redirect-action) - full action schema.
+- [configuration.md](configuration.md#redirect) - full action schema.
 - `examples/74-bulk-redirects/` - runnable CSV + inline example.

docs/exposed-credentials.md

@@ -77,5 +77,5 @@ Switch `action: block` once those response loops are wired up and the false-posi
 
 ## See also
 
-- [configuration.md](configuration.md#exposed-credentials) - schema reference.
+- [configuration.md](configuration.md#exposed_credentials) - schema reference.
 - `examples/77-exposed-credentials/` - runnable example.

docs/feature-flags.md

@@ -85,4 +85,4 @@ The store does not currently emit metrics. Wire a metric of your choice around t
 ## See also
 
 - `crates/sbproxy-extension/src/flags.rs` - source.
-- [scripting.md](scripting.md#cel-functions) - full CEL surface.
+- [scripting.md](scripting.md#3-cel-expressions) - full CEL surface.

docs/routing-strategies.md

@@ -1,7 +1,7 @@
 # Routing Strategies
 *Last modified: 2026-04-27*
 
-The `RoutingStrategy` trait is an opt-in extension point for plugging custom upstream selection logic into a `load_balancer` action. It lives in `sbproxy-modules::action::routing` and is the OSS scaffold that production work in [Fail-6](roadmap.md) (LoRA-aware, GPU-aware, contextual-bandit routing) will build against. The trait runs on the request hot path, so it is synchronous, takes a borrowed slice of already-projected target state, and returns the index of the chosen target or `None` to fall through to the configured `lb_method`.
+The `RoutingStrategy` trait is an opt-in extension point for plugging custom upstream selection logic into a `load_balancer` action. It lives in `sbproxy-modules::action::routing` and is the OSS scaffold that production work (LoRA-aware, GPU-aware, contextual-bandit routing) will build against. The trait runs on the request hot path, so it is synchronous, takes a borrowed slice of already-projected target state, and returns the index of the chosen target or `None` to fall through to the configured `lb_method`.
 
 The existing built-in algorithms (`round_robin`, `weighted`, `least_connections`, `consistent_hash`, `random`, `priority`, ...) are unchanged and are not yet behind this trait. They continue to handle every request the way they always have. Strategies plug in alongside them: when a `RoutingStrategy` returns `None`, the configured built-in `lb_method` runs as the fall-back. The migration of the built-ins to live behind the trait, plus the three concrete production strategies, is tracked separately under Fail-6 in the roadmap.
 

docs/web-bot-auth.md

@@ -97,7 +97,7 @@ A signed crawler still pays per request unless its `Crawler-Payment` token redee
 
 ## See also
 
-- [configuration.md](configuration.md#bot_auth) - schema reference.
+- [configuration.md](configuration.md#authentication) - schema reference (`bot_auth` provider).
 - [RFC 9421](https://www.rfc-editor.org/rfc/rfc9421.html) - the underlying signature standard.
 - `crates/sbproxy-modules/src/auth/bot_auth.rs` - source.
 - `examples/91-web-bot-auth/sb.yml` - runnable example.