Verify record inheritance through pipeline resolution
This commit is contained in:
@@ -186,6 +186,14 @@ step requirement. Validator chains are not automatically identified. Authors
|
||||
may declare identities for other lists when needed. CLI list assignment replaces
|
||||
the complete decoded list.
|
||||
|
||||
Record inheritance does not create template-only steps: every record in the
|
||||
final step list executes and must have artifact lanes. A child that inherits
|
||||
its parent's named lanes also conflicts with the requirement that lane IDs be
|
||||
unique across steps; adding differently named lanes does not remove inherited
|
||||
ones. Use pipeline-level inheritance with step upsert for pipeline variants.
|
||||
Native identified-record inheritance is also available in compatible collections,
|
||||
such as an author-identified validator list, subject to ordinary domain validation.
|
||||
|
||||
For example, an overlay can opt into replacing a pipeline's steps:
|
||||
|
||||
~~~yaml
|
||||
|
||||
@@ -360,7 +360,12 @@ was identified. One additional test/documentation integration gap remains.
|
||||
|
||||
### Finding CK-3 — Verify Identified-Record Inheritance At The Runtime Boundary
|
||||
|
||||
Priority: P3. Category: integration coverage and support-scope clarity. Status: open.
|
||||
Priority: P3. Category: integration coverage and support-scope clarity. Status: complete.
|
||||
|
||||
Completed 2026-11-18: reframed the reference-only step fixture as a negative
|
||||
resolution case and added compatible validator-record inheritance that reaches
|
||||
Config.Resolve and verifies inherited options. Documented step/lane constraints
|
||||
without relaxing them. Core configuration and CLI/example suites pass.
|
||||
Affected stages: 4, 9, and 11.
|
||||
|
||||
`TestIdentifiedStepRecordInheritance` in
|
||||
|
||||
Reference in New Issue
Block a user