Align collection proposal with implemented ConfigKit capabilities

This commit is contained in:
2026-10-16 11:51:18 +00:00
parent c7490b783b
commit b5866dd749
2 changed files with 270 additions and 170 deletions

View File

@@ -492,10 +492,13 @@ uses an opt-in upstream extension for identity-based record composition and
inheritance. [Proposal 3: mounted fragments](configuration-collections-mounted-fragments.md)
uses explicit upstream source placement and collection-local mapping keys,
with one installed definition per prompt and an optional flat version field.
All three retain main-owned specification versioning; independent collection
checks remain a separate upstream question. These are proposals for comparison;
this decision remains open. Proposal 3 deliberately revises the version-selection
and listing assumptions elsewhere in this roadmap if that alternative is adopted.
Proposal 3 now targets implemented ConfigKit development-branch capabilities,
including relative imports and shared source-version checks with `IfPresent`. It
uses `release_version` for collection metadata; proposals 1 and 2 preserve their
earlier baselines for comparison. This overall decision remains open. Proposal 3
deliberately revises the version-selection, metadata, and listing assumptions
elsewhere in this roadmap if that alternative is adopted. Its remaining questions
are PromptKit policy/API choices, not pending requests for those ConfigKit features.
**Desired capability:** describe collection namespace and release version in
configuration and expose an API through which downstream applications can list