Settle native discovery and single-file PromptKit configuration
This commit is contained in:
@@ -3,7 +3,7 @@
|
||||
## Status And Intent
|
||||
|
||||
Initial roadmap, prepared 2026-11-19. The product direction is agreed;
|
||||
implementation has not begun. This document owns the target and product intent,
|
||||
implementation is underway. This document owns the target and product intent,
|
||||
incorporating the decisions in the [migration notepad](commandkit-notepad.md).
|
||||
The notepad remains the discussion
|
||||
record. The [Narratio proposal](narratio-feature-request.md) supplies consumer
|
||||
@@ -173,20 +173,18 @@ loader rather than retaining the old flag parser as a compatibility layer.
|
||||
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.
|
||||
`--against-set` where supported. Remove `--promptkit-source` and `--schema-dir`
|
||||
from all commands. Native resource IDs select loaded prompts and profiles;
|
||||
installation configuration supplies their definitions and schema source.
|
||||
|
||||
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.
|
||||
|
||||
The recommended preset order is `WorkingDirectory`, `UserConfigDirectory`,
|
||||
`HomeDirectory`, then `UnixSystemDirectories`, using each preset's native
|
||||
Replace the legacy two-file search. The selected 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.
|
||||
ConfigKit selects one main file, with native optional-search exhaustion and
|
||||
selected-file error behavior; this is not a merge of all discovered files.
|
||||
|
||||
Enable temporary configuration overrides where the loader supports them,
|
||||
passing native override records into loading. ConfigKit owns rejection and
|
||||
@@ -196,13 +194,26 @@ 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 through native flags alone.
|
||||
|
||||
Keep the established collection-discovery model: ConfigKit imports discover
|
||||
`collection.yml` and `collection.yaml` entry points; each independently
|
||||
Use an application `promptkit` settings section containing `configuration`, the
|
||||
path to one external framework entry file, and `schema_dir`, the output-schema
|
||||
root. Replace the general `promptkit_sources` file/directory list and top-level
|
||||
`schema_dir`. Pass the selected file to PromptKit as its native main input with
|
||||
ConfigKit imports enabled. Keep the bundled upstream defaults.
|
||||
|
||||
Keep the established collection-discovery model: that entry file's ConfigKit
|
||||
glob imports discover `collection.yml` and `collection.yaml` entry points; each independently
|
||||
maintained collection declares its namespace and imports its own definitions
|
||||
through relative references. Retain the
|
||||
[discovery example](../../examples/config.discovery.yml) and representative
|
||||
multi-definition collection documentation. No Git update manager or custom
|
||||
collection traversal is part of this migration.
|
||||
multi-definition collection documentation, updating the application example to
|
||||
the new settings. No repeated source flag, separate directory-source mechanism,
|
||||
Git update manager, or custom collection traversal is part of this migration.
|
||||
|
||||
Embedding actual PromptKit definitions under the application's `promptkit` key
|
||||
is deferred pending suitable upstream support. The current section contains
|
||||
application settings for acquiring the separate framework document. Do not
|
||||
extract, reserialize, or reload a resolved application subtree as a substitute
|
||||
for a native upstream handoff. This deferred capability does not block adoption.
|
||||
|
||||
Use native prompt, profile, and backend namespace selectors independently on
|
||||
applicable commands. Short caller-supplied IDs use their selected namespace;
|
||||
@@ -342,9 +353,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. 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.
|
||||
adapter mappings, verification steps, and sprint status. The discovery and
|
||||
source/schema decisions are settled. Neither the selected-format accessor nor
|
||||
embedded framework configuration is a migration prerequisite.
|
||||
|
||||
The [release policy](../policy/release.md#versioning-and-compatibility) governs
|
||||
the eventual breaking release version. This migration does not itself select
|
||||
|
||||
Reference in New Issue
Block a user