Enhance documentation completeness and add diagram links and SLA/SLO targets

[OgeonX-Ai]

Motivation

• Improve completeness and navigability of core service documentation by ensuring each major doc points to its corresponding Mermaid diagram.
• Make SLA/SLO expectations explicit in the metrics/KPI guidance to support operational clarity and measurable service targets.
• Surface missing diagram references in architecture, operating model, IR, change, and exception docs so diagrams are discoverable from the canonical Markdown.
• Keep changes documentation-only and public-safe (no secrets or infra changes).

Description

• Added diagram references to docs/05-operating-model.md, docs/04-reference-architecture.md, docs/11-incident-response.md, docs/12-change-and-release.md, docs/13-exception-handling.md, docs/16-logging-monitoring-siem.md, and docs/19-devsecops-pipelines.md to point at files in docs/22-diagrams/.
• Expanded docs/07-metrics-and-kpis.md with a service-level SLA/SLO targets table and ensured the KPI catalog and sample dashboard remain present.
• Committed the documentation updates as a focused change set with the message Enhance documentation completeness and diagram links.
• No functional or infrastructure code was modified; changes are limited to Markdown and diagram-linking updates.

Testing

• Verified file contents and previews using local text inspection commands (e.g., sed -n) and confirmed the modified Markdown files were staged and committed with git commit.
• Performed basic repository status checks to confirm the set of modified docs were updated and included in the commit.
• No CI workflows were executed in this environment, and no automated linters or link-checkers were run as part of this change.
• Change is documentation-only and does not require cloud or secrets validation.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 267c4b020f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use page-relative links to avoid broken nav on subpages

The navigation links are hard-coded as pages/... paths, which resolve correctly from site/index.html but break on any page under site/pages/ (e.g., site/pages/overview.html resolves pages/overview.html to site/pages/pages/overview.html, which doesn’t exist). This means the nav/search links won’t work on subpages. Consider using root-relative paths (if served from a web root) or computing the base path so links resolve from both the index and subpages.

Useful? React with 👍 / 👎.