Keep configuration commands native and refine discovery direction

This commit is contained in:
2026-11-20 04:07:40 +00:00
parent 9e5cc60d09
commit f88c679a06
2 changed files with 71 additions and 58 deletions

View File

@@ -114,8 +114,8 @@ references use `--input-file`.
Reuse applicable ckprompt resource, input, and execution bindings for `run`.
Preserve explicit-value presence, including zero and empty values, and native
repeated mapping semantics. Do not carry forward comma splitting or obsolete
aliases merely because the old parser accepted them. Keep application source
selectors, server settings, output destinations, and whole-operation deadlines
aliases merely because the old parser accepted them. Keep application-only
controls, including HTTP settings, reporting, and whole-operation deadlines,
distinct from framework request controls.
Completion initially uses native command, flag, static-value, and path
@@ -170,7 +170,11 @@ sources. Adopt native `--overlay` selection and upstream selection presence
semantics. For ConfigKit v1.2.1 the supplied value selects an overlay by name,
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.
Keep HTTP-related named flags on `serve`. The `config` family exposes only
upstream commands and flags: add no application selectors or custom
`--against-*` flags. Retain native `--against-config`, `--against-overlay`, and
`--against-set` where supported. Retention of `--promptkit-source` and
`--schema-dir` outside `config` remains under review.
For implicit application configuration discovery, adopt ConfigKit's built-in
directory presets and their native filename conventions through `SearchConfig`.
@@ -179,15 +183,18 @@ selection and ordering to the application; settle that choice before completing
the loader migration. Selection, exhaustion, and selected-file errors remain
native ConfigKit behavior.
The recommended preset order is `WorkingDirectory`, `UserConfigDirectory`,
`HomeDirectory`, then `UnixSystemDirectories`, using each preset's native
filename rules. This implements current-directory, user, then system discovery;
the two user presets cover the platform configuration directory and home layout.
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
for duplicate or ancestor/descendant-overlapping override records; `--set` does
not supersede named selectors. Do not filter or merge conflicts locally.
passing native override records into loading. ConfigKit owns rejection and
diagnostics for duplicate or ancestor/descendant-overlapping records. 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.
both sides in both scopes through native flags alone.
Keep the established collection-discovery model: ConfigKit imports discover
`collection.yml` and `collection.yaml` entry points; each independently
@@ -335,9 +342,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. Discovery preset
selection and ordering remain to be settled; the selected-format accessor is
not a release prerequisite.
adapter mappings, verification steps, and sprint status. Confirm the recommended
discovery order and settle the remaining source/schema interface before completing
the affected stages. 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