Use derived artifact catalogs throughout planning and execution

This commit is contained in:
2026-11-20 04:42:23 +00:00
parent 6900cad104
commit 065a615e5f
36 changed files with 377 additions and 205 deletions

View File

@@ -233,6 +233,16 @@ selection reaches family members and players; collisions remain errors.
## Stage 5: Wire derived products through planning and execution
**Completed.** Analysis selection, planning, fingerprinting, reconciliation,
previous-session requirements, runtime registration, and artifact inspection use
the separate concrete catalog. Run options retain normalized family selection
and origins through the stage environment; Scriptorium requests borrow genuine
shared settings. An assembled bounded run verifies explicit-roster players,
family dependencies, adapter variables, durable identities, and unchanged native
configuration. Configuration, stage, and artifact suites, focused runner and
bounded-composition checks, and builds pass with Go 1.27.4. CLI tests awaiting
the later native command/inspection conversion remain transitional.
Read: `internal/app/analyze_artifacts.go`, `runner_runtime.go`,
`bounded_prerequisites.go`, `internal/stage/stage.go`, `analyze*.go`,
`trim.go`, and the artifact catalog/resolution owners.