feat: publish command Node Results #339

New issue

Closed

opened 2026-07-15 15:56:38 +02:00 by dries · 0 comments

dries commented

2026-07-15 15:56:38 +02:00

Owner

Parent

#337

What to build

Publish a canonical Node Result for command nodes and require successful commands to write exactly one valid JSON value to stdout. Keep collectors temporarily available so this expand step remains compatible with existing workflows.

Acceptance criteria

Command run details expose exactly id, name, started, ended, status, and output as the canonical result envelope.
Known timestamps are RFC 3339 UTC and unavailable timestamps are null.
Valid stdout preserves every JSON value type in output.
Empty or malformed command stdout fails without rerunning and exposes an error output.
Existing collector workflows continue to run during the migration.
Workflow service integration tests prove the behavior and coverage does not drop.

Blocked by

None — can start immediately.

## Parent #337 ## What to build Publish a canonical Node Result for command nodes and require successful commands to write exactly one valid JSON value to stdout. Keep collectors temporarily available so this expand step remains compatible with existing workflows. ## Acceptance criteria - [ ] Command run details expose exactly `id`, `name`, `started`, `ended`, `status`, and `output` as the canonical result envelope. - [ ] Known timestamps are RFC 3339 UTC and unavailable timestamps are null. - [ ] Valid stdout preserves every JSON value type in `output`. - [ ] Empty or malformed command stdout fails without rerunning and exposes an error output. - [ ] Existing collector workflows continue to run during the migration. - [ ] Workflow service integration tests prove the behavior and coverage does not drop. ## Blocked by None — can start immediately.