chore: add YAML frontmatter to subagent definitions

Add name/description frontmatter to all 10 .claude/agents/*.md files so
they are discoverable and routable as Claude Code subagents.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.claude/agents/biological-process-engineer.md

@@ -1,3 +1,8 @@
+---
+name: biological-process-engineer
+description: Use for biological wastewater modeling on reactor, settler, and monster nodes — ASM1 to ASM3 kinetics, nitrification/denitrification, sludge settling, plug-flow hydraulics, oxygen demand, temperature compensation, and HRT/SRT retention-time calculations.
+---
+
 # Biological Process Engineer — Reactor, Settler & Biological Treatment
 
 ## Identity

.claude/agents/commissioning-compliance.md

@@ -1,3 +1,8 @@
+---
+name: commissioning-compliance
+description: Use for commissioning and compliance — FAT/SAT planning, acceptance-criteria definition, audit trails and control-action traceability, regulatory and effluent reporting, simulation-to-field validation gaps, and Waterschap Brabantse Delta compliance context.
+---
+
 # Commissioning & Compliance Agent — Validation, Regulatory & Audit
 
 ## Identity

.claude/agents/evolv-orchestrator.md

@@ -1,3 +1,8 @@
+---
+name: evolv-orchestrator
+description: Use this agent to decompose complex, multi-domain or cross-node EVOLV tasks, route work to specialist agents, and run decision-gate interviews. Invoke whenever the user says "team", when task ownership is unclear, or for cross-cutting changes affecting topic contracts, output schemas, or parent-child relationships.
+---
+
 # EVOLV Orchestrator — Multi-Domain Task Router
 
 ## Identity

.claude/agents/general-functions-library.md

@@ -1,3 +1,8 @@
+---
+name: general-functions-library
+description: Use when modifying anything in nodes/generalFunctions/ (logger, configManager, outputUtils, PIDController, MeasurementContainer, predict, interpolation, coolprop, convert, MenuManager, childRegistrationUtils, and similar) — assess platform-wide cross-node impact and export backward-compatibility before changing shared exports.
+---
+
 # General Functions Library Agent — Shared Library & Cross-Node Contracts
 
 ## Identity

.claude/agents/instrumentation-measurement.md

@@ -1,3 +1,8 @@
+---
+name: instrumentation-measurement
+description: Use for the measurement node and sensor behavior — signal conditioning, scaling and smoothing, outlier filtering, data-quality flags, NRMSE drift detection, calibration management, MeasurementContainer usage, unit conversions, and warmup/cooldown modeling.
+---
+
 # Instrumentation & Measurement Agent — Sensors, Data Quality & Signal Conditioning
 
 ## Identity

.claude/agents/mechanical-process-engineer.md

@@ -1,3 +1,8 @@
+---
+name: mechanical-process-engineer
+description: Use for rotating equipment and hydraulics work on rotatingMachine, pumpingStation, machineGroupControl, valve, valveGroupControl, and diffuser nodes — pump curves, power and efficiency prediction, pressure-flow models, PID tuning, BEP tracking, and affinity-law and specific-energy validation.
+---
+
 # Mechanical & Process Engineer — Rotating Equipment & Hydraulics
 
 ## Identity

.claude/agents/node-red-runtime.md

@@ -1,3 +1,8 @@
+---
+name: node-red-runtime
+description: Use for Node-RED runtime and editor work — nodeClass.js/specificClass.js structure, RED.nodes.registerType registration, config management, tick loops, admin endpoints, HTML editor forms, menu.js/configData.js endpoints, and dynamic editor behavior.
+---
+
 # Node-RED Runtime & Editor Agent
 
 ## Identity

.claude/agents/ot-security-integration.md

@@ -1,3 +1,8 @@
+---
+name: ot-security-integration
+description: Use for OT/IT security and edge integration — OPC UA/Modbus/fieldbus integration, admin-endpoint security review, control-topic input validation, control-message safety, threat modeling, edge-to-cloud security, PLC reconnect behavior, and injection-risk review of dynamic config.
+---
+
 # OT/IT Security & Edge Integration Agent
 
 ## Identity

.claude/agents/quality-test-engineer.md

@@ -1,3 +1,8 @@
+---
+name: quality-test-engineer
+description: Use after code changes to review quality and tests — regression checks, test-coverage gap analysis across the basic/integration/edge tiers, DRY/complexity/naming review, function-anchor compliance, and technical-debt prioritization.
+---
+
 # Quality & Test Engineer — Code Quality, Testing & Technical Debt
 
 ## Identity

.claude/agents/telemetry-database.md

@@ -1,3 +1,8 @@
+---
+name: telemetry-database
+description: Use for telemetry and database work — the dashboardAPI node, Port 1 InfluxDB payload design, tag-vs-field schema decisions, Grafana and FlowFuse chart compatibility, KPI definitions, aggregation windows, and retention policy design.
+---
+
 # Telemetry & Database Agent — InfluxDB, Dashboards & Analytics
 
 ## Identity