auto(docs): add CHANGELOG, W21 example README stubs, regen STATUS

Autonomous daily run (DOCS mode).
- Introduce CHANGELOG.md with [Unreleased] grouping of W21 commits
- Add examples/ README stubs for autosar-swc, dbc, 8d-problem-solving
- Regenerate STATUS.md (76/76 paired, all fresh)

Generated by automotive-skills-daily-standup scheduled task.

examples/8d-problem-solving-builder/README.md

@@ -0,0 +1,11 @@
+# 8d-problem-solving-builder — Example
+
+**What this skill produces:** An 11-tab audit-ready xlsx 8D (Eight Disciplines) problem-solving workbook — D1 Team through D8 Team Recognition, with Is/Is-Not and 5W2H problem description, root cause analysis, and corrective/preventive action tracking.
+
+**Typical input shape:** Problem context — issue ID, customer, open/due dates, owner, cross-functional team members, problem description, interim containment actions, root causes, and permanent corrective actions.
+
+**Expected output:** `<issue-id>-8d-report.xlsx` — 11 tabs with formulas that auto-sum action status and due-date tracking.
+
+**Sample I/O:** Input a warranty claim summary for issue `WC-2026-014` → Output `WC-2026-014-8d-report.xlsx`.
+
+**Run:** Trigger by phrasing, e.g. "Build an 8D for warranty claim WC-2026-014".

examples/autosar-swc-builder/README.md

@@ -0,0 +1,11 @@
+# autosar-swc-builder — Example
+
+**What this skill produces:** A 13-tab audit-ready xlsx AUTOSAR Classic Platform SWC (Software Component) specification workbook per AUTOSAR R22-11 — SWC type, port interfaces (sender-receiver, client-server, mode-switch, NV-data, parameter, trigger), internal behavior, runnables, RTE events, exclusive areas, and data types.
+
+**Typical input shape:** A JSON file with SWC name, category (Application / Sensor-Actuator / Service / Complex Driver), ports, internal behavior, runnables, events, exclusive areas, and data type definitions.
+
+**Expected output:** `<swc-name>-swc-spec.xlsx` — 13 tabs from Title and Document Control through Port Inventory, interface tabs, Runnable Catalog, Event Catalog, and References.
+
+**Sample I/O:** Input `door-control-swc.json` (category: Application) → Output `door-control-swc-spec.xlsx` with Port Inventory and Runnable Catalog tabs populated.
+
+**Run:** `/autosar-swc-builder <SWC name> <category>`

examples/dbc-builder/README.md

@@ -0,0 +1,11 @@
+# dbc-builder — Example
+
+**What this skill produces:** An 11-tab audit-ready xlsx DBC (CAN database) specification — ECU inventory, message catalog, signal catalog with bit-level encoding, signal-group/multiplexing, value tables, network topology, and validation rules per ISO 11898 and CAN 2.0A/2.0B.
+
+**Typical input shape:** A JSON definition with project context, ECU list, messages (identifier, DLC, cycle time, sender, frame type), signals (bit start/length, byte order, scale/offset, min/max, unit, receivers), value tables, and multiplexing structure.
+
+**Expected output:** `<network>-dbc-spec.xlsx` — 11 tabs from Title Page through References; the generator also prints a JSON summary with message, signal, and ECU counts.
+
+**Sample I/O:** Input `examples/sample_input_can.json` → Output `powertrain-can-dbc.xlsx`.
+
+**Run:** `python scripts/generate_dbc.py <input.json> <output.xlsx>`