Skip to content

Require nullable function result fields in native acceptance - #594

Merged
SaladDay merged 1 commit into
aos/cutoverfrom
aos/require-nullable-function-result-fields
Oct 8, 2026
Merged

SaladDay merged 1 commit into
aos/cutoverfrom
aos/require-nullable-function-result-fields

Conversation

@SaladDay

@SaladDay SaladDay commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

The native pending-action acceptance rejected a successful tool result because the request omitted error, while the pinned resource schema requires error: null. Compare the resource’s required output and error fields with the request’s nullable values, preserving exact output contents and rejection of missing resource fields.

Validation: 24 focused runner/schema checks passed. Replaying the captured durable input and result fails the old assertion and passes the corrected assertion; missing error, changed output, and changed error remain rejected. No production behavior changes. The original live failure is retained, and the remaining live rounds still need qualification.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit 4b9d92d into aos/cutover Oct 8, 2026
18 checks passed
@SaladDay
SaladDay deleted the aos/require-nullable-function-result-fields branch October 8, 2026 20:16
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