Compose grouped underlays in shared load lifecycle
This commit is contained in:
@@ -363,6 +363,16 @@ diagnostics remain stable. Run the everyday checker and engine race tests.
|
||||
|
||||
## Stage 6: Implement private grouped-underlay orchestration
|
||||
|
||||
**Completed 2026-09-29.** Ordinary and grouped engine loads now use one private
|
||||
request lifecycle. Group-local strict composition and repetition tracking,
|
||||
load-wide source/byte/node/glob accounting, main-owned version checking,
|
||||
underlay layer/index metadata, and precedence-ordered assembly feed one final
|
||||
decode, resolution, validation, and publication. Engine tests cover two tiers,
|
||||
multiple contributions, source/history order, absent main/defaults-only loads,
|
||||
main/import and group conflicts, version protection, shared limits, reusable
|
||||
files across tiers, and replacement of invalid intermediate typed input. The
|
||||
everyday checker and engine race suite passed. No root layered API is exposed yet.
|
||||
|
||||
1. Add private request/input/group structures matching the settled facade design.
|
||||
Adapt ordinary `Load` to the shared core while preserving its options and
|
||||
source-order behavior. Keep its existing validation order where observable.
|
||||
|
||||
Reference in New Issue
Block a user