Hubert Gancarczyk fdd1774ca4 fix(flows): stop reporting what a script prints, on both sides ...

A `script:` step used to bring its stdout and stderr back with it. The
recorder returned `log`/`logTruncated`, the step report carried
`scriptLog`/`scriptLogTruncated`, and the CLI and the MCP content builder
each rendered them. Both surfaces land in an agent's context, and nothing
in the flow file declares what a script prints, so nothing can decide in
advance whether that text is safe to forward. The channel goes rather than
being gated behind a parameter the agent would set itself.

A script step now answers with its verdict and its `reason` only. Deleting
the capture removes what existed to bound it: the 64 KiB per-step cap, the
256 KiB run-wide budget, the V8 frame collapser, the partial-marker guard
and the streaming half of the secret scrub.

Both pipes are still drained, and stderr is still scanned for V8's
heap-exhaustion banner and for a watchdog that never armed.

2026-09-09 16:23:04 +02:00

..

scripts

feat(flows): run a local script in a bounded child process (#864)

2026-09-07 11:34:30 +02:00

src

fix(flows): stop reporting what a script prints, on both sides

2026-09-09 16:23:04 +02:00

test

fix(flows): stop reporting what a script prints, on both sides

2026-09-09 16:23:04 +02:00

LICENSE

…

package.json

chore: bump all versions to 0.25.0 (#1083)

2026-09-09 15:00:24 +02:00

tsconfig.json

feat: attach to devices offered by external providers (#735)

2026-09-04 22:02:57 +02:00

tsconfig.test.json

…

vitest.config.ts

test: stop the suite and the process environment leaking into each other (#1058)

2026-09-09 12:38:51 +02:00