docs: merge duplicate OpenRouter entry, fix broken plugin anchor links

docs/plugins/architecture.md

@@ -684,7 +684,10 @@ api.registerProvider({
   live-model policy.
 - OpenRouter uses `catalog` plus `resolveDynamicModel` and
   `prepareDynamicModel` because the provider is pass-through and may expose new
-  model ids before OpenClaw's static catalog updates.
+  model ids before OpenClaw's static catalog updates; it also uses
+  `capabilities`, `wrapStreamFn`, and `isCacheTtlEligible` to keep
+  provider-specific request headers, routing metadata, reasoning patches, and
+  prompt-cache policy out of core.
 - GitHub Copilot uses `catalog`, `auth`, `resolveDynamicModel`, and
   `capabilities` plus `prepareRuntimeAuth` and `fetchUsageSnapshot` because it
   needs provider-owned device login, model fallback behavior, Claude transcript
@@ -701,9 +704,6 @@ api.registerProvider({
   modern-model matching; Gemini CLI OAuth also uses `formatApiKey`,
   `resolveUsageAuth`, and `fetchUsageSnapshot` for token formatting, token
   parsing, and quota endpoint wiring.
-- OpenRouter uses `capabilities`, `wrapStreamFn`, and `isCacheTtlEligible`
-  to keep provider-specific request headers, routing metadata, reasoning
-  patches, and prompt-cache policy out of core.
 - Moonshot uses `catalog` plus `wrapStreamFn` because it still uses the shared
   OpenAI transport but needs provider-owned thinking payload normalization.
 - Kilocode uses `catalog`, `capabilities`, `wrapStreamFn`, and

docs/plugins/manifest.md

@@ -33,7 +33,7 @@ plugin errors and block config validation.
 
 See the full plugin system guide: [Plugins](/tools/plugin).
 For the native capability model and current external-compatibility guidance:
-[Capability model](/tools/plugin#public-capability-model).
+[Capability model](/plugins/architecture#public-capability-model).
 
 ## Required fields
 
@@ -135,7 +135,7 @@ See [Configuration reference](/configuration) for the full `plugins.*` schema.
   `--auth-choice` resolution, preferred-provider mapping, and simple onboarding
   CLI flag registration before provider runtime loads. For runtime wizard
   metadata that requires provider code, see
-  [Provider runtime hooks](/tools/plugin#provider-runtime-hooks).
+  [Provider runtime hooks](/plugins/architecture#provider-runtime-hooks).
 - Exclusive plugin kinds are selected through `plugins.slots.*`.
   - `kind: "memory"` is selected by `plugins.slots.memory`.
   - `kind: "context-engine"` is selected by `plugins.slots.contextEngine`