Derive artifact catalogs from the selected party without changing configuration
This commit is contained in:
@@ -197,6 +197,15 @@ no later operation changes the captured session or campaign result.
|
||||
|
||||
## Stage 4: Derive party products and concrete artifact catalogs
|
||||
|
||||
**Completed.** Exposed the retained typed party result and exact explicit-roster
|
||||
selection. Concrete artifacts, dependency closure, family/member provenance,
|
||||
players, and publication rules are derived separately; completed pipeline and
|
||||
campaign values remain unchanged. Removed expansion state from PipelineConfig.
|
||||
The full configuration package and maintained examples pass with Go 1.27.4,
|
||||
including the dependency tests deferred from Stage 2 and independent-roster
|
||||
regressions. Whole-application compilation awaits the family-origin consumers'
|
||||
catalog wiring in Stage 5; no compatibility dispatcher or snapshot was added.
|
||||
|
||||
Read: `internal/config/party*.go`, `artifact_families.go`, `artifact_catalog.go`,
|
||||
the family declarations in `config.go`, and the roadmap's ownership boundary.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user