Compare commits

...

5 Commits

Author SHA1 Message Date
lzm
1854431ba3 merge: integrate origin/development into dev-lzm
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 15:49:14 +02:00
lzm
285faf873b chore(submodules): fast-forward 4 nodes to development
Bring dev-lzm in sync with origin/development for generalFunctions,
machineGroupControl, pumpingStation and rotatingMachine (clean
fast-forwards, no divergence).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 15:10:49 +02:00
lzm
96e7c56bbe 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>
2026-05-29 15:02:56 +02:00
Rene De Ren
8a5cc552ab chore(submodule): bump pumpingStation ef07f2a -> 2fb083d
Promotes the pumpingStation development tip into the superproject. On top of the
ef07f2a already pinned by the 5-node bump, this adds the contract/docs work:
- docs(contract): close output-contract gaps — mode/manualDemand, Port-2 topic,
  output manifest (4889fda)
- docs(contract): worked msg examples for every input topic + output port (2fb083d)
- fix(ps): persist stopLevel/holdLevel as numbers; flow output in m³/h; etc.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-05-29 13:59:28 +02:00
lzm
c02cb68791 chore: sync submodules + add npm hardening config
- bump 5 submodules: generalFunctions / MGC / pumpingStation /
  rotatingMachine to development tip (UnitPolicy.convert refactor +
  test rewires); measurement to local d7f661 (editor modularization)
- add .npmrc with ignore-scripts=true + min-release-age=7
- resync package-lock.json (was missing @flowfuse dashboard subtree)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-28 09:15:30 +02:00
18 changed files with 1943 additions and 40 deletions

View File

@@ -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 # Biological Process Engineer — Reactor, Settler & Biological Treatment
## Identity ## Identity

View File

@@ -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 # Commissioning & Compliance Agent — Validation, Regulatory & Audit
## Identity ## Identity

View File

@@ -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 # EVOLV Orchestrator — Multi-Domain Task Router
## Identity ## Identity

View File

@@ -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 # General Functions Library Agent — Shared Library & Cross-Node Contracts
## Identity ## Identity

View File

@@ -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 # Instrumentation & Measurement Agent — Sensors, Data Quality & Signal Conditioning
## Identity ## Identity

View File

@@ -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 # Mechanical & Process Engineer — Rotating Equipment & Hydraulics
## Identity ## Identity

View File

@@ -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 # Node-RED Runtime & Editor Agent
## Identity ## Identity

View File

@@ -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 # OT/IT Security & Edge Integration Agent
## Identity ## Identity

View File

@@ -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 # Quality & Test Engineer — Code Quality, Testing & Technical Debt
## Identity ## Identity

View File

@@ -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 # Telemetry & Database Agent — InfluxDB, Dashboards & Analytics
## Identity ## Identity

2
.npmrc Normal file
View File

@@ -0,0 +1,2 @@
ignore-scripts=true
min-release-age=7

1919
package-lock.json generated

File diff suppressed because it is too large Load Diff