feat: add CONFIG_REGRESSION sub-agent concern to upstream merge review

Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
This commit is contained in:
markijbema
2026-06-25 07:11:22 +00:00
parent e000cbe2c3
commit db6425515b
+12
View File
@@ -62,6 +62,18 @@ Pay special attention to:
When in doubt, add a finding. A human will verify it. Compiling code is not proof the chain is intact.
## CONFIG_REGRESSION.md
Check whether this PR introduces or re-introduces fallback logic for non-`.kilo` config files (e.g. `opencode.json`, `.kilocode` config paths), or accidentally breaks code that now correctly expects only `.kilo`-based configuration.
Kilo removed fallback support for non-`.kilo` config directories. Look for:
- Any new or restored code that reads from `opencode`, `.kilocode`, or other non-`.kilo` config paths.
- Upstream additions to config discovery, loading, or path resolution that add fallback candidates we stripped.
- Changes that break `.kilo`-only config lookup by removing or reordering it in a multi-path search.
When in doubt, add a finding. A human should verify config path changes manually.
## TESTS.md
Check whether this PR removed any Kilo-specific tests.