Plan native ConfigKit discovery conventions

This commit is contained in:
2026-11-20 03:56:11 +00:00
parent d903a1aa4e
commit 9e5cc60d09
2 changed files with 34 additions and 14 deletions

View File

@@ -172,6 +172,13 @@ not an arbitrary file path. Map selections through the application's ConfigKit
loader rather than retaining the old flag parser as a compatibility layer.
Preserve useful application source and server controls through appropriate selectors.
For implicit application configuration discovery, adopt ConfigKit's built-in
directory presets and their native filename conventions through `SearchConfig`.
Replace the legacy two-file search. ConfigKit deliberately leaves preset
selection and ordering to the application; settle that choice before completing
the loader migration. Selection, exhaustion, and selected-file errors remain
native ConfigKit behavior.
Enable temporary configuration overrides where the loader supports them,
passing native override records into loading. Named selectors and `--set` may
be combined for nonconflicting paths. ConfigKit owns rejection and diagnostics
@@ -328,8 +335,9 @@ documentation and examples describe the shipped interface. In particular:
report availability, quiet behavior, and changed exit statuses.
The [implementation plan](implementation.md) owns task sequencing, concrete
adapter mappings, verification steps, and sprint status. There are no unresolved
product decisions or selected-format accessor release prerequisite.
adapter mappings, verification steps, and sprint status. Discovery preset
selection and ordering remain to be settled; the selected-format accessor is
not a release prerequisite.
The [release policy](../policy/release.md#versioning-and-compatibility) governs
the eventual breaking release version. This migration does not itself select