This commit is contained in:
team 1
2026-05-01 11:08:02 +02:00
parent 0c7fca9b46
commit b466f85e2f
4 changed files with 283 additions and 3 deletions

View File

@@ -471,6 +471,10 @@ Verifizierte relevante Commands im aktuellen Stand:
- `mto:agent:tags:job:run`
- `mto:agent:tag:health`
- `mto:agent:system:rebuild`
- `mto:agent:config:validate`
- `mto:agent:config:audit-source`
- `mto:agent:config:dump-effective`
- `mto:agent:regression:test`
- `mto:agent:test:shop-search`
- `mto:agent:test-vector`
- `mto:agent:user:create`
@@ -481,4 +485,29 @@ Verifizierte relevante Commands im aktuellen Stand:
```bash
bin/console mto:agent:vector:control --status
bin/console mto:agent:vector:control --install --start --reload
bin/console mto:agent:vector:control --install --start --reload
```
---
## Developer Policies / Governance
The YAML-only migration is treated as completed after Patch 11.0a, as long as these checks stay green:
```bash
php bin/console mto:agent:config:validate
php bin/console mto:agent:config:audit-source --details
php bin/console mto:agent:regression:test
```
From now on, developers must follow `DEVELOPER_POLICIES.md`.
Core rules:
- YAML under `config/retriex/` is the source of truth for configurable behavior.
- No new PHP-only semantic defaults, token lists, prompt texts, matching rules or business fallbacks.
- New configurable behavior must be added through YAML and wired explicitly.
- Regression-sensitive flows from the 1.4.2/1.5.0 baseline must remain protected.
- Strict YAML validation is deferred and must remain disabled by default when introduced later.