Adopt ConfigKit native override conflict behavior

This commit is contained in:
2026-11-20 03:47:30 +00:00
parent 26ac62fbb7
commit d903a1aa4e
2 changed files with 37 additions and 16 deletions

View File

@@ -173,10 +173,14 @@ loader rather than retaining the old flag parser as a compatibility layer.
Preserve useful application source and server controls through appropriate selectors.
Enable temporary configuration overrides where the loader supports them,
passing native override records into loading. The reviewed PromptKit scope
does not support these overrides; do not emulate them locally. Configuration
comparison must support independent selections for both sides in both scopes,
including corresponding application selectors where needed.
passing native override records into loading. Named selectors and `--set` may
be combined for nonconflicting paths. ConfigKit owns rejection and diagnostics
for duplicate or ancestor/descendant-overlapping override records; `--set` does
not supersede named selectors. Do not filter or merge conflicts locally.
The reviewed PromptKit scope does not support these overrides; do not emulate
them locally. Configuration comparison must support independent selections for
both sides in both scopes, including corresponding application selectors where
needed.
Keep the established collection-discovery model: ConfigKit imports discover
`collection.yml` and `collection.yaml` entry points; each independently