feat: automate versioned CLI command documentation scaffolding and changelog engine

.github/docs-template/config/README.md

@@ -0,0 +1,134 @@
+# `kdm config` — Configuration Management
+
+**Version:** v1.2.1
+
+## Overview
+
+The `kdm config` command group manages KDM CLI configuration, including notification service setup, custom settings, and credential management. Configuration is stored locally using the `conf` package.
+
+## Syntax
+
+```bash
+kdm config <subcommand>
+```
+
+## Sub-commands
+
+### `kdm config setup`
+
+Interactively sets up the notification service (Discord webhook or Email SMTP).
+
+**Example:**
+
+```bash
+kdm config setup
+```
+
+**Interactive Flow:**
+
+1. Select a notification service:
+   - **Discord** — Send alerts to a Discord channel via webhook.
+   - **Email (SMTP)** — Send alerts via email SMTP.
+   - **None** — Disable notifications.
+
+2. For **Discord**, you will be prompted for a webhook URL.
+3. For **Email**, you will be prompted for SMTP host, port, user, and recipient email.
+
+**Discord Webhook Setup:**
+
+1. Open your Discord server settings.
+2. Go to **Integrations > Webhooks**.
+3. Create a new webhook and choose the alert channel.
+4. Copy the webhook URL (must start with `https://discord.com/api/webhooks/`).
+
+**Email SMTP Setup:**
+
+| Setting | Default | Description |
+|---------|---------|-------------|
+| Host | `smtp.gmail.com` | SMTP server address |
+| Port | `587` | SMTP port (STARTTLS) |
+| User | — | Your email address |
+| To | — | Alert recipient email |
+
+> **Note:** SMTP passwords must be set via the `KDM_SMTP_PASSWORD` environment variable.
+
+---
+
+### `kdm config set <key> <value>`
+
+Sets a specific configuration value.
+
+**Example:**
+
+```bash
+kdm config set alert_cooldown 300
+kdm config set email_port 465
+```
+
+**Supported Keys:**
+
+| Key | Type | Description |
+|-----|------|-------------|
+| `alert_cooldown` | number | Cooldown period between alerts (seconds) |
+| `email_port` | number | SMTP port |
+| `notification_service` | string | `discord`, `email`, or `none` |
+| `discord_webhook` | string | Discord webhook URL |
+| `email_host` | string | SMTP host |
+| `email_user` | string | SMTP username |
+| `email_to` | string | Alert recipient email |
+
+---
+
+### `kdm config list`
+
+Lists all current configuration values.
+
+**Example:**
+
+```bash
+kdm config list
+```
+
+**Expected Output:**
+
+```
+Current KDM Configuration:
+──────────────────────────────────────────────────
+ notification_service   : discord
+ discord_webhook        : https://discord.com/api/webhooks/...
+──────────────────────────────────────────────────
+
+ Note: SMTP passwords must be set via KDM_SMTP_PASSWORD env var.
+```
+
+---
+
+### `kdm config clear`
+
+Clears all configuration and resets to defaults.
+
+**Example:**
+
+```bash
+kdm config clear
+```
+
+**Expected Output:**
+
+```
+✓ Configuration cleared.
+```
+
+## Configuration File Location
+
+Configuration is stored in the default `conf` package location:
+
+- **macOS:** `~/Library/Application Support/kdm-cli`
+- **Linux:** `~/.config/kdm-cli`
+- **Windows:** `%APPDATA%\kdm-cli`
+
+## Common Errors
+
+- **Invalid webhook URL** — Must match `https://discord.com/api/webhooks/<id>/<token>`.
+- **Invalid email address** — Must be a valid email format.
+- **Invalid port number** — Must be between 1 and 65535.

.github/docs-template/health/README.md

