Crate day_script 

day-script — the embedded dayscript engine (DESIGN.md §14). Bind-only-when-invited: the server starts ONLY when DAYSCRIPT_PORT + DAYSCRIPT_TOKEN are present in the environment (never otherwise), listens on 127.0.0.1, and accepts only the step catalog. Steps execute as synthesized Day events on the main thread between flushes — deterministic and toolkit-uniform. Locator steps get an implicit bounded wait (default 5s).

Re-exports

pub use record::play;

Modules

record

The dayscript recorder and in-process playback (§14.6): capture the events an app receives back into a replayable dayscript, and replay one against the live UI. See record::start/record::play. The dayscript recorder (DESIGN.md §14.6): the inverse of playback. Where the engine turns a script into synthesized Day events, the recorder turns the events an app actually receives back into a script. It rides one seam — [day_core::set_event_observer], the single point EVERY backend funnels its native events through ([day_core::enqueue_events]) — so it needs no per-toolkit code, and it emits an ordinary dayscript that replays cross-toolkit through the same executor as any hand-written one.

Structs

Reply

Request

Enums

Step

Constants

DEFAULT_MAIN_TIMEOUT_SECS

How long ONE dispatch may wait for the main thread before the step is failed.

DEFAULT_TIMEOUT_SECS

Functions

b64decode

b64encode

init

Start the engine iff invited via env (call before launch_with; inert otherwise).