📝 [docs] Updates doc front matter metadata

📝 [docs] Replaces reserved front‑matter fields with doc‑specific metadata across docs and guidance to avoid TypeDoc routing side effects, plus refreshes review dates. 🧭
🧹 [chore] Tightens front‑matter schema, validation rules, and serialization order to require the schema reference and new doc metadata fields. ✅
📝 [docs] Normalizes formatting, list styles, and navigation aids while trimming front‑matter from TSDoc tag pages. 📚
🔧 [build] Expands TypeDoc markdown generation options and adjusts link validation and Docusaurus warning behavior for docs builds. 🧰

Signed-off-by: Nick2bad4u <20943337+Nick2bad4u@users.noreply.github.com>

Author: Nick2bad4u

.github/Markdown.instructions.md

@@ -27,6 +27,6 @@ Follow these guidelines for formatting and structuring your markdown content:
 
 -   **Front Matter**: Use `---` to delimit YAML front matter when a file needs metadata.
     -   In general markdown files (e.g. `README.md` at the repo root), choose fields that are useful to readers and tooling.
-    -   For documentation pages under `docs/**`, follow the schema in `config/schemas/doc-frontmatter.schema.json` and keep fields (such as `title`, `summary`, `category`, and `tags`) valid per that schema. Use `scripts/validate-doc-frontmatter.mjs` and the `docs:validate:frontmatter` / `docs:check` scripts to verify correctness.
+    -   For documentation pages under `docs/**`, follow the schema in `config/schemas/doc-frontmatter.schema.json` and keep fields (such as `doc_title`, `summary`, `doc_category`, and `tags`) valid per that schema. (We intentionally avoid TypeDoc-reserved keys like `title`/`category`/`group` in this repo's docs frontmatter.) Use `scripts/validate-doc-frontmatter.mjs` and the `docs:validate:frontmatter` / `docs:check` scripts to verify correctness.
 -   **Metadata**: Ensure that metadata is accurate and up to date. When a document uses front matter, update date or version fields when content meaningfully changes.
 -   **Tooling alignment**: The repository enforces Markdown style via Remark (`.remarkrc.mjs`). Run `npm run remark:check` (or `npm run docs:check` for doc bundles) before committing to catch lint issues.

config/schemas/doc-frontmatter.schema.json

@@ -2,7 +2,7 @@
     "$id": "https://uptime-watcher.dev/schemas/doc-frontmatter.schema.json",
     "$schema": "https://json-schema.org/draft/2020-12/schema",
     "additionalProperties": false,
-    "description": "Schema for YAML front-matter used in Uptime Watcher Markdown guides (e.g. docs/Guides/*.md).",
+    "description": "Schema for YAML front-matter used in Uptime Watcher Markdown guides (e.g. docs/Guides/*.md). NOTE: This schema intentionally avoids TypeDoc-reserved keys (title/category/group) because TypeDoc's external-documents frontmatter handling can change output routing when those keys are present.",
     "properties": {
         "$schema": {
             "description": "Optional JSON Schema reference used by editors to validate front matter.",
@@ -23,16 +23,26 @@
             "minLength": 1,
             "type": "string"
         },
-        "category": {
-            "description": "Coarse document type; currently always 'guide' for docs/Guides/*.md.",
-            "enum": ["guide"],
-            "type": "string"
-        },
         "created": {
             "description": "Date the document was originally created (YYYY-MM-DD), usually from git log.",
             "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
             "type": "string"
         },
+        "doc_category": {
+            "description": "Coarse document type; currently always 'guide' for docs/Guides/*.md. Named 'doc_category' to avoid TypeDoc frontmatter routing side-effects.",
+            "enum": ["guide"],
+            "type": "string"
+        },
+        "doc_group": {
+            "description": "Optional grouping label for internal tooling. Named 'doc_group' to avoid TypeDoc frontmatter routing side-effects.",
+            "minLength": 1,
+            "type": "string"
+        },
+        "doc_title": {
+            "description": "Human-friendly document title (usually matches the H1). Named 'doc_title' to avoid TypeDoc frontmatter routing side-effects.",
+            "minLength": 1,
+            "type": "string"
+        },
         "last_reviewed": {
             "description": "Date the content was last reviewed/updated (YYYY-MM-DD).",
             "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
@@ -67,11 +77,6 @@
             "type": "array",
             "uniqueItems": true
         },
-        "title": {
-            "description": "Human-friendly document title (usually matches the H1).",
-            "minLength": 1,
-            "type": "string"
-        },
         "topics": {
             "description": "Optional higher-level areas (e.g. monitoring, architecture).",
             "items": {
@@ -84,12 +89,13 @@
     },
     "required": [
         "author",
-        "category",
         "created",
+        "doc_category",
+        "doc_title",
         "last_reviewed",
         "summary",
         "tags",
-        "title"
+        "schema"
     ],
     "title": "Uptime Watcher Documentation Front Matter",
     "type": "object"

docs/Architecture/ADRs/ADR_001_REPOSITORY_PATTERN.md

@@ -1,19 +1,18 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-001: Repository Pattern for Database Access"
+doc_title: "ADR-001: Repository Pattern for Database Access"
 summary: "Establishes a repository pattern for all database access with transaction safety, caching, and event-driven hooks."
 created: "2025-08-05"
-last_reviewed: "2025-11-17"
-category: "guide"
+last_reviewed: "2026-01-31"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "database"
- - "repository-pattern"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "database"
+  - "repository-pattern"
 ---
-
 # ADR-001: Repository Pattern for Database Access
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_002_EVENT_DRIVEN_ARCHITECTURE.md

@@ -1,20 +1,19 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-002: Event-Driven Architecture with TypedEventBus"
+doc_title: "ADR-002: Event-Driven Architecture with TypedEventBus"
 summary: "Defines an event-driven architecture using a TypedEventBus for decoupled, type-safe communication across backend and frontend."
 created: "2025-08-05"
 last_reviewed: "2026-01-11"
-category: "guide"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "events"
- - "typed-event-bus"
- - "ipc"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "events"
+  - "typed-event-bus"
+  - "ipc"
 ---
-
 # ADR-002: Event-Driven Architecture with TypedEventBus
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_003_ERROR_HANDLING_STRATEGY.md

@@ -1,19 +1,18 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-003: Comprehensive Error Handling Strategy"
+doc_title: "ADR-003: Comprehensive Error Handling Strategy"
 summary: "Establishes a comprehensive multi-layer error handling strategy with shared utilities, store-safe patterns, and production-grade resilience."
 created: "2025-08-05"
-last_reviewed: "2025-12-11"
-category: "guide"
+last_reviewed: "2026-01-31"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "error-handling"
- - "resilience"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "error-handling"
+  - "resilience"
 ---
-
 # ADR-003: Comprehensive Error Handling Strategy
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_004_FRONTEND_STATE_MANAGEMENT.md

@@ -1,20 +1,19 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-004: Frontend State Management with Zustand"
+doc_title: "ADR-004: Frontend State Management with Zustand"
 summary: "Defines the frontend state management strategy using Zustand with modular composition and selective persistence."
 created: "2025-08-05"
-last_reviewed: "2025-12-11"
-category: "guide"
+last_reviewed: "2025-12-23"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "zustand"
- - "state-management"
- - "frontend"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "zustand"
+  - "state-management"
+  - "frontend"
 ---
-
 # ADR-004: Frontend State Management with Zustand
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_005_IPC_COMMUNICATION_PROTOCOL.md

@@ -1,20 +1,19 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-005: IPC Communication Protocol"
+doc_title: "ADR-005: IPC Communication Protocol"
 summary: "Defines a standardized, type-safe IPC communication protocol using Electron's contextBridge with validation, error handling, and static guard rails."
 created: "2025-08-05"
-last_reviewed: "2026-01-08"
-category: "guide"
+last_reviewed: "2026-02-01"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "ipc"
- - "electron"
- - "communication"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "ipc"
+  - "electron"
+  - "communication"
 ---
-
 # ADR-005: IPC Communication Protocol
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_006_STANDARDIZED_CACHE_CONFIGURATION.md

@@ -1,19 +1,18 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-006: Standardized Cache Configuration"
+doc_title: "ADR-006: Standardized Cache Configuration"
 summary: "Defines standardized cache configuration constants and patterns for managers and services to ensure consistent TTLs and limits."
 created: "2025-08-23"
-last_reviewed: "2025-11-17"
-category: "guide"
+last_reviewed: "2025-12-16"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "cache"
- - "configuration"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "cache"
+  - "configuration"
 ---
-
 # ADR-006: Standardized Cache Configuration
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_007_SERVICE_CONTAINER_DEPENDENCY_INJECTION.md

@@ -1,20 +1,19 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-007: Service Container and Dependency Injection Pattern"
+doc_title: "ADR-007: Service Container and Dependency Injection Pattern"
 summary: "Establishes a centralized dependency injection container for managing service lifecycles, initialization order, and inter-service communication in the Electron main process."
 created: "2025-11-25"
-last_reviewed: "2025-11-25"
-category: "guide"
+last_reviewed: "2025-12-17"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "dependency-injection"
- - "service-container"
- - "electron"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "dependency-injection"
+  - "service-container"
+  - "electron"
 ---
-
 # ADR-007: Service Container and Dependency Injection Pattern
 
 ## Table of Contents

docs/Architecture/ADRs/ADR_008_MONITOR_TYPE_REGISTRY.md

@@ -1,20 +1,19 @@
 ---
 schema: "../../../config/schemas/doc-frontmatter.schema.json"
-title: "ADR-008: Monitor Type Registry and Plugin Architecture"
+doc_title: "ADR-008: Monitor Type Registry and Plugin Architecture"
 summary: "Establishes an extensible plugin-based system for registering monitor types with dynamic validation schemas, UI configuration, service factories, and version tagging (for future migration support)."
 created: "2025-11-25"
-last_reviewed: "2026-01-11"
-category: "guide"
+last_reviewed: "2026-02-10"
+doc_category: "guide"
 author: "Nick2bad4u"
 tags:
- - "uptime-watcher"
- - "architecture"
- - "adr"
- - "monitor-types"
- - "plugin-architecture"
- - "extensibility"
+  - "uptime-watcher"
+  - "architecture"
+  - "adr"
+  - "monitor-types"
+  - "plugin-architecture"
+  - "extensibility"
 ---
-
 # ADR-008: Monitor Type Registry and Plugin Architecture
 
 ## Table of Contents