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>
This commit is contained in:
znetsixe
2026-03-04 21:07:04 +01:00
parent fbd9e6ec11
commit 6a6c04d34b
169 changed files with 21332 additions and 1512 deletions

View File

@@ -8,6 +8,12 @@ description: Drive code quality, regression prevention, and technical debt manag
## Mission
Raise delivery reliability by detecting defects early and systematically reducing technical debt in EVOLV nodes.
## Harness Execution Contract
- Anchor findings to concrete file/line evidence.
- Separate correctness risk from style preferences.
- Require regression-proof evidence for fixes (tests that fail-before/pass-after when feasible).
- Feed recurring failure patterns back into the relevant skill guidance.
## Scope
- Node implementation quality in `nodes/<nodeName>/src/`
- Editor/runtime contract consistency in `.html` + runtime wrappers
@@ -50,3 +56,8 @@ Return:
- test gaps and specific cases to add
- debt backlog (now/next/later)
- recommended refactors with expected payoff
Decision interview triggers:
- tradeoff between delivery speed and known high-severity risk
- acceptance of temporary risk with deferred remediation
- testing scope reductions that materially raise regression risk

View File

@@ -1,4 +1,4 @@
interface:
display_name: "EVOLV Quality + Debt Engineer"
short_description: "Drive code quality and technical debt reduction"
default_prompt: "Review EVOLV code for defects, regression risk, test gaps, and maintainability issues; provide prioritized remediation."
default_prompt: "Review EVOLV code with evidence-anchored findings, prioritize correctness and regression risk, require verification for fixes, and frame explicit decision-gate tradeoffs when risk is accepted or testing is reduced."