feat(engine): embedded Nushell engine with in-process stream combinators #4

Closed
opened 2026-09-09 10:08:48 +00:00 by larandar · 1 comment
Owner

Proposal

Embed the Nushell execution engine so workflow expressions can run in-process with deterministic stream combinators and without an external shell process.

Design

Link the required Nushell crates and expose the executor's in-process combinator layer for par-each, reduce, chunks, zip, and window.

Tasks

  • 1.3 Link nu-engine, nu-protocol, nu-parser, nu-cmd-lang, and nu-command.
  • Implement in-process stream combinators: par-each, reduce, chunks, zip, and window.

Gherkin Specification Delta

must.contracts.ting-workflows.executor.embedded-nu-engine

Scenario: Execute a workflow stream with embedded Nushell combinators

  • GIVEN a valid workflow stream and an embedded Nushell engine
  • WHEN a workflow invokes the supported combinators
  • THEN the combinators execute in-process and return the expected transformed stream
  • AND engine errors are returned as structured workflow failures.
## Proposal Embed the Nushell execution engine so workflow expressions can run in-process with deterministic stream combinators and without an external shell process. ## Design Link the required Nushell crates and expose the executor's in-process combinator layer for `par-each`, `reduce`, `chunks`, `zip`, and `window`. ## Tasks - 1.3 Link `nu-engine`, `nu-protocol`, `nu-parser`, `nu-cmd-lang`, and `nu-command`. - Implement in-process stream combinators: `par-each`, `reduce`, `chunks`, `zip`, and `window`. ## Gherkin Specification Delta ### must.contracts.ting-workflows.executor.embedded-nu-engine **Scenario: Execute a workflow stream with embedded Nushell combinators** - **GIVEN** a valid workflow stream and an embedded Nushell engine - **WHEN** a workflow invokes the supported combinators - **THEN** the combinators execute in-process and return the expected transformed stream - **AND** engine errors are returned as structured workflow failures.
Author
Owner

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).

Superseded by 1-feature deliverable decomposition per freeholder ruling (issues #11+).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Ting/workflows#4
No description provided.