From db6425515bd155532bc198069512c1f3a90085d0 Mon Sep 17 00:00:00 2001
From: markijbema <624143+markijbema@users.noreply.github.com>
Date: Thu, 25 Jun 2026 07:11:22 +0000
Subject: [PATCH] feat: add CONFIG_REGRESSION sub-agent concern to upstream
 merge review

Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
---
 .kilo/command/review-upstream-merge.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/.kilo/command/review-upstream-merge.md b/.kilo/command/review-upstream-merge.md
index 36237d81c1..b6c62f5742 100644
--- a/.kilo/command/review-upstream-merge.md
+++ b/.kilo/command/review-upstream-merge.md
@@ -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.