Clarify optional collection discovery globs

This commit is contained in:
2026-11-18 18:46:12 +00:00
parent ca7c7faf5c
commit 247b67312e

View File

@@ -94,7 +94,10 @@ through the same Scriptorium invocation model.
Use ConfigKit imports in a selected framework source to discover collection
entry files. Establish `collection.yml` and `collection.yaml` as equivalent
Scriptorium conventions for the collection-root entry file, and select both
spellings through the installation's import declarations. Each entry file
spellings through the installation's import declarations. When using a
separate glob for each spelling, leave each glob optional (omit
`required: true`) so either spelling can have zero matches. An installation
using only one spelling still discovers its collections. Each entry file
declares its own namespace under PromptKit's native `collections` mapping and
uses relative imports to assemble its profiles, prompts, and other definition
files. The checkout directory name does not determine the namespace; callers
@@ -237,11 +240,12 @@ serve the application independently of wire compatibility.
and real-engine adapter tests. Exercise native source composition,
qualified selection, source-local resources, captured inspection,
render and execution, and representative failures for obsolete formats
and selectors. Verify both collection entry-file spellings, multiple loaded
collections, relative imports, and discovery of an added collection without
editing the installation's source configuration. Include unrelated YAML
outside the authored import selections to verify that entry-file discovery
does not treat an entire repository as framework configuration.
and selectors. Verify collection discovery with either entry-file spelling
alone and with both spellings across multiple checkouts. Verify relative
imports and discovery of an added collection without editing the
installation's source configuration. Include unrelated YAML outside the
authored import selections to verify that entry-file discovery does not
treat an entire repository as framework configuration.
Update affected inspection tests to cover required adaptations, accurate
optional-value handling, and preserved disclosure boundaries. Reuse existing
coverage and keep new inspection checks focused on migration regressions;