Clarify precedence for discovered collections
This commit is contained in:
@@ -82,9 +82,13 @@ Convert framework source controls from `configkit:` to `config:` and add
|
||||
header, if present, is `version: 2`. Use sibling inheritance such as
|
||||
`extends: {id: base}`.
|
||||
|
||||
Composition now replaces a whole record when a later source selects the same
|
||||
ID; supply the complete intended replacement, or create a distinct inherited
|
||||
record. Null profile endpoint, credential, or provider-map settings can fall
|
||||
Across ordered `promptkit_sources` entries, a later framework underlay replaces
|
||||
the whole record for the same ID. Supply the complete intended replacement,
|
||||
or create a distinct inherited record. Checkouts imported by the same
|
||||
[discovery file](../config.md#collection-checkout-discovery) are peers:
|
||||
conflicting definitions of the same ID fail instead of overriding one another.
|
||||
|
||||
Null profile endpoint, credential, or provider-map settings can fall
|
||||
back to the selected backend; review behavior rather than assuming null clears
|
||||
backend values. Keep JSON schemas self-contained instead of depending on remote
|
||||
schema references. Application selectors remain separate from these framework
|
||||
|
||||
Reference in New Issue
Block a user