Skip to content

strut/run-workflow: parse a JSON-string input before launching on the peer - #135

Merged
Evanfeenstra merged 1 commit into
mainfrom
fix/peer-launch-json-string-input
Oct 10, 2026
Merged

Evanfeenstra merged 1 commit into
mainfrom
fix/peer-launch-json-string-input

Conversation

@Evanfeenstra

Copy link
Copy Markdown
Contributor

The job agent on swarm38 (run 1791645581902) called strut/run-workflow with input as a JSON string. launchOnPeer sent it as-is, and the peer's explore refused it twice with expected object, received string.

The builder's run_workflow { peer } and meta/run-workflow already run tool args through coerceJsonArg. launchOnPeer now does too (input and params), so every peer launch is covered. coerceJsonArg moves to core.ts (re-exported from authoring.ts), so peers.ts and the lib step don't import authoring.ts.

Test: peers.test.ts launches with a string input and params and checks the peer receives objects. npm test: 1416/1416 pass.

… string

The job agent on swarm38 (run 1791645581902) called strut/run-workflow as a
tool with `input` as a JSON string; launchOnPeer sent it verbatim and the
peer's explore refused it (expected object, received string), twice. The
builder's peer run_workflow and meta/run-workflow already coerce through
coerceJsonArg; launchOnPeer now does too, covering every peer launch.
coerceJsonArg moves to core.ts so peers.ts need not import authoring.ts.
@Evanfeenstra
Evanfeenstra merged commit 1863272 into main Oct 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant