Migrate to new Gitea instance (gitea.wbd-rd.nl)

- Update all submodule URLs from gitea.centraal.wbd-rd.nl to gitea.wbd-rd.nl
- Add settler as proper submodule in .gitmodules
- Add agent skills, function anchors, decisions, and improvements
- Add Docker configuration and scripts
- Add manuals and third_party docs
- Update .gitignore with secrets and build artifacts
- Remove stale .tgz build artifact

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.agents/skills/evolv-mechanical-rotating-equipment/SKILL.md

@@ -8,6 +8,14 @@ description: Provide rotating equipment engineering guidance for EVOLV machine a
 ## Mission
 Keep rotating equipment behavior physically plausible, safe, and diagnosable in EVOLV JavaScript domain classes.
 
+## Harness Execution Contract
+- Start from equipment assumptions and current curve/sensor sources in repo.
+- Define invariants before edits:
+  - physical plausibility constraints remain enforced
+  - degraded/fail-safe behavior remains explicit
+  - outputs remain diagnosable for operations teams
+- Validate with boundary-condition evidence and deterministic test outcomes.
+
 ## Scope
 - `nodes/rotatingMachine/`
 - `nodes/machineGroupControl/`
@@ -43,3 +51,8 @@ Return:
 - implemented constraints and rationale
 - test coverage for boundary cases
 - remaining mechanical uncertainties requiring field data
+
+Decision interview triggers:
+- safety envelope changes (speed, power, flow/head boundaries)
+- curve-source replacement with uncertain field alignment
+- degraded-mode changes that affect availability vs protection tradeoffs

.agents/skills/evolv-mechanical-rotating-equipment/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "EVOLV Rotating Equipment Engineer"
   short_description: "Model rotating assets with physical realism"
-  default_prompt: "Review and implement rotating-machine logic with unit consistency, envelope constraints, failure-safe behavior, and regression tests."
+  default_prompt: "Review EVOLV rotating-machine logic from current curves/sensors, enforce physical and fail-safe invariants, verify with boundary evidence, and trigger decision-gate interviews before changing safety envelopes."