Connect processing preflight and output reporting
This commit is contained in:
@@ -344,6 +344,12 @@ retain already published output and primary failure details.
|
||||
|
||||
## Stage 8: Wire processing, common preflight, and reporting modes
|
||||
|
||||
**Completed.** Processing now acquires typed inputs, prepares outputs, and
|
||||
finalizes through CommandKit. The `executePipeline` handoff is intentionally
|
||||
implemented with the ordered runner work below; until then the application and
|
||||
unconverted tests do not build. The handler was checked with a controlled runner
|
||||
boundary; later readiness checks and assembled validation remain assigned below.
|
||||
|
||||
Own `internal/cli/process.go` and the new `internal/framework/preflight`.
|
||||
Use the [named preflight boundary](glossary-stages.md#empty-collections-and-audita-preflight--resolved)
|
||||
and the [CommandKit reporting decisions](commandkit.md#debug-reporting-and-artifact-capture--resolved).
|
||||
|
||||
Reference in New Issue
Block a user