pj 66fd5bce5d fix(runner): a secure field's value does not reach state.lastAction either ...

folio extracts lastAction, and extractor values are persisted as
extractor_changes, so the password still reached the run directory
through the spec after the three render sites were closed.

The wrap sits in the runner rather than in lastActionFields because the
hosts hold the next step's tree, not the one the action was chosen
against: a field that stops being secure between the two would publish
what the trace withheld. Live and replay now agree byte for byte.

2026-08-18 17:32:28 +05:30

..

case-study.md

correctness fixes from the first real folio dispatch, and spec authoring skills (#82)

2026-08-16 13:23:53 +05:30

cli.md

docs(cli): document --label-source

2026-08-18 16:11:45 +05:30

getting-started.md

correctness fixes from the first real folio dispatch, and spec authoring skills (#82)

2026-08-16 13:23:53 +05:30

index.md

docs update with case study (#63)

2026-06-09 20:13:54 +05:30

introduction.md

ci: dispatch workflows for folio and the replay ui (#73)

2026-08-15 13:01:27 +05:30

replay.md

docs update with case study (#63)

2026-06-09 20:13:54 +05:30

runs.md

fix(runner): a secure field's value does not reach state.lastAction either

2026-08-18 17:32:28 +05:30

spec-language.md

fix(runner): a secure field's value does not reach state.lastAction either

2026-08-18 17:32:28 +05:30