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-database-influx-architecture/SKILL.md

@@ -8,6 +8,14 @@ description: Design and review EVOLV data modeling and storage architecture for
 ## Mission
 Shape telemetry data so it is queryable, performant, and maintainable for operations dashboards and analytics.
 
+## Harness Execution Contract
+- Start from current measurement/tag/field usage and dashboard queries.
+- Define invariants before edits:
+  - query compatibility for existing Grafana/consumer flows
+  - bounded tag cardinality
+  - explicit units and timestamp policy
+- Provide validation evidence using representative payloads and queries.
+
 ## Scope
 - Output payload structure from EVOLV nodes
 - InfluxDB write model: measurement, tags, fields, timestamp policy
@@ -43,3 +51,8 @@ Return:
 - rationale tied to dashboard and analytics use
 - changed files/tests
 - migration and retention plan
+
+Decision interview triggers:
+- schema changes that break existing queries/panels
+- retention/downsampling policies with data-loss tradeoffs
+- backfill rules that alter historical comparability

.agents/skills/evolv-database-influx-architecture/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "EVOLV Database + Influx Architect"
   short_description: "Design telemetry schema for Influx and Grafana"
-  default_prompt: "Define EVOLV telemetry modeling, Influx measurement/tag/field choices, retention strategy, and Grafana-compatible query shape."
+  default_prompt: "Define EVOLV telemetry schema from current payload/query usage, enforce cardinality and compatibility invariants, validate with representative queries, and escalate decision-gate tradeoffs for retention/backfill or breaking schema changes."