Skip to content

Fix nullable blocker in strict coding result schema - #685

Merged
witbrock merged 1 commit into
mainfrom
codex/retry-result-schema
Sep 13, 2026
Merged

witbrock merged 1 commit into
mainfrom
codex/retry-result-schema

Conversation

@witbrock

Copy link
Copy Markdown
Member

The deployed DGX controller failed before coding began because its strict output schema declared blocker but omitted it from required (provider invalid_json_schema, run c0c2946529f4497580cfeea84e0f6270). Require the nullable field for new model output and instruct the agent to use null when inapplicable. Keep validation compatible with previously retained results that omit blocker or deploy_commit.

Validation: 97 worker/retry tests passed, including a regression check for the strict object-schema contract and legacy result recovery. Existing Ruff findings in unrelated lines remain unchanged. Merge decision: ready; no retry-admission changes. After merge, the operator will install through the existing idle release handoff and reconcile one continuation of task #V#task_agent_78d57451e04f1ac9ca7acea3800d0e06. No public web deployment.

@witbrock
witbrock merged commit eea35dd into main Sep 13, 2026
2 checks passed
@witbrock
witbrock deleted the codex/retry-result-schema branch September 13, 2026 23:19
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