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-frontend-node-red/SKILL.md

@@ -8,6 +8,14 @@ description: Design and implement Node-RED node editor UI and runtime-facing con
 ## Mission
 Implement robust Node-RED editor experiences that keep UI defaults, runtime config parsing, and behavior in lockstep.
 
+## Harness Execution Contract
+- Start from impacted files and active runtime/editor contracts.
+- Define invariants before editing:
+  - `.html` defaults and runtime parsing parity
+  - endpoint path stability (`/<nodeName>/menu.js`, `/<nodeName>/configData.js`)
+  - released topic/output compatibility unless migration is declared
+- Provide evidence for changed behavior (tests or smoke checks).
+
 ## Repo-Specific Rules
 - Use CommonJS patterns in runtime files.
 - Keep node names aligned across `RED.nodes.registerType('<nodeName>', ...)`, runtime registration in `<nodeName>.js`, and package/node mapping.
@@ -52,3 +60,8 @@ Return:
 - changed files
 - tests added and what they prove
 - migration notes if backward compatibility changed
+
+Decision interview triggers:
+- form or default changes that alter existing deployed behavior
+- endpoint contract/path changes
+- UI/runtime migration that could break saved Node-RED flows