Union of every input's AffectedTables, de-duplicated.
One description per input, in input order.
Number of migrations in this batch.
Expected total steps for the run — the denominator of a determinate progress bar.
OptionalErrorMessage?: stringPresent when the run failed — the first failing step's message.
OptionalErrorStep?: stringPresent when the run failed — the name of the step that failed.
A lifecycle notification from the RSU pipeline, delivered to an out-of-band RSUPipelineObserver.
Why an observer instead of emitting progress directly: an RSU run's steps (CodeGen, compile, restart) take minutes, and until now the only live signal was
GetStatus()polling — a caller had no durable record of what a run did, and a restart mid-run left nothing to read. The durable artifact stream that solves that lives in@memberjunction/integration-progress-artifacts, which is a LAYER ABOVE this package. So SchemaEngine publishes plain lifecycle events and lets the server wire them to the emitter, keeping the dependency direction intact.