Validate hidden base artifact ownership conflicts
This commit is contained in:
@@ -87,7 +87,13 @@ directory resolves from the pipeline root. Preserve digest relocation invariance
|
||||
|
||||
## 3. Enforce unique base definitions even when a profile removes them
|
||||
|
||||
Status: Open — P2
|
||||
Status: Resolved — P2
|
||||
|
||||
Resolution: Named-profile loading now validates the independently resolved base
|
||||
through the same ConfigKit definition and public metadata history before accepting
|
||||
the selected result. Duplicate ordinary or family definitions therefore fail even
|
||||
when an overlay nulls their container or all of Scriptorium. A single base owner
|
||||
with a legitimate profile override remains supported.
|
||||
|
||||
**Evidence:** `rejectDuplicateBaseDefinitions` at
|
||||
`internal/config/pipeline_configkit.go:354` enumerates only artifact/family keys
|
||||
|
||||
Reference in New Issue
Block a user