Compose glossary collections through configuration
This commit is contained in:
@@ -388,6 +388,11 @@ roadmap's selected flag combinations; avoid retesting the full upstream parser.
|
||||
|
||||
## Stage 9: Compose and validate native glossary definitions
|
||||
|
||||
**Completed.** Typed glossary definitions use native identified collection
|
||||
composition and main-relative optional imports. Application source evidence
|
||||
includes consumed glossary files; selection resolution and runtime consumers
|
||||
remain assigned below. Focused configuration tests passed.
|
||||
|
||||
Own the glossary definition types and application load inputs. Read
|
||||
[glossary ownership and named collections](glossary-stages.md#glossary-configuration-ownership--resolved)
|
||||
through its default-source and entry-contract sections.
|
||||
|
||||
Reference in New Issue
Block a user