Summary
Add one stable top-level string field to openclaw code run --json named publishedPullRequestBody.
Problem to solve
Downstream tooling currently has to inspect draftPullRequest.body directly just to read this nested string value. That is awkward for simple JSON consumers.
Proposed solution
Update src/commands/openclawcode.ts so the JSON output includes publishedPullRequestBody: string | null.
- set it to the nested
draftPullRequest.body value when present
- otherwise emit
null
Add or adjust unit tests in src/commands/openclawcode.test.ts to cover both cases.
Impact
Affected users/systems/channels
Tools and scripts that read openclaw code run --json.
Severity
Low.
Frequency
Whenever downstream tooling wants this string value without unpacking nested workflow metadata.
Consequence
Without the derived field, simple consumers keep reimplementing the same nested null-check logic.
Summary
Add one stable top-level string field to
openclaw code run --jsonnamedpublishedPullRequestBody.Problem to solve
Downstream tooling currently has to inspect
draftPullRequest.bodydirectly just to read this nested string value. That is awkward for simple JSON consumers.Proposed solution
Update
src/commands/openclawcode.tsso the JSON output includespublishedPullRequestBody: string | null.draftPullRequest.bodyvalue when presentnullAdd or adjust unit tests in
src/commands/openclawcode.test.tsto cover both cases.Impact
Affected users/systems/channels
Tools and scripts that read
openclaw code run --json.Severity
Low.
Frequency
Whenever downstream tooling wants this string value without unpacking nested workflow metadata.
Consequence
Without the derived field, simple consumers keep reimplementing the same nested null-check logic.