Summary
Add one stable top-level boolean field to openclaw code run --json named rerunHasReviewContext.
Problem to solve
Downstream tooling currently has to inspect several nullable rerun review fields (rerunReviewDecision, rerunReviewSubmittedAt, rerunReviewSummary, rerunReviewUrl) to decide whether a workflow run carries GitHub review context from a rerun. That is awkward for simple JSON consumers.
Proposed solution
Update src/commands/openclawcode.ts so the JSON output includes rerunHasReviewContext: boolean.
true when any rerun review field is present in run.rerunContextfalse otherwise
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 needs to quickly branch on whether a rerun includes GitHub review context.
Consequence
Without the derived boolean, simple consumers keep reimplementing the same null-check logic.
Summary
Add one stable top-level boolean field to
openclaw code run --jsonnamedrerunHasReviewContext.Problem to solve
Downstream tooling currently has to inspect several nullable rerun review fields (
rerunReviewDecision,rerunReviewSubmittedAt,rerunReviewSummary,rerunReviewUrl) to decide whether a workflow run carries GitHub review context from a rerun. That is awkward for simple JSON consumers.Proposed solution
Update
src/commands/openclawcode.tsso the JSON output includesrerunHasReviewContext: boolean.truewhen any rerun review field is present inrun.rerunContextfalseotherwiseAdd 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 needs to quickly branch on whether a rerun includes GitHub review context.
Consequence
Without the derived boolean, simple consumers keep reimplementing the same null-check logic.