/**
 * Section runtime engine outputs (M7 — Variant C, layered core).
 *
 * Outputs are the closed discriminated union of effects the transition
 * function returns. The adapter (PR 2) takes the output array, walks
 * it in order, and dispatches each one to the right bridge (DOM
 * events, framework-error bus, subscriber fan-out).
 *
 * Outputs carry only plain data so the transition table can be tested
 * exhaustively without any DOM or coordinator wiring.
 *
 * Adjustment A2 from the M7 implementation plan: `loading-complete`
 * is an output, **not** an FSM phase. The transition emits it from
 * the `interactive` phase when the readiness signals indicate every
 * item has finished loading. This mirrors today's
 * `pie-loading-complete` DOM event semantics.
 *
 * Readiness alias output kinds (`readiness-change`,
 * `interaction-ready`, `ready`) were removed in the broad
 * architecture review compat sweep along with their DOM-event bridge
 * event bridge. Stage and readiness changes now flow
 * through `stage-change` (with `EngineReadinessDetail` available via
 * `SectionEngineCore.getState()` / kernel `selectReadiness()`); the
 * "all items loaded" signal flows through `loading-complete` only.
 */
export {};
//# sourceMappingURL=engine-output.js.map