@@ -0,0 +1,154 @@
+# `kdm health` — Health Status
+
+> **Version:** `v1.2.1`
+
+---
+
+## Overview
+
+The `kdm health` command checks and reports the health status of Kubernetes pods or Docker containers. It provides a clean, color-coded table with real-time status fetched directly from Docker and Kubernetes clients.
+
+> **Fix (Issue #1):**  
+> This command previously returned only a placeholder message. It now displays real health data from Docker containers and Kubernetes pods.
+
+---
+
+# Syntax
+
+```bash
+kdm health <target>
+```
+
+---
+
+# Parameters
+
+| Parameter | Description | Valid Values |
+| :--- | :--- | :--- |
+| `target` | The workload type to check | `pods`, `containers`, `all` |
+
+---
+
+# Usage
+
+---
+
+## `kdm health pods`
+
+Checks the health status of all Kubernetes pods.
+
+### Example
+
+```bash
+kdm health pods
+```
+
+### Expected Output
+
+```text
+╭──────┬─────────────────────────────┬─────────┬──────────────────────────────────────╮
+│ TYPE │ NAME                        │ HEALTH  │ DETAILS                              │
+├──────┼─────────────────────────────┼─────────┼──────────────────────────────────────┤
+│ pod  │ node-app-6f65c56b74-7tkvf   │ Running │ namespace: default, restarts: 0      │
+│ pod  │ nginx-deployment-abc123     │ Failed  │ namespace: production, restarts: 5   │
+╰──────┴─────────────────────────────┴─────────┴──────────────────────────────────────╯
+```
+
+### Health Indicators
+
+| Status Color | Meaning |
+| :--- | :--- |
+| 🟢 Green | `healthy`, `running`, `Running` |
+| 🔴 Red | `unhealthy`, `exited`, `Failed` |
+| 🟡 Yellow | Other states like `Pending`, `paused` |
+
+### Use Cases
+
+- Monitor pod health in real time
+- Identify failing services before outages occur
+
+---
+
+## `kdm health containers`
+
+Checks the health status of all Docker containers.
+
+### Example
+
+```bash
+kdm health containers
+```
+
+### Expected Output
+
+```text
+╭───────────┬────────────┬─────────┬───────────────╮
+│ TYPE      │ NAME       │ HEALTH  │ DETAILS       │
+├───────────┼────────────┼─────────┼───────────────┤
+│ container │ test-nginx │ running │ Up 8 minutes  │
+│ container │ my-app     │ exited  │ Exited (1)    │
+╰───────────┴────────────┴─────────┴───────────────╯
+```
+
+### Use Cases
+
+- Verify container health
+- Detect unhealthy or restarting containers
+
+---
+
+## `kdm health all`
+
+Checks health for both pods and containers in a single command. If one source (Docker or Kubernetes) is unavailable, the other still renders successfully.
+
+### Example
+
+```bash
+kdm health all
+```
+
+---
+
+### Expected Output (Kubernetes unavailable)
+
+```text
+⚠ Kubernetes unavailable: connect ECONNREFUSED 127.0.0.1:8080
+
+╭───────────┬────────────┬─────────┬──────────────╮
+│ TYPE      │ NAME       │ HEALTH  │ DETAILS      │
+├───────────┼────────────┼─────────┼──────────────┤
+│ container │ test-nginx │ running │ Up 8 minutes │
+╰───────────┴────────────┴─────────┴──────────────╯
+```
+
+---
+
+### Expected Output (Both available)
+
+```text
+╭───────────┬───────────────────────────┬─────────┬──────────────────────────────────────╮
+│ TYPE      │ NAME                      │ HEALTH  │ DETAILS                              │
+├───────────┼───────────────────────────┼─────────┼──────────────────────────────────────┤
+│ container │ test-nginx                │ running │ Up 8 minutes                         │
+│ pod       │ node-app-6f65c56b74-7tkvf │ Running │ namespace: default, restarts: 0      │
+╰───────────┴───────────────────────────┴─────────┴──────────────────────────────────────╯
+```
+
+---
+
+# Common Errors
+
+| Error | Cause | Fix |
+| :--- | :--- | :--- |
+| `Unknown target` | Invalid target passed | Use `pods`, `containers`, or `all` |
+| `No workloads found` | No containers or pods running | Start Docker containers or Kubernetes pods |
+| `Docker unavailable` | Docker daemon not running | Run `sudo systemctl start docker` |
+| `Kubernetes unavailable` | No cluster connection | Run `minikube start` or configure `kubectl` |
+
+---
+
+# Notes
+
+- Supports both Docker and Kubernetes environments
+- Displays partial results even if one backend fails
+- Provides readable CLI tables for faster debugging and monitoring