Module dev_ui 

Local dev-server surface: trigger a run, stream it over the existing firehose, mock a named activity per-run, and replay a failed run — all over the real engine, store, and event stream. Local dev-server surface with production parity.

The dev surface gives an author a faithful local UI over the REAL engine, store, and event stream — never a mock-only engine and never an execution path whose semantics diverge from production (CN4). It is dark by default, gated on [dev].enabled, exactly like the deploy and authoring surfaces.

The surface is four operations, each built on existing infrastructure:

• trigger a run — the same start path /workflows/start drives;
• stream that run’s events — the existing /events/stream WebSocket firehose, reused (no second stream is built); the trigger response carries the exact per-workflow subscription frame;
• mock a named activity per-run — a shared ActivityMockRegistry the engine’s dispatcher already consults via DevMockingDispatcher, so the engine is untouched;
• replay a failed run — re-drive it through the real engine and store.

Re-exports

pub use handlers::MockOutcome;

pub use handlers::RegisterMockRequest;

pub use handlers::RegisterMockResponse;

pub use handlers::ReplayRunRequest;

pub use handlers::ReplayRunResponse;

pub use handlers::StreamSubscription;

pub use handlers::TriggerRunRequest;

pub use handlers::TriggerRunResponse;

pub use handlers::register_mock;

pub use handlers::replay_run;

pub use handlers::trigger_run;

pub use mock::ActivityMockRegistry;

pub use mock::DevMockingDispatcher;

pub use mock::MockedActivity;

Modules

handlers

Transport-agnostic dev-server handlers. Transport-agnostic dev-server handlers over the REAL engine, store, and event stream.

mock

Opt-in per-run activity mocking layered over the production dispatcher. Opt-in per-run activity mocking, layered over the production dispatcher.