docs: add Related sections to remaining CLI, gateway API, and help pages

docs/help/debugging.md

@@ -321,3 +321,8 @@ Default file:
 - Raw stream logs can include full prompts, tool output, and user data.
 - Keep logs local and delete them after debugging.
 - If you share logs, scrub secrets and PII first.
+
+## Related
+
+- [Troubleshooting](/help/troubleshooting)
+- [FAQ](/help/faq)

docs/help/faq.md

@@ -1967,3 +1967,9 @@ moved to a dedicated page:
 ---
 
 Still stuck? Ask in [Discord](https://discord.com/invite/clawd) or open a [GitHub discussion](https://github.com/openclaw/openclaw/discussions).
+
+## Related
+
+- [FAQ — quick start and first-run setup](/help/faq-first-run)
+- [FAQ — models and auth profiles](/help/faq-models)
+- [Troubleshooting](/help/troubleshooting)

docs/help/gpt54-codex-agentic-parity-maintainers.md

@@ -168,3 +168,7 @@ The parity harness is not the only evidence source. Keep this split explicit in
 | `/elevated full` hints were sometimes misleading            | PR B ties guidance to actual runtime capability and blocked reasons                     |
 | Long tasks could disappear into replay/compaction ambiguity | PR C emits explicit paused, blocked, abandoned, and replay-invalid state                |
 | Parity claims were anecdotal                                | PR D produces a report plus JSON verdict with the same scenario coverage on both models |
+
+## Related
+
+- [GPT-5.4 / Codex agentic parity](/help/gpt54-codex-agentic-parity)

docs/help/gpt54-codex-agentic-parity.md

@@ -226,3 +226,7 @@ Keep the default contract when:
 - you want the existing looser behavior
 - you are not using GPT-5-family models
 - you are testing prompts rather than runtime enforcement
+
+## Related
+
+- [GPT-5.4 / Codex parity maintainer notes](/help/gpt54-codex-agentic-parity-maintainers)

docs/help/scripts.md

@@ -49,3 +49,8 @@ Examples:
 
 - Keep scripts focused and documented.
 - Add a short entry in the relevant doc (or create one if missing).
+
+## Related
+
+- [Testing](/help/testing)
+- [Testing live](/help/testing-live)

docs/help/testing.md

@@ -699,3 +699,8 @@ When you fix a provider/model issue discovered in live:
 - SecretRef traversal guardrail:
   - `src/secrets/exec-secret-ref-id-parity.test.ts` derives one sampled target per SecretRef class from registry metadata (`listSecretTargetRegistryEntries()`), then asserts traversal-segment exec ids are rejected.
   - If you add a new `includeInPlan` SecretRef target family in `src/secrets/target-registry-data.ts`, update `classifyTargetClass` in that test. The test intentionally fails on unclassified target ids so new classes cannot be skipped silently.
+
+## Related
+
+- [Testing live](/help/testing-live)
+- [CI](/ci